This content has been marked as final. Show 8 replies
In Premiere Elements, have you gone to the Device Manager and unchecked the option to abort capture on dropped frames?
It could be that Premiere Elements is just confused because it can't find timecode. Unchecking this option should release it from that.
Regardless, if the pass-through works with Windows MovieMaker (hardly a downgrade, since the capture quality will be identical) you can certainly capture with it and then edit in Premiere Elements. You can also capture DV with the free utility WinDV.
I'll check those things right now, steve(?)
Yes, Movie Maker is capable but I'd rather work with one tool if I can, and it may be an opportunity for the programmers.
WinDV is easily findable..?
I'll return presently. Thanks.
No luck. In PremEles4 under Edit, Preferences, Device Control, DV/HDV device, Preroll 2 secs, Time offset 0 secs - I chose Options with PAL, Panasonic, Standard, and Timecode Format at Non-drop Frame the tick isn't alterable. The device is seen as Online.
Back a bit at Capture, Report capture on dropped wasn't, and still isn't, ticked. Report dropped frames had a tick in it.
I've tried a few options there in capture but F5 Capture still reports Tape ejected. Any attempt to red-button record reports 'Stopped'. :(
Okay, found and installed WinDV and it seems to do a very nice job. I must ask him to include a Stop button.
Although I haven't found a way to do the capture with one tool I've certainly simplified the process with the tiny WinDV tool. Thanks.
Glad you've got some kind of workable workflow, Peter.
Peter, you went to the wrong place to find Device Control. You can get to that option right from the capture window. There is a chevron in the upper-right of the capture screen that you can click. One of the items is "Device Control."
Okay, thanks Robert; I'll try that.
I found WinDV stumble last night when taking straight off a DV tape it stumbled when the output file had grown to about 9GB. Started dropping frames with gay abandon.
The box is a 2.2GHz dual-core Vista HP with 1GB RAM. It just might have been overstressed. We'll see.