Not complaining here-- please keep that in mind.
Perhaps there is a way to do this other than the way I've been doing it... for a year now.....
When assigning key switches to matrices, it's SO easy to click a note on the keyboard in the console-- but the console keyboard only goes down to A0, a note which is often already assigned to A/B patches.
"Normal" keyswitches are already in place for C1, C#1, D1, etc-- and for those that aren't, the keyswitches automatically default to the "octave 1" notes.
I am wondering if there can't be keyswitch notes included on the keyboard-- accessible through an octave transposition button or a horizontal scroll bar or something similar--- to access C0, C#0, D0, etc.
Yes, I've been triggering these notes on my midi keyboard, but because the matrix keyswitch doesn't "set" itself once it is entered (remaining actively outlined in red), it's too easy for this to get changed inadvertently. It's happened SO many times-- and going back to correct these inadvertent changes adds to sluggish workflow.
This wouldn't be such a problem, except that the VI console "stands in front of" or "stands apart from" the DAW. Therefore, accessing VSL Cube consoles means clicking in the DAW window first, setting the proper track and then clicking back in the VI console. For other instruments, the DAW key commands are available even when its console is on top.
I'll even deal with the extra Audio Unit window that opens up in addition to the VI Console. But even a second or third monitor doesn't address the fact that the VI Consoles override the host's commands-- the only plugin I know of that does this.
I along with many others would love to just hit the space bar to play the sequence while looking at the VI Console, but it's quite an ordeal to click the DAW, click the space bar, and then to click the proper VI console just to monitor a matrix or keyswitch-- only to find out that I wasn't in the proper window on the VI. Then, the whole window clicking/keyboard stroking starts all over.
I'm averaging about 7 minutes per *initial* keyswitch doing this. That doesn't sound like a lot of time, but average number of keyswitches per track are totaling more than 60 for a 10 minute score. That's 420 minutes per track just navigating windows.
Many times (during the ealier stages of assigning patches and keswitches), I really need to watch the Vi Console during playback, and that would be facilitated by being able to start and stop playback with the VI console on top-- the same way other plugins behave.
Generally, I don't care how software works as long as it works and can be navigated in such away as it does not impede workflow. I've read threads about this before and only now see how time becomes a casualty of the process.
Will we see a version of VI to come that will not override the host app?
And if someone has another way of dealing with this, I'd love to know about it. I'm all for thinking differently and all suggestions are welcome.
Thanks!
J.
Perhaps there is a way to do this other than the way I've been doing it... for a year now.....
When assigning key switches to matrices, it's SO easy to click a note on the keyboard in the console-- but the console keyboard only goes down to A0, a note which is often already assigned to A/B patches.
"Normal" keyswitches are already in place for C1, C#1, D1, etc-- and for those that aren't, the keyswitches automatically default to the "octave 1" notes.
I am wondering if there can't be keyswitch notes included on the keyboard-- accessible through an octave transposition button or a horizontal scroll bar or something similar--- to access C0, C#0, D0, etc.
Yes, I've been triggering these notes on my midi keyboard, but because the matrix keyswitch doesn't "set" itself once it is entered (remaining actively outlined in red), it's too easy for this to get changed inadvertently. It's happened SO many times-- and going back to correct these inadvertent changes adds to sluggish workflow.
This wouldn't be such a problem, except that the VI console "stands in front of" or "stands apart from" the DAW. Therefore, accessing VSL Cube consoles means clicking in the DAW window first, setting the proper track and then clicking back in the VI console. For other instruments, the DAW key commands are available even when its console is on top.
I'll even deal with the extra Audio Unit window that opens up in addition to the VI Console. But even a second or third monitor doesn't address the fact that the VI Consoles override the host's commands-- the only plugin I know of that does this.
I along with many others would love to just hit the space bar to play the sequence while looking at the VI Console, but it's quite an ordeal to click the DAW, click the space bar, and then to click the proper VI console just to monitor a matrix or keyswitch-- only to find out that I wasn't in the proper window on the VI. Then, the whole window clicking/keyboard stroking starts all over.
I'm averaging about 7 minutes per *initial* keyswitch doing this. That doesn't sound like a lot of time, but average number of keyswitches per track are totaling more than 60 for a 10 minute score. That's 420 minutes per track just navigating windows.
Many times (during the ealier stages of assigning patches and keswitches), I really need to watch the Vi Console during playback, and that would be facilitated by being able to start and stop playback with the VI console on top-- the same way other plugins behave.
Generally, I don't care how software works as long as it works and can be navigated in such away as it does not impede workflow. I've read threads about this before and only now see how time becomes a casualty of the process.
Will we see a version of VI to come that will not override the host app?
And if someone has another way of dealing with this, I'd love to know about it. I'm all for thinking differently and all suggestions are welcome.
Thanks!
J.