Re: Scope NSA Offer 2: All Zarg synths (Solaris, Quantum Wav
Posted: Fri Sep 27, 2013 2:00 am
Hi, the idea of setting the number of voices to zero is to allow you reliably have an approach for discovering how many voices your DSPs can handle per preset. I need to have this going on myself, since I'm on 21 DSPs of PCI cards, so I don't have the same DSP power as ye Xiters. I've started to put the voice count in my preferred presets in brackets at the end of the preset name in a separate preset bank file.
And indeed, I am not a live-player of Scope stuff. Some day, maybe if/when I get an Xite, but I'm not lugging out a desktop PC with PCI cards now - for many obvious reasons. The few synth bits I play in my little band, I happily use my Micron for latched sequences (I'm the bass player mostly)...
If you're setting up a Scope Project for Live use, I think you should consider setting up many slots with Zarg synths, all routed to your mixer, each with a voice count of zero. If the voice count for a device is zero, then the device won't be loaded in your DSPs.
Then, to change presets, you set to voice count of your currently-playing device to zero, and increase the voice count for the 'next' device to whatever you need.
Alternatively (and I haven't tried this), setting the voice count to zero, then spinning your Program Change knob on your hardware device, will move thru presets quickly, without the latency of loading the DSP with that preset.
It is a strategy that may or may not work for you. I understand that it's (unnecessarily!) fiddly. But it would work.
If you're changing presets mid-song, yeah it'd be a nightmare.
Ideally, you wouldn't need a mouse for setting the voice count - but I'm not aware of any midi-controllable interface to setting voice counts in device slots...
I think the reason why you get that behaviour of noisy partially-loaded presets is because those particular synths themselves have slots for other devices. That is the power of such devices like Solaris and RD... Self-contained devices won't exhibit that behaviour. What's unfortunate is that it appears that Scope loads these 'sub-devices' synchronously - there's no ability to load these asynchronously, and then 'move' the fully-loaded synth into the DSPs that are connected to the mixer.
Given that I'm not a live Scope user, I'm not the man best place to give good advice!
And indeed, I am not a live-player of Scope stuff. Some day, maybe if/when I get an Xite, but I'm not lugging out a desktop PC with PCI cards now - for many obvious reasons. The few synth bits I play in my little band, I happily use my Micron for latched sequences (I'm the bass player mostly)...
If you're setting up a Scope Project for Live use, I think you should consider setting up many slots with Zarg synths, all routed to your mixer, each with a voice count of zero. If the voice count for a device is zero, then the device won't be loaded in your DSPs.
Then, to change presets, you set to voice count of your currently-playing device to zero, and increase the voice count for the 'next' device to whatever you need.
Alternatively (and I haven't tried this), setting the voice count to zero, then spinning your Program Change knob on your hardware device, will move thru presets quickly, without the latency of loading the DSP with that preset.
It is a strategy that may or may not work for you. I understand that it's (unnecessarily!) fiddly. But it would work.
If you're changing presets mid-song, yeah it'd be a nightmare.
Ideally, you wouldn't need a mouse for setting the voice count - but I'm not aware of any midi-controllable interface to setting voice counts in device slots...
I think the reason why you get that behaviour of noisy partially-loaded presets is because those particular synths themselves have slots for other devices. That is the power of such devices like Solaris and RD... Self-contained devices won't exhibit that behaviour. What's unfortunate is that it appears that Scope loads these 'sub-devices' synchronously - there's no ability to load these asynchronously, and then 'move' the fully-loaded synth into the DSPs that are connected to the mixer.
Given that I'm not a live Scope user, I'm not the man best place to give good advice!