PlanetZ forums - scopeusers.com

Hi

I am sorry i cant help you directly, but googling "asio crackles cubase multicore" brings a lot of hits, regardless of soundcard being used....

Might be a steinbug problem.

next to nothing wrote:Hi

I am sorry i cant help you directly, but googling "asio crackles cubase multicore" brings a lot of hits, regardless of soundcard being used....

Might be a steinbug problem.

I have to agree

there are improved ASIO drivers with the 5.1 RC, maybe worth a try...

Important! Window 7 sometimes stops the loading of drivers,
allthough you have updatet them. in those cases you need to
delete their entry in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

This can happen to files of the Sys folder e.g. "MidiAck.sys".


Delete all Scope.sys entries there in the registry and do an over install with RC 1.


from SC support.

In case it's useful, the following app was recommended on soundonsound.com forums: http://www.resplendence.com/latencymon

Similar to the DPC Latency checker, but more detailed information.

w_ellis wrote:In case it's useful, the following app was recommended on soundonsound.com forums: http://www.resplendence.com/latencymon

Similar to the DPC Latency checker, but more detailed information.

Oh, come on...this is weird. I run cubase and scope without any processor affinity settings and get plenty of crackles. Then I switch on this latency mon utility and I have lesser crackles but still enough for being annoyed...

Good Setups (in terms of processor affinity) are:
1.) Scope on core 0, 2, 4, 6 (leaving the pseudo Hyperthreading "cores" unused) and Cubase on 0 and 2
2.) Even Scope on 0, 2, 4, 6 and Cubase on 0, 2, 4 works pretty good (very few crackles)
As soon as assigning the 4th processor to cubase the crackle rate rises dramatically

Does XTC mode works now on the RC ?
I gave it a try and got the rapi error message (I copied the dll to system 32 in case it would help).
The beta mentionned the non working Xtc status but since there are no mentions on it in the RC, I thought It was fixed.
If somebody is willing to give it a go, I'd like to hear about your luck or lack of.
Thansk.

soylent.green wrote:...this is weird

Being new to Windows 7, I didn't consider for a moment that my DPC latency could be different from the same PC running XP, but it seems from what I've read now that I was very wrong about this. I was still having audio glitch issues with some projects, so I fired up the latency checker - latency was massive, around 1,500us on average and peaking up to 18,000us. After a short investigation I found it was my nVidia graphics card. The weird thing is how to fix it, which I found out quite by accident - play a video in MPC using DXVA, then pause it. DPC latency is now around 160us and all the glitches go away. So, if it is your video card causing some of your latency, it's not impossible that the latency checker's display updates are actually affecting the latency.

soylent.green wrote:...affinity

As for your processor architecture, if you have 4 physical cores plus hyperthreading then assuming you aren't running a server-class processor you've probably got a Core i7. Unlike the earlier Core 2 Quads, this has a fairly symmetrical micro-architecture so affinity shouldn't make all that much difference as far as the physical cores are concerned. One point I would make, though, is that as far as I was aware, cores 0, 1, 2 and 3 are your "real" ones, and 4, 5, 6 and 7 are your "pretend" ones. So, the moment you start using core 4 and above, you're hyperthreading.

PaulSh wrote: As for your processor architecture, if you have 4 physical cores plus hyperthreading then assuming you aren't running a server-class processor you've probably got a Core i7. Unlike the earlier Core 2 Quads, this has a fairly symmetrical micro-architecture so affinity shouldn't make all that much difference as far as the physical cores are concerned. One point I would make, though, is that as far as I was aware, cores 0, 1, 2 and 3 are your "real" ones, and 4, 5, 6 and 7 are your "pretend" ones. So, the moment you start using core 4 and above, you're hyperthreading.

Okay, I've assumed that the core numbering is related to the cpu display where there's a pair of real core + hyperthread core next to each other. Therefore I thought core 0 = real, core 1 = hyperthread.
My latest experiments showed though, that even if I switch off hyperthreading in bios, I end up getting crackles. This is true for affinity setting to all cores. As soon as I "switch off" the last core, ie. number 3, crackles are allmost gone.

Could it really be the graphic card? I have got my system equipped with a very low end nvidia card. Could this card be the cause of my crackels? But on the other hand, I had never had any problems with the built in SoundMAX card. Cubase runs fine with all cores and ht switched on...

the regular soundcard is NOT a realtime instrument.

ht and core stepping on the cpu will only make trouble. YES, your graphic card may even be working improperly, and may be using extra cpu cycles. many things can go wrong including a corrupted driver. it's very hard to say what is making trouble, you can only be sure that you haver the latest bios and unistall and reinstall the latest video driver and maybe even swap out the card with another similar card, if you suspect the video card. one thing is for sure, though. if the computer is set up properly with not irq conflicts, it definitely should run without crackles.

garyb wrote:the regular soundcard is NOT a realtime instrument.

ht and core stepping on the cpu will only make trouble. YES, your graphic card may even be working improperly, ...

This is somehow embarraising: After switching off a unused fire-wire port in bios setup and after having my motherboards bios updated, it seems like my problems are gone.
It's completly made: is nowadays pc technology really so complex, that it is almost impossible to find out the faulty component/configutation with tool support (sonic core havn't been able to name a tool to support me). is it really a game of guessing and being lucky to figure out the right lever..?

yes, unfortunately.

I have this problem with missing dsp files.
When I try for example the samplers or vdat it says somting about missing dsp files.
When I run scope as administrator everything seems to work.

I have tried to delete the scope entries in the register and reinstalled several times but I can't get rid of the problem.

Any new tricks to solve this? (or old)

I'm running windows 7 64 bit with Scope 5.1 rc2 (pci)

Scope needs to be run as administrator when using sample, iirc....

Is it true that a new keyfile is needed to run Scope 5.1 64-bit? If so, how long does is it taking, in gerneral terms, for SC to issue this file?

FWIW, while i'm not able to open Scope in standalone mode (keys not recognized), i have been able to run Scope in XTC mode.

Regards
Glenn

braineeter wrote:Is it true that a new keyfile is needed to run Scope 5.1 64-bit? If so, how long does is it taking, in gerneral terms, for SC to issue this file?

FWIW, while i'm not able to open Scope in standalone mode (keys not recognized), i have been able to run Scope in XTC mode.

Regards
Glenn

.............xtc works without key... but without synths and modules.

anyone noticed that wav device plays the channels inverted in windows7 64x? left for right and right for left?
24 bit wav driver plays the channels correctly but has several drop outs on various multimedia players

yes. wav drivers have this problem and therefore have to be connected instead of L/R > R/L

Seems that my beta as expired!Some days ago i got an error at windows startup refered to my scope keyfile (i don't remember the right message now).
Scope don't starts anymore you can use it only in XTC mode.
Anybody with same problem?

Same situation (second expiry). XTC does not even work anymore.
Two days ago, I paid for the keys but I'm still waiting for the authorisation to be delivered.

I wonder when will SonicCore actually finishes this 64 bits venture (and Solaris, OSX...).

Too much work lately ?