Interpreting this error message?

[terrypin]

When I open any of my digicam movie clips in VirtualDub 1.6.17, I get this:

"Video codec "Panasonic DV CODEC" is claiming to be able to decompress formats that it does not actually support. This can cause the Windows video codec system to malfunction and may cause applications to crash. Please remove the errant codec or replace it with an updated version from the original vendor."

Yet after closing that message, the AVI seems to play OK.

I have no idea how to interpret this. As far as I know the clip has no 'Panasonic connections'. If I open it in GSpot I get (amongst a lot of other stuff):

Video Codec Type: mjpg
Video Codec Name: Motion JPEG
Video Codec Status: Codec(s) are Installed

However, if (without really understanding what I'm doing) I use the bottom section of GSpot, I first get this:

(Src)-->>--(A)-->[AVI Splitter ]>--(cool.gif-->[MJPEG Decompressor ]>--©-->[Video Renderer ]
Status: not rendered yet. Use [2] to render
(Src)-->>--(A)-->[AVI Splitter ]>--(cool.gif-->[Canon Motion-JPEG Decoder ]>--©-->[Nero Format Converter ]>--(D)-->[Color Converter ]>--(E)-->[Video Renderer ]
Status: not rendered yet. Use [2] to render

If I do as instructed and click '2', I get:

Failed to connect Output pin 0x00e17c24 ("Video Out") on Nero Format Converter 'input pin 0x02bc3e8c ("XForm In") on filter 0x01d6b306 ("Color Converter").ConnectDirect() failed. Error: 0x80040207: There is no common media type between these pins.

Which is all completely incomprehensible to me!

Can someone step me through a practical solution of whatever the problem is here please? Or problems, if these are two separate issues, one about Panasonic and the other about these mysterious 'pins'...

Happy to provide any other information that will help isolate the issue.

--
Terry, West Sussex, UK

[celtic_druid]

The way VfW works is first it requests a decoder for the FourCC, then if none is found it asks all the registered codecs if they can handle it. So say you have a file with the FourCC DX50, if you have DivX installed then it will be registered as DX50 and used. Say you don't though, but you have Xvid installed. Xvid can handle the 4cc DX50, so after checking all other decoders, it gets to Xvid and the file opens. You have a broken codec installed though that will answer yes to anything, so before the app gets to Xvid this DV codec is claiming that it can handle DX50 when it can't.

In the case of MJPEG VDub has its own decoder installed, so I guess you are ok. My advice would be to follow the advice in the message and update or remove it.

[Ditka1985]

Interesting...

I used the same version of vdub just yesterday to successfully work with DV files.

The Panasonic DV Codec is a decompressor for DV AVI files. It should not be reporting as a compatible codec for a 4cc of "mjpg", at least to the best of my knowledge. It *should* be reporting as a possible codec for a 4cc of "dvsd"...

I would concur with the previous recommendation to remove or re-install the panasonic DV codec. If it (or, in reality your system) believes that it can decompress stuff that it can't, you're going to have issues!

I *can* explain the mysterious "pins" that are appearing in the error message. The term "pin" is part of the parlance for Microsoft DirectShow (as is the term "filter"). A given filter may have the capability of producing several different flavors of output -- each appearing on a different (virtual) "pin". The programmer "wires" different filters together, selecting an output "pin" and an input "pin" on each (like a virtual patch panel). The only caveat is that the "pins" connected together must have compatible formats. The error you are receiving indicates that this situation is not occurring, and the message is telling the developer exactly what went wrong.

[terrypin]

Thanks both, very helpful.

I'm pretty sure I need this codec, but for the moment I'm darned if I can remember exactly why Anyway, for now, I've used a program called DirectShow Filter Manager 0.5 to change its 'merit' from Preferred to Do not use.

Ditka1985: Could you tell me what executable you used to setup the Panasonic codec please? I think mine was from this file PANADV.INF, dated 2002, extracted from pdvcodec.zip which I downloaded. I've just searched for it online again and downloaded from http://users.tpg.com.au/mtam/install_panvfwdv.htm

Later, I'll try re-installing, but I reckon I'll get same problem.

As for that pin issue, I'm not really clear what if any steps I should now take?

--
Terry, West Sussex, UK

[Ditka1985]

I used the same procedure as you to install the PanaDV codec -- downloaded, unzipped, right-clicked the INF and selected Install.

[celtic_druid]

It isn't how you install it. It is just broken. You need a newer version if one exists or use a different DV codec. There are plenty out there including free ones such as ffdshow and cedocida.

As for "DirectShow Filter Manager", as I said we are talking VfW here.

[terrypin]

I used the same procedure as you to install the PanaDV codec -- downloaded, unzipped, right-clicked the INF and selected Install.

Thanks. Just trying to check it's OK (i.e. not 'broken'.) Mine is 1,199 bytes, and is dated Tue 27 August 2002, 00:42:18. Looks like this:
---------
[version]
signature="$CHICAGO$"
Class = MEDIA

[DefaultInstall]
CopyFiles = Util.Files.Sys
AddReg = Util.Add.Reg.Sys
UpdateInis= AddSysIniEntry

[DefaultUnInstall]
DelFiles = Util.Files.Sys
DelReg = Util.Del.Reg.Sys
UpdateInis= DelSysIniEntry

[DestinationDirs]
Util.Files.Sys = 11

[SourceDisksNames]
1="PANA",,1

[SourceDisksFiles]
pdvcodec.dll=1


[Util.Files.Sys]
pdvcodec.dll
panadv.inf

[Util.Add.Reg.Sys]
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\icm\vidc.dvsd,Description,,%*PANA.DeviceDesc%
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\icm\vidc.dvsd,Driver,,pdvcodec.dll
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\icm\vidc.dvsd,FriendlyName,,%*PANA.DeviceDesc%

[Util.Del.Reg.Sys]
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\icm\vidc.dvsd,Description
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\icm\vidc.dvsd,Driver
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\icm\vidc.dvsd,FriendlyName

[AddSysIniEntry]
system.ini, drivers32,,"vidc.dvsd=pdvcodec.dll",0

[DelSysIniEntry]
system.ini, drivers32,,"vidc.dvsd=pdvcodec.dll",0

[Strings]
*PANA.DeviceDesc="PANA"
---------

--
Terry, West Sussex, UK

[terrypin]

It isn't how you install it. It is just broken. You need a newer version if one exists or use a different DV codec. There are plenty out there including free ones such as ffdshow and cedocida.

Thanks. The one I've been using came via this site, i.e. 'Panasonic DV Codec'. But I should have read the comments! The first of 10 begins
" If you are using this codec there are some important issues you should know. As mentioned, this codec conflicts with videos other than the standard fourcc type 'dvsd'. In my situation, it would interrupt videos of type 'mjpg'..."
So I've clearly been getting some form of conflict.

I'll try that alternative called Cedocida DV Codec.

Note that my knowhow in this area is only at the 'does it work or not?' level!

As for "DirectShow Filter Manager", as I said we are talking VfW here.

Please bear with me while I get a grip on this. As I understand it, you're reminding me that this codec is a 'Video for Windows' type, not a 'DirectShow', yes? That squares with the fact that if I use the drop down box in DSFM to show 'Video Compressors', I do indeed find 'Panasonic DV Codec' listed. But there's nothing there that helps me diagnose the problem. If I show its properties, I see:

AMR Parser

CLSID: D31DB211-4549-4FC0-8B9D-53D118A74B3A
CatID: 083863F1-70DE-11D0-BD40-00A0C911CE86

Category CLSID:{33D9A760-90C8-11D0-BD43-00A0C911CE86}
CLSID: {D76E2820-1563-11CF-AC98-00AA004C0FA9}

Merit = Normal
which, apart from the merit, means absolutely nothing to me!

But that's now probably academic, having pretty well established that I'm getting a conflict.

However, this does raise the question as to what that entry I found in the DirectShow list actually is? I wrongly assumed 'DV Codec' was the Panasonic codec under discussion. So was it coincidence that after changing it from 'Preferred' to 'Do not use', I was able to open my AVI 'MJPEG' files without getting that error message? Or are we getting close to the source of the conflict here? In any case, should I now expect negative consequences popping up somewhere else if I leave it disabled?

IOW, what should I do next to track down the source of the conflict and fix it please?

--
Terry, West Sussex, UK

[jagabo]

The INF file is just only contains installation instructions. The codec itself is PDVCODEC.DLL. It's very old, 1999. I have the same problem as you. I got rid of it and installed cedocida.

[guns1inger]

I have had, on the odd occasion, the Panasonic DV codec try to take over the Div3 as well. I use FFDShows vfw config to set things right again.

I tried cedocida, but couldn't get anything readable out of of it

[terrypin]

Thanks both.

guns1inger: I have FFDshow VFW Configurator. What were the key steps to 'set things right again' please.

I've also just had a very helpful (and rather reassuring) post from phaeron, VirtualDub developer. I'll paste an extract below for general interest:

"As for the warning from VirtualDub, the Panasonic DV codec driver has a dumb bug in it where every time it is asked if it can decode a video stream, it says "yes!" without even checking if the video is DV. Thus, you can get into goofy situations where programs will crash because the Panasonic driver volunteers itself to decode MPEG-4 and Cinepak videos and then promptly blows up. Like GSPOT, most video players use DirectShow and thus will end up with proper MJPEG drivers rather than the Panasonic codec. However, other applications that happen to use Video for Windows may malfunction; don't be surprised if Windows Explorer fails to build thumbnails for some videos.

VirtualDub itself has a workaround for this problem, so it won't be affected by this -- as the warning implies, it can identify and bypass codecs that lie about their format support."

--
Terry, West Sussex, UK

[terrypin]

The INF file is just only contains installation instructions. The codec itself is PDVCODEC.DLL. It's very old, 1999. I have the same problem as you. I got rid of it and installed cedocida.

jagabo: I forgot to ask in my reply just now - how exactly did you get rid of it? If I decide to do the same, there doesn't appear to be any Uninstall routine. Can I use DS Filter Manager and the Unregister button? Or should I delete all references in the XP registry?

--
Terry, West Sussex, UK

[celtic_druid]

DIV3, MJPG, whatever. That is the point about it being broken. As I understand it, it will claim to be able to handle anything. Change a files 4cc to CELT or GUNS and it should claim it can handle it. Got nothing to do with install scripts, registry entries, etc. either. Such a problem would be have to be down to the code of the dll.

Assuming VfW works alphabetically, ffdshow would be asked to handle DIV3 before Panasonic. Sounds like VDub has code to work around it anyway. Still best not to have it installed at all. I'm sure that there would be other free codecs than ffdshow and cedocida.

[guns1inger]

Open the FFDShow vfw Configuration option via the Start menu, and locate mjpeg in the list of Decoder codes. If it is set to disabled, set it to libavcodec and try again.

[jagabo]

The INF file is just only contains installation instructions. The codec itself is PDVCODEC.DLL. It's very old, 1999. I have the same problem as you. I got rid of it and installed cedocida.

jagabo: I forgot to ask in my reply just now - how exactly did you get rid of it?

I think I first tried Control Panel -> Sounds and Audio Devices -> Hardware -> Video Codecs -> Properties -> Properties, then hilited the codec and pressed Remove. But when I closed the dialog and reopened it, the codec was there again. So using Windows Explorer I went to C:\Windows\System32 and deleted PDVCODEC.DLL. If you get a message saying the file is in use, try renaming it instead. Then reboot the system and delete the renamed file. You may also want to use something like Codec Sniper afterwards to unregister it.

[terrypin]

Thanks for all the follow-ups.

I'll first have a crack at 'fixing' the Panasonic, along the lines of guns1inger's suggestion. Although as this sounds like an inherent problem with the codec itself, rather than my system, I'm not too hopeful. So if necessary I'll then remove it.

Before installing the cedocida alternative, I need to be clear exactly why I need the codec, as I've forgotten what it's doing for me!

I've also now got another problem that I think may be related, but if I can't sort it I'll start a new thread on that.

--
Terry, West Sussex, UK

[guns1inger]

You only need either the Panasonic or Cedocida DV codecs if you need to read or write DV avi files from a vfw based encoder such as virtualdub. If you don't use virtualdub, or don't create DV content using it, then you probably don't need either of them.

[terrypin]

Thanks guns1inger. It's going to take me a while to fully get a grasp of all this. But my current take is that I work with DV avi files only when
- I save from MovieMaker in DV-AVI format (my usual choice when I use that program).
- I open them in VirtualDub (usually to compress them with either DivX or Cinepak).

But some weeks ago I recall being advised in a forum/newsgroup that I'd need to download the Panasonic codec. Haven't yet had time to track that down, but will do so and report back.

Status here is that I have renamed pdvcodec.dll, to take it out of the equation.

I'd forgotten that I uninstalled Ffdshow a few weeks ago, because I was getting conflicts implicating it in MemoriesOnTV. I haven't yet re-installed it. Is that likely to cause other problems please?

In particular, I'm wondering if that's why I'm getting Codec Sniper and Sherlock Codec Utility reporting that DivX MPEG-4 DVD Video Decompressor is broken? Not that I seem to use MP4 files...

--
Terry, West Sussex, UK