TMPGEnc use it's own or Usoft codec for DV type 1 decoding?

[Lamont Cranston]

Does TMPGEnc use it's own or Microsoft's codec to decode DV type 1 avi files?

[tjdmobile]

AFAIK - TMPGenc does not support Type-1 DV files. Only Type-2 DV files are able to be read.

This would be consistent with my findings - I also believe it uses the first Codec that it finds, typically MS's.

[Bondiablo]

I can confirm TMPGEnc does in fact read Type 1 DV files but what it uses to read them I don't know. From the VFAPI plug-in tab in Environmental setting, I think it's either the DirectShow Multimedia File Reader or AVI VFW compatible Reader, both of which show path: TMPGEnc built-in and the TMPGEnc Project File Reader gives an actual path so I'm guessing TMPGEnc built-in means built-in to the operating system so how you would know or change exactly which codec it's using I have no idea. If more than one of the readers can open a file it uses the first it finds starting with the ones set to the highest priority.

[JasonK]

It will use the Microsoft DV directshow decoder filter.

[Lamont Cranston]

Is there a way to get TMPGEnc to use the MainConcept DV codec?

[Bondiablo]

Ok, now I'm curious, how do you get TMPGEnc to use the MainConcept or Canopus DV codec and will it make any difference in the quality of the resulting mpg?

[BJ_M]

yes -- it is better to use main concept or other codec's except when re-encoding to mpeg -- where it is only a decode of the dv file (except speed can be an issue) but if filtering first -- THEN use MC or other codec besides MS native one..

this is how you do it (reprinted from abcdv - but some info is posted elsewhere also, this is for premiere but same concept applies, hack files are at the bottom (link)) ...


Use the MainConcept DV codec in Premiere 6.X
Author: Alan
Publishing date: 24.09.2002 19:29


With Premiere 6 and a very cheap OHCI compliant Firewire card in your PC, it is now finally possible to start editing your DV footage without any expensive DV cards. No more DVRaptor, DV300, DV.now, ... with their own Premiere plugins and codecs. Now you just buy such a cheap PCI card, plug it in your PC, install Premiere 6 and use it's default DV Preset Project Settings.



This leaves only one problem: you can't choose which codec you want to use. It's well known that Canopus builds a good, if not the best DV codec. But Adobe's presets in Premiere 6 force you to use the Microsoft DV codec. While the one included in DirectX 8, which is installed by Premiere 6, is a huge improvement over previous attempts, it's still far from perfect. However, MainConcept, a German software developer, known of NLE software as MainVision and MainActor, has developped a DV codec that's OHCI compliant and can be used in Premiere 6's presets as a replacement for the Microsoft DV codec.

The workaround will allow you to do all the following using the Main Concept codec and an OHCI card:
Play out to the external monitor over firewire from the timeline. Alt-scrub preview ANYTHING to external monitor over firewire from timeline.
Trim mode a split screen out to the external monitor from the timeline.
High speed playback over firewire to external monitor or deck.
Mix with the automated Audio Mixer (on my box I can mix 22 stereo tracks with only 15% cpu overhead)

In short, it will allow you to take advantage of ALL the great DV playback mode features of Premiere 6 while using the Main Concept codec to render Previews and Export clips. You will still have to CAPTURE with the Microsoft codec. There is no performance hit here as the Microsoft codec only wraps the footage anyway (there is no compression involved in capture). If you're satisfied with the quality of the MS codec you don't need to implement the workaround but if you want to work with the higher quality Main Concept Codec, use this trick to use the MainConcept DV codec.

The trick involves copying the qcap.dll file (which contains the MS DV codec) to another location, making room for other codecs. To help you do that and move it back when needed, we provide two batch files that do the copying for you. Read how to use it on the next page.

Before you proceed: read these warnings and additional things to consider before you go ahead!
this hack is not sanctioned by Adobe, Main Concept or any other entity. The fix has only been tested on a PAL dual PIII 800 MHz machine running Windows 2000 Service Pack 1 and Media Player7/DirectX 7 or 8. Others have it working on Windows 98 systems
do not try this workaround if you do not have an existing OHCI compliant Firewire card that works in Premiere 6 in DV mode with Adobe's generic plug-in. This fix will NOT help you resolve any issues you currently are experiencing with these cards and their functionality within Premiere. Please solve any existing DV/OHCI system issues before trying this, as this fix will only allow you to render and export with the MainConcept codec in DV mode rather than using the Microsoft Codec. The MainConcept codec is faster in Premiere and as clean as the Canopus codec. It does not clamp luma like many other codecs
For Windows 2000 users only: you MUST apply the Qcap Registry tweak from the zip file on the next page (qcap.reg) for the following to work. The registry tweak disables a little feature called SFC (System File Checker) in Win 2k that re-copies any system file that gets moved. Unfortunately, with SFC enabled, Microsoft determines what files should be on your system. Applying the registry tweak lets you decide what files should be on your system. If you don't apply this, the workaround will NOT work for Windows 2000 users. You can disable SFC yourself if you know how to use regedit or regedit32 by setting the following:
go to HKEY_LOCAL_MACHINE SOFTWAREMicrosoft Windows NTCurrentVersion Winlogon and set SFCDisable=dword:ffffff9d. This is ONLY for Windows 2000! Win 98 users do not need to do this. If you want to set your SFCDisable back to default, set it to 0.


