Gary, you've touched on something that a few others, including myself, have mentioned. Just think-- we only have HALF of the Cube! Imagine yourself using VI to do a Wagnerian-size score!!
The floating consoles and AU-GUI interfaces indeed do get quite unwieldy very quickly. I do like the large console of VI, but I confess that I get lost and often go "click crazy" keeping up with which GUI interface goes with which console, ducking consoles onto the dock, etc., etc.
I'd like to see, at the least, some sort of VI preference to disable the floating window option. This would accommodate those who don't mind the floating window as well as those who do. I'd thought about getting a second monitor, but that would only serve as a dumping ground with the consoles and AU-GUI clutter remaining.
Also, if the AU-GUI must be there, I'd like to better understand how saving data in the AU-GUI differs from saving matrices in the console itself. Some people have stated that they don't bother with saving in the GUI ('.aupreset'), but if I don't save in both places my custom setups do not load. I really don't quite understand why this is necessary for some and not for others.
But another thought I had must be directed at Audio Units itself. If this GUI option is indeed part of the function of Audio Units, then much could be remedied if the AU-GUI was ONE SINGLE WINDOW with a list of all loaded virtual instruments, whether VSL or not. A "hot" button could be by each instrument loaded in the sequence that would allow the user to choose at a glance which consoles of which instruments can be seen at any time in any combination.
Yet, this observation brings me back to VI's integration with AU. VI is the only virtual instrument I have which dominates my system and screen the way it does. It is common to hit the space bar to start and stop playback, even if other instrument consoles are open and on top of the DAW. VI uses the space bar (where is that documented?) to turn certain PERFORM/CONTROL features on and off. It gets so confusing (being a creature of habit or 'standard') to hit the space bar to not only hear nothing playing back but also to have unwittingly deactivated an important control feature which must be searched and remedied before continuing. Not being able to reprogram this keystroke is a problem. If it IS possible to reprogram these computer keystrokes, I've not found that feature. I've only been able to assign and un-assign controller numbers.
On the one hand, one can say that "it just takes some getting used to", but more and more it feels like your 3 year old kid who stands in front of the TV without regard to others who are watching.
Once again, preference options to activate or deactivate these overrides would come in quite handy. Short of expecting an unlikely update of AU from Apple, it is even more crucial for VI to nestle itself a bit better into the OS without taking it over.
... and I can't get it out of my head that some people just don't have a problem with this--!!
The floating consoles and AU-GUI interfaces indeed do get quite unwieldy very quickly. I do like the large console of VI, but I confess that I get lost and often go "click crazy" keeping up with which GUI interface goes with which console, ducking consoles onto the dock, etc., etc.
I'd like to see, at the least, some sort of VI preference to disable the floating window option. This would accommodate those who don't mind the floating window as well as those who do. I'd thought about getting a second monitor, but that would only serve as a dumping ground with the consoles and AU-GUI clutter remaining.
Also, if the AU-GUI must be there, I'd like to better understand how saving data in the AU-GUI differs from saving matrices in the console itself. Some people have stated that they don't bother with saving in the GUI ('.aupreset'), but if I don't save in both places my custom setups do not load. I really don't quite understand why this is necessary for some and not for others.
But another thought I had must be directed at Audio Units itself. If this GUI option is indeed part of the function of Audio Units, then much could be remedied if the AU-GUI was ONE SINGLE WINDOW with a list of all loaded virtual instruments, whether VSL or not. A "hot" button could be by each instrument loaded in the sequence that would allow the user to choose at a glance which consoles of which instruments can be seen at any time in any combination.
Yet, this observation brings me back to VI's integration with AU. VI is the only virtual instrument I have which dominates my system and screen the way it does. It is common to hit the space bar to start and stop playback, even if other instrument consoles are open and on top of the DAW. VI uses the space bar (where is that documented?) to turn certain PERFORM/CONTROL features on and off. It gets so confusing (being a creature of habit or 'standard') to hit the space bar to not only hear nothing playing back but also to have unwittingly deactivated an important control feature which must be searched and remedied before continuing. Not being able to reprogram this keystroke is a problem. If it IS possible to reprogram these computer keystrokes, I've not found that feature. I've only been able to assign and un-assign controller numbers.
On the one hand, one can say that "it just takes some getting used to", but more and more it feels like your 3 year old kid who stands in front of the TV without regard to others who are watching.
Once again, preference options to activate or deactivate these overrides would come in quite handy. Short of expecting an unlikely update of AU from Apple, it is even more crucial for VI to nestle itself a bit better into the OS without taking it over.
... and I can't get it out of my head that some people just don't have a problem with this--!!