Open a session, and \'Locate file...\' comes up..... two questions....

I should know this by now, but I don't...(so thanks for any help). Sometimes, when I'm opening an existing session, and it stops with the prompt, 'Locate file:...bass_02.WAV (for example), one of two things happens. 1. Sometimes, even though I find the exact file it's asking for, it will say 'Cannot complete...too few samples', even though it is THE file. Can anyone explain this? 2. Sometimes, it will stop and ask for a file that (I'm pretty sure) is non-existant, because it was deleted. Is there a way to make it stop asking for this file? Thanks very much, Roy

thats weird Roy. I havent encountered that before. Are these files that have been on your hard drive for a while or have you recently reloaded them to your computer? The reason I asked is because when I installed my new HDD and transferred the songs to the new disc, my computer took it unto itself to stick some of my .wav's in the wrong folders. Luckily I found them all, but have no idea why it happened.

Hey Roy This is more of a support-group type of comment than actual help. I've had the latter happen to me just the other night. I'd deleted some files from a PT session that I had imported. Once deleted from the session, I deleted the source waves from the drive. The next time I loaded that session, it asked for them...I chose skip all, and went along just fine afterwards. I guess there may be some sort of table of contents of files that lists what a session will load, and perhaps deleting from a session doesn't delete from that table of contents. Yes, I'm pulling that explanation out of my behind, but it sounds good to me, so I'll keep lying to myself As far as the too feww samples message: how did you solve it? Did you try to re-import the wave file into the session? Paul

I have encountered the exact same thing. I was working with a stereo drum file and to this day when I open that session I'm still prompted for that file. Seems to me that when that prompt comes up there should be a button that stops that. Delete Association or something. I havn't quite figured out how to tell what files in a session are actually being used either. Every time I re-track something, trim, add AS plugs a new file is created. It doesn't seem to me that there's a simple way to see what files aren't being used to delete them. Wav files don't take a small bit of disk space. Brian

There is a known bug (on the Mac anyway).. if you get the Find message every time you load a session.. even tho'you've done it before and saved the session.. it's because the file is used in an unused (non displayed) playlist. If PT is saying that the number of samples don't match.. it's normally right.. and you're pointing to the wrong file (even tho' the name may be the same). A way to fix the problem.. Use Save Session Copy IN... and elect to copy all the media to a new location. Rail

I had this problem quite alot. The way I fixed it was to hit the "skip all" and then go into the session. Pull out your regions list and "select unused" and then "Delete unused" As for the too few samples part of the question, I have never had that happen to me before. Best of luck Roy.

I've run into this a couple times and I have an idea about whats going on. Before I got the new 60 gigger I was using a 10 gig drive for recording. Needless to say space was a premium for a while (had several sessions on that one drive that were all active and couldn't be archived at that point), so I tended to use destructive recording alot. Also, I would delete a track off of the edit view, but leave the track itself (ie, highlighting and pressing the delete key) and then record a new signal into the same track with the same name. I think these situations (and prolly others) cause PT to look for multiple files with the same name but different id info, which causes both the "where is the file" message and the two few samples message, because while the file name itself is correct, the files id info that PT has stored is different. Like as the post a couple above, I'm pulling all this outta northern end of a southbound engineer . However, since I got a new drive, I don't do destructive record anymore and these problems stopped. I imagine that if you consolidated your session after it loaded, I think the message would stop. Not sure if I am saying that right, so what I mean is the process where it generates new files from the active files in the session and then deletes any files not currently used in the session. Hope this helps.