audyovydeo
25th September 2009, 15:04
commit 496d79dfcb90066f0254e07d593471f2c885a153 r1271
Author: Jason Garrett-Glaser <darkshikari@gmail.com>
Date: Thu Sep 24 08:40:45 2009 -0700
Fix 10l in API change
frame_num was set to 1, not 0, for the first frame. This broke spec compliance.
Didn't actually seem to cause any problems though except for breaking decoding on Quicktime.
Am I to understand that after years of QuickTime bashing (
http://forum.doom9.org/archive/index.php/t-143680.html comes to mind, among other) it turns out that it was a (minor) x264 bug ?
Preliminary tests seem to give better QT playback, but I'm on my P4 machine, I'll have to wait until I get my C2D back.
cheers
audyovydeo
Author: Jason Garrett-Glaser <darkshikari@gmail.com>
Date: Thu Sep 24 08:40:45 2009 -0700
Fix 10l in API change
frame_num was set to 1, not 0, for the first frame. This broke spec compliance.
Didn't actually seem to cause any problems though except for breaking decoding on Quicktime.
Am I to understand that after years of QuickTime bashing (
http://forum.doom9.org/archive/index.php/t-143680.html comes to mind, among other) it turns out that it was a (minor) x264 bug ?
Preliminary tests seem to give better QT playback, but I'm on my P4 machine, I'll have to wait until I get my C2D back.
cheers
audyovydeo