Home/ Questions/Q 8269851
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T06:22:04+00:00

I have an issue with one of the applications utilizing an AVI Decompressor Filter.

  • 0

I have an issue with one of the applications utilizing an AVI Decompressor Filter. The error returns that there is no suitable decompresser that could be found… however it has worked everyday for the past several months. I thought about re-registering quartz.dll however no luck.

I then cracked open Graphedit and found that I could load the filter into the graph but not connect anymore.

Has anybody come across this scenario before? Any help would be greatly appreciated.

Cheers.

EDIT
If the issue is in the registry, than would a simple system restore do the trick to put the registry back to the way it was. It is too late now to figure out the bug as it happened at a clients end and we had decided to recover windows to get them back up and going. But redundancy checks can be put into place such as automated restore points build into the application to rectify the issue if it ever occurs again. Does anybody think this would work?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    AVI Decompressor Filter is an adapter filter which makes VFW/VCM codecs available to DirectShow. The fact that you can add the filter manually to the graph does not mean it will be useful. This filter typically does not work this way, and in most cases it is added by fitler graph as a part of Intelligent Connect.

    In your case important is the media type you had converted by AVI Decompressor Filter to something better suited for further processing or presentation. The media type there might be not the one you expected, or the underlying VCM codec is gone and VI Decompressor cannot pick it up any longer.

    In Windows 7, AVI Decompressor uses internally msyuv.dll, which is “Microsoft UYVY Video Decompressor”. Something is perhaps wrong with it in your system. You might want to check its registration as VFW codec:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
VIDC.UYVY="msyuv.dll"

    With 64-bit OS, you might need to look at another key affecting 32-bit apps in 64-bit OS:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32]
VIDC.UYVY="msyuv.dll"
    • 0