vdat...
- Gordon Gekko
- Posts: 1104
- Joined: Fri Jan 11, 2002 4:00 pm
- Location: paname
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
- Gordon Gekko
- Posts: 1104
- Joined: Fri Jan 11, 2002 4:00 pm
- Location: paname
- Gordon Gekko
- Posts: 1104
- Joined: Fri Jan 11, 2002 4:00 pm
- Location: paname
- Gordon Gekko
- Posts: 1104
- Joined: Fri Jan 11, 2002 4:00 pm
- Location: paname
- Gordon Gekko
- Posts: 1104
- Joined: Fri Jan 11, 2002 4:00 pm
- Location: paname
ok, sorry for the delay, i tripped over few glasses of wine on my way back
two modules in sfp:
- vrc-128 midi out connected to a sequencer midi destination, and the clkO connected to VDAT clkI
- VDAT which accepts the inputs and routes them to asio dest
In logic:
- optionsong settingsmidi synchronization
there under the general tab you set: sync mode=internal, 2nd & 3rd parameter ticked, MTC pickp delay=0, frame speed 25 and make sure the vrc-128 is also set to 25, MTC auto format detection ticked, MTC validate=permanentactivate smpte offset vue separated ticked and then this should sync with vdat whenever vadat plays or records. The descriptions might be twitchy as i have a french localized logic... cheers
<font size=-1>[ This Message was edited by: legros on 2003-05-07 16:52 ]</font>

two modules in sfp:
- vrc-128 midi out connected to a sequencer midi destination, and the clkO connected to VDAT clkI
- VDAT which accepts the inputs and routes them to asio dest
In logic:
- optionsong settingsmidi synchronization
there under the general tab you set: sync mode=internal, 2nd & 3rd parameter ticked, MTC pickp delay=0, frame speed 25 and make sure the vrc-128 is also set to 25, MTC auto format detection ticked, MTC validate=permanentactivate smpte offset vue separated ticked and then this should sync with vdat whenever vadat plays or records. The descriptions might be twitchy as i have a french localized logic... cheers
<font size=-1>[ This Message was edited by: legros on 2003-05-07 16:52 ]</font>
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
-
- Posts: 1743
- Joined: Wed May 15, 2002 4:00 pm
- Contact:
Hey guys, what exactly are you talking about?! Ok about the "feels like a DAT machine" but about the sound... Why would it be any diferent than, say, recording it to Samplitude or Cubase or whatever other multitrack??? The VDAT does not come with any additional AD/DA which are responsabile for the sound.
Sorry, but I really don't understand what you're talking about...
Sorry, but I really don't understand what you're talking about...
Hello! 
I got a bit confused here At0mic
So lets take the things from the beginning:
- the sharcs are 32bit integer
- in the SFP you can load various ASIO modules: 16bit, 24bit or 32bit floating
And my questions:
1) Where is the sample depth conversion that you are talking about? You meant from 32bit integer to 32bit floating? If yes, then the same and worse happens when you use 24bit, or even worse, 16bit modules.
2) This question is linked to the 1st one. Does SFP apply any sort of dithering then *all the time*, since 32bit integer modules do not exist?
3) With VDat which modules do you use and you have 32bit integer sample depth?
Thank you

I got a bit confused here At0mic

- the sharcs are 32bit integer
- in the SFP you can load various ASIO modules: 16bit, 24bit or 32bit floating
And my questions:
1) Where is the sample depth conversion that you are talking about? You meant from 32bit integer to 32bit floating? If yes, then the same and worse happens when you use 24bit, or even worse, 16bit modules.
2) This question is linked to the 1st one. Does SFP apply any sort of dithering then *all the time*, since 32bit integer modules do not exist?
3) With VDat which modules do you use and you have 32bit integer sample depth?
Thank you

"The one who asks, makes a fool of himself once.
The one who doesnt ask, remains always a fool."
The one who doesnt ask, remains always a fool."
I guess At0mic wanted to say that whatever sound 'data' you have in SFP (generated or processed) gets recorded to vdat in exactly that quality.
Asio modules are for communication with external apps and obviously those do 'render' or process the data in some noticable way in their own engines.
my 2 cents, Tom
Asio modules are for communication with external apps and obviously those do 'render' or process the data in some noticable way in their own engines.
my 2 cents, Tom
Exactly.
32-bit fixed point is exactly what runs on dsp. I don't have VDAT, but I like it cos of it's exact recording to disk.
A 32-bit floating point wav is about the same as a 24-bit fixed point wave: the extra bits are used to 'scale a 24-bit' to any headroom u could dream of. That's a major benefit, but do you need all that headroom, quasi infinite dB? It kills precision, it doesn't render Pulsar's audio exactly to disk, apparently it rescales the 24-bit if you use more headroom. Unfortunately, Cubase doesn't record 32-bit fixed point.
24-bit is next best IMO, after 32-fixed, compromising headroom yet very accurate. So this is what I use.
Cubase VST & SX process audio internally in 32 bit float resolution. Too bad Cubase doesn't do 32 fixed point...
I've been told -haven't read it anywhere official- that ASIO, wav drivers, 16bit ADAT or S/P-DIF and 24bits Z-Link connections don't require dithering, only software upon lowering of bit depth: when exporting or rendering usually.
I hope this made sense,
at0mic.
32-bit fixed point is exactly what runs on dsp. I don't have VDAT, but I like it cos of it's exact recording to disk.
A 32-bit floating point wav is about the same as a 24-bit fixed point wave: the extra bits are used to 'scale a 24-bit' to any headroom u could dream of. That's a major benefit, but do you need all that headroom, quasi infinite dB? It kills precision, it doesn't render Pulsar's audio exactly to disk, apparently it rescales the 24-bit if you use more headroom. Unfortunately, Cubase doesn't record 32-bit fixed point.
24-bit is next best IMO, after 32-fixed, compromising headroom yet very accurate. So this is what I use.
Cubase VST & SX process audio internally in 32 bit float resolution. Too bad Cubase doesn't do 32 fixed point...
I've been told -haven't read it anywhere official- that ASIO, wav drivers, 16bit ADAT or S/P-DIF and 24bits Z-Link connections don't require dithering, only software upon lowering of bit depth: when exporting or rendering usually.
I hope this made sense,
at0mic.