Page 1 of 1

Scope STDM cable

Posted: Tue Feb 19, 2019 9:40 am
by sethius
Hey guys,

I have a problem running more than 2 cards.

I have a Pulsar 2 and a SRB installed and connected with an STDM cable, but when I add a pulsar 1 to the PC and connect to the STDM cable I get errors when loading plugins in scope.

Do I need an additional STDM cable to connect the other connectors on the Pulsar 2 and the SRB?

Thanks.

Re: Scope STDM cable

Posted: Tue Feb 19, 2019 9:50 am
by Bud Weiser
stdmpage.jpg
stdmpage.jpg (46.04 KiB) Viewed 5095 times
does that help ?

:)

Bud

Re: Scope STDM cable

Posted: Tue Feb 19, 2019 11:15 am
by petal
You only need "one cable to rule them all"

But as many as possible "to bind them" the best way you can together.

Re: Scope STDM cable

Posted: Tue Feb 19, 2019 11:47 am
by garyb
bad cable?
dirty connectors on the cards?
broken card?

Re: Scope STDM cable

Posted: Tue Feb 19, 2019 1:40 pm
by sethius
Thanks guys.. I might have to pull the cards out and just test the pulsar 1 on it's own to be sure it works.. or I'm hooking them up wrong lol!

or maybe it's the cable?

Ok so I understand this correctly, the 2x pulsar 2 card I have have 2 connectors and are PROJECT cards?
- do I need 2 cables for them? They seem to work together with 1 cable..

The pulsar 1 has 1 connector

so to connect the 2x pulsar 2 cards (PROJECT?) and the Pulsar 1 (HOME?) all together I need 2 cables - like example 2 (SCOPE Professional + Project + Home)?

Thanks!

Re: Scope STDM cable

Posted: Tue Feb 19, 2019 1:46 pm
by garyb
one cable should be sufficient.

just connect them all via the "front" connector, which is the one closest to the back of the case.

Re: Scope STDM cable

Posted: Sun Feb 24, 2019 4:07 pm
by pdistefano
I've got a machine running 2x luna's and a 6dsp pulsar. Recently I've started getting messages "Luna 1 doesn't seem to have an STDM cable attached"
(a) Is there a way to clearly identify which specific card Scope is calling "luna 1" and (b) work out whether it's a bad cable or an issue with the card itself and/or connectors.......I've tried cleaning the connectors and reconnecting which seems to work as a start, but then after a month or so it happens again.... I'm suspecting possibly since the 3 cards are not perfectly aligned the cable in tension may be being gradually pulled off the "luna 1" card connection??

Re: Scope STDM cable

Posted: Sun Feb 24, 2019 4:58 pm
by garyb
just make a new cable. it's too cheap and easy.

Re: Scope STDM cable

Posted: Sun Feb 24, 2019 8:00 pm
by pdistefano
or easier just gaffer the cable to the card ?? :lol:

Re: Scope STDM cable

Posted: Sun Feb 24, 2019 8:16 pm
by garyb
hahaha!

Re: Scope STDM cable

Posted: Mon Feb 25, 2019 5:52 am
by sethius
Hey guys thanks again for the advice on the cable.

I've managed to take pictures of the error messages that i'm getting when I put the pulsar 1 into the system with the 2x pulsar 2 cards. I mainly get this message with the solaris 5.. maybe also the rotor ex?

Any idea if these errors are related to me only using 1 cable, or if not what the problem could be? Like I said before, i have no problems if i just use 2x pulsar 2 cards.

Thanks.

Re: Scope STDM cable

Posted: Mon Feb 25, 2019 6:40 am
by Janni
Did you check IRQ-sharing?
Maybe your P1 shares an IRQ with an other controller...
If not you could try to clean your PCI-connector with alcohol.

Re: Scope STDM cable

Posted: Mon Feb 25, 2019 7:30 am
by sethius
No no yet, good idea!

Re: Scope STDM cable

Posted: Mon Feb 25, 2019 10:22 am
by garyb
what are you adding?

all resources are limited. the problem with Solaris and other Bowen synths is that they use a lot of resources. it's likely that the project you are using forces the synth to use dsps across both cards, because a big patch with a lot of voices can easily fill 6 dsps. when the dsps are physically too far apart, the slight latency between dsps can make the patch impotent. does reducing voices or simplifying the project help?

Re: Scope STDM cable

Posted: Mon Feb 25, 2019 10:53 am
by astroman
Set the patch to a single voice and watch the DSP meter. The Exception error might as well point to a hidden bug in the synth's routing. Solaris is one of the most complex Scope synths and such things may happen.
(if it's not triggered by overloading as mentioned)