PlanetZ forums - scopeusers.com

This could be construed as a problem, a tip, or just a discovery for those using VDAT.

For my start up projects I always have an instance of VDAT loaded.
This is a good idea if one uses VDAT as much as I do, but there's a new caveat I recently discovered.

I just spent the entire day loading new Vienna String libraries and Ensemble.
To make more room on the 150GB Raptor, I deleted MUSE sample folders, and then deleted them further in the Recycle Bin also.
I came back and deleted the vtp. and WAV files of VDAT.
Then I began ny 8 hour loading of the new content.
VE makes the best sampled instruments and hosting app out there IMHO. Everything takes forever but their applications run flawlessley everytime I load something new.

I then defragged the drives and checked for errors etc.
Then I re started after power down and everthing would go fine until the start project was just about loaded, then CRASH. Several times in a row as a matter of fact.
I assumed it was the drive causing this so I how swapped it and rebooted....everything was fine but I couldn't get to my content.
So I tried this again ....CRASH< BOOM< BANG.
I knew it was something to do with the drive, and it happened while I was close to bring finished loading the start up project.
So I had an idea and decided to disable the drive and start it up again.
Everything worked fine. Out of curiosity I deleted the instance of VDAT I had, and saved the project.
Then enabled the 4th HDD again where the VDAT files use to be and re booted.
Everything worked fine since I deleted the instance of VDAT.

Lesson learned............wherever your VDAT files are located, when you delete them but still load a project with VDAT in it, it seems to crash the app...
I am not sure why, but all I know after hours of troubleshooting, that VDAT seems to remember some paths or small amounts of data that causes SFP to crash.
Don't waste hours pulling your hair out like I did. When you start up a project w/o VDAT and add an instance after SFP is open, then record a couple of tracks and leave them so VDAT can find it's home.
Better yet, unless you use VDAT live for playback of high fidelity tracks, don't save it in a project unless you can leave the files as a trace path, and then don't change that.

I have used VDAT for the last year in an excessive way, Even playback of VDAT files live and recording those to another instance. So I have months of experience using this under pressure, and here again I learn something new.

Be Warned........

good tip to keep in mind.

what i do is always use the same VDAT output files, which is as long as i am ever likely to record (i have it set to 20 min)

then when it comes to using them i copy them from that folder and rename them accordingly. that way you dont have hundreds of VDAT files all over the place.

next project will use the exact same VDAT files

of course this wont work for everyone, especially peiople who use VDAT in a more traditional "multitracking" way.

Actually I had 45 minute continuos ones. ( SET 1, 2, 3 etc.)
I didn't know I could do that until the last couple months of the gig, but it was the best way to use backing vocal tracks and drums live. The click was only on the intro and went to the IEMs and not the mains, thanks to the DAS IEM Mixer. I even had muted mains and talkback features, etc.
Once I heard the fidelity from VDAT I could never use Cubase as backing tracks, that why I never really learned how to use Cubase yet. One I compared the tracks when I first started I quickly realized VDAT's true strengths.
I wonder how VDAT will be in SFP 5.0 & XITE-1...
I became so happy w/ the KS88's as controllers I had to buy 2 new ones.
Here's what I am thinking of getting to use with the surround features of XITE-1.
I already have the BCF & BCR, but w/ the KS88 and the Surround Panner Tool I might have a cheap giant Multitracker @96k 5.1, thanks to JL Cooper. They are 1100 new, but I am looking at one on ebay for 700 USD used.

is that thing real? if so why did they spoil the nice symmetry by having those top buttons facing the same way

They have some interesting concepts.
JL Cooper is one of the best companies for hardware MIDI controllers.
I have had some of his stuff for 25 years and it still works.
I still use his lighting controllers. They are only good for PAR Lamps and ACL's, but his stuff is amazingly ahead of it's time, especially the video controllers.
My first sequenced band had the ancient Alesis MIDI FX and MIDI Verb for automated vocal effects, the JL Cooper MIDI Lights and the ancient QX-1. We took Vegas like Grant took Richmond...
I had just brought back the sequencer from Japan in 1984 and decided to put a high tech band together w/ lights and Fog, etc. This stuff was the bomb back then and nobody was using it live. The JL Cooper boards was so cool, you just play back the tracks and add and overdub lights and then quantize it on the sequencer. To make it tight though we would clock it to the left, which is similar to track compensation in the VST world. That way the lights were real snappy. The stuff they got now has motorised rail movement, and their dimmer packs can handle literally hundreds of thousands of watts for really large shows.
My little rig works fine for a decent stage, but someday I might get into the newer stuff.
Anyway they even have a motorized Joystick for surround......
That's just plain silly, so I'll use the one above.

Neutron wrote:is that thing real? if so why did they spoil the nice symmetry by having those top buttons facing the same way

They are conceived for the majority that uses the right hand so the led is not hidden during operation. I think....