Vegas is wasting my money......

Comments

bruceo wrote on 12/18/2008, 4:27 PM
Yes I've tested the drive mapping thing and it doesn't make a difference on the drive letter. In fact it shouldnt matter because vegas builds the sfk and parks it in the same directory so if m2t is accessed it looks into the same directory for the sfk.... Remember I'm using the EXACT SAME 30+ drives, computers and SAME WORKFLOW for at least the last 3 revisions of Vegas, never the peak rebuilding issue that is happening now. It is a probem with Vegas and if you are doing this amount of work (40 hrs HDV/month) with an external drive workflow and not having this issue at all I would be surprised and I want to know where you are and I want to have a visit.....
Steve Mann wrote on 12/18/2008, 9:32 PM
"But if I have been recently editing a vegas project that uses lots of media from that drive, and then I close Vegas, this is when I find I have to wait, and wait and wait...."

Is Indexing turned off?
bruceo wrote on 12/29/2008, 4:04 PM
"Is it possible that a USB stick/drive can skew the mapping?"

Possibly, but that still doesn't matter. We already tried makring the initial drive letter and making sure that letter is assigned when loading .vegs and same symptoms occur
farss wrote on 12/29/2008, 4:13 PM
Been a while, don't know if I suggested this before or not, apologies if I'm repeating myself.

I'd really suggest you try using either firewire or eSATA drives.
One of my 'students' had no end of wierdness happening using USB external drives with Vegas. I know, I know it shouldn't make any difference and it should work the same even if a bit slower. All I can say is since he moved the exact same disks to firewire enclosures the problem of what looked like tape dropouts in the rendered files went away.

I know, your problem is different but for all the grief you're having it would seem prudent to just buy a firewire drive to test this theory.

Bob.