On Wed, Feb 04, 2015 at 09:13:57PM +0100, Timo Rothenpieler wrote: > > Could I get a proper review on this? I'd like to believe that we have a > > consensus that, independent of whether we think there's merit in this > > compensation logic, it shouldn't exist in a single encoder, out of > > step with all the other encoders in ffmpeg. > > > > Thanks, > > It looks good to merge for me,
applied thanks > i haven't had time to test this issue > myself yet, but it definitely should behave like all other encoders do. > If Nvidia ever changes the behaviour of this(So it would suddenly work > as it should in a new driver release), an option do disable the > compensation would be nice to have, so users aren't stuck with the then > broken compensation. > > > Timo > > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is what and why we do it that matters, not just one of them.
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
