I 'm wondering if anyone has had any experiences with slaving VDAT to the
MOTU AV with ADat 9 pin.
I have two 6 DSP Pulsar 2 boards on a P4/ Asus machine There is nothing else on it as I use Nuendo 3 and Giga3 on two other machines.
Also, the sync plate will only function when its connected to the main board for some reason and not the booster.
VDAT refuses to slave to the MOTU and always pops up "overload DSP" errors in both 48khz and 44. I've tried the PCI Latency tweaks and cleaned all the contacts. If its a case of giving up trying to make it work, as I've read about the BRC, I guess that will have to do.
Any help much appreciated.
MOTU AV & VDAT
all I can tell is that VDAT is a bitch when it comes to syncing to whatever.
if there is only the slightest thing wrong in your setup (possibly hidden and not disturbing anything else), VDAT will throw the towel, so to say.
you should try to find out if you can setup VDAT as you want it to perform and operate it reliably the manual way. Only then consider syncing it externally or to a remote control like the BRC (imho)
cheers and welcome, Tom
if there is only the slightest thing wrong in your setup (possibly hidden and not disturbing anything else), VDAT will throw the towel, so to say.
you should try to find out if you can setup VDAT as you want it to perform and operate it reliably the manual way. Only then consider syncing it externally or to a remote control like the BRC (imho)
cheers and welcome, Tom
I use the MOTU as the Master to slave Nuendo on a seperate machine which is hooked up to Giga3 on a seperate machine via GigaTeleport. An LX20 (which I still have and when its a paper weight I will get an HD24, the LX20 is getting fixed for the last time) is added to transfer additional tracks when necessary for final mixdowns. The VDAT would be slaved after the ADAT as it is described in the manuals, to provide extra prerecorded tracks. I don't use a BRC.
Just to save wear and tear on the ADAT I thought using the VDAT without the LX20 in the chain for awhile might be an option to work with. The LX20 works fine with MOTU as Master and I control everything with with the small LRC plugged into the MOTU.
I assumed, as is advertised, the VDAT could function as a second ADAT but all the hassle trying to get it to work is getting to be not worth it. I would have thought something like this would not be that finicky when a seperate machine is dedicated just to Scope/ VDAT at a particular time. The old Triple Dat module in Win98 was at least reliable in syncing with MMC but then I had Logic on the same machine which might be the difference.
Since both my boards are Pulsar 2 (both 6 DSP's) I thought that the insert of [board0] etc in that .ini file wasn't necessary. I did try putting it in but it had no effect.
It isn't much use though if I can't get it to slave to anything out side the box it is in via the sync plate.
Thanks.
Just to save wear and tear on the ADAT I thought using the VDAT without the LX20 in the chain for awhile might be an option to work with. The LX20 works fine with MOTU as Master and I control everything with with the small LRC plugged into the MOTU.
I assumed, as is advertised, the VDAT could function as a second ADAT but all the hassle trying to get it to work is getting to be not worth it. I would have thought something like this would not be that finicky when a seperate machine is dedicated just to Scope/ VDAT at a particular time. The old Triple Dat module in Win98 was at least reliable in syncing with MMC but then I had Logic on the same machine which might be the difference.
Since both my boards are Pulsar 2 (both 6 DSP's) I thought that the insert of [board0] etc in that .ini file wasn't necessary. I did try putting it in but it had no effect.
It isn't much use though if I can't get it to slave to anything out side the box it is in via the sync plate.
Thanks.
My audio system isn't online. I couldn't get a basic Sync plate to VDAT with analog in and out to work however. The samplerate window was slaved to EXT Adat at 48 khz.
Now to make matters worse the booster board I have has failed. I left the system on and when I came back to it later it indicated the first Dsp of the booster was not working.
The software will boot with the main project board but as soon as the booster board is in the machine and it is referenced in the Cnet.ini file I get the error that the software can't communicate with the board. The first few times the software would start and show 0 at the first DSP but now it won't even start.
This is even without the STDM cables attached.
I wonder if this was the issue with VDAT.
Have you heard of this?
I read somewhere on the forum that they repair the boards?
Now to make matters worse the booster board I have has failed. I left the system on and when I came back to it later it indicated the first Dsp of the booster was not working.
The software will boot with the main project board but as soon as the booster board is in the machine and it is referenced in the Cnet.ini file I get the error that the software can't communicate with the board. The first few times the software would start and show 0 at the first DSP but now it won't even start.
This is even without the STDM cables attached.
I wonder if this was the issue with VDAT.
Have you heard of this?
I read somewhere on the forum that they repair the boards?
yes. likely the board failing wasn't making anything work any better...
write to rb[AT]soniccore.de and ask for an rma. a screenshot of the error would be helpful to Ralf. at any rate, write a clear explanation of what has happened with the card and what you have tried to fix or suss out the problem.
write to rb[AT]soniccore.de and ask for an rma. a screenshot of the error would be helpful to Ralf. at any rate, write a clear explanation of what has happened with the card and what you have tried to fix or suss out the problem.
this is exactly what I meant in my first answer:mikek wrote:... The first few times the software would start and show 0 at the first DSP but now it won't even start.
This is even without the STDM cables attached.
I wonder if this was the issue with VDAT.
Have you heard of this? ...
if something is wrong with the system, be it the card not properly in the slot, problems with the clock, parts of the hardware not working, badly placed cables, whatever comes to mind - VDAT will fail 100%
it will most likely work reliably if the rest of the system is set up properly
the only bad thing is that VDAT will just fail on 'hidden' errors but not report them...
cheers, Tom