Solved Help on 1080p24 support on Apple TV1
#16
LB06 Wrote:Try to remove the "1920x1080" and "1920x1080_60" modes

Even if I dont mention the modes xbmc gets the list of modes from xrandr and decides to pick the 120Hz every single time. This is kind of irritating now, the only way to truly get 24Hz playback is if I request 1920x1080_24 in the mode and disable "Adjust display refresh rate to match video".
#17
Hi Bharath,

Either use 1920x1080_24 as a ModeLine (downside: whole UI is @24Hz), or perhaps you can craft a custom EDID binary that will exclude 120Hz as a supported mode.

Can you also verify this 120Hz Mode is not being triggered by your TV (i.e. it is receiving a 24Hz signal and displaying at 120Hz).
#18
Sam.Nazarko Wrote:Hi Bharath,

Either use 1920x1080_24 as a ModeLine (downside: whole UI is @24Hz), or perhaps you can craft a custom EDID binary that will exclude 120Hz as a supported mode.

Can you also verify this 120Hz Mode is not being triggered by your TV (i.e. it is receiving a 24Hz signal and displaying at 120Hz).
Yeah I also considered that, but the logs show that it's really 120Hz that is being outputted by the box. So it's not just internal 5:5 pulldown or some stupid frame interpolation within the TV.

Running everything @24p is not really an adequate solution, as there's also stuff that has to be outputted at 50 or 60Hz (PAL/NTSC caps). It really sounds like a bug in the driver.
#19
The problem is that I have a mix of both 24Hz and 60Hz content in my library. Some of the recorded sports that I have are 60p and the TV shows and Movies are 24p. If I enable just 24Hz the 60p recordings dont play. Here is some of the output from xbmc.log

xbmc.log: http://pastebin.com/aDuEv2Mr

Here is the list of video modes that xbmc detects.
Code:
21:09:19 T:3045476080 M:200359936    INFO: Available videomodes (xrandr):
21:09:19 T:3045476080 M:200298496    INFO: Number of connected outputs: 1
21:09:19 T:3045476080 M:200298496    INFO: Output 'default' has 11 modes
21:09:19 T:3045476080 M:200298496    INFO: ID:0x15c Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x15d Name:1920x1080 Refresh:120.000000 Width:1920 Height:1080
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x15e Name:1920x1080 Refresh:24.000000 Width:1920 Height:1080
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x15f Name:1440x480 Refresh:120.000000 Width:1440 Height:480
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x160 Name:1280x1024 Refresh:60.000000 Width:1280 Height:1024
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x161 Name:1280x720 Refresh:60.000000 Width:1280 Height:720
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x162 Name:1024x768 Refresh:60.000000 Width:1024 Height:768
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x163 Name:800x600 Refresh:60.000000 Width:800 Height:600
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x164 Name:720x480 Refresh:120.000000 Width:720 Height:480
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x165 Name:720x480 Refresh:60.000000 Width:720 Height:480
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000
21:09:19 T:3045476080 M:200298496    INFO: ID:0x166 Name:640x480 Refresh:60.000000 Width:640 Height:480
21:09:19 T:3045476080 M:200298496    INFO: Pixel Ratio: 1.000000

Here is the log where it sets the UI to 1920x1080 @ 60Hz
Code:
16:09:21 T:3045476080 M:198995968    INFO: XRANDR: /usr/local/lib/xbmc/xbmc-xrandr --output default --mode 0x15c

Here is the log where it decides to change the resolution to 1920x1080 @ 120Hz instead of 1920x1080 @ 24Hz

Code:
16:09:38 T:2848623504 M:126603264  NOTICE:  fps: 23.976024, pwidth: 1280, pheight: 720, dwidth: 1280, dheight: 720
16:09:38 T:2848623504 M:126603264   DEBUG: OutputPicture - change configuration. 1280x720. framerate: 23.98. format: YUY2
16:09:38 T:2848623504 M:126603264  NOTICE: Display resolution ADJUST : default: 1920x1080 @ 120.00Hz (14) (weight: 0.001)

The relevant log where it is calling xrandr to set the mode to 1920x1080 @ 120Hz
Code:
16:09:40 T:3045476080 M: 89706496    INFO: XRANDR: /usr/local/lib/xbmc/xbmc-xrandr --output default --mode 0x15d

This is where it is switching back to 1920x1080 @ 60Hz for the UI once I stopped the playback.

Code:
16:10:03 T:2928208784 M:141520896  NOTICE: CDVDPlayer::OnExit() deleting demuxer
16:10:03 T:2928208784 M:141606912  NOTICE: CDVDPlayer::OnExit() deleting input stream
16:10:03 T:2928208784 M:141606912   DEBUG: CAnnouncementManager - Announcement: OnStop from xbmc
16:10:03 T:2928208784 M:141606912   DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnStop
16:10:03 T:2928208784 M:141606912   DEBUG: Thread CDVDPlayer 2928208784 terminating
16:10:03 T:3045476080 M:141606912  NOTICE: DVDPlayer: finished waiting
16:10:03 T:3045476080 M:141606912   DEBUG: LinuxRendererGL: Cleaning up GL resources
16:10:03 T:3045476080 M:147206144   DEBUG: CGUIWindowManager::PreviousWindow: Deactivate
16:10:03 T:3045476080 M:147247104   DEBUG: ------ Window Deinit (VideoFullScreen.xml) ------
16:10:03 T:3045476080 M:147247104    INFO: XRANDR: /usr/local/lib/xbmc/xbmc-xrandr --output default --mode 0x15c

