SX3 Arghhh

OllieSDM · Post by **OllieSDM** » Mon Nov 15, 2004 1:21 pm

Ok, using sx3, I cant make my PowerPulsar sync to s/pdif, and when I'm recording I'm getting about 900 samples of latency actually recorded, so i have had to use the record placement offset, set t 950 samples or something. I know that fixes it, but i shouldnt have to be doing it, and not being able to sync to s/pdif is a right kick in the cunt.
Anyone else having these probs?
Cheers
Ollie

astroman · Post by **astroman** » Mon Nov 15, 2004 8:35 pm

I don't have that sequencer, but I doubt that the recording latency (or offset) has anything to do with the sync to samplerate.
The first one is related to drivers asio, wdm, etc. the 2nd is a hardware negotiation between the 2 interfaces.

I dunno what gear you're gonna connect by s/pdif, but unless it's a very high quality device - (imho) it's not recommended to slave the Pulsar to a possibly uncertain external clock.

In this case (if the clock is less stable than Pulsar's) not only the data transferred via s/pdif is spoiled, but the complete sound processing - even the synths derive their master clock from the external device...

the analog outputs of external gear are often preferable to their digital bros, that 'extra conversion loss' is a fairy tale, at least in the context of an unstable clock

cheers, Tom

Post by **garyb** » Mon Nov 15, 2004 11:10 pm

use asio drivers in your app. you set latency in the set/settings/ulli window in scope, NOT in sx3.

what does your peoject look like? do you have an sp/dif source module in your project?

OllieSDM · Post by **OllieSDM** » Tue Nov 16, 2004 8:42 am

The external thing I am syncing to is an apogee converter, so Its clock is much better than that on the scope board.
It is a problem within SX3, not a problem with the scope platform.
The record offset is needed to compensate anything I record, be it through my normal converter controlled by the pulsars clock, or through s/pdif, but the s/pdif wont sync so anything I record through that is unusable, at the mo I have just gone back to SX2, the bug fix hopefully will fix these problems..
Oh and the record offset I am having to use is seperate from SX calculating the input latency.. Its just SX3 being buggy.
Cheers though.
Ollie

astroman · Post by **astroman** » Tue Nov 16, 2004 9:16 pm

On 2004-11-16 08:42, OllieSDM wrote:
The external thing I am syncing to is an apogee converter, ...

there was a 0.01% chance for this answer, but I took the opportunity to make an idiot of me

your description reads as if SX2 is working, but SX3 prevents the sync, which would indeed be a far reaching effect.

cheers, Tom

<font size=-1>[ This Message was edited by: astroman on 2004-11-16 21:20 ]</font>

liberty · Post by **liberty** » Wed Nov 17, 2004 2:49 am

i have the same problem!

i have tested, i connected my dbx376 to A16 (analog) and S/PDIF from dbx to Pulsar

i have recorded in sonar (ASIO2) 2 tracks on one time, first - A16 input, second - S/PDIF input.. all from dbx source..

and i found, that S/PDIF has recorded with latency!!!
(i have used the dbx - master, pulsar - slave)

i think, it is problem of pulsar (ASIO).. i dont think, that dbx (or other preamp) will send S/PDIF with latency..

Post by **garyb** » Wed Nov 17, 2004 3:00 am

sx won't affect sp/dif. i use sp/dif(aes/ebu) all the time. i have sx3.

*edit* also, the pulsar1 won't do an sp/dif loop(in AND out)...

<font size=-1>[ This Message was edited by: garyb on 2004-11-17 03:04 ]</font>