No Audio on Capture

[NTSCrelic]

Hi All,

Having a problem capturing the audio portion of a DV stream depending on the capture software used. When using MainConcept MPEG Encoder or Canopus Picture Controller 300, both video and audio are present without problem. When using WinDV or VirtualDubMod, video is present but there is no audio.

Noteworthy is that each capture program appears to utilize a specific capture driver with no option of changing to a different driver. Here's the list of what works and what doesn't along with the capture driver it says it is using.

• MainConcept MPEG Encoder (audio, video ok) - Canopus DV (NTSC) VCR
• Canopus Picture Controller 300 (audio, video ok) - (unknown driver)
• WinDV (no audio, video ok) - Microsoft DV Camera and VCR
• VirtualDubMod (no audio, video ok) - Microsoft WDM Image Capture (Win32)

Also, here's the System lineup.

• Canopus ADVC-300 DV Converter
• Adaptec AFW-4300 Firewire Card
• 2.4 GHz P4, 1 GByte DDR
• Windows XP SP2

Any ideas how to get these capture apps with no audio talking?

[NTSCrelic]

"Swan's" responses in the post
http://forum.doom9.org/showthread.php?t=48252&highlight=canopus
seem to hint strongly at a DV Type 1 stream from the Canopus ADVC-300 as being the reason for "no audio captured" with certain capture apps like VirtualDub.

I'm not familiar with a way to determine the actual make-up of the DV stream coming from the ADVC-300. The specifications in the ADVC-300 manual list only that the DV stream is available at eaither of two Firewire connectors. Nothing is said about the stream make-up itself. I think I read somewhere that Canopus's DV streams are propriatary. Have not seen anything to confirm or deny that idea.

Any thoughts about all of this?

[Paul Glagla]

I suggest that you open the different captured samples with or without audio
in DVdate and check what it says about type1 or type 2 (and about audio).
It could give you some clues about your issue.

[NTSCrelic]

Paul,

Very cool. Using "DVapp" I can capture to either DV1 or DV2, video and audio. "DVdate" identifies both file types correctly. Gspot however, identifies a codec only for the DV2 file. Gspot showes no codecs for the DV1 file (codec section grayed out completely. Is there no codec on my system for DV1???).

Had difficulty installing the complete package so I used your standalone executable. 1st install error was "MSVCR70.dll not found". 2nd was "Unable to register the DLL/OCX: LoadLibrary failed; code 126", presumably from the missing dll. OS is XP prof w/SP2

Also downloaded and installed "Captureflux". It seemed to display a few frames, both audio and video, and then stop. The most recent frame would remain on the Captureflux screen. No other clues to provide except the same hardware works with other capture apps without dropped frames, etc. It would be nice to see what the incoming DV stream actually is. If you have suggestions, I will be glad to try.

Thank you for your help.
Regards

[Paul Glagla]

You should fix the MSVCR70.DLL issue. Download it on the web (it is found free in many places) and put it in you windows/system32 folder.

About DV codec, let me remind you that when transfering in DV type 1 or DV type 2 from camcorder tape to computer, there is no compression or decompression, so no codec involved. The compression is made in the camcorder when the video is written to tape.

Computer codecs are used when editing DV video, or of course when previewing a file.

There are different DV codecs, but when not otherwise specified the computer uses dvsd (Microsoft's DV codec) included in DirectX. All DV codecs are interoperable, and may decode all DV clips.

You may experiment with this fact, by using a command in DVdate for changing codecs. Try to set the missing codec to "dvsd" to see if it helps.

[NTSCrelic]

Paul,

Ok. Thanks for the info. I'll figure out what's going on with that dll.

I spent some more time with CaptureFlux and see that it is capturing and without frame drops. The status area is showing

"Vid: DV Type 1 - Aud: DV"

I presume this is showing the stream type input to the PC's Firewire port. From what I've been reading, this could easily explain why VirtuaDub and possibly a few other apps are unable capture this stream correctly.

Regards