|
A user noticed that they "suddenly got no video when streaming to red5"
http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=7&t=686 "Builds starting from a85b4a5'ish all default to yuv444p here, it used to be yuv420p." Anybody know if this is expected? Just wondering. Thanks! -roger- _______________________________________________ ffmpeg-user mailing list [hidden email] http://ffmpeg.org/mailman/listinfo/ffmpeg-user |
|
Roger Pack <rogerdpack2 <at> gmail.com> writes:
> A user noticed that they "suddenly got no video when streaming to red5" > http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=7&t=686 > "Builds starting from a85b4a5'ish all default to yuv444p here, it used > to be yuv420p." I considered it a bug that ffmpeg chose yuv420p if the input pixel format was bgr24 and the encoder supports yuv444. I agree that in the case of x264 this could be seen as unexpected, but only because the commercial h264 decoders typically do not support decoding anything except yuv420p. Please remember how many reports "If I encode my rgb input to mpeg2/mpeg4 the output quality is bad no matter the chosen bitrate!" we only received this week! A workaround is to add a special x264 encoder for yuv != yuv420p (as it was done for rgb), if you look at dd974c1b you should be able to produce a patch if you think it is a good idea. Carl Eugen _______________________________________________ ffmpeg-user mailing list [hidden email] http://ffmpeg.org/mailman/listinfo/ffmpeg-user |
|
>> A user noticed that they "suddenly got no video when streaming to red5"
>> http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=7&t=686 >> "Builds starting from a85b4a5'ish all default to yuv444p here, it used >> to be yuv420p." > > I considered it a bug that ffmpeg chose yuv420p if the input > pixel format was bgr24 and the encoder supports yuv444. > > I agree that in the case of x264 this could be seen as > unexpected, but only because the commercial h264 decoders > typically do not support decoding anything except yuv420p. > Please remember how many reports "If I encode my rgb input > to mpeg2/mpeg4 the output quality is bad no matter the > chosen bitrate!" we only received this week! Ok then as long as it's expected. Thanks! -r _______________________________________________ ffmpeg-user mailing list [hidden email] http://ffmpeg.org/mailman/listinfo/ffmpeg-user |
|
>> I considered it a bug that ffmpeg chose yuv420p if the input
>> pixel format was bgr24 and the encoder supports yuv444. >> >> I agree that in the case of x264 this could be seen as >> unexpected, but only because the commercial h264 decoders >> typically do not support decoding anything except yuv420p. >> Please remember how many reports "If I encode my rgb input >> to mpeg2/mpeg4 the output quality is bad no matter the >> chosen bitrate!" we only received this week! > > Ok then as long as it's expected. > Thanks! And just received my second bug report in this regard. I suppose we can't all win, can we :) -roger- _______________________________________________ ffmpeg-user mailing list [hidden email] http://ffmpeg.org/mailman/listinfo/ffmpeg-user |
|
Roger Pack <rogerdpack2 <at> gmail.com> writes:
> And just received my second bug report in this regard. You did not answer my suggestion on how this can be solved. Carl Eugen _______________________________________________ ffmpeg-user mailing list [hidden email] http://ffmpeg.org/mailman/listinfo/ffmpeg-user |
| Powered by Nabble | Edit this page |
