• SONAR
  • "Add Track Flyout" - Bakers, please catch these problems before they get baked>copied F&I (p.2)
2016/01/14 14:58:00
declan
 
A week ago I wouldn't have had any idea what an "add track flyout" was.  I saw a tutorial for Omnisphere 2 and it was in Logic, and I re-winded it just to see what had happened, because I knew I couldn't do that in Sonar nearly that quickly. Two clicks and a midi track added and routed looked pretty sweet to me.
 
 
 
 
 
 
 
 
2016/01/14 15:20:36
Bristol_Jonesey
jpetersen
In the Flyout, add the option "Above" or "Below", I think the Clone Track function already has this.
And perhaps Shift/Alt/Ctr+Insert for the hotkey variant (not sure which combination is free, am not at my DAW).
 

Not quite, what it does have is the ability to specify the Starting Track for subsequent clone(s) which obviously can be above or below the source track
 
 
2016/01/14 15:29:38
Bristol_Jonesey
Atsuko
jpetersen
I'd edited down my original posting for brevity. It lost clarity. Here's the preamble to #1.
 
If one inserts a track,
99% of the time one would want it UNDER the selected track.
1% of the time one would want it ABOVE the selected track.
0% of the time one would want it down at the bottom. (well, let's say very rarely)
 
Edit:
A. If I insert with the Insert key, I get the 0% option.
B. If I insert with right-click/Insert Audio Track, I get the 1% option.
 
I just noticed this different behavior now because I usually use method A.
Why are they different? Most likely there's near-identical code in the two events
handling the menu and the hotkey, instead of having one single method being called from both.
 
Anyway, my appeal to the Bakers is to have a look since they plan to work on this area of the code anyway.
 


In my opinion, inserting ABOVE is better because it's easier when you want to insert a track #1. How do you do it when you want it in the first position if it inserted under the selected track?


I have to agree.
 
I can think of scenarios when the inserted track should be above, below, or even at the bottom.
I think jpetersen's percentages need to be modified!!
 
Interesting concept though, can't wait to try it out
2016/01/14 15:30:52
streckfus
Not to be an annoying stickler here, but at least to my way of thinking, if a track is selected, inserting a track should put the new track above what was selected.  If you're working in a spreadsheet and want to insert a row in the middle of a bunch of rows, you'd select the point (row) where you want the new one to go.  Then the selected row and everything below gets bumped down a notch when the new one is inserted.  Seems to me the same sort of behavior should be expected within a list of tracks as well.
2016/01/14 15:41:22
Bristol_Jonesey
It's nice that currently we can choose exactly where it will appear, at least when cloning.
This behaviour should really be 'ported over to Inserts
2016/01/14 16:44:20
Dan Gonzalez [Cakewalk]
From my perspective, working on a desk or in a DAW is an additive experience that follows a top-to-bottom and left-to-right methodology. Most would agree that working in a downward fashion matches the same feeling as working from left to right. This is why tracks in SONAR (and every other DAW) are reflected like this when switching from the Track View to the Console View. 
 
If you apply that logic to creating a new track with a track selected, inserting it underneath or to the right makes the most sense. This is also an additive experience. To invert that process feels like you're working backwards or in reverse.
 
Imagine typing a sentence and ".typed just you word the of left the to inserted was word every"
Doesn't make any sense now, does it?
 
What I'm trying to say is , I agree with your suggestion.
-DG
2016/01/15 02:22:41
Bassman002
HI:)
 
To have it under the selected Track, just select the next track:)
 
Bassman
 
2016/01/15 02:38:29
KPerry
streckfus
Not to be an annoying stickler here, but at least to my way of thinking, if a track is selected, inserting a track should put the new track above what was selected.  If you're working in a spreadsheet and want to insert a row in the middle of a bunch of rows, you'd select the point (row) where you want the new one to go.  Then the selected row and everything below gets bumped down a notch when the new one is inserted.  Seems to me the same sort of behavior should be expected within a list of tracks as well.


I'd say the Excel analogy is pretty damn close and consistent with other behaviour, so that should be the default. That said, and this might be me, but I'd want some weirdness where insertion should be below the last track in a folder but above everywhere else, just because of my workflow...that's pretty idiosyncratic though :-)

The obvious(?) solution is to have an option like we do for clip selection on split (left, right etc) for above/below as the default, with (say) shift held reversing this (compare space bar with shift+space bar, so there is a precedent for this behaviour in SONAR already).
2016/01/15 10:17:20
tenfoot
Basseman
HI:)
 
To have it under the selected Track, just select the next track:)
 
Bassman
 


Indeed! I think it is a good sign for Sonar when these are the big 'probems' being discussed:)
2016/01/15 10:20:49
Anderton
Basseman
HI:)
 
To have it under the selected Track, just select the next track:)
 
Bassman



I love it! So simple...how to put the inserted track anywhere you want.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account