Weird problems - thinking of doing a rollback SOLVED

[luigicampala]

Since i´m running Scope 5 i encounter a strange mixture of problems. Inserting for example B-2003 won´t let me play, changing the device to let´s say Blue-Synth works, then the compressors work one time, but won´t when reopening the project. Or, and that´s most strange, some of the channels at the 16-channels mixer suddenly won´t work and so on and so on. The main problems is: I can´t reproduce the bugs, they just come and go.....ghost in the machine????
All other programs (Live or Samplitude) run well. No overheating.
Anybody out there with the same problems?
I use 3 Pulsar2 cards on a Gigayte DS-3R board, Core Duo E4500, Win XP

I have a production to be finished and i am at the point to decide wether or not to do a rollback to Scope 4.5.
Any hints or recommendations?
Thanks in advance!

[garyb]

at least for how i use it, v5 is pretty solid for me right now.

[luigicampala]

yes it is, also for me, as long as i just use the in and outs and the asio-channels. Most of the times the mixer works, but as soon as i start to use the fx´s things get complicated. Or, even worse, if i use XTC-mode, the songs ihave been using the xtc-plug-ins in won´t open.
So i am using it at a very,very low level.
So the question is maybe, is it a hardware problem, is one of the cards going nuts and it is just a coincidence that this happens on Scope 5 software?

[Fluxpod]

Are you using the inserts on the mixer for as example ssd delay and reverbs? I just encountered very strange behaviour when inserting a ssd delay on a ch in the stm 2448
and the rmx 160 or any other reverb on another channel.It works for a few seconds or sometimes minutes then channels cut out and metallic spikes emmit from the ch with the ssd delay inserted.After that the pc freezes.No problem when only inserting comps-ssd delays but letting reverbs sit in the routing window connected via aux and returned to a ch.Maybe similar things happen in the stm16? If you have reverbs on any insert remove it and try again.Was a headache to find it out for me but now everything works as expected.

You could just download scope 5 again and install it over.That fixed wiered behavious for me in the past.

[luigicampala]

i don´t remember placing reverbs in the inserts. mainly comps or the SPL Transient-designer.
Also i had no freezes (poooh!!!). and synths won´t give a sound, sometimes connecting them to a different mixer channel helps, but sometimes not...

[Fluxpod]

Tried another mixer?

[luigicampala]

yep

[Fluxpod]

Hmpf.I would install scope 5 again.Takes just about 2 min.

[luigicampala]

i forgot to mention: it is the second installation

But if there are others with a similar problem then it points to software bugs.
my other thought was maybe one of the sharcs is damaged and now it works or not, depending on the dsp placement....but i don´t know if it works like this

[Mr Arkadin]

Not heard of anyone with that problem. Sounds specific to your system.

[astroman]

first of all: can you rule out heat for sure ?
often the source of wiered or kind of random errors.
PCI cards are at a position that's notorious for bad airflow, so even if system temperatur at the sensor seems healthy, it may be much higher locally.

cheers, Tom

[luigicampala]

well, i can´t say for sure.
But it´s independant of how long i have been running the system. It appears also at the start.
But i think i´ll try the 4.5 . I have parked it by renaming the folder, so it should be easy to manage.
That would be a way to make sure that the problem is not hardware related.

[astroman]

well... according to my memory 'parking' an older version isn't recommended at all with version 5.
You MUST uninstall the previous one (which was not necessary in any pre-5 system) otherwise there's some collision with system settings or so...
Hopefully I didn't mess it completely (still on 4.x here, no hurry), but that point caught my attention somehow.

cheers, Tom

[luigicampala]

Another observation:
In my default project i am using the 4 midi merger.
When i insert the lightwave v5 i won´t get no sound, no matter if it´s connected to the merger or the midi in. But the midi - light flashes.
So if i delete the merger and put in the lightwave it works

At a certain point some devices (lightwave, vectron, b2003, minimax...) stop to give a sound, while other (modular, blue synth...) don´t have that problem

[iSiStOy]

Do you plug your mixer's midi in?
Could that be midi related?
As a test, you could disconnect midi from mixer (if plugged) and place midi filters on your cables before merger to filter sysex, active sensing, etç...

[luigicampala]

no, sorry, the mixer is not midi connected.

[luigicampala]

So just to let you know: I think i solved the problem by removing one of my three cards. Now i´m running just 12 DSPs, but everything works fine. So i think it was a coincidence that this hardware-problem appeared when updating to v5. What i don´t know by now is: Is the card broken or was it just the IRQ sharing with the SATA and PCI-e port.
Anyway: glad it works!....somebody selling a 15DSP card?