Capturing (Sony Vegas vs Window Movie Maker)

[Clear_Mist]

Hi guys,

I'm looking for some insight from you some of you experts if you would be so kind.

OS : Windows XP Pro 64-bit
Capture device : Canopus ADVC-55
Software : Sony Vegas 9.0, DVD-Lab Pro 2.0, ImgBurn


I have started the task of capturing my 8mm analogue home-videos. At first all seemed to go ok but now (after capturing 4-5 tapes) things are not so good. After burning to a DVD I have found that the footage flicker, jumps and is no longer stable.

At first I thought that the 8mm tape was damaged but after playing it direct to the TV, it plays completely ok.
So next I suspected the Canopus capture box but after capturing using Windows Movie Maker the finished dvd was stable.

So my questions are :-

How comes Windows Movie Maker can capture ok and Sony Vegas can not ?
Has anyone had this issue with Sony Vegas ?

Generally speaking, would the quality of captured footage via Windows MM be of less quality to Sony Vegas capture footage ?

[edDV]

OS : Windows XP Pro 64-bit
Capture device : Canopus ADVC-55
Software : Sony Vegas 9.0, DVD-Lab Pro 2.0, ImgBurn

First, almost no software supports XP 64bit. Upgrade to Win7 64 bit first.

XP 64bit was mostly a developer release pre Vista 64 bit that very little software supports. Don't bother with Vista 64, app developers focused on Win7.

FYI - I'm still using 32 bit with little compatibility issue. The only current advantage of 64 bit is ability to use more than 4GB RAM.

[Clear_Mist]

Thanks for the reply edDV.

Sony Vegas 9.0 is the 64-bit version.
Tried Windows 7 but could not get on with it so returned back to XP.

I don't think its a compatibilty issue because I have already manage to capture 4 to 5 8mm tapes without any issues.
For some unkown reason I am now unable to get a stable capture when using Vegas, however I am able to when using Windows Media Manager.

I was hoping that any other Vegas users could shed some light on the problem.

The other answer that I am seeking, is whether capturing with WindowsMM is frowned upon in terms of quality ?

[aedipuss]

it probably doesn't run correctly, version 9 wasn't much different then 10.

Vegas Pro 10 system requirements

• Microsoft® Windows® XP 32-bit SP3, Windows Vista® 32-bit or 64-bit SP2, or Windows 7 32-bit or 64-bit

[edDV]

Vegas 9.0 should work well with the ADVC-55. The problem with Vegas capture is it has so many preference options, it may be possible to get into trouble. One setting that must be unchecked for ADVC is device control. Otherwise the capture hangs waiting for camcorder cue data.

For simple DV capture I prefer WinDV. Then import the DV-AVI file into Vegas. This file will be first generation digital.

Windows Movie Maker can capture a clean DV-AVI but M$ attempts to steer you into a much lower quality WMV export. You must export to DV-AVI under "other" formats.

[edDV]

...After burning to a DVD I have found that the footage flicker, jumps and is no longer stable.

This sounds like reverse field order. For DV format, the source file, Vegas project and DVD "Render As" should all be lower field first.

[Clear_Mist]

Thanks for the replies guys.

Aedipuss, that right Vegas 10 requires XP Service PK 3 which of course is not available for XP 64-bit. This is why I am using Vegas 9.0 which up until recently I have been very happy with.


edDV,
I can confirm that when I select 'render as DVD Pal seperate streams' the field order is Lower first.

By the way, the flickering/jumping is not constanly throughout the dvd. Sometimes its a 10 minute section and the rest of the dvd is stable.


After reading more of your past replies (before and since), I have :-

Unchecked 'enable dv device control' (some time ago)

Downloaded WinDV and captured a couple of tapes... I am hoping this solves my issues. I will report back later.


Knowing that when capturing, the system should not by used for anything else, I would turn off the firewall, AV, disconnect the internet.
I would even run the vidcap60.exe capture utility directly and not load it through Vegas... Would this cause any problems ?


EdDV, I've only just relised that you also use Sony Vegas. So can I ask you a couple of Vegas questions ;

Am I right in thinking that any settings in 'Project Properties' would have no affect on the actual capture itself ?

Before, when starting a capture Vegas would prompt for a filename Tape 16 or something... now it does not prompt and saves the captured clips as Unkown Clip 001 ...any ideas why this is ?

[Clear_Mist]

edDV... you still there ?

[edDV]

...

Knowing that when capturing, the system should not by used for anything else, I would turn off the firewall, AV, disconnect the internet.
I would even run the vidcap60.exe capture utility directly and not load it through Vegas... Would this cause any problems ?

If this i7 is a desktop and you are capturing to an internal disk other than the OS drive there should be full isolation of the capture from other applications. You just need to isolate the capture drive (i.e. don't access the disk from other apps while capturing).

Am I right in thinking that any settings in 'Project Properties' would have no affect on the actual capture itself ?

Yes, if settings are correct in vidcap60.exe properties.

Vidcap or WinDV will capture to a DV-AVI file which is 720x576 interlace lower field first. When you set the Vegas project to the "PAL DV 720x576 25 fps" template, it should auto set to lower field first.

Assuming DVD is the target, in "Render as", Select "DVD Architect PAL video Stream" That should default to lower field first.

This all assumes the VHS tape was recorded with proper frame rate and field order.

Before, when starting a capture Vegas would prompt for a filename Tape 16 or something... now it does not prompt and saves the captured clips as Unkown Clip 001 ...any ideas why this is ?

Because you are now set to capture with an ADVC (analog capture device), not a DV camcorder. You need to name the clips manually.

If you were capturing from a DV tape in a DV camcorder and for some reason the captured file was lost, the Vegas database would prompt you to load a particular tape, then using the timecode in/out points in the database, it would auto recapture the missing clip using device control.

None of this works for analog capture.

[Clear_Mist]

Thanks edDV.


Update :

WinDV, great little program! Although I have managed to capture a couple more tapes successfully, others still get the jumping and flickering. After more reading I'm thinking it could be this Timebase Correction problem .

...However, if this was my problem then wouldn't every single capture be faulty ?

If a capture is with faults then sometimes another recapture of it gives me a fault free capture. Only downside here is drive space and having to watch the hour and half captured at least twice.

[edDV]

Thanks edDV.


Update :

WinDV, great little program! Although I have managed to capture a couple more tapes successfully, others still get the jumping and flickering. After more reading I'm thinking it could be this Timebase Correction problem .

...However, if this was my problem then wouldn't every single capture be faulty ?

If a capture is with faults then sometimes another recapture of it gives me a fault free capture. Only downside here is drive space and having to watch the hour and half captured at least twice.

Test the ADVC and software by capturing a known good source, like a cable/sat box. If that works then the fault centers on the VHS VCR, timebase corrector or a particular tape.