The trick is that you *must* use these small batch files to delete the all qcap.dll files at the same time - otherwise the wise protection function of win2000 or winXP will always restore that file from other sources.

So, to learn where the qcap.dll file is stored (it can be two or three places), search with the explorer for that file. Typically, you will find it in "systems32", but not only there.

Then make sure that you save the qcap.dll file to another neutral place (create a directory at c:\q or on an external floppy, whatever you like). Without that, you may loose the file at all, what could result in the need to reinstall windows again (but that threat can be avoided by storing the file that you delete - very simple).

To delete the file before the security system overrules you, you have to adjust the small batch files with an editor, to delete all versions of qcap.dll you have found - and then run the batch file. Of course - you will not delete your security version stored at c:\q!


I had to adjust the approach a little bit - the way to success was to install the MC-DV codec first. Then I searched for the file qcap.dll, and I found it three times - in the windows system32 directory, but also under dllcache and servicepack1. If you find it only at two places - fine. But in order to disable the MS-DV codec, you have to take out qcap.dll from all system directories under XP (what is typcially under c:\windows\system32, but also in the cash directory and servicepack 1 directory if you have installed SP1).

Important: to be able to restore the original system, you MUST save the qcap.dll file to another place - I did it both on the boot drivce c:\q, but also on another harddisk (or use a floppy disk to stay on the secure side!). There is not a real risk associated with that, but make sure that you save the original qcap.dll - to avoid that you have to re-install your system. Take also care to avoid that you delete other system files too (simple, but could happen!).

What was not necessary for me was to disables the called SFC (System File Checker), what exists also in XP and copies back any system file that gets moved. At least for me it was fine to delete qcap.dll from the three identified places, the registry change as described by Alan was not necessary for me.

I modified the batch files, what is very simple, to delete the three qcap.dll files at the same time. The modification in the batch file can be done easily in Alan´s files, and you have to put in the correct pathes anyway - that is why I do not load them up.

If you try to do that manually, the system recreates the file all the time - what is a nice feature of XP, but must be overruled here off course.

When you run the batch file that deletes the three qcap.dll files, the system asks you to put in the windows XP service pack 1 disk - what you do not, but you tell the system that you stick to the changes.

After that, you can start Adobe Premiere 6.5 - and setup the settings as described by Alan. Of course, you cannot avoid that the capturing settings is still addressing the firewire interface, and is not able to detect the MC-DV codec. But install the MC-DV codec for the project setting as described by Alan - and ignore the red coloured warning you that you have different settings for capuring - project - files - export.

Be aware that the DV-capturing will not work, but also the timeline export to DV tape does not work under that settings.

To restore the system back to the MS-DV codec, you also have to adjust the second small batch file in a way, where it copies back the qcap.dll to the three places where it was stored originally.

Capturing - is another issue, since it does not work without the MS-DV codec in Premiere 6.x. Either you folllow Alan´s advice and copy the MS-DV codec with this second batch file back, or you apply the Scenalizer LIVE.

Scenalizer LIVE is a wonderfull software, allowing automatical scene change detection and stores each scene under a seperate DV-file. After that, you import the files in the project window into Premiere, what works fine.

That scene detection is still not supported by Premiere 6.5, what is a shame. However, Scenalizer LIVE works extremely well - both for original DV files but also for older analog Hi-8 files, that must be imported via your DV-camcorder and firewire. Scenalizer LIVE incorporates scene detection by both DV-timemarkers, but also optical analysis - the later works fine too.

Under our specific conditions, Scenalizer LIVE has another huge advantage: you can capture to MC-DV directly too with Scenalizer LIVE, all what you have to do is to capture to DV-typ 2 files. If you have installed MC-DV, then your DV files are stored as MC-DV files.

If you capture with Premiere, to must capture to MS-DV, what is no loss in quality - but why not capture to MC-DV if we wish to utilize the better quality of the mainconcept codec?

