<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - audio broken in 24Hz/24p since 3.11 (regression)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69675#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - audio broken in 24Hz/24p since 3.11 (regression)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69675">bug 69675</a> from <a class="email" href="mailto:pierre-bugzilla@ossman.eu" title="Pierre Ossman <pierre-bugzilla@ossman.eu>"> Pierre Ossman</a> <pre>(In reply to <a href="show_bug.cgi?id=69675#c1">comment #1</a>) > IIRC it was the XBMC people that wanted the ntsc variants in the first place > as their player defaults to sync to video exactly and would need to resample > sound at 24Hz because of this (blu-ray are 24/1.001). > Sure? The source material is 24 Hz, and wasn't the whole point of 24p to get away from NTSC conversions? TV shows might be a different matter though... > Assuming you can reproduce the issue just using mplayer playing a CD - then > I can't, maybe your receiver is just more fussy than my TV. > > Does it claim CEA compliance? > I would assume so. But it's not really something blingy enough to brag about on the box. There are specs here: <a href="http://eu.harmankardon.com/harman-kardon-product-detail-eu/avr_265.html">http://eu.harmankardon.com/harman-kardon-product-detail-eu/avr_265.html</a> > Of course your GPU is likely different to mine (HD4890) so I can't test like > for like properly. > > The old mode is the first one listed by xrandr - can't you just avoid the > ntsc ones rather than needing them to be removed? If I can, I don't know how. It is xbmc that's my use case, and it tends to pick that mode. Besides, we shouldn't have modes listed that don't work properly. :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>