PlanetZ forums - scopeusers.com

Thank you for the prompt reply.
I'm running Scope 5.1.2709x64
ULLI is at max, ie 12ms @ 96kHz.
Using the ASIO2 Flt Source 64

I thought about that too, so I tested it at both Cubase 8 x64 and 7.5.3 x64, same result. I tried the ASIO guard, no difference.
If it were a recording app issue, wouldn't ...

sounds like a sync issue. it could be a simple as a dusty optical connector. are you sure you're synced properly?

Good day Gary,

The cables are brand new, and when using the ADAT A or B source device, the recordings are flawless.
Moreover, when monitoring in either ADAT or S/MUX, the sound is ...

which machine is recording ? Scope or the 'other' one you're slaved to...
what kind of sync-master is used on that ?
are TOSLink cables ok ? connection boxes clean ?

according to your description I'd rather guess a buffer problem than TOSLink sync
otherwise you'd hear it on the monitors...

cheers ...

Hi all,

I am using the Scope as a slave via adat and sending 96kHz via s/mux.

The sound is great and no problems at all when monitoring.

BUT : when listening to the recorded result it's full of crackle.

p.s. I recorded in every possible combination, straight from the s/mux in, via direct console ...

HNY !!!

As I understand, they are used as oscillators !!!
http://www.matrixsynth.com/2013/06/unbo ... ophet.html

Like a pro

https://www.steinberg.net/en/support/kn ... -windows-8

awesome work!

Thanx Gary, and great quote

garyb wrote:little things can equal a big improvement.

garyb wrote:
yes, but in what way?

yes sorry for that, quality wise.

lower noise floor, I guess you are referring to ad/da's ?
phase issues, I understood, and really important in case of a big mixer.
transparency, again, I guess you are referring to ad/da's ?

latency really can't go lower without an unreasonable increase in the use of CPU resources. latency is all about giving the cpu time to complete all of it's tasks. the D is quite a better deal than the old pci cards were, dollar vs processing power, but the real plus is that the XITEs also sound ...

anyone got one yet? how's the quality?

what is really interesting though, is that the cpu is working flawlessly with 2 other non sonic core audio interfaces, and the same cpu is working also flawlessly in windows xp...
last but not least, the pops and clicks are not only part of the asio drivers but also the wav drivers...

It's really sad, but I tried those settings and nothing changed. I was working with xp flawlessly even without making those changes in BIOS so.... why is it the CPU's fault ?

Moreover, the official response I got from S|C Support Team is to deactivate the following settings
in BIOS :

Intel EIST ...

Conclusion: Serious work needs to be done next week, reinstalling XP32 SP3.

"Wavelab 7 has a problem, when Scope is installed, it is not able to initialize
our ASIO driver, although all other applications can. Steinberg is informed."

answer is from S|C Support Team

The answer I got was to deactivate the following settings
in BIOS :

Intel EIST
Intel C State
C1E Support
Overspeed Protection
Hyperthreading
Execute Bit Support
Set Limit CPUID MaxVal to 3 (maybe not so important)
Intel Virtual Tech
Intel VT-d Tech

Will do it tonight, expecting your answers as well.

siriusbliss wrote:You guys posting these to SC?
I doubt that they're reading this thread.

I will also try to ask them about these at NAMM.

Greg

Even though I am sure they read here, yeah, I emailed them as well.

same for me. no asio for wavelab