Also, you can use Scenalizer LIVE to export back the MC-DV file to the DV-tape.

You can test Scenalizer LIVE without risk, download the latest version from http://www.scenalyzer.com/. The testversion has a logo, if you like it buy it and then you have no logo anymore.

Last comment: other software - like Pinnacle Studio 7 - who needs the MS-DV codec, crashes if you do not re-install the MS-DV codec before starting Pinnacle Studio. That is another reason why the two small batch files make sence - I have shortcuts on my desctop, what makes live comfortable.

Thanks to Alan, who wants to stay unknown!

Alan's MainConcept 'hack' files :
http://www.abcdv.com/filemanager/download/1/MainConFix.zip

[Thorn]

Since the MainConcept DV codec has a different fourCC code than the MS one, I would think simply having your DV file use the MC code would cause TMPGenc to use the MC codec. I don't know how much the quality would change.

[chaseru]

The way I make TMPGEnc use the Main Concept codec is to frameserve from VirtualDub. VirtualDub doesn't read dv files until you install another dv codec like Main Concept. You can use the Main Concept trial version for read only without the watermark.

[yg1968]

I am not sure how to tell what TMPGEnc is using as a DV codec but I noticed that you can change the environmental seetings of the Canopus DV codec in TMPGEnc 2.53, so I am assuming that it is able to use the Canopus DV codec. I don't have any problems opening type 1 DV avi files and encoding them to mpeg with TMPGEnc.

*Note for Specification Change in TMPGEnc 2.57

When opening MPEG file with TMPGEnc. Because current version of TMPGEnc does not have own MPEG-2 decoder feature, it relies on other MPEG-2 decoders installed onto Windows system through Microsoft DirectShow to read MPEG-2 file.

Although Microsoft DirectShow does not support playbacking MPEG-2 file as default, by installing software DVD player etc., it is possible to playback MPEG-2 file. Microsoft Although DirectShow has such structure that additional component of DirectShow extends capabilities to read/playback other formats, however this is totally depending on software installed in your system, and it may be sometime unstable because of compatibility or conflict between such additional components, thus, we are not officially support/warrant the feature to read movie file Microsoft DirectShow.

The meaning of movie file is, AVI(Type1 DV format), .mpg(MPEG-1/2) .asf .wmv .mov in this case.

Just to add confusion to this issue. This quote from the 2.57 upgrade indicates that TMPGEnc does not officially support Directshow (which includes type 1 DV avi). Should we therefore assume, from this statement, that TMPGEnc "unofficially" supports Direct Show (including DV avi type 1 files) if you install a software DVD player?

[Bondiablo]

Yep, that note was why I never downloaded a more recent version, I use 2.56. Missed the part about Type 1 DV though, I thought it only applied to MPEG-2 files. Now that I think about it, the ealier versions can't open MPEG-2 files at all without an extra plug-in anyway, which I didn't know until recently when I tried loading an MPEG-2 file as a source, so maybe not upgrading was a mistake. Anyway, I've never had a problem loading Type 1 DV files as a source even before I had a software DVD player installed but then I have a firewire card and the Microsoft DV Camera and VCR driver installed on my system so I imagine that's why it works, though why would you be loading a DV file if you didn't.

[yg1968]

Maybe the software DVD player is only necessary for the mpeg-2 decoder. Nevertheless, the word "officially" in their satement makes it sound that they are "unofficially" supporting Directshow (and therefore DV avi type 1). Perhaps their statement is clearer in Japaneese.

Anyways, here is background information on type 1 vs type 2 DV and Direct Show:

http://www.microsoft.com/hwdev/tech/stream/vidcap/dvavi.asp

http://thetechnozone.com/videobuyersguide/Codecs/Type1-Type2-DV.html

[Lamont Cranston]

I am using TMPGENC Plus V2.59. If I uncheck DirectShow Multmedia File Reader in VFAPI Plug-in under Environmental Setting in Tmpgenc, TMPGEnc will post the error message "cannot open or unsupported' when I try to open a DV Type 1 AVI file. This means to me that TMPGEnc is using the Usoft DirectShow filter to decode the DV Type 1 avi files

[Bondiablo]

Same in 2.56, by checking and unchecking boxes it seems Type 1 DV can be opened with either the DirectShow Multimedia File Reader or the AVI VFW compatible Reader and Type 2 can be opened with either of those as well as the AVI2(Open DML) File Reader.

Decided to try 2.59 and for those it's the same but for MPEG 2 seems the only reason I can open them in win98 is I have Power DVD installed. I only have WinDVD installed on win2k and can't open MPEG 2 in TMPGEnc 2.59.

