[Koying]

Surely the Nvidia graphics hardware inside the chipset and GeForce drivers most be capable out 23.976p or? And if so could that mean the limitation is only in Android or the firmware?

Koying would probably know the answer.

Not a big specialist, either. If I understand the issue, it gets down to fractional HDMI clocks in kernel.
Surely nothing to do with GPU/VPU, though. It's a pure HDMI/display thing.

[wrxtasy]

Ah yes. And to confuse those reading some more....

23.976 fps is not a fraction of a frame, there are only ever whole frames of video. It is 24 frames every 1.001001... seconds.

[wesk05]

It is complex, the hardware should have support for the required pixel clock (HDMI PLL registers), the kernel should have support for the appropriate modelines for resolution, the audio clock has to sync (N/CTS, MCLCK) etc..

[Koying]

23.976 fps is not a fraction of a frame, there are only ever whole frames of video. It is 24 frames every 1.001001... seconds.

It's 24 * 1000 / 1001 actually. One of the shitty legacy of analog TV... ( http://en.wikipedia.org/wiki/24p#23.976p )

[sm_x]

Does anyone know what the default mapping for the controller is? In terms of controls in KODI. Does any one a have a good keyboard.xml file that takes advantage of all the buttons in the controller?

[Kris404]

Does anyone know what the default mapping for the controller is? In terms of controls in KODI. Does any one a have a good keyboard.xml file that takes advantage of all the buttons in the controller?

No idea how they're mapped. Koying, can you comment?

For 'NVIDIA STB' Harmony device profile, these are the buttons that are unassigned:

DVR, Guide, Info
Ch (Channel +), Pg (Channel -)
Record, E, .-




For the record, here are all available commands:

Code:

A
B
Back
Brake
DirectionDown
DirectionLeft
DirectionRight
DirectionUp
FastForward
Gas
Language
LeftBumper
LeftTrigger
Menu
Mute
OK
Pause
Play
PowerOff
PowerOn
PowerToggle
Return
Rewind
RightBumper
RightTrigger
Shield
Stop
VolumeDown
VolumeUp
X
Y
0, 1, 2, 3, 4, 5, 6, 7, 8, 9

[Koying]

Controller buttons are mapped exactly the same way on all of them.
Android has standard button names, so any controller will work exactly the same.

[Tinwarble]

For the record, here are all available commands:

Code:

A
B
Back
Brake
DirectionDown
DirectionLeft
DirectionRight
DirectionUp
FastForward
Gas
Language
LeftBumper
LeftTrigger
Menu
Mute
OK
Pause
Play
PowerOff
PowerOn
PowerToggle
Return
Rewind
RightBumper
RightTrigger
Shield
Stop
VolumeDown
VolumeUp
X
Y
0, 1, 2, 3, 4, 5, 6, 7, 8, 9

And at the least A, B, Gas, Brake, X, Y don't work or I couldn't get then to work with the unassigned buttons.

[Kris404]

And at the least A, B, Gas, Brake, X, Y don't work or I couldn't get then to work with the unassigned buttons.

What are Kodi mappings for those 41 IR commands?

[Tinwarble]

As far as I can tell, nothing for those I mentioned.

I'm using Keymap Editor, and those inputs don't register at all. The corresponding buttons on the remote do register, but not when you add them to the remote.

[Koying]

Not sure what's the issue here (if there's one).

Those are the mappings, and they work on every single droid controller I use, including the shield one: https://github.com/xbmc/xbmc/blob/master...xml.sample

[Tinwarble]

@Koying, it's not a matter of mapping, it appears that some of the commands that you can assign to the remote buttons are wrong. If that's correct then it needs to be fixed on logitechs' side.

[Koying]

Ah, it's in the context of Harmony, right?
I have the bluetooth-enabled hub model, so I just use a generic bluetooth keyboard profile, personally...

A debug log should tell what Kodi receives vs. what Harmony sends.

[RockerC]

Surely the Nvidia graphics hardware inside the chipset and GeForce drivers most be capable out 23.976p or? And if so could that mean the limitation is only in Android or the firmware?

Koying would probably know the answer.

Not a big specialist, either. If I understand the issue, it gets down to fractional HDMI clocks in kernel.
Surely nothing to do with GPU/VPU, though. It's a pure HDMI/display thing.

Maybe this is the perfect timed opportunity to try to have a manufacturer with some pull like Nvidia to effectively change those currently inherit limitations in the Android TV platform.

Checkout this blog post from Nvidia http://blogs.nvidia.com/blog/2015/05/28/...ving-room/

Relevant quotes that gives motivation to Nvidia and Google: "This isn’t the first time that tech giants have tried to reinvent TV. But it is the first time all the pieces have been in place." and "The stakes are enormous. The new generation of smart entertainment apps promises to reshape some of the world’s biggest — and most influential — industries. The worldwide pay TV business is worth $257 billion. The TV advertising business is worth $170 billion. Console games generate $26 billion in revenue. And that’s just the start."

So perhaps it is now really possible to for the Kodi team to inform about these use cases and target market to Nvidia for implementing perfect video and audio playback on Android TV?

Since Nvidia as the hardware manufacturer in this case actually seems to be listening to its customers/developers wants and needs, including video playback specifics, and with Nvidia probably having a very close working relationship with Google regarding the upstream Android TV platform. If the Kodi team could manage to convince the right people at Nvidia that these type of features will be commonly wanted in a platform like Android TV then just maybe they could in turn have a real impact on the actual Android TV developers at Google in order for them to finally make such core changes to the kernel, APIs, drivers, etc.. This could be a win-win situation for all involved, Nvidia could extend their market as the "perfect" media player device, Google gets an improved Android TV platform, and Kodi users in the end gets a better experience on Android all around in the future.

I think that these changes will happen in Android sooner or later with or without the Kodi team and Nvidia, but it would be great if they could make it happen sooner rather than later.

[lartomar2002]

Not sure what's the issue here (if there's one).

Those are the mappings, and they work on every single droid controller I use, including the shield one: https://github.com/xbmc/xbmc/blob/master...xml.sample

Damn that would be one hell of a big remote to handle all those buttons. ;D