Comments

Marco. wrote on 5/7/2009, 2:23 PM
Is it PAL DV?

Marco
Geoff_Wood wrote on 5/7/2009, 4:03 PM
Source was PAL VHS acquired with Pyro AV. Project is PAL DV 720x 576.

g.
rmack350 wrote on 5/7/2009, 4:10 PM
There are a lot of Pyro AV products. What is the 3 hour file in the timeline? DV-AVI? h.264? MPEG2?

What we're getting at here is that the clip on the timeline is probably not one that's easy for Vegas to handle. If it were DV-AVI, for example, Vegas would probably be pretty spritely.

Other problems could be things like a full disk, no available swap space...

Rob
Geoff_Wood wrote on 5/7/2009, 6:25 PM
Pyro A/V Link

DV AVI 720x5876x24 (????)
25 fps
Lower field first
1.0926 (PAL DV)

Sorry, that data disk only going UMDA 5

No anti-virus or other invasive or CPU intensive processes running.

geoff
Marco. wrote on 5/7/2009, 10:19 PM
I assume there's a typo and it's DV AVI 720x576. In this case timeline navigation should work without any noticeably latency. I often edit live concerts with two or three hours (actually 4 or 5 times of it because these are multi camera edits) of dv footage in the timeline. Moving the cursor takes less than a second.

So I also think you either have a hardware problem or your file is broken in another way.

Marco
rmack350 wrote on 5/7/2009, 10:48 PM
One thing that can happen if there's been a disk problem is that Windows can turn off DMA on the disk. You could try turning it back on. Also, I suppose that jumpers can be set incorrectly on the PATA disk. I think, if I remember correctly, that the master must be at the end of the ribbon cable and the slave in the middle, but you could wash that whole issue by setting the disks to cable-select.

Do you happen to have an optical disk drive on the same ribbon as this data disk? That would slow down the hard drive to match the optical drive's speed.

Forgive me for asking. These are basic considerations and if you already know it you don't need to be told, but they're common mistakes.

I can't think of many things within Vegas that would cause this. It kind of sounds like the file was closed and then opened again, which is the default behavior of Vegas when you take a break and go use another program for a minute. Vegas closes your media files when it loses system focus so that other programs can open your media files. That can be turned off, btw.

Could be all of the above.

Rob Mack
Geoff_Wood wrote on 5/10/2009, 7:27 PM
Naa, the problem turns out to be Video Capture 6.0. Each time it receives dropped frames ( Pyro A/V Link outputting Firewire DV from composite input VHS PAL), Sony Vid Cap seems to blast out a wad of crap data into the AVI, which Vegas has trouble navigating within.

Solution seem to be to use an alternative video capture app. Adobe Premiere Elements VERSION 1.1 (!!!) worked fine, as does Scenalyzer. Wonder if that behaviour is fixed in V9.

Granted it was a very bad compilation tape, with lots of start/stops/scenes, but those other apps can handle it just fine ....

geoff