ADVC-50 / 100 questions

[begu]

Well, I have read many good posts about these converters.
I still want to ask someone, who has either of them, copule of quoestions.

System: WinXP Pro, SP1, DX9b // P4 2.4C, HyperThreading turned ON.

- does the retail package contain any software (codec, driver [WDM?])?
- do I need to install some DV-codec (for V-dub) or use M$-DV codec?
- does the ADVC-50/100 restrict the usage of my GeForce4 capture driver (will there be any conflicts)?
- what is the difference in type-1 and -2 DV when doing conversion in V-dub (AV-sync / speed / filesize issues )?
- does the "DV-stream" from the AVDC-50/100 (via firewire) use type-1 or -2?
- any difference between PCI and firewire connection (ADVC-50)?

I know these:
- bitrate is high, ~13GBytes for 1 hour on HD
- type-1 codec is good for AV-sync, but bad for editing
- type-1 can be opened with somekind of avisynth script for V-dub
- there is some issues with WinXP SP1.. is there anymore?

I will be doing long captures and using V-dub for conversion to AVI.
Codecs will be Xvid (latest Koepi) for video and Fraunhofer Prof. MP3 CBR for audio.

I have read Swan's comments about Ulead's moviefactory and realtime MPEG2 conversion using ADVC-100. I assume that the same can be done using ADVC-50 and Ulead's Videostudio 6 SE.. ?

