Hiya, Ralf et al, >But nevertheless, there is work to do identifying/fixing the >non-compliant tools one by one. Which tools are known to be compliant? >Which have clearly identified problems with value-ranges? Which have an >unknown state?
It would indeed be good to keep track of such info --- perhaps the BUGS file is an appropriate place? I'll start a little table/chart later in the week if no one beats me to it. >After jpeg2yuv I measured no out-of-range values. But after yuvdenoise, I >did. Yuvdenoise seems to be the tool that broadens the value-range. When >I leave it out of the chain the clipping effect dissappears. So I expect a >problem there, too. Hmm... it seems like some people have noticed problems with yuvdenoise, and other people haven't. Could you (anyone) create a small YUV4MPEG2 stream (minimal frame count) which triggers the problems in yuvdenoise, and then post it somewhere on the web? Along with the version info for the copy of yuvdenoise you are using, the command-line, and the resulting output YUV4MPEG2 stream? I get the feeling that this might be the best way to nail down this problem. (Perhaps only one execution branch in yuvdenoise has a miscalculation.) -matt m. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
