PlanetZ forums - scopeusers.com

I wish I could post a poll lol, but what do you all think?

Nothing like having a large project withg a minimax or two saved in the .pro and trying to load your project will not let it happen due to this bug.

Also any one know a fix or a work around for this issue?

Cheers!

[EDIT] I should mention I get this error no matter what is going on in SFP, I could have a blank project with nothing loaded yet aside from the mixer and I get this error with like a 10% DSP load, infact I would go asfar to say I get this error 99% of the time I try and load Minimax.

I had this in 3.1c and also 4.0, on teo seperate machines no less, this leads me to believe it is a software issue..

<font size=-1>[ This Message was edited by: Basic Pitch on 2004-08-23 14:43 ]</font>

Something like that used to happen to me. It was around the times of SFP 2.4.
I would get the DSP overload message, and even though I tried to decrease the number of voices or try to delete some devices, the project wouldn't respond any more.
So the only thing left to do was to save the project and hope next time you opened it, everything would be just fine. But the truth is that it wouldn't keep answering.
It doesn't happen to me any more.
I don't have Minimax, though.

Martin

Basic,

I get this error too, but 95% of the time it happens if I load Minimax as the first synth device. If I load Profit5 or something else THEN Minimax, I rarely get the error.

Of course the error causes my card to lose sound. Rather than close the ASIO host (Cubase SX) and restart the project, I've found a less painful work around. I simply change the sample rate within Scope. Cubase responds to the change and then I return it back to 44k. Every single time it's worked so far and has allowed me not to restart Cubase or the Scope project.

Again, I only get the error if Minimax is the first device other than a mixer to load. Odd if I think about it now?

I rarely get the problem with MiniMax, but when it happens, I just change to 48KHz and back. It's not too big of a deal. I do wish they'd fix it, though.

I may be wrong but I don't think CW has ever issued an update to any plug-in device. Ever.

You're probably right on that, for individual devices. But devices are always updated in OS changes - with exception of the last SP4 update.

hi,
I've got the slowest pc in this forum, still I can load the minimax without problems, on scope 4 that is...

not to push here, but on mac I see no problems with Minimax or any other synth, not with presets memorising, mixer insert memorising nor with CC.
So it actually is a Windows bug, or is this argueing too easy?
Anyway it says it's a hard job for Creamware to to 'fix' these kind of irregularities
Not of any help, I know

hi fellows,
try setting your graphic card to 24 bit, I did some experience the other night, setting it to 32 bit makes scope behave strangely, I think that could the answer to that bug, since I've always kept my setting to 24 bit and never experienced anything odd, hope it will help. Well it all depends on one's setting too I guess, but Have a try tho....

You really shouldn't need more than 24bit in your display adaptor settings for typical audio work anyway...16bit graphics would work fine as well I would think... (used to be necesary on slower systems).

(edit: clarified the post)

<font size=-1>[ This Message was edited by: valis on 2004-08-31 03:06 ]</font>

He meant 24-bit graphics, not 24-bit audio. I can't even do 24-bit graphics; only 16-bit and 32-bit.

I understood his post (I'm a graphic artist). Thanks for pointing out the confusion though, I was in 'graphics' mode and neglected being specific; I edited my post to clarify it.