CCE and the HUFFYUV Codec

slk001 · 1st October 2003, 20:43

I have been fighting the CCE HUFFYUV codec issue for quite a while. I have the proper codec loaded onto my WIN2K Pro system, but it never seems to load (it's in the WINNT/SYSTEM32 directory). Instead, the MSYUV.DLL codec is being loaded. I have even go so far as to try to delete the MSYUV.DLL codec, but it is like the "codec that won't die". I no sooner delete it, when it reappears back in the directory.

I'm at my wit's end. Does anyone know how to get rid of the MS codec and get the CCE HUFFYUV codec to play?

DDogg · 3rd October 2003, 13:22

Did you change the VIDC.YUY2 to equal huffyuv.dll in your drivers32 section of the registry?

r6d2 · 3rd October 2003, 14:05

Quote:

Originally posted by DDogg
Did you change the VIDC.YUY2 to equal huffyuv.dll in your drivers32 section of the registry?

Uh...? Just in case I checked and it is set to msyuv.dll! What am I missing?

slk001 · 3rd October 2003, 14:31

I wasn't aware that a .DLL required a registry entry. I will try changing this entry to my HUFFY codec.

auenf · 4th October 2003, 12:26

Quote:

Originally posted by slk001
I have even go so far as to try to delete the MSYUV.DLL codec, but it is like the "codec that won't die". I no sooner delete it, when it reappears back in the directory.

WFP

DDogg · 5th October 2003, 15:26

From the avisynth docs:http://www.avisynth.org/index.php?page=Convert

You can also edit the registry to force your system to use HuffYUV as the system YUY2 codec. Look under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 (the location will be different for Win9x). You should find a string named VIDC.YUY2; its value will vary according to your software and hardware configuration (for example, installation of an ATI All-In-Wonder Radeon set this to ATIVYUY.DLL). Change this to huffyuv.dll and HuffYUV will be called upon for YUY2 conversions. Encoding quality from an Avisynth script with TMPGEnc is much better with HuffYUV as the YUY2 decoder than with some other codecs; with ATIVYUY.DLL, for instance, subtle color variations became posterized. Acceptable results were possible with the ConvertToRGB filter, but this increased encoding time substantially as TMPGEnc needed to convert back to YUV as it encoded. Changing the system YUY2 codec to HuffYUV eliminates the expensive (and lossy) YUV->RGB->YUV conversion while maintaining the quality of the encoded output.

Use a convertToYuY2() at the end of scripts you are using with CCE. See CCE faq for more detail.

r6d2 · 5th October 2003, 18:32

From the HuffYUY official site:

Quote:

Huffyuv is intended to replace uncompressed YUV as a video capture format. It is fast enough to compress full-resolution CCIR 601 video (720 x 480 x 30fps) in real time as it's captured on my machine. Huffyuv also supports lossless compression of RGB data, so it can be used for the output of programs like VirtualDub.

So, it seems to be useful only for captures. Is there really a benefit using it on regular DVD conversions wih CCE?

DDogg · 5th October 2003, 23:38

Quote:

So, it seems to be useful only for captures.

As a byproduct, it can also replace the MSYUV.DLL, which IIRC is buggy, as the system YUY2 codec.

r6d2 · 6th October 2003, 01:30

Quote:

Originally posted by DDogg
As a byproduct, it can also replace the MSYUV.DLL, which IIRC is buggy, as the system YUY2 codec.

So be it. Installed it as default.

slk001 · 6th October 2003, 18:56

Changed the entry in the registry as suggested above, and CCE works okay now.

auenf: What do you mean by WPF?

DDogg · 7th October 2003, 03:19

I think that means Windows File Protection. The OS seeks to be self repairing and replace certain files it deems critical. It is a real PITA

Poutnik · 20th October 2005, 11:06

Quote:

Originally Posted by DDogg

As a byproduct, it can also replace the MSYUV.DLL, which IIRC is buggy, as the system YUY2 codec.

Should I understand a note above as this ? :
"It is adviced to replace msyuv.dll by huffyuv.dll in all VIDC.XXX items,
where msyuv.dll occurs" ?
In my Win98SE there 2 other formats, IMHO closely related to YUV2, associated with msyuv.dll.

Boulder · 23rd October 2005, 14:00

You should change only vidc.yuy2 because that's what CCE uses.

Poutnik · 24th October 2005, 16:09

Quote:

Originally Posted by Boulder

You should change only vidc.yuy2 because that's what CCE uses.

I do not use CCE ( neither exactly know what it is

).
I thought it was a general advice.

But I have realized already mentioned issue that
even my Win98SE restored VIDC.YUY2 settings in both places
(registry and system.ini) back to msyuv.dll.....

Boulder · 24th October 2005, 17:24

I think you have to delete/rename msyuv.dll in safe mode from the System folder to make sure it doesn't get back there.

HuffYUV probably cannot handle anything else but RGB and YUY2.

1st October 2003, 20:43	#1 \| Link
slk001 Registered User Join Date: Apr 2002 Posts: 399	CCE and the HUFFYUV Codec I have been fighting the CCE HUFFYUV codec issue for quite a while. I have the proper codec loaded onto my WIN2K Pro system, but it never seems to load (it's in the WINNT/SYSTEM32 directory). Instead, the MSYUV.DLL codec is being loaded. I have even go so far as to try to delete the MSYUV.DLL codec, but it is like the "codec that won't die". I no sooner delete it, when it reappears back in the directory. I'm at my wit's end. Does anyone know how to get rid of the MS codec and get the CCE HUFFYUV codec to play?

5th October 2003, 15:26	#6 \| Link
DDogg Retired, but still around Join Date: Oct 2001 Location: Lone Star Posts: 3,058	From the avisynth docs:http://www.avisynth.org/index.php?page=Convert You can also edit the registry to force your system to use HuffYUV as the system YUY2 codec. Look under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 (the location will be different for Win9x). You should find a string named VIDC.YUY2; its value will vary according to your software and hardware configuration (for example, installation of an ATI All-In-Wonder Radeon set this to ATIVYUY.DLL). Change this to huffyuv.dll and HuffYUV will be called upon for YUY2 conversions. Encoding quality from an Avisynth script with TMPGEnc is much better with HuffYUV as the YUY2 decoder than with some other codecs; with ATIVYUY.DLL, for instance, subtle color variations became posterized. Acceptable results were possible with the ConvertToRGB filter, but this increased encoding time substantially as TMPGEnc needed to convert back to YUV as it encoded. Changing the system YUY2 codec to HuffYUV eliminates the expensive (and lossy) YUV->RGB->YUV conversion while maintaining the quality of the encoded output. Use a convertToYuY2() at the end of scripts you are using with CCE. See CCE faq for more detail. Last edited by DDogg; 5th October 2003 at 15:33.

23rd October 2005, 14:00	#13 \| Link
Boulder Pig on the wing Join Date: Mar 2002 Location: Finland Posts: 5,843	You should change only vidc.yuy2 because that's what CCE uses. __________________ And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon...

24th October 2005, 17:24	#15 \| Link
Boulder Pig on the wing Join Date: Mar 2002 Location: Finland Posts: 5,843	I think you have to delete/rename msyuv.dll in safe mode from the System folder to make sure it doesn't get back there. HuffYUV probably cannot handle anything else but RGB and YUY2. __________________ And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon...

3rd October 2003, 13:22	#2 \| Link
DDogg Retired, but still around Join Date: Oct 2001 Location: Lone Star Posts: 3,058	Did you change the VIDC.YUY2 to equal huffyuv.dll in your drivers32 section of the registry?

3rd October 2003, 14:31	#4 \| Link
slk001 Registered User Join Date: Apr 2002 Posts: 399	I wasn't aware that a .DLL required a registry entry. I will try changing this entry to my HUFFY codec.

6th October 2003, 18:56	#10 \| Link
slk001 Registered User Join Date: Apr 2002 Posts: 399	Changed the entry in the registry as suggested above, and CCE works okay now. auenf: What do you mean by WPF?

7th October 2003, 03:19	#11 \| Link
DDogg Retired, but still around Join Date: Oct 2001 Location: Lone Star Posts: 3,058	I think that means Windows File Protection. The OS seeks to be self repairing and replace certain files it deems critical. It is a real PITA