PlanetZ forums - scopeusers.com

Bought that software last weekend and I have to say... that its sound beats everything i've heard on pc. Really feels and sounds like a DAT recorder. What are those of you using it thinking about this?

Heh, you know what i think of it...

This is the only recorder i've ever used that i could say after listening to a recorded track : 'This is exactly what i've heard when recording'

yep, thx for making me profit from your culture, i had like a fucking revelation; at last recordings on pc that don't sound dull

I actually don't use VDAT to record audio at this point and the simple reason is I can't sync it with my sequencer, either for recording or playback.

I also find it a little fiddly to use with some annoying crashes.

*sigh*

intermittent crashes are a pain and sometimes can't be fixed without testing hardware. It's rock solid here, this machine is the most stable i ever got: P4B533. Used to work with AMD and although it was really workable, sometimes it would just die on me

legros, if you mind tell about the sync with Logic, I'd appreciate that.

No probs, I'm at work right now and will write back as soon as i get to my place.. One thing though, vdat drives logic and it doesn't work the other way around. laterz

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>

Thanks legros. Unfortunately although my host supports MTC out, it doesn't provide MTC in. That's why I can't synchronise the two.

What host are you using?

I know only of fruityloop that can't be sync slave...

Hello!

Forgive my ignorance...what is vdat?

Thank you

Muzys is my host. Excellent sync master but no sync slave unfortunately.

How tight is midi+audio?
Thx!

rodos,
http://www.creamware.de/EN/products/sof ... efault.asp

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...

It doesn't make much sense to record 32flt to Cubase, as SFP works with 32(flat). You don't want any sample depth conversions when recording. 16 or 24Bit is the only way to go with Cubase, cos of that...

SFP has floating point drivers - I use those with Samplitude floating point recording.

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 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

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.