By the way, what's Usoft?

[Bondiablo]

One other thing I've found is that the Canopus DV codec is only used to open Canopus DV files which it seems no program can open without the Canopus codec. Good news is if you can save your files to a Canopus compatible file, like with Scenalyzer Live if you don't actually have a Canopus card or if you use the Canopus DV File Converter, TMPGEnc can ONLY read it with the Canopus DV codec.

[Lamont Cranston]

One other thing I've found is that the Canopus DV codec is only used to open Canopus DV files which it seems no program can open without the Canopus codec. Good news is if you can save your files to a Canopus compatible file, like with Scenalyzer Live if you don't actually have a Canopus card or if you use the Canopus DV File Converter, TMPGEnc can ONLY read it with the Canopus DV codec.

I have a Canopus ADVC100 and TMPGEnc. Ulead MSP V6.51a, Ulead DVDWS, and MainConcept Mpeg encoder all can read the DV type 1 avi files created by Canopus. The file is DV Type 1.

[Bondiablo]

Yes, I have the ADVC-100 too but in it's case the Canopus codec is part of the boxes hardware and just used for the analog to digital conversion it's not actually on your computer anywhere so the DV file you save on your hard drive isn't really a Canopus DV file. If you were using their software or had one of their cards installed like the EZDV, Raptor or Storm it would be different.

Try downloading Scenalyzer Live which has an option for saving as a Canopus compatible file or use the Canopus file converter to make one of your DV files into a Canopus file and then try loading it without the Canopus codec installed and you'll find nothing can read it.

[Lamont Cranston]

Bondiablo
Yes, you are right. The Canopus software codec is creates it's own DV Type 1.

Usoft = Microsoft
U is a 'bad' substitute for the Greeek letter Mu which for EEs means micro

[JasonK]

I've used Canopus products for years. There are some misleading and downright incorrect statements in this thread about the Canopus codec/files. And there were a few other DV related comments.

The first thing I want to clear up is that the Canopus DV codec is a VFW codec. Their software/plugins work with type 2 files. Any AVI file which is associated with the Canopus DV codec is a TYPE 2 AVI file, NOT a Type 1 avi file. The Canopus DV converter does NOT capture to Canopus files, but to files as determined by the capture software, so it is irrelevant to a discussion of "Canopus files."

The second thing is that if you have a standard Canopus avi file, but don't have the Canopus DV codec installed, you can play it back by using the MainConcept DV codec (although there may be some exceptions depending on the software which rendered the files.) I assure you I have played back Canopus AVIs using MainConcept's DV codec on a system that did not have Canopus DV codec installed.

The key difference with the Canopus DV files vs other type 2 DV files is that Canopus uses a proprietary FOURCC of CDVC instead of DVSD. By simply editing the FOURCC, you can open the Canopus file with the Microsoft DV codec.

Some Canopus DV files are captured as "reference avis" which are a special case. Most people don't use these. These use a wrapper avi which links to the video data in sequential numbers files such as video.000, video.001, etc. So the MainConcept DV codec or FOURCC editing tricks will not work with them. They also present some complications when moving files between drives/partitions.

There is a free playback-only version of the Canopus DV codec which does not allow you to render with it.

There is an unofficial "hacked" version of the Canopus DV codec that allows it to open and encode DV files using the standard FOURCC of DVSD. I don't have it and don't know where you can get it, but it was fairly common knowledge a couple years ago.

NO, type 1 doesn't refer to MPEG. Type 1 is one of the types of DV files which directshow can read/write. Also, Type 1 and Type 2 AVIs are not the only types of DV files.

Yes, TMPGenc uses the MS DV directshow decoder filter (within the file qdv.dll) to decode type 1 files. Qdv.dll contains other directshow filters as well including an encoder, muxer, splitter.

Regarding's Alan's workaround. That's only applicable to Premiere. And the statements about capturing with the Microsoft codec are downright incorrect. I've been saying that for about 2 years now thanks to those sites which imply recompression with a codec when capturing via firewire. When capturing via firewire, the video is simply copied. Directshow filters are used such as muxers/splitters, but the encoder and decoder filters are not required for capture or output to tape, NOT as a wrapper or otherwise. They are used for playing and rendering only. The Alan workaround allows the MainConcept codec to be used for playing/rendering when using the MSDV editing mode. Some applications wont' allow you to use Mainconcept at all, and some allow you to use MainConcept without having to do any tricks. The batch files are not really required, but some people find that easier. I had some discussions with Alan when we were discussing ways to do this. He's still around.