Song End Marker Hunting

[Number6]

So I'm always doing this:

I want to set the end marker of the song, so I open the marker track, zoom out and go hunting for it, then I move it to where I want, and eventually I get what I want. It's a fiddle.

Is there any way to just move that End Marker to exactly where I want it to be without having to hunt around for it?

Thx,

 

[Wolfger]

There is a key command for markers: Set start and end to selection

Make a selection with the range-tool and execute the key command:

 

[Number6]

OK thanks.
So for Windows it's select all events (CTRL+A) and then ALT+Y.

Appreciated.

Something I found odd (although some may disagree, if they do I would like to understand). See image in my first post, if I enable that loop so it loops across the whole song, it will stop at the end marker.

IMHO if the end marker is before the end of the loop that would make absolute sense, but if the end marker is in exactly the same position as the end of the loop, that end marker should be ignored. There are lots of scenarios where I would want to quickly loop the entire song, right now I would have to move the end marker a few extra bars forward (an unnecessary step) to get that to work, and then when I'm done I would have to put it back.

 

[Wolfger]

In the scenario you are describing, I would move the End Marker just a little bit to the right.

 

[lokeyfly]

Is there any way to just move that End Marker to exactly where I want it to be without having to hunt around for it?

Thx,

Right from the start of creating and naming your song, you can set the song length. Its probably set to 5 or 6 minutes now, so instead of hunting around for it (your words) later, simply set the song length from the start. You can always reset this later by relocating the end marker within the arrangement view. By initially setting it shorter, it should be easier for you to find or define right away.

You can also go into your Song information and set it there. No need for hunting. ; )

 

[Number6]

In the scenario you are describing, I would move the End Marker just a little bit to the right.

Well as I stated:

right now I would have to move the end marker a few extra bars forward (an unnecessary step) to get that to work, and then when I'm done I would have to put it back.

Regardless I've now experienced the opposite behaviour, the loop is now overriding the end marker when it's in the same position, I have no idea why I'm getting inconsistent behaviour (so far).

I thought it might be something to do with what I did first.
i.e. did I set loop end marker first or did I set song end marker first?
That theory isn't reproducible right now.

 

[lokeyfly]

Something I found odd (although some may disagree, if they do I would like to understand). See image in my first post, if I enable that loop so it loops across the whole song, it will stop at the end marker.

End markers do not stop play, loops enabled or disabled. Play will stop at a marker designated to stop. So unless something is different in the latest v7.2, an end marker does not stop the progress of a song. They will end a song in mixdown mode because its a designated end. As Wolfger mentioned, in the scenario you mentioned, move the end marker to the right. In any event, it won't stop play progress

IMHO if the end marker is before the end of the loop that would make absolute sense, but if the end marker is in exactly the same position as the end of the loop, that end marker should be ignored.

The end marker is ignored anyway. It is only a place holder for the song to end when designating a mixdown, or stem operation (as loop settings can also be).

There are lots of scenarios where I would want to quickly loop the entire song, right now I would have to move the end marker a few extra bars forward (an unnecessary step) to get that to work, and then when I'm done I would have to put it back.

FWIW, you could set up various loop scenes from the launcher, and also for that matter from the scratchpad. Just an alternative, but Im still wondering why your end marker is stopping play. The subject here is a bit sketchy. Why are you ever having to move an end marker, unless its the designated end of a song? Setting loop regions before, after, over, weather enabled or not do not impact it. Sorry if Im not getting what is fiddly, here.

 

[Number6]

If you right click the.song end marker there is a tickbox to stop play. That's what I've got engaged (sorry I should have said).

I am sync'ing with other apps so it's useful. BTW sync wasn't engaged whilst I was testing and reproducing.

Reproducing both scenarios where it worked and when it didn't, sync wasn't engaged.

 

[lokeyfly]

If you right click the.song end marker there is a tickbox to stop play. That's what I've got engaged (sorry I should have said).

Ok, to be clear, that is not an end marker, but a marker, checked off to stop play (it additionally turns blue once Stop is checked).

A song always has a Start and End marker.
So placing such a marker designated to stop is just going to be fiddly, anyway. If you need to rename a marker, you can if that helps. It looks as though you did, and named it "End" as it is the color white. Probably not the best name you gave it, imo.

I am sync'ing with other apps so it's useful. BTW sync wasn't engaged whilst I was testing and reproducing.

Reproducing both scenarios where it worked and when it didn't, sync wasn't engaged.

Going to sign off here. TY for noting this is a marker named "End" you are electing to stop at times.

 

[Jens]

Regarding "Song End Marker Hunting":
Right click on the timeline, select "End" marker. And done.

 

[Number6]

Ok, to be clear, that is not an end marker, but a marker, checked off to stop play (it additionally turns blue once Stop is checked).

A song always has a Start and End marker.
So placing such a marker designated to stop is just going to be fiddly, anyway. If you need to rename a marker, you can if that helps. It looks as though you did, and named it "End" as it is the color white. Probably not the best name you gave it, imo.


Going to sign off here. TY for noting this is a marker named "End" you are electing to stop at times.

Lovely.....

Firstly I've moved on how to move the end marker where I've want, the first reply was the solution to this (I responded as such).

As stated I've clicked on the song end marker and flagged it to end playback. That stops the transport when it is reached. It is actually the song end marker, not just any old marker, please go and try it yourself.

