I haven't had this problem with captures made in Premiere.

According to VirtualDub the audio stream in the AVI is uncompressed pcm. TMPGEnc converts it to a wav before encoding.

"Most of the stuff you mentioned will only take analog type avi files, not DV.."
Huh? Avi is Avi is Avi so long as the appropriate codecs exist for playback. mikkie, I know you know your stuff so I would think I must be reading this wrong.

MichelleT, so, if the video is in Vegas and you export the audio as a wav file, how does it sound? Regarding the video, If you use Satish's frameserver, what happens when you play the signpost file in WMP?

Sorry, too quick of a fired off response on my part?

Avi is a sort of file wrapper in windows, that you can stuff with all sorts of stuff from winmedia to mpg2, even as a storehouse for multi channel audio over the 4 gig wav file limit. The software that works with media files have a few ways they can do so, through the older video for windows spec, through the direct show stuff and so on. A lot of stuff like V/Dub relies on the Video for Windows stuff - DV footage compatibility depends on how it well the codec works with VFW.

I've got an older version of TMPGEng I haven't used for quite a while, and it wouldn't touch a test video rendered in VV4c to the NTSC DV template - neither would the latest version of V/Dub. Transcoding the test file to DV in Prem. (using the windows DV codec) gave a different sized file, but no different results trying to open it.

Prem doesn't seem to have it's own DV codec, & won't recognize/use the SOFO version, so I assume Michelle has some other codec installed that prem used for capture. That codec is probably better suited to Video For Windows stuff then the SOFO codec, though any DV working with VFW is to my knowledge a bit of a conversion and perhaps iffy.

While I couldn't open my test files, it's quite possible I could install or set windows to default to another codec for DV and it might work, providing that codec translated itself into the video for windows code/routines that stuff like V/Dub depend on. What can happen though is say I have a DV file encoded by Vegas, but windows is set to use another codec to play/open DV video by default. Where the two codecs agree, then there's no problem and windows or whatever software will happily use this other codec for my video. But if there is a dissagreement, or if something is missing from the Vegas DV file that this other codec inserts, wierd stuff can happen (like all black frames).

The audio I'm guessing at because if the video was a problem as encoded, perhaps the audio was as well in it's captured format. There's a bit of slop I'd call it in the specs, so there are audio files that threw errors in some apps, but are perfectly happy in others. It could be a similar prob with different codecs used, one to write and another to read - DV audio has a few peculiarities I think comparred to a standard windows wav.

Something to watch for in a lot of apps lately is there seems to be a lot of auto conversions from 48kHz to 44.1, which can cause all sorts of problems, especially if dither isn't applied. Yet another possibility if the audio was run through V/Dub, is that the latest version has some prob. of it's own, plus I read something the other day about a prob with one version of TooLAME.

At any rate, nothing at all wrong with rendering audio to wav in Vegas, or mp3 for that matter - doubt seriously you'll do much better with any other software in that respect. RE: mpg2 encoders, just personally with nothing to back it up, I still like the Ulead/Ligos stuff but it requires a bit of tweaking to use & you're stuck using a Ulead app (& I"m still ticked at them).

i answered and fixed your problem on another forum and you said everything works now ..

but for all who want to know ..

the audio problem was because the source and encode sample rate was mixed up ..

the tmpgenc problem was because the vfapi avi plugin for opendml was not set high enough (+3 for vegas DV, the other AVI reader set at 0) )

"I've got an older version of TMPGEng I haven't used for quite a while, and it wouldn't touch a test video rendered in VV4c to the NTSC DV template - neither would the latest version of V/Dub."

mikkie, you do have a VFW DV codec installed, right? Standard NTSC renders from Vegas 4c work fine in VDub and TMPG. I do it all the time.

@BJ_M, good call. I thought it might be something like that but the information was a little on the sparse side :)

The audio problem turned out to be caused by a setting that changed in TMPGEnc and it's ok now. The video problem was solved by increasing the priority of the AVI2 file reader in the VFAPI plugin tab of Environmental Setting.