Reaktor at one Cpu and Sequencing on another..

How are you calculating this 52ms of delay? Which program is telling you that there is exactly 52ms of delay?

By using my ears.

Have you tried loading Cubase onto the tower PC with the RME audio card and seeing if Vierring syncs when running inside of Cubase on that particular setup?

No but i'll try when i get home today..

It still sounds like the audio buffer on your RME card is set too high, or that the wrong driver option for the RME card was selected inside of Reaktor to begin with. Are you using the latest RME ASIO driver for that setup?

Yes im using the latest driver for both sound card's, and im using the asio driver for both sound card too, the audio buffer is set to 512 which should append to 11 ms, i can't increase it without having "clicks" in the sound..

Could it in any way be some hardware that's "broken" ?
I haven't discovered any other prob's...

Friendly
thomas

 

>>How are you calculating this 52ms of delay? Which program is telling you that there is exactly 52ms of delay?

>By using my ears.

So your control panel in Reaktor is telling you 11ms, but to you it sounds like more than that? Veirring is not a good choice for checking latency issues, use Junatik with all envelopes set to zero attack instead. If Junatik responds perfectly in your setup, then your problem is not an audio-buffer latency issue, but a midi clock syncing issue.


>>Have you tried loading Cubase onto the tower PC with the >>RME audio card and seeing if Vierring syncs when running >>inside of Cubase on that particular setup?

>No but i'll try when i get home today..

yeah, I think something is up with that RME card, it should be able to get waaaay below 11ms latency. My cheap Echo Mia does 11ms, you very expensive RME that was basically designed to do exactly this kind of thing, should be able to approach 5ms or better.



>Could it in any way be some hardware that's "broken" ?
>I haven't discovered any other prob's...

yes, it sounds like something is not working right. Weather or not something is actually broken on the hardware, rather than just not being setup or installed correctly, is something that nobody can really determine with any certainty without examining your setup and running test in person.

-wh

 

This is wierd...

If im setting the buffer to 64 (1.5 ms) at both cpu's they are in synch But:

At the Centrino cpu (Audiolink96) Reaktor as stand alone the sound is fine, then if im going into Cubase sx 2.2 import an audio file and play, the sound is still fine, then if i open Reaktor the sound from Reaktor and the imported audio is getting "very glitchy" sounds a little like bit crushing...

Then if i close Reaktor the imported audio is only a little "glitchy"... (but need to go out and in again to get the sound fine again)

Then i go into Logic 5.3 and there is no problem at all...

Then i open Reaktor as stand alone at the other cpu (Intel P4 RME HDSP 9652) still with buffer set to 64 (1.5 ms) and the sound is "very glitchy"...

If im going into Cubase sx the same thing happening as at the Centrino cpu...

Then i go into logic and no problem, rather than the cpu use is around 95 % so i need to run Reaktor as stand alone...

But why can Reakor as stand alone, play with no problem at the Centrino but not at the Intel P4 ?

And why does the sound "work" in Logic but not in Cubase sx ?

If im playing an mp3 or something there's no problem at both cpu.

If im setting the buffer to 512 (11 ms) the sound is fine every where, but then there is no synch...

Any help is very appreciated.

Friendly
thomas

 

Thomas,

If Reaktor is set to 11ms of latency on either system and to you it sounds "out of sync", THAT is the problem. Changing latency settings isn't going to solve anything if 11ms sounds wrong to you. Anything less than 15ms is not humanly perceptable. You need to get it working right and sounding "in sync" to your ears with a buffer size of 512 before you try lowering the buffer even further.

Like I said, in my opinionn there are just too many factors in this situation to figure out what is wrong over the internet. It sounds to me like you're going to need a professional to come to your studio in person and figure out the problem.

Good luck,

wh