32bit or 32float

[Paralon]

im use live 6 and i wander what is the best asio driver to use ?

[voidar]

I would guess Live prefers FLT drivers. I personally prefere the ASIO1 drivers as my clinical test shows they actually pass the full 32-bit signal headroom.

[Paralon]

i was read an topic about the vdat that use 32bit integer resolution and from what i read its sound quality was the best compare to other sequncers.
If i use the asio1-32 that give me the 32bit intiger it not suposed to sound like the vdat in term of quality ??

[astroman]

VDAT isn't a sequencer, but a (virtual) tape recorder - you would not be able to tell the difference if you'd send exactly the same data to whichever program that can record wave files.

the point is that it's almost impossible to retain the exact level of the tracks and so it often seems that VDAT has a better audio quality, while it really is just 0.5 db more volume - not to forget that the Scope mixing engine is extremely good.

this assumes that (in case you use a classic sequencer) all default processing and channel/bus inserts are disabled in the sequencer - to compare on an equal base.
But since there's usually a numeric conversion a small deviation in level is almost unavoidable, see above.

I don't claim that this is the final truth, but it's reasonable imho.
From the pure math point of view Voidar is of course correct (and why should you convert if it's not needed) - I just wanted to prevent another myth and keep things simple.

cheers, Tom

[voidar]

As astroman said, VDAT is a linear "tape recorder" and as the name implies, a virtual ADAT that can work together with hardware ADATs if setup as so.

From my tests, I get the same performance on record/playback from an ASIO-host (32-bit float files) as with VDAT (32-bit linear files), when using the ASIO1 drivers. You won't be able to use ASIO 2.x features like Direct Monitoring and sync with those drivers though, naturally. I personally find those features useless, and I would rather monitor via the Scope-environment as it is actually "latency free".

Most ASIO-hosts (Live, Cubase etc.) seem to look for 32-bit float drivers, though REAPER (my prefered ASIO-host) won't even start without integer drivers.

[Paralon]

ok thx ppl you help me a lot
Voidar you riht i working with asio1 too

[Paralon]

ok thx ppl you help me a lot
Voidar you right i working with asio1 too

[musurgio]

Anyone knows whats the purpose of the clk of the asio2 dest module ?
Can you actually Clock the asio destinations ???
Or is it just for mtc/clock syncing ?
I would love the fact that the asio destination routings could be clocked via syncplate's clock out which is driven from external great clock like mytek !
Anyone knows ?
Regards,
Dimitrios

[voidar]

That's for sample accurate sync with something. I don't remember what it's for at the moment.

[musurgio]

Thanks,
To avoid any misunderstanding, I know that using syncplate you ca sync puilsar with high quality clock but I also know that asio introduces jitter !.
So a re-clocking of the asio routings would be great.
I wonder so if this clk delivers also that !
Regards,
Dimitrios

[garyb]

yes, the asequencer can use the asio clk input as it's clock source. you can sync the sequencer to another sequencer or device that way via midi clock as well.

[musurgio]

Good !
So you can provide a stable great clock like from ytek and have Cubase follow this clock for recording and playing back avoiding any extra jitter ,right ?
Regards,
Dimitrios

[garyb]

yes, but i don't see the connection being more jitter free than the standard connection. either way wordclock can be used.

[voidar]

I would never have thought of syncing an ASIO-host like that. I think of the host as software and my Pulsars as hardware, and I only see the use in syncing multiple hardware.
The host will slave to the audio hardware installed on the machine.