I know this is a sore point. A lot of people reference the logic in the solo functions, but I have not seen anyone say what they think it SHOULD do.
I would like to hear from other Forum Members what they think the proper behavior should be.
I'll go first.
Folder Solo - Not necessary. Solo the Submix instead. Folder is always active, no need to solo it to work on tracks within. Mute, however would continue to mute everything in the Folder.
Subhire Solo - Should affect all tracks in the submix turning them all on or offk kind of like how the Folder solo works now.
Track Solo (Depending on singular or cumulative setting)
Singular - Solo the track directly to the default output. No need to do anything to the Folder or Submix to activate.
Cumulative - Multiple tracks may be soloed to the default audio output (bypassing the Submix) at once by clicking the solo buttons. Kind of how Alt-Solo works now. Lose the Alt, it would not be needed.
Maybe have 'Pass Solo Tracks through Submix' could be a system settings option, if people put plugins there and want to hear them.
Maybe my approach is lame-brained but I truly want to hear others opinions of how they would prefer the function to work.
Fixing Folders/Submixes and Tracks 'Solo problem'
-
- KVRist
- 96 posts since 22 Jan, 2009 from California
Sworkshop
"The tide of amateurism cannot but recede, until there will be left only the mechanical device and the professional executant." - John Philip Sousa, 1906
"The tide of amateurism cannot but recede, until there will be left only the mechanical device and the professional executant." - John Philip Sousa, 1906
-
- KVRAF
- 1790 posts since 30 Dec, 2012
What version of Waveform are you using?
I spent a lot of time on this about half a year ago and think I've got the behaviour everyone was asking for...
I spent a lot of time on this about half a year ago and think I've got the behaviour everyone was asking for...
-
- KVRist
- Topic Starter
- 96 posts since 22 Jan, 2009 from California
I am in T7. I own Waveform but my big projects are in T7...are you saying I should test it out in Waveform. it works differently? That would be great.
Sworkshop
"The tide of amateurism cannot but recede, until there will be left only the mechanical device and the professional executant." - John Philip Sousa, 1906
"The tide of amateurism cannot but recede, until there will be left only the mechanical device and the professional executant." - John Philip Sousa, 1906
-
- KVRAF
- 1790 posts since 30 Dec, 2012
-
spoontechnique spoontechnique https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418750
- KVRist
- 492 posts since 7 May, 2018
In W10, I'm pretty sure Submixes work exactly as I expect them too. Since you can now render tracks within submixes in W10.
Would still be nice to have sidechain inputs or recording inputs from submixes, though.
Would still be nice to have sidechain inputs or recording inputs from submixes, though.
Linux version?
-
- KVRist
- 325 posts since 25 Aug, 2016
When I solo a track in T7 I should hear the output.
There is no ouput of solo'd tracks if the track is muted (solo logically overrides other status), or if tracks are in a submix bus.
This is a deal breaker for the submix bus to the extent that I don't even use submix buses, but rather select all the tracks and route them to a normal track manually.
I then route buses to another track to be used as the master track, which both solved bizarre nested submix bugs I've had in the past, and having only the uncharacteristically limited master track.
This routing method automatically solves several routing problems and seemingly makes sense to implement by default, if applicable to the cosmetic submix bus.
Sidechain workflow is greatly improved by the new plugin window sidechain input menu, but buses cannot be routed to the input, though thankfully the signal can be fed to a bus compressor.
Another routing issue is the state of the master track which appears to only contain 4 plugin slots (?). The T7 modular workflow is far too slow for me given that I don't know of any way to add plugins or move plugins in racks such that they automatically connect, like synthmaker/flowstone's node proximity indicator with right click to confirm, though in this simpler environment drag auto connect/disconnect would work excellently too, and be a huge relief.
There is no ouput of solo'd tracks if the track is muted (solo logically overrides other status), or if tracks are in a submix bus.
This is a deal breaker for the submix bus to the extent that I don't even use submix buses, but rather select all the tracks and route them to a normal track manually.
I then route buses to another track to be used as the master track, which both solved bizarre nested submix bugs I've had in the past, and having only the uncharacteristically limited master track.
This routing method automatically solves several routing problems and seemingly makes sense to implement by default, if applicable to the cosmetic submix bus.
Sidechain workflow is greatly improved by the new plugin window sidechain input menu, but buses cannot be routed to the input, though thankfully the signal can be fed to a bus compressor.
Another routing issue is the state of the master track which appears to only contain 4 plugin slots (?). The T7 modular workflow is far too slow for me given that I don't know of any way to add plugins or move plugins in racks such that they automatically connect, like synthmaker/flowstone's node proximity indicator with right click to confirm, though in this simpler environment drag auto connect/disconnect would work excellently too, and be a huge relief.
quick, _ake what you want in life
-
- KVRist
- 320 posts since 9 Sep, 2017
I can confirm the solo problem. I never use submixes, I have sometimes used folders if there are 20 or so harmony vocal tracks, or 30 stacked guitars... ^_^
when a bus is soloed, I can sometimes mute away some sub trees of it. I always have complex, nested trees of busses.
unfortunately, it is not perfect in T7, while in T6 this went better. but T6 tends to crash with racks and with automation.
if you move ONE plugin into a new rack with the context menu, it will be auto-connected, though.
I'm using T7 as well, and I think for a free teaser to WF it works great.
I am using racks quite a lot, and have created a number of complex presets, e.g. a mastering processing set (about 10 optional compressors, limiters, EQs etc.), and a mastering analyzer set (with all those spectrum, correlation, VU etc. displays, and a utility that can switch to mono, L/R reverse, or listen to selected frequency bands).
beware that automation into racks seems not to work. it shows the curves, but when it plays or renders, there is no real activity with these parameters.
when a bus is soloed, I can sometimes mute away some sub trees of it. I always have complex, nested trees of busses.
unfortunately, it is not perfect in T7, while in T6 this went better. but T6 tends to crash with racks and with automation.
if you move ONE plugin into a new rack with the context menu, it will be auto-connected, though.
I'm using T7 as well, and I think for a free teaser to WF it works great.
I am using racks quite a lot, and have created a number of complex presets, e.g. a mastering processing set (about 10 optional compressors, limiters, EQs etc.), and a mastering analyzer set (with all those spectrum, correlation, VU etc. displays, and a utility that can switch to mono, L/R reverse, or listen to selected frequency bands).
beware that automation into racks seems not to work. it shows the curves, but when it plays or renders, there is no real activity with these parameters.
-
- KVRAF
- 2140 posts since 16 Jan, 2013 from USA
Is T7 actually still being actively supported?