PlanetZ forums - scopeusers.com

actually I checked the date of my vdat.mdl, it is from august 2008, is that the version you guys have too?

I erase everything all of the time. I have done this even when I used a hardware Sequencer.
I use this stuff for live work and since most of the material is not original I don't care about having copies cluttereing up my sample drives. Whatever I sequence is usally very easy to redo since the parts are sparse.
With VDAT we usually record in realtime, the background parts are used and when the gig is over and I no longer will need the 20-30 songs, I delete the files.
I also need to double check every MIDI CC I use for the B2003' and Modular synths, effects and mixers. So its no biggie loading up a VDAT and VRC-S then calling up the file using the Settings browser.
Plus its only 1 large file. When I do use it can run w/o using transports, or I can use the song start/stop features from my controller.
The performers I work with are pretty polished cats, so these little chores for recording are mostly one take and we're done. I spend more time adding effects post than the recording.
I really want my files on this super fast USB 3.0 RAID stick, mostly because the transfer rates are so fast I don't have to wait but a few minutes.
VDAT usually takes 10-12 minutes to load the way I have used it in the past.
But once VDAT is loaded it has never caused a problem. The new x64 is still being tested though.

tomylee, will check MDL date when next in studio. But last night I tried to reproduce the bug but couldn't on Scope 5.0 PCI. heres what I did :

1 ) created a new scope project, set up a VDAT on it.
2 ) In VDAT, pressed 'CREATE' and created tape and files in same folder as the Scope Project.
3 ) Checked the VTP file, it had the full correct path of the WAV files in it.
4 ) Did a 'Save As' of the Scope Project to a new folder.
5 ) Closed Scope
6 ) Re-opened Scope
7 ) Loaded the second project from step 4 )
8 ) VDAT was present with the correct tape files already loaded ( no new ones created on my hard drive ).
9 ) Checked the VTP file, it was unchanged in the original folder from step 2 )

Have I missed a step or something else - or is my system behaving differently from yours ?

hi dante...its long ago, but since I have a new system and the newest scope version (5.1) and the problem still persists I wonder about 9): did you check if the newly created files actually play (sound) and did you do a search for newly created files with the same filename on your system?

in my case the vtp file remains unchanged but playback comes from another emty file with the same file name which was newly created in the folder the scope.exe was last active...

about 2) did you try to create the vdat file somewhere else than on your scope main folder? try for example to create it on a different partition

maybe we can get this sorted finally

Well, that was 18 months ago so I kinda forgot. I will re-do the tests and get back...

if you move the folder with the wave files into another location, you must open the .vtp file in a text editor(word pad, note pad, open office, word, whatever) and edit the addresses to reflect the files' new location and then save the changes. then open vdat and load the tape, or load the project with vdat in it. naturally, the first time that you open a project with an edited tape in a new location, the Scope loader won't know were the tape files have moved to, so you'll have to manually load the tape, the first time that you use the tape from a new location.

p.s. make a backup of the vtp file. you may make a few mistakes getting the format correct.

the work around is to have "working" drive, one to do work on and a storage drive, where things go when you are done working, and always copy the files into the working drive while you are using them. you can then move them off the working drive back onto the storage drive("copy" then "delete" after pasting to the destination is safer than "move"). this way the files are always used with the proper location.

it's actually pretty easy to edit the vtp file. remember, the computer is just a big filing cabinet. as long as files are where they are supposed to be, things work. the computer is constantly just pointed from one file to another. when something doesn't work, it's the file being corrupted, the file's location changed or the file is missing, the cpu is stuck on a pointless task, either maliciously, or from a bad or missing file, or the hardware is broken. for all it's complexity, the computer's actual operations are very simple. they are just very fast.

hi gary, the issue here is not due to folders being moved - In my case scope projects dont load correctly if the vdat tape was not created in the scope main directory, like E:\Vdat\ no folders or files moved or edited...just plain creating vdat files in scope at a folder other than the scope main directory, saving it with the project, closing project, loading it up again and tape is "gone", while gone means: it looks like it is still here, but without the recorded sound, after that it always turns out that scope created a new vdat file with the same filename as the "missing" one on a completely other (mostly scope main directory or bin directory) location...

ralf btw confirmed this bug and reccomended to unload vdat before saving the scope project, but what a bummer..

I just find it strange than none of you can recreate this behaviour...I actually had this on windows xp and now on win7 - completely new fresh install...before with scope 5.0 now with scope 5.1..

well, it's a very old plugin, one of the earliest. it's a really good model of an ADAT. you have to load the tapes every session.

yeah thats right - I would not use it but to my ears - and this may very well be subjectively biased by myself - it just sounds better If I record my mixes into vdat rather than my sequencer (cubase)...apart from that it could be a nice tool to record Ideas for or to quickly give a scope project an audio file

I hope it will be fixed...