Log in

View Full Version : errors in cce 2.5 when re-encoding. please look!!


jaay
26th March 2002, 15:27
firstly when i click the advanced tab next to multi-pass vbr i get the following msg: "could'nt find appropriate video codec for 'YUY2'" i dont know what this means!?! how can i rectify this error?? also when changing local bit rate settings (as in doom9's guide) i can get rid of the grey areas by increasing min bitrate but then when i hit 'fix' the grey comes back - why is this? are these errors just my cce? please help, thanx.

whosithis
9th May 2002, 13:21
If you're using Windows 2000 (and this fix may possibly work for others) you can edit your registry at this key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

and add a String Value there called "vidc.yuy2" with a value of "msyuv.dll".

I just had this problem. If you're like me you're using AviSynth to feed into CCE, but for some reason CCE wants to decode what is already a YUY2 uncompressed frame. It's looking for a codec to do this with. What the registry key above does is tell Windows to use the above DLL to decode YUY2 frames.

TRILIGHT
9th May 2002, 20:45
Is it changing to gray within the section you selected or outside of it? In order to keep the overall average you've chosen, if certain areas are raised really high, it will reduce other areas in order to keep your average. If these areas are just on the line, they could be lowered such that they become gray when they were green before. What I usually do it start by increasing my minimum global bitrate to 1000. Then I play with the global average to get rid of most of the gray areas (if there are a lot). Then, I step through and do any local areas. The entire time I do all of this, I am watching my total filesize so that I stay below the mark I don't want to go higher than. I haven't had a problem yet doing it this way.

Gorr
11th May 2002, 16:05
Well done whosith!
Been having the exact same problem

Thanks!

Gorr
11th May 2002, 16:12
One other thing.
On one machine I have a strange slider behavior of slider in frame search: when the slider is moved forward, the frame number gets prefixed with minus sign "-". Never seen anything like this on other machines.

Did anyone happen to have same error?

Thanks