hush
Regular
Reged: 12/23/07
Posts: 109
|
|
Further from the following and without uploading yet another screen-shot, I am at a loss as to the reason why there are solo and mute buttons on Folder Tracks and when creating a Group Track, it puts it in its' own container.
http://www.steinbergusers.com/forums/showflat.php/Cat/0/Number/7526/an/0/page/0#7526
|
hush
Regular
Reged: 12/23/07
Posts: 109
|
|
Hi,
I know the time is restricted as to how long I can edit a post, so to add..
I've found that when soloing or muting a Group Track, it doesn't change the solo and mute lights on Grouped Tracks to be the same as the Group Track itself and I believe it really should.
Thank you
|
hush
Regular
Reged: 12/23/07
Posts: 109
|
|
Hi,
I thought I'd upload an image of especially the above point in order to illistrate what I'm talking about.
I don't believe that this is a feature request as such but rather an enhancement to how something already works, so that there is less confusion regarding both the aforementioned track types.
I have since learned that as for the mute/solo buttons I cannot get rid of them even if I had wanted to which is a real shame since not only can I not do that on Folder Tracks but also I cannot do it for Group Tracks either and all I can really do is hide text, which is ok for the time being but I would like to see the situation changed by the next forthcoming update or if not before the next whole numbered version.
Thank you
|
hush
Regular
Reged: 12/23/07
Posts: 109
|
|
Hi again,
I've been learning more about VST Connections, Group Tracks and Busses etc., and I do see the great flexibility in how they are all intended to work.
I understand now that channel eq. etc is built as an instance of a track is created and there is no global method in order to turn it on and that is fine since I can simply "clear" all channels that currently exist regardless of their type.
About Groups themselves I understand I can either send them to other groups or to output busses respectively but not both at the same time so far as I am aware, nor does there seem to be an easy way to route them back to particular input "tracks" as per bouncing type method, which I believe if implemented would help many users as well as myself in the future especially with respect to audio notwithstanding feedback loops being created.
The discussion engaged in the initial post was an attempt at submitting a feature request which in this thread is such that I feel Group Tracks should engage the mute/solo status on any and all Group Tracks assigned to a Group Fader as this would be more intuitive in my view, however I am supposing that the problem may be completely unrelated in that re-wire "tracks" in particular cannot be placed at arbitrary locations in the project or the mixer and do not obey the laws of the Generic Remote, as neither do Group Tracks unless a secondary mixer is specified.
I do believe there is cause for change here and I would appreciate it being addressed in the next Hotfix notwithstanding a new whole numbered version, since I am aware that the update cycle for all version 4 programs is not yet complete and it may serve to have this issue sorted prior to the next release of the program.
Thank you and kind regards.
|
JoshMatlock
Moderator
Reged: 10/22/07
Posts: 392
|
|
Hello,
I will forward this information on to our developers.
Thank you for your feedback.
Edited by JoshMatlock (09/30/08 04:09 PM)
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