I also assume that because the AV streams are locked in hardware, there will be no AV-sync problems, when editing the MPEG2-streams (captured with Ulead's programs). I have read that for example the (un)famous Hauppauge's PVR-250 (-350) realtime MPEG2-cards produce AV-sync problems, when editing videos created with them. As far as I can understand this issue comes from the fact that MPEG2-stream can internally maintain AV-sync (even if the sampleclocks for video and audio differ). And if You edit or "broke" the stream, the AV-sync starts to drift. So, using ADVC devices insted, there is no problem, because the AV-sync is perfect (thanks to locked clock signals for audio and video in hardware).

Well that's for it. Maybe someone will help me to decide if I shall buy the ADVC-50/100 or not. Thanks in advance.

[stickboy]

(I have an ADVC-100.)
- does the retail package contain any software (codec, driver [WDM?])?
Nope.
- do I need to install some DV-codec (for V-dub) or use M$-DV codec?Canopus has a free DV codec available for download (http://www.canopus.us/US/Products/DV_Codec/pm_dvcodec.asp) (it's actually only a decoder).
- does the ADVC-50/100 restrict the usage of my GeForce4 capture driver (will there be any conflicts)?No.
- what is the difference in type-1 and -2 DV when doing conversion in V-dub (AV-sync / speed / filesize issues )?VirtualDub can't open Type-1 files. (See the FAQ (http://forum.doom9.org/showthread.php?s=&threadid=30495).)
- does the "DV-stream" from the AVDC-50/100 (via firewire) use type-1 or -2?I think that depends on what program you use to download the video.

Canopus also provides a free DV converter (http://www.canopus.us/US/products/DV_file_converter/pm_dv_file_converter.asp) if you really need it.

[Swan]

- does the retail package contain any software (codec, driver [WDM?])?

No software, at least not with the ADVC-1000.
But you can use free software like WinDV (http://windv.mourek.cz/) to capture with, if you like. There is no driver to install. A Firewire (IEE1394) port is all you need (unless you buy the ADVC 1394 which includes a Firewire port), Windows contains the driver that is needed to communicate with the ADVC-100/50/1394.

- do I need to install some DV-codec (for V-dub) or use M$-DV codec?
To view your captured videos with Mediaplayer, no. To edit them in software that uses DirectShow (Ulead's software, Adobe Premiere, Vegas Video, etc), no. You need a VFW DV video codec if you plan to edit your files in VirtualDub, as it cannot use the MS DV (DirectShow) codec. Also, for Avisynth (using "avisource =" command), you need a VFW codec.

- does the ADVC-50/100 restrict the usage of my GeForce4 capture driver (will there be any conflicts)?
Doubt that. I have a Pinnacle PCTV pro card installed (WDM capture device), plus a Matrox G450 graphics card which also can capture video. None of these interfear with the ADVC-100. :)

- what is the difference in type-1 and -2 DV when doing conversion in V-dub (AV-sync / speed / filesize issues )?

I've not used Type-1, as VirtualDub cannot access the audio part of Type-1 avi files. So, I just capture to Type-2 OpenDML, for simplicity's sake.

- does the "DV-stream" from the AVDC-50/100 (via firewire) use type-1 or -2?
The type of avi file you get on your HD is not decided by the ADVC.
It is just delivering a stream of data. It's the capturing software you use that decides how to write data into a file; depending on what it offers, you'll get your data arranged in a file that is Type-1, Type-2 or perhaps tagged as something else. If you plan to use VirtualDub, use a software to capture (write down the 0's and 1's to the HD) as Type-2 OpenDML avi.

- any difference between PCI and firewire connection (ADVC-50)?
I don't understand the question here. Video is transferred via Firewire on all ADVC-models. The difference between ADVC-50 and ADVC-1394 is that the 1394 has Firewire on the card, and the 50 has not (so you need to have a Firewire port).

- type-1 codec is good for AV-sync, but bad for editing
It's not a "bad" format. It's just bad for use in VirtualDub.:)

- type-1 can be opened with somekind of avisynth script for V-dub
Haven't thought of that being a problem (opening Type-1 avi files in an Avisynth script), but yes, it should tricky to get audio, since Avisynth uses the VFW DV codec.
So, I just tested it.
I captured a short type-1 avi file using Scenalyzer and
wrote this simple script:
AVISource("testvideo.avi")
When I try to open the avi-script in VirtualDub, I get an error message saying "Avisynth Open Failure: Evaluate: Unrecognized exception!".

Using DirectshowSource("testvideo.avi"), the avs opened in VirtualDub, but without audio and when seeking forwards and backwards a message pops up in the preview window of VirtualDub saying "Video Desync!" and sometimes VirtuaDub even hangs.

So, I believe that Avisynth is not able to deal with Type-1 avis, just like VirtualDub.

- there is some issues with WinXP SP1.. is there anymore?
The issue with XP SP 1 is pretty annoying. I'd buy the ADVC-100 if I used XP (I am on Windows 2000).
Other than that, I can only highly recommend the ADVC-1000 and warn you to stay away from Pinnacle's Moviebox DV.

And yes, I have captured TV programs, DVD-preset, Mpeg-2 on-the-fly, in Ulead VideoStudio 6 and 7, edited out the commercials and then joined the commercial free segments and the sync was perfect.
Your conclusion on why this works when using the ADVC products is correct.

[bb]

It is not true that VirtualDub cannot open or deal with type-1 files. It will give you a warning, if you open a type-1 file concerning the audio. You can process the video, though. That's the only drawback: that it doesn't recognize the audio; so if you want to have audio in VirtualDub (why the heck would you want to?) you need to extract a WAV file from your type-1 DV and open it through "Audio / WAV audio". The extraction can be done with almost any DV editing program.

Of course you may also choose to convert to type-2, which is about 5% bigger because it contains the audio twice (once interleaved with the video, which VirtualDub doesn't recognize, and twice as a separate auds stream, which VirtualDub can recognize).

To open a DV type-1 file in AviSynth, use DirectShowSource("C:\blabla\myType1DV.avi", 25), maybe with a third parameter set to false (to disable seeking). Seeking can indeed cause problems like Swan described, so better avoid it. It's the fault of M$'s DirectShow as far as I understand it.

Regarding the audio, I prefer to do it separately using BeSweet. Depending on the target format I mux it later with VirtualDub(Mod) or my DVD authoring program (I use DVDlab).

bb

[Swan]

that it doesn't recognize the audio; so if you want to have audio in VirtualDub (why the heck would you want to?)
I certainly want to be able to hear the audio when I edit. I often edit out the stuff I want from a large file and save to a new file.
I capture a lot of music videos where there are, for example, long fades to and from black between the videos and how can one tell where one ends and the other begins without hearing the audio?
Likewise on music shows with a presenter, where I want to cut at an *exact* point in the introduction of a band or song. Also, when I'm editing a program with commercials in it, I find it invaluable to be able to hear exactly when a segment of the show ends and the commercial starts/ends.

It was sloppy of me to say VirtualDub *doesn't handle Type-1 avi*. It does, like you point out, bb, but it *doesn't handle it very well * in my view. ;)

I'd appreciate if VirtualDub could have a preview window of the audio, like Aviutil. It makes it even easier to make precise cuts.

[FredThompson]

The free Canopus codec does not provide full-range luminance. This is usually not a problem if you use videotapes as your source. If you use laserdisc or modern digital formats , it can be.

If NTSC, be sure to use Xesdeeni's 411Helper if VirtualDub, trbarry's 411to422 Converter if AviSynth. If at all possible, don't do image processing in VirtualDub, just use it for cuts. Best option is to filter with AviSynth as a frame server. NTSC DV has some horrible chroma problems horizontally. Search the forums and you'll find those discussions.

[begu]

Thanks for info.
I'll be using PAL only.

Swan: did You mean that there is difference between ADVC 50 and 100, when speaking of SP1 compatibility?

So I can use -50 with SP1 .. ? I visited in canopus forums, and there seems to be some problems with SP1. So maybe I have to install another XP for capturing (dual boot). But I think it's worth it.

[FredThompson]

As I understand it, the Canopus ADVC-100 will work with PAL or NTSC sources, maybe SECAM, but not that funny pseudo-PAL-from-NTSC common to PAL VCR. However, I don't own one of these. I use passthru on a camcorder or the ADS USB MPEG2 2.0 capture device.

[Swan]

@begu

Swan: did You mean that there is difference between ADVC 50 and 100, when speaking of SP1 compatibility?
Yes, in a way. I think the problems I got after installing DirectX 9 (I use Windows 2000) and the problems people with XP SP1 have are the same.
When going through the messages at Canopus's forum, it's hard to get a grip on what the "XP SP1" problem actually is, but users (and I too) are reporting having various problems, like the preview window of the capturing app going black, Windows saying the device is in use, etc.
I've had the same problems on, but was able to fix it, thanks to a tip from a guy in the forum.

The thing that helps some to restore the preview of incoming audio and video, and the other problems, is turning the power to the ADVC on and off. For me, it was either rebooting or, when having the ADVC powered on, removing and reinserting the firewire cable.
These things are really hard to do if the device is inside the PC, mounted in a PCI slot, as opposed to a separate box. That's why I recommend anyone to buy the ADVC-100 and not the internal cards. ;)

/Maria

PS The ADVC-100 does not work with PAL-60.