PlanetZ forums - scopeusers.com

by braking my head to find a solution i realized this.
tell me if i am wrong please.

my two cards 14 and 6 dsps which is 20 dsp's total show their amount of load in dsp load panel.
when i load minimax for example the dsps are loaded and when i raise the polyphony to 16(minimax does this more easily with the update i downloaded) the dsp load increases not instantly but needs about 5 to 10 seconds to load fully.
this means that if i try to play before dsp load has finished there might be some instability.
so the solution of reloading a synth in order to fix stucking keys is not about just reloading. the reloading must be done fully and after when numbers of dsps that getting loaded are becoming stable, then it is the time to be able to play the synth with more stability.
in simple words we should "wait" till the dsp load gets spread to dsps.

also, after many hours of tetsing, i see that six-string does not stuck when is playing back midi data from nuendo.
now i start thinking as it is a sequencer issue and not a scope issue.
to be honest i really hope that this will be my final conclusion.

current working configuration.
scope midi source and seq midi source in merger>from merger connection to seq midi dest and to scope synths seperatlly.
the routing: scope source>seq dest,seq source>synths, made me having troubles so far.
the next step offcourse will be to get i very good hardware synth and use it as a controller as well, or at least a controller only.

On 2006-03-17 06:32, ARCADIOS wrote:
...this means that if i try to play before dsp load has finished there might be some instability. ...
in simple words we should "wait" till the dsp load gets spread to dsps.

should ???
Arcadios, I've spent many holidays in Greece (even if there's no tourism at all), but your humor outperforms everyone I ever met there - and you (the Greece...) have such a talent to take things easy

you HAVE TO wait until everything is well and settled.

I wouldn't even think of setting Minimax from 1 to 16 voices in the middle of a complex project.
Better have a high-poly-mini-project so it's properly initialized.
The reloading of the DSPs is a rather difficult process - and Minimax (as mentioned) needs continuous DSPs, it cannot be spread across cards.

It's not unlikely that such processes accidently move the midi buffers (for example) or mess other things - at least the risk increases heavily.
no dogma though, but avoid if possible

cheers, Tom

ok. as time passes with scopes equipment i realize that the NECESITY is to make slow movements. move slow when loading, changing devices, ......and wait.
next days i will try an m-audio, and i am looking forward for getting a novation.

astroman, you mean that if i used just one card(the scope pro dsp) instead of 2 cards, would it be more safe and stable according to loading modules?
i read somewere that it is possible to choose in which card to load a selected device. is that true?
can i set for example minimax to be loaded on one of the two boards only? or is it spread at both cards necessarilly?


_________________
ELVIS LIVES

<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-18 02:35 ]</font>

<font size=-1>[ This Message was edited by: ARCADIOS on 2006-03-18 02:38 ]</font>

the only devices to be manually locked to a certain board (that I'm aware of) are (most of) the mixers.
As mentioned the process is reallycomplicated - it's not like '...dear Scope, please load my mixer...'
have a look at the count of items in the DSP folder inside the Scope application directory.

All structures are loaded in (these) rather small blocks and the system has some rules to squeeze as much as possible onto the chips.
It is NOT inteliigent but it certainly knows that some devices cannot cross board boundary (some cannot even cross DSP boundary).

Let's take the Mini as an example - it happens to get (for 1 voice) the last 2 chips on a 6-DSP card (because it would fit).
Now you increase poly and the allocation of further DSPs fails, for obvious reasons.
If the Mini would have been loaded with all 16 voices allocated, it would have been automatically loaded on the other board (assuming this has enough chips free)

I don't know the Mini's internals, so the above may not be true in all details but the mechanism should work somewhat this way.

The DSP allocation is pretty good on Scope boards - as frequently mentioned Protools is much, much simpler in this context - often leaving 30% of the capacity unusable.

In early Scope devices people sometimes overlooked sample accuracy, but currently ALL developers are aware of what happens if a device is spread over several DSPs and adjust it accordingly.

Under regular conditions the system does what it's supposed to - if you plan to use a Minimax with lots of voices then things should be easier if it's loaded with all allocated.

Thinking about it, the Mini seems indeed to load with a certain lookahead for voice increase.
My basic project is very 'light' and synths are added as it comes to mind.
There's always the message that the Mini needs a retry to allocate DSP resources when I add it - but it certainly doesn't look for 16 voices ahead

cheers, Tom

Hi,

I have sometime stucking notes with creamware synths, but far less then what I had with Halion (until halion 3.2 release). You should look at cubase.net the haion forum!!!
(by the way, cubase allow you to "reset" your synth through midi->reinitialize menu selection.)

I use XTC and I have some template with Minimax mono AND minimax 6 voices AND Six Strings 3 voices and everything is OK.

From what I have observed, minimax, sixstring and pro 12 are really sensitive devices but I found that my way to work with them reliably.

FIRST: I use template in cubase which hold the config (vsti and creamware synth) and I design them by taking care of the loading order (minimax is always my first creamware synth loaded, followed by halion which take some time to load its samples, leaving that way some time to the DSP loader to stabilize). Interleaving VSTi and Scope synth help.

SECOND: I allways use template as starting point for a project. When you make a lot of change to your synths (synth selection and patches), you will encounter error which seems not "completely cleared" by changing smaple clock or optimisation reloading. When I have found a "generic" setting which fit my needs, I create a template, exit cubase and restart from the template I just created.

Working that way, I do not have any issue anymore with creamware (and I use it "realtime").

Hope that it will help you

Cheers

Michel

<font size=-1>[ This Message was edited by: md69 on 2006-03-19 09:29 ]</font>

I have a sticking note once every 6 months, like garyb.

>stuck notes

I have solved this problem using another midi interface. I use a midisport USB 2x2 midi interface.
Stop stuck notes!

On 2006-03-19 06:34, wayne wrote:
I have a sticking note once every 6 months, like garyb.

You know Midi Stucking Notes isn't a bad name for a bit of electronica...

i try to fix things by always waitting for dsps to stabilize when loading a synth, even when changing sounds.
i suppose you all who do not have stucking notes do the same,
also i send straight to synths and straight to sequencer, and i do not use seq bypassing anymore.
it sounded simple but midi singal travels too much when passing from sequencer and through sequencer sending to synths.
furthermore i can shut down sequencer and still be playing on scope.
i hope that i have made a step forward according to stability.