Dave--
One interesting thing I've found is that in DP's settings, I can only set the buffers to 1024. All other higher buffer settings are grayed out, unless I'm in a different session. Lower buffers than 1024 are resulting in serious cracks and pops. When not using VI, I can access buffers higher than 1024. Hmmm. Could VI be taking over DP so much that it puts a brick wall on my normal settings and options?
I haven't yet dared VI with Logic-- and didn't even consider the headache of the extra dongle!! In fact, my USB hub is SO loaded right now that I had to remove my Logic XSKey just to get my iLok, Vienna Key, and other essential USB items connected at once.
But back to the issue at hand, here's what I suspect is happening:
Since VI's floating windows fight for domination, I think that whenever I change a keyswitch manually in the MIDI edit window, the VI console wants to be on top again, but because I'm clicking constantly inside DP's MIDI edit window, it fights against VI's floating priority and eventually crashes. I can see the different matrices being highlighted as I move a MIDI note keyswitch. Because the matrix keyswitches work better at C0-B0 (being off the keyboard), they must be changed in the MIDI window.
I've also written to the VSL Team about another issue which they can't sort out. It just so happens to deal with odd keyswitch behavior-- some keyswitches cause a new attack to be triggered during a sustained note, even though the keyswitch is out of range of the instrument.
This brings me to the thought of another feature for VI-- to be able to set some sort of transpostion +/- 1 octave right on the console in an effort to assign keyswitches which are above or below the range of the 88-key controller.
Lastly, for the moment, I've also been wondering if having 2 consoles with 2 matrices each is better than having one console with 4 matrices (being of the same instrument such as a violin). Since so many of the PERFORM controls are global this may also offer some additional flexibility. I'm not getting any sort of CPU spikes at all in with VI in DP as I do with other sample libraries. The one caveat is that if VI maxes out at 24 instances, it seems to be a bit of a waste of resources to just add more instances for the sake of convenience. What shall we do with the entire Cube loaded?
One interesting thing I've found is that in DP's settings, I can only set the buffers to 1024. All other higher buffer settings are grayed out, unless I'm in a different session. Lower buffers than 1024 are resulting in serious cracks and pops. When not using VI, I can access buffers higher than 1024. Hmmm. Could VI be taking over DP so much that it puts a brick wall on my normal settings and options?
I haven't yet dared VI with Logic-- and didn't even consider the headache of the extra dongle!! In fact, my USB hub is SO loaded right now that I had to remove my Logic XSKey just to get my iLok, Vienna Key, and other essential USB items connected at once.
But back to the issue at hand, here's what I suspect is happening:
Since VI's floating windows fight for domination, I think that whenever I change a keyswitch manually in the MIDI edit window, the VI console wants to be on top again, but because I'm clicking constantly inside DP's MIDI edit window, it fights against VI's floating priority and eventually crashes. I can see the different matrices being highlighted as I move a MIDI note keyswitch. Because the matrix keyswitches work better at C0-B0 (being off the keyboard), they must be changed in the MIDI window.
I've also written to the VSL Team about another issue which they can't sort out. It just so happens to deal with odd keyswitch behavior-- some keyswitches cause a new attack to be triggered during a sustained note, even though the keyswitch is out of range of the instrument.
This brings me to the thought of another feature for VI-- to be able to set some sort of transpostion +/- 1 octave right on the console in an effort to assign keyswitches which are above or below the range of the 88-key controller.
Lastly, for the moment, I've also been wondering if having 2 consoles with 2 matrices each is better than having one console with 4 matrices (being of the same instrument such as a violin). Since so many of the PERFORM controls are global this may also offer some additional flexibility. I'm not getting any sort of CPU spikes at all in with VI in DP as I do with other sample libraries. The one caveat is that if VI maxes out at 24 instances, it seems to be a bit of a waste of resources to just add more instances for the sake of convenience. What shall we do with the entire Cube loaded?