Mac and SCOPE 4 installation problem
- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
hehe, i did a fresh install a few weeks ago, too. and i had the same exact problem (error -39) as you have now.
what exactly cured the problem, i don't know. but i got it working fairly quick. i did try several times, but (i think) only succeeded after downloading Scope4 again.
i don't think the locked files have anything to do with it, as a lot of files seem to be locked in my new install. could be wrong though.
<font size=-1>[ This Message was edited by: borg on 2005-02-03 08:16 ]</font>
what exactly cured the problem, i don't know. but i got it working fairly quick. i did try several times, but (i think) only succeeded after downloading Scope4 again.
i don't think the locked files have anything to do with it, as a lot of files seem to be locked in my new install. could be wrong though.
<font size=-1>[ This Message was edited by: borg on 2005-02-03 08:16 ]</font>
- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
Hhhm... well here's a thing. i tried reinstalling from the .sit, but this time i didn't run the installer to load the keys etc. i just launched from the SCOPE icon, had to enter my key then and it seems to work! Don't use the installer seems to be the Mac trick.
BTW, i found the loading of graphics, changing polyphony etc. took ages, far longer than SFP3.1c - any other Maccers find this? i may just stick to SFP3.1c to be honest, but it was worth a go.
Cheers for all the replies,
Mr A
BTW, i found the loading of graphics, changing polyphony etc. took ages, far longer than SFP3.1c - any other Maccers find this? i may just stick to SFP3.1c to be honest, but it was worth a go.
Cheers for all the replies,
Mr A
- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
OK i got SCOPE 4 working OK now, but i still have a problem:
i have a default project with STM1632, 16 stereo ASIO sources, STS5000 and MasterVerb Pro. i have 21 DSPs (SCOPE SRB and PulsarII, largest board first (although i've tried them swapped) and about a third of the DSP meter is used. i have two STDM cables.
The problem comes if i try to load Profit 5 - i get an "Unexpected DSP Overload" error. Hitting either Cancel or Retry ends with the same result, Profit 5 loads, but now i have no sound coming out of the card (the STM meters display level though).
This doesn't happen when i load other big synths like MiniMax, and also doesn't happen when loading Profit 5 into smaller default projects. However, a third of the total DSP allocation isn't a lot and i wonder why this is happening and (more importantly) how i can cure it. i'm getting slighty peeved with all this palaver i must say.
Contributions welcome,
Mr A.
<font size=-1>[ This Message was edited by: Mr Arkadin on 2005-02-09 20:54 ]</font>
i have a default project with STM1632, 16 stereo ASIO sources, STS5000 and MasterVerb Pro. i have 21 DSPs (SCOPE SRB and PulsarII, largest board first (although i've tried them swapped) and about a third of the DSP meter is used. i have two STDM cables.
The problem comes if i try to load Profit 5 - i get an "Unexpected DSP Overload" error. Hitting either Cancel or Retry ends with the same result, Profit 5 loads, but now i have no sound coming out of the card (the STM meters display level though).
This doesn't happen when i load other big synths like MiniMax, and also doesn't happen when loading Profit 5 into smaller default projects. However, a third of the total DSP allocation isn't a lot and i wonder why this is happening and (more importantly) how i can cure it. i'm getting slighty peeved with all this palaver i must say.
Contributions welcome,
Mr A.
<font size=-1>[ This Message was edited by: Mr Arkadin on 2005-02-09 20:54 ]</font>
you might want to speak to cwa first, as you could void the warranty, but putting the i/o on the srb to make a scope pro with a 6 dsp srb would probably help(it's really easy, just 4 plastic screws). it doesn't matter which card is first right now, the srb is always seen as second. for the moment, hitting retry a bunch of times should work. you could also remove the sts-5000, open the p5, and then reopen the sts, but loading a couple of smaller devices first might help most....
the cause is that the profit is using resources that are split between the two cards, causing errors. if the bigger card had the i/o, this wouldn't be happening as 1/3 of 20 usable dsps is about 6, the size of the p2.....
good luck!
<font size=-1>[ This Message was edited by: garyb on 2005-02-09 21:44 ]</font>
the cause is that the profit is using resources that are split between the two cards, causing errors. if the bigger card had the i/o, this wouldn't be happening as 1/3 of 20 usable dsps is about 6, the size of the p2.....
good luck!
<font size=-1>[ This Message was edited by: garyb on 2005-02-09 21:44 ]</font>
- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
Thanks chaps, i'll try all these (i'll even double-check Appletalk which should be off). i'll check with CWA regarding the swapping of the I/Os, i have Pulsar2 Plus though, so i'm not sure if it's the same deal in terms of ease of swapping. As to warranty i've had these cards at least four years now so i think it was void a long time ago! All my software is assigned to the Pulsar2, so if i swap the outputs to the SRB are there any issues there?
Cheers for the replies,
Mr A
<font size=-1>[ This Message was edited by: Mr Arkadin on 2005-02-10 07:12 ]</font>
Cheers for the replies,
Mr A
<font size=-1>[ This Message was edited by: Mr Arkadin on 2005-02-10 07:12 ]</font>
If I did read well, you just have a problem with loading the Profit in one specific default project, is that right?
You could try loading the Profit first, then the sampler and other modules.
You're so close, if you can't get this isolated problem solved I'd say just start working with Scope and see what happens.
Maybe you find a solution 'on the road' .
good luck
You could try loading the Profit first, then the sampler and other modules.
You're so close, if you can't get this isolated problem solved I'd say just start working with Scope and see what happens.
Maybe you find a solution 'on the road' .
good luck

- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
Well i created a new default project exactly as before but including Profit 5 (with 5 note polyphony), and if i load that it's fine (and still uses less than half my DSP power). So WTF is going on?
This is OK as a workaround, but i have to know i want to use Profit 5 when i start a project, which is never the case - that's the whole point of SCOPE - building it up as you go along. Oh well, i guess i'll just load this new default then delete Profit 5 if i don't use it. At least this way it works.
Cheers all,
Mr A.
This is OK as a workaround, but i have to know i want to use Profit 5 when i start a project, which is never the case - that's the whole point of SCOPE - building it up as you go along. Oh well, i guess i'll just load this new default then delete Profit 5 if i don't use it. At least this way it works.
Cheers all,
Mr A.
there should be no issues with the swap. the fact that your new project works shows that it is the distribution of dsp usage. the first card is almost full then you put in a big device that gets shared between two cards making trouble. when the devices get loaded in a different order, they fit better. having the i/o on the bigger card, should make that problem less likely.On 2005-02-10 06:41, Mr Arkadin wrote:
Thanks chaps, i'll try all these (i'll even double-check Appletalk which should be off). i'll check with CWA regarding the swapping of the I/Os, i have Pulsar2 Plus though, so i'm not sure if it's the same deal in terms of ease of swapping. As to warranty i've had these cards at least four years now so i think it was void a long time ago! All my software is assigned to the Pulsar2, so if i swap the outputs to the SRB are there any issues there?
Cheers for the replies,
Mr A
<font size=-1>[ This Message was edited by: Mr Arkadin on 2005-02-10 07:12 ]</font>
anyway, glad it works. now that you know the cause, it's really a minor problem.