auto-scroll view with moving locator
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
That would make more sense - if the main composition is playing, it can keep scrolling. If I grab some of it, it floats into its own window (or tab, if you prefer) for focused editing.
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
It's been awhile since this discussion came up... but no, I don't remember what the reason was. Regardless I know I still have to keep hitting the cmnd. key over and over which I never do in Logic. It's always on. So again, is that a feature I'm not understanding or something that doesn't work correctly?
Auto scroll: the playback cursor automatically moves to a new screen as the composition plays back
Auto scroll: moves the screen - when navigating to markers with the left and right arrow keys from the keyboard
Using Mouse wheel or scroll bars turns off auto scroll... to do the above it has to be re-activated
Like I said, why would scrolling with the mousewheel have anything to do with "playback" behavior...
Auto scroll: the playback cursor automatically moves to a new screen as the composition plays back
Auto scroll: moves the screen - when navigating to markers with the left and right arrow keys from the keyboard
Using Mouse wheel or scroll bars turns off auto scroll... to do the above it has to be re-activated
Like I said, why would scrolling with the mousewheel have anything to do with "playback" behavior...
-
- KVRAF
- 2938 posts since 18 Jul, 2005
I think what DHR53 might be talking about is that autoscroll is disabled by manual scrolling even when playback is stopped and autoscroll is effectively inactive already. I agree this doesn't make much sense.
On the other hand, as for it always being on: autoscroll is a feature that moves the screen to track the play cursor while it is moving. Manual scroll is also a feature that moves the screen. It's obvious that if both of these are happening simultaneously there is a conflict and both actions cannot produce their normal behaviour.
You haven't stated the behaviour you want, DHR53. E.g. would you want autoscroll reactivated as soon as you release the scrollbar? Only if the playback cursor is on-screen and reaches the right?
On the other hand, as for it always being on: autoscroll is a feature that moves the screen to track the play cursor while it is moving. Manual scroll is also a feature that moves the screen. It's obvious that if both of these are happening simultaneously there is a conflict and both actions cannot produce their normal behaviour.
You haven't stated the behaviour you want, DHR53. E.g. would you want autoscroll reactivated as soon as you release the scrollbar? Only if the playback cursor is on-screen and reaches the right?
- KVRAF
- 3160 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Was this a dig at me?DHR53 wrote:If my song is 154 bars and I hit the spacebar to play back this song... why would I want to look at the first 24 bars only? While playback is happening... Once again, I'm baffled at user response.
Whether it is or not, you might want to open your mind a little and realise that not everyone wants to work the same way as you do! Your way is not the only way, it is not the best way, it is just one way.
Perhaps you might want to share your life path with us all so that we may see the perfection?
-
- KVRist
- Topic Starter
- 83 posts since 19 May, 2012
Just give the user the option to disable the automatic turn off and everything is fine. But indeed, I prefer how it's in Cubase and Reaper; if u turn on auto-scroll, it stays on.
It's things like this that show the differences between the DAW user audiences. The ppl who are more into composition will expect different features then those who are more into repetitive, loop based music.
However, even the loop based music that I see in the tutorial videos does not need auto scroll to be turned off because the user turns on the loop function and the view zoom is adjusted to the loop which is being worked on, so auto scroll is not even required in such a case. That's why I see them as separate situations and if this is indeed the case,there's no need for auto turn off of auto scroll at all. Unless I overlook something?
It's things like this that show the differences between the DAW user audiences. The ppl who are more into composition will expect different features then those who are more into repetitive, loop based music.
However, even the loop based music that I see in the tutorial videos does not need auto scroll to be turned off because the user turns on the loop function and the view zoom is adjusted to the loop which is being worked on, so auto scroll is not even required in such a case. That's why I see them as separate situations and if this is indeed the case,there's no need for auto turn off of auto scroll at all. Unless I overlook something?
- KVRAF
- 3160 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I do a bit of both LoopBased and non LoopBased. But I see no purpose of AS except it annoys me. I prefer to leave the seq running and turn loop on or off to work on a section, but that's just my preference, probably where I started with hardware it's an overspill.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Even when playback is stopped autoscroll can be active. Handy when rewinding/frowarding to different sections in your composition. So it's independent from playback state.robenestobenz wrote:I think what DHR53 might be talking about is that autoscroll is disabled by manual scrolling even when playback is stopped and autoscroll is effectively inactive already. I agree this doesn't make much sense.
Anyway, as i wrote before i can see that there is room for improvement. As there is room for improvement in many aspects in many apps. I've added a note on the wishlist. It's not something i can change quickly and i'm currently concentrated on something else. But i've taken note.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
+1.sl23 wrote:Was this a dig at me?DHR53 wrote:If my song is 154 bars and I hit the spacebar to play back this song... why would I want to look at the first 24 bars only? While playback is happening... Once again, I'm baffled at user response.
Whether it is or not, you might want to open your mind a little and realise that not everyone wants to work the same way as you do! Your way is not the only way, it is not the best way, it is just one way.
Cfr the other topic (the 'Split' topic) i have the impression that Dhr gets kind of angry if i don't immediately follow his requests. I try to communicate about things but it seems that Dhr doesn't give much attention to other ones' posts. In that case it's difficult to communicate of course.
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Maybe you think that the way this is implemented in Logic is unusual? It surely wasn't my idea... they didn't ask me how I wanted it or how I worked. I adapted to Logic, not the other way around. This is a feature in all DAWs... scrolling behavior/zoom and autoscroll are 2 different things. If I zoom my entire composition into the window obviously it doesn't matter... but most people don't do that and prefer to zoom in on areas while they work. But if the area of my composition I'm working on happens to be on the right side of my window and I hit play. I expect it to go past the current screen to the next. I don't expect to have to turn on autoscroll "again" for the 10th time in 30 minutes time.
Not sure why you can't see that is not "MY" idea, but the clear purpose of the function.
Not sure why you can't see that is not "MY" idea, but the clear purpose of the function.
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
You know... I usually come here when I discover something that doesn't behave like every other DAW I have or have used... and I wonder if this is implemented differently or is it something that just doesn't work correctly? So I ask the question and down the rabbit hole we go. Obviously I don't expect Jo to change something that no one else notices. But, implying that it's my idea or I'm asking for "my way" is nonsense. My workflow has developed over the years from using the same functions in Logic, Reason, Cubase etc. I still maintain that changing some of this stuff wouldn't affect the "MuLab" way but it might make it easier for some of us "traditional" users to get along...
I'll move along...
I'll move along...
-
- KVRAF
- 2938 posts since 18 Jul, 2005
That's true, I hadn't thought of that. Although I do think that since autoscroll is not constantly taking effect in the stopped state, it's less likely that the user wants autoscroll automatically disabled.mutools wrote:Even when playback is stopped autoscroll can be active. Handy when rewinding/frowarding to different sections in your composition. So it's independent from playback state.
- KVRAF
- 3160 posts since 28 Mar, 2008 from a Galaxy S7 far far away
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
It does. That's what i meant.robenestobenz wrote:Although I do think that since autoscroll is not constantly taking effect in the stopped statemutools wrote:Even when playback is stopped autoscroll can be active. Handy when rewinding/frowarding to different sections in your composition. So it's independent from playback state.
- KVRAF
- 3160 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Jo, I think what's being said is that if stopped and you scroll manually it cancels AS meaning it has to be turned on again. Perhaps in this situation it shouldn't being cancelled.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I know that that is what is being said. Again: AS is also active when playback is stopped (when AS is enabled of course). That's logically why AS is also disabled when scrolling even when playback is stopped. That's the current situation. Whether AS should work when playback is stopped is another question and i've taken note about that on the wishlist. Both ways has advantages and disadvantages i think. I already mentioned an advantage when it does (=when enabled AS also works when not playing). But i've taken note to further evaluate this topic because i understand the criticism on the current way, as i mentioned already.
