Posts by triminmotion

Kodi seems to like the modeline you provided. I'm still getting 23.97610, but skipping is gone and a/v sync values are stable.

And yes, I'm using different mode lines for 23.976 and 24.

Thanks for the help!

OK, got this resolved.

Looks like there's been some syntax change in these keymap files.

Every occurrence of the word "joystick" in the file needs to be replaced with "customcontroller". A quick search and replace, then a restart of Kodi, fixes this.

After upgrading to 8.0.1 I've started to see frame skipping at 1920x1080@24p (23.976fps) about a couple of times a minute or so on an Intel GMA 950.

I've been using a custom xorg.conf for years and have had perfect spot on 1920x1080@24p, prior to upgrading.

I've been reading that there's a bug on some Intel GPUs that keeps them from doing 23.976fps, and they're stuck at 24fps, which could cause similar symptoms, but that doesn't explain why it's been working perfectly with 7.0.3 and prior versions of LE and previous versions of OE.

Here are copies of my relevant modeline in xorg.conf and output of my kodi-xrandr. Interestingly, there's an auto-detected 23.97608 mode, but that one threw in some skipping every once in a while even in older versions. That's why I manually created the 1920x1080@24p mode. That one clocks in at 23.97610hz. One wouldn't think that those 0.00002hz would make a difference, but in previous versions, that was the difference between almost no skipped frames and absolutely no skipped frames.

Modeline "1920x1080@24p" 74.230 1920 2560 2604 2752 1080 1084 1089 1125 +hsync +vsync

<screen id="0" minimum_w="8" minimum_h="8" current_w="1920" current_h="1080" maximum_w="32767" maximum_h="32767">
<output name="DVI1" connected="true" w="1920" h="1080" x="0" y="0" crtc="0" wmm="1620" hmm="910">
<mode id="0x47" name="1920x1080@24p" w="1920" h="1080" hz="23.97610" current="true" preferred="true"/>
<mode id="0x48" name="1920x1080@50p" w="1920" h="1080" hz="50.00000" current="false" preferred="false"/>
<mode id="0x49" name="[email protected]" w="1920" h="1080" hz="59.94020" current="false" preferred="false"/>
<mode id="0x4a" name="1920x1080" w="1920" h="1080" hz="30.00000" current="false" preferred="false"/>
<mode id="0x4b" name="1920x1080" w="1920" h="1080" hz="24.00000" current="false" preferred="false"/>
<mode id="0x8f" name="1920x1080" w="1920" h="1080" hz="23.97610" current="false" preferred="false"/>
<mode id="0x4c" name="1920x1080" w="1920" h="1080" hz="29.97010" current="false" preferred="false"/>
<mode id="0x4d" name="1920x1080" w="1920" h="1080" hz="23.97608" current="false" preferred="false"/>
</output>
<output name="TV1" connected="false">
</output>
<output name="VGA1" connected="false">
</output>
<output name="VIRTUAL1" connected="false">
</output>
</screen>

Thanks for any help!

Hi everyone,

In 8.0.1, Kodi seems to be ignoring my .kodi/userdata/keymaps/joystick.AppleRemote.xml file.

This is probably more of a straight Kodi question than a LibreElec question... but does anyone know how to get this keymap file working again? Does it need to be renamed? Moved someplace new?

Thanks!

An old bug that was resolved for Mac Mini's, and potentially other older Mac platforms is back. I'm experiencing it in 8.0.1.

The bug is present on Macs that use the IR device ID 05ac:8240 for atvclient. The old thread here describes the issue and the fix: OpenELEC Mediacenter - OpenELEC Forum - Apple Mac Mini and Apple Remote not working (1/3)

I've fixed the problem for myself by recompiling atvclient and changing 0x82 to 0x83 in line 857. The complete fix as posted by the OP in the above thread involved figuring out whether the user's Mac required 0x82 and 0x83, and assigning the proper value to a variable that's used in line 857, rather than a fixed value.

This problem wasn't present in LibreElec 7.0.3, and was eliminated from OpenElec about 3 years ago. I have a feeling that recent upgrades to atvclient in LibreElec pulled in an unpatched version of atvclient, resulting in the problem resurfacing, but that's just a theory.

In either case, would be great to get this fix back into LibreElec officially. Please let me know if anyone needs more info.

Wanted to send an update on this.

I've temporarily (?) fixed this by taking a hint from the OpenElec thread referenced above that we worked on 3 years ago.

I have the 05ac:8240 IR receiver. In order to fix the problem, just like in the OpenElec thread, I changed line 857 in atvclient.cpp to 0x83 instead of 0x82, recompiled, and voila, it works. atvclient loads up perfectly, doesn't get stuck in the Got nuffing CPU hog loop, and passes commands to Kodi perfectly.

It doesn't look like the 0x83 fix ever made it into Evinyatar's Git repository, even 3 years ago, so makes me wonder how all the updates over that time have managed to work...

But it would be nice to get this nailed down so people with the 05ac:8240's don't need to use a custom one-off atvclient.

Let me know how I can help.

I'm having a similar problem with older Mac Mini

Just upgraded to 8.0.1 from 7.0.2. In 7.0.2 atvcilent worked perfectly, and perfectly for years with Openelec.

In 8.0.1, atvclient loads at startup but pushes one of my cores to 100% and doesn't respond. When I kill it and restart it manually from shell, it again pegs a core at 100%, and doesn't show any commands received. With -d I get a loop of Got nuffing: -5.

dmesg: cTci
journalctl -a: KPVK
lsmod: VPaJ

Chewitt, you, I, and a whole bunch of other people went through a similar exercise a few years ago with OpenElec. Reading my post from back then, the symptoms seem identical. See here: OpenELEC Mediacenter - OpenELEC Forum - Apple Mac Mini and Apple Remote not working (3/3)

I tried an older atvclient binary from a previous version and it loads OK and reads the remote key presses fine. It just doesn't communicate them to Kodi.

I've been looking at the changes you made in GitHub and can't really see why it wouldn't load up right compared to the old version. Seems like the only thing you changed is how commands are sent to Kodi. But I"m no programmer. Something weird is clearly happening since atvclient won't even start up stable.

Thanks for helping.