PlanetZ forums - scopeusers.com

Hi!

Some month ago I started a thread about direct monitoring with Cubase VST 5.1.

ASIO direct monitoring did not work with scope 4.0 but it did with 3.1.
(if you check "direct monitoring" there's nothing to hear, but uncheckt you hear the input signal routed through cubase)

Someone told me, that this is no problem with Cubase SX3. BUT IT IS!

I have a new computer (P4 3GHz Asus P4C800 Board) and Cubase SX3. But again.
If I check "direct monitoring" the moritored signal is just switched off.)

Is there are a problem with Scopes 4.0 ASIO2-drivers?

Greetings Thomas

Are you using more than 1 Pulsar board? And did you manually change the sequence of the boards in cset.ini? Then try it again without that. It worked for me and BLUEmotion in this thread:

http://www.planetz.com/forums/viewtopic ... 62&forum=1

Are you using more than 1 Pulsar board?

Yes, I do.
PulsarII, PulsarI and PulsarI SRB.

And did you manually change the sequence of the boards in cset.ini?

Not on the new computer.

But I will play with this.

Any luck?

I hadn't any time to try it the last days.

No luck!

End even more strange...the setting in cset.ini
[board0]
boardid=0
etc. pp.

seems to heve no effect. I tried all 7 possibilities. 012, 021, 102, 120, 201, 210 and no entries.

The DSP dialog only shows te 6 DSPs of the pulsar 2 first and then 2x four DSP of the pulsarI and SRB.
An in the header line it shows always
"pulsar+pulsarSRB+pulsar2".

Try adding this entry in the cset.ini.

[HV]
numboards=3