Noel Borthwick [Cakewalk]
What do you want to see? I'm terrified of that thing - it was one of the most complex features I've implemented in SONAR, touching almost the whole signal path of the engine :)

This is not a signal path thing at all but more related to workflow: list of returns does not show inputs that are used at any track, even archived one. Could this restriction be more liberal? Say I want to create external insert to feed my Axe FX II (soon III :)). I may have already recorded 20+ guitars from my dedicated Axe FX II inputs and in order to use external insert I have to assign every tracks's input away from that channel. This is true also for archived tracks.
 
If input channel must be reserved strictly for the external insert, why not ask user "Channels are already used in tracks [track list here]. Use channel anyway (track inputs will be assigned to none)?" or similar.
 
Same applies to send channels, too.
 
^ This is not a problem in small projects but it slows down things on big projects.
 

panup

Noel Borthwick [Cakewalk]
What do you want to see? I'm terrified of that thing - it was one of the most complex features I've implemented in SONAR, touching almost the whole signal path of the engine :)

This is not a signal path thing at all but more related to workflow: list of returns does not show inputs that are used at any track, even archived one. Could this restriction be more liberal? Say I want to create external insert to feed my Axe FX II (soon III :)). I may have already recorded 20+ guitars from my dedicated Axe FX II inputs and in order to use external insert I have to assign every tracks's input away from that channel. This is true also for archived tracks.
 
If input channel must be reserved strictly for the external insert, why not ask user "Channels are already used in tracks [track list here]. Use channel anyway (track inputs will be assigned to none)?" or similar.
 
Same applies to send channels, too.
 
^ This is not a problem in small projects but it slows down things on big projects.
 

Hi Panu... Good to see you still around! Sorry for being out of topic, but is there any news about DuckBar? Do you have any plan to port it to CbB ? Looking forward to hear any good info about it. Thanks a lot man.
 
Jaymz

I would also be happy to see External inserts integrated in the pro channel. I have many external MIDI controlled sound/fx modules, as well as just the regular hands on fx's. Would be great to have automatically latency/delay compensated external inserts, both from perspective of the external module's audio path, as well as it's corresponding MIDI signals.

Hi Panu... Good to see you still around! Sorry for being out of topic, but is there any news about DuckBar? Do you have any plan to port it to CbB ? Looking forward to hear any good info about it. Thanks a lot man.
 
Jaymz



+1 for sorry for a brief off-topic:
Duckbar for CbB: I have ported it already and I'm testing it myself. Release date is stil open.
The upcoming version is streamlined version of the old Duckbar; many old features (such as batch freeze/unfreeze tracks, full screen mode, etc.) are now included in the official Cakewalk and I have removed them from the codebase. I removed all old mods and themes, too, because they were designed for SONAR before Theme Editor era.