I dont believe I have to use custom EDID, I would just disable EDID information and manually have to enter all the required modelines.

My inkling here is that for some reason xbmc is picking the 120Hz incorrectly, on my TV 120Hz is firstly a mode for interlaced content and not progressive.

edit:
I would move away from HDMI audio, but then there is no way to connect my gaming consoles. Unfortunately I have the version one of xbox 360 which never had HDMI output Sad. My component inputs are all taken.
#20
Component switch?
#21
Sam.Nazarko Wrote:Component switch?

Trying to avoid it if possible.
#22
LB06 Wrote:It really sounds like a bug in the driver.

Could it be a bug in xbmc? Isnt the decision to which mode to be selected is taken by xbmc rather than the driver?
#23
Likely the driver, it was compiled in 09/2007. Nouveau doesn't support @24Hz otherwise I'd recommend that -- future nv modules break HDMI audio as you know.

Very outside the box, but if we could xrandr refresh rates:

http://forum.xbmc.org/showthread.php?tid=42530

you could dynamically change refresh rate by getting Media Info.
#24
Easy to find out. Backup and upgrade the driver to 280. Still sounds more like a bug in the driver though. There's some negotiating between XBMC and the hardware going on, but the hardware is exposed to applications like XBMC through the drivers. So it could be either one, or maybe a combination, but considering the fact that only you are suffering from this problem, I'd say drivers are the most likely explanation. Isn't there some ATV1 topic where you can ask? I'm sure you're not the only one with an ATV1..
#25
@LB06: he's hardly the only one. There are around 5k people running this distro daily, and I bundled 100.14.19 because it's last ver with HDMI sound. Updating the driver will fix this, but as OP said, he does not want to lose HDMI audio.
#26
Sam.Nazarko Wrote:@LB06: he's hardly the only one. There are around 5k people running this distro daily, and I bundled 100.14.19 because it's last ver with HDMI sound. Updating the driver will fix this, but as OP said, he does not want to lose HDMI audio.
Yeah ok, so it's the driver then. That was my point really Smile. bharath23 was asking if it was an XBMC bug. At this point that seems highly unlikely, given that with a driver update the problem can be resolved.
#27
LB06 Wrote:Yeah ok, so it's the driver then. That was my point really Smile. bharath23 was asking if it was an XBMC bug. At this point that seems highly unlikely, given that with a driver update the problem can be resolved.

The reason why I wondered if the bug was with XBMC is as follows, sorry if I am wrong about it.

On start up XBMC gets the list of mode and their capabilities using xrandr. When it has to change to different mode XBMC is the one that selects the mode it wants X to switch to using xrandr again. If you look at the debug logs it is obviously picking up an incorrect mode.
#28
Sam.Nazarko Wrote:Likely the driver, it was compiled in 09/2007. Nouveau doesn't support @24Hz otherwise I'd recommend that -- future nv modules break HDMI audio as you know.

Very outside the box, but if we could xrandr refresh rates:

http://forum.xbmc.org/showthread.php?tid=42530

you could dynamically change refresh rate by getting Media Info.

It is out of the box, I would have to try to get the fps and if it matches 24Hz call xrandr.

LB06 Wrote:Easy to find out. Backup and upgrade the driver to 280. Still sounds more like a bug in the driver though. There's some negotiating between XBMC and the hardware going on, but the hardware is exposed to applications like XBMC through the drivers. So it could be either one, or maybe a combination, but considering the fact that only you are suffering from this problem, I'd say drivers are the most likely explanation. Isn't there some ATV1 topic where you can ask? I'm sure you're not the only one with an ATV1..

I can try this out and let you know.

I wish I could do it over the week I only have time over the weekend to devote to significant chunk of my time for this, but unfortunately I am out of town till the end of the month to be able to try this over the weekend.
#29
I upgraded the NVIDIA driver to 280.13 and 24Hz playback works without any issues. Here are X -logverbose 5 outputs for both 100.14.19 and 280.13 drivers

100.14.19: http://pastebin.com/VnkC2LdB
280.13: http://pastebin.com/r4hQ5KkP

Looking at the difference in the logs the only difference that I notice is that the older 100.14.19 mode detects the additional 120Hz interlaced mode. This mode is not discovered by the 280.13 version. As a result the modes added to the list of available video modes are different. I am still not able to understand how the availability of 120Hz interlaced mode causes issue.
#30
I bumped the driver to 100.14.23, still no luck with 24Hz support. The only good thing is that I havent lost HDMI audio.

Logout Mark Read Team Forum Stats Members Help
Help on 1080p24 support on Apple TV10