I guess you aren't seeing it. All you are seeing is that end means end, but not considering the fact that end loop also means end loop.

So what is a sensible priority here? I appreciate this clearly doesn't matter to you but it does to me with my current workflow.

This may seem ridiculous to you, but my use case is I'm sync'ing apps here and I'm having to employ various workarounds as Studio One won't receive time code correctly, nor does it receive midi clock for syncing. That has been discussed in another thread and is beyond the scope of this discussion. Regardless all these workarounds I'm employing are hurting my brain and any little thing to make life easier obviously helps

Studio One Sync Ableton Live via MIDI Timecode

Hi I'm sync'ing Studio One 7.1.1 (master) with Ableton Live 10 via MIDI Timecode (note I'm NOT using Ableton Link for the purposes of this exercise) using Windows 11 and LoopBe. I don't have to use LoopBe I guess (maybe there are better methods? And yes I know.... Ableton Link probably is...

studiooneforum.com

When the loop end marker is on the song end marker it makes sense for it to continue looping and not to end, otherwise I have to muck around with moving the song end marker backwards and forwards all the time with my workflow. I've previously explained this in detail.

But if you've got a better use case for the song end marker to take priority let's hear it (other than *end means end*).

The thing is, that behaviour I want is actually happening now, and it wasn't before (which is good news to me). So there is clearly something inconsistent going on and I will return to this thread when I find the reason.

 

[lokeyfly]

Allow me to clarify, and of course we're all here to help.

Something I found odd (although some may disagree, if they do I would like to understand). See image in my first post, if I enable that loop so it loops across the whole song, it will stop at the end marker.

Yes, I figured end marker, or in fact any marker. Once you addressed you ticked the marker to stop, that pretty much tells the tale. Only, we're now away from the solve of locating the end marker (now resolved).

Number6 wrote: "I'm sync'ing apps here and I'm having to employ various workarounds as Studio One won't receive time code correctly, nor does it receive midi clock for syncing. That has been discussed in another thread and is beyond the scope of this discussion."

You make no mention of other apps in your thread, or Studio One's inability to recieve time code, so let's please stop expanding on the subject and keep points defined.

There's nothing "ridiculous", so going forward, if this loop positioning is impacted by a marker ticked to stop, then as in other posts related to MIDI clock, we'd likely need to know more. What might be the program slaved, clock position, and so on.

I stated earlier I would bow out, to keep the conversation in-line with the posts subject. That is often bolstered by moderators and such. So my intention was favorable.

You found locating the end marker fiddly. Sorry, but I cant help you any further.

 

[hieroglyph]

Lovely.....

Firstly I've moved on how to move the end marker where I've want, the first reply was the solution to this (I responded as such).

As stated I've clicked on the song end marker and flagged it to end playback. That stops the transport when it is reached. It is actually the song end marker, not just any old marker, please go and try it yourself.

I guess you aren't seeing it. All you are seeing is that end means end, but not considering the fact that end loop also means end loop.

So what is a sensible priority here? I appreciate this clearly doesn't matter to you but it does to me with my current workflow.

This may seem ridiculous to you, but my use case is I'm sync'ing apps here and I'm having to employ various workarounds as Studio One won't receive time code correctly, nor does it receive midi clock for syncing. That has been discussed in another thread and is beyond the scope of this discussion. Regardless all these workarounds I'm employing are hurting my brain and any little thing to make life easier obviously helps

Studio One Sync Ableton Live via MIDI Timecode

Hi I'm sync'ing Studio One 7.1.1 (master) with Ableton Live 10 via MIDI Timecode (note I'm NOT using Ableton Link for the purposes of this exercise) using Windows 11 and LoopBe. I don't have to use LoopBe I guess (maybe there are better methods? And yes I know.... Ableton Link probably is...

studiooneforum.com

When the loop end marker is on the song end marker it makes sense for it to continue looping and not to end, otherwise I have to muck around with moving the song end marker backwards and forwards all the time with my workflow. I've previously explained this in detail.

But if you've got a better use case for the song end marker to take priority let's hear it (other than *end means end*).

The thing is, that behaviour I want is actually happening now, and it wasn't before (which is good news to me). So there is clearly something inconsistent going on and I will return to this thread when I find the reason.

I think if you untick the "stop playback at marker" setting on the End marker, the loop will continue. But for now, it looks like the "stop at marker" function may be overriding the loop.

 

[Number6]

I'll just rewrite what I said earlier.

To summarise I'm putting the end loop marker and end song marker (ticked to end the transport) in the same position.

The stop at end of song marker is *no longer* overriding the lend of loop anymore.
The transport doesn't stop until I disable the loop, and that is good behaviour as far as I'm concerned and if anybody disagrees with it please state your case.

As I clearly stated I wasn't syncing with other apps when I reproduced this, so discussions about my workflow is irrelevant in reproducing this issue. I clearly stated that this is beyond the scope of this thread (nevertheless I have provided a link to that thread should the topic be of interest). It does however demonstrate a.clear use case as to why loop end marker being priority over the end song marker (when ticked to end the transport) is important. That's why I wrote it here.

However this behaviour is inconsistent, song end loop marker WAS stopping the loop earlier with the loop marker in the same place and loop enabled. I will post more when I get steps to reproduce.