Thanks mglae. At least I know it's not just me now.
For a while I've had videos with an AAC encoded soundtrack not playing anymore, and I'm not seeing anything weird in my logs. So I'm looking for some pointers. I've just upgraded to the latest 8.1.1 beta to be sure there's nothing that has been fixed in the meantime.
I have checked the audio settings in Kodi and there's no checkbox for AAC passthrough as far as I can see; nor does my receiver support it.
Mediainfo output for the audio channel of one of the offending files:Code
- ID : 2
- Format : AAC
- Format/Info : Advanced Audio Codec
- Format profile : HE-AAC / LC
- Codec ID : A_AAC
- Duration : 23 min 29 s
- Bit rate : 64.0 kb/s
- Channel(s) : 2 channels
- Channel positions : Front: L R
- Sampling rate : 48.0 kHz / 24.0 kHz
- Frame rate : 23.438 FPS (1024 spf)
- Compression mode : Lossy
- Stream size : 10.8 MiB (3%)
- Default : Yes
- Forced : No
Kodi log shows the following:Code
- 18:49:24.372 T:140307588970240 INFO: ffmpeg[7F9BE7FFF700]: Stream #0:1: Audio: aac (HE-AAC), 48000 Hz, stereo, fltp (default)
- 18:49:41.501 T:140307547100928 INFO: ffmpeg[7F9BE5811700]: Stream #0:1: Audio: aac (HE-AAC), 48000 Hz, stereo, fltp (default)
- 18:49:41.515 T:140307429615360 DEBUG: ffmpeg[7F9BDE806700]: [aac] element type mismatch 1 != 0
- 18:49:42.009 T:140307429615360 DEBUG: ffmpeg[7F9BDE806700]: [aac] element type mismatch 1 != 0
- 18:49:42.019 T:140307429615360 DEBUG: ffmpeg[7F9BDE806700]: [aac] element type mismatch 1 != 0
Updating to the beta fixed it for me (CEC was indeed broken on the last alphas). Newer CEC library etc.
It looks like kzaq's Amlogic build.
Does LibreELEC support anything non x86 with their Chromium builds? I thought not.
Thanks, looking forward to it!
Kore doesn't use CEC, so it's a workaround. So how does it fix that for you?
On 7.0.x CEC worked fine for me, but since i upgraded to 7.90 alpha 10, it will break whenever the screensaver kicks in (or the backlight dims due to prolonged inactivity). I can force this behaviour by switching video inputs on the TV.
Behaviour is erratic - it just happened that CEC stopped working again, my TV switched off (as I configured Kodi to do when inactive for a while), and when it came back from standby, CEC worked again; then a few minutes later, the screen switched off again, I turn it on again, no response when I use the remote.
My log (debugging enabled) can be found here.
If there's anything I need to test, let me know.
- Sony KDL52-NX800
- Gigabyte Brix GB-BXA8-5545 with Pulse-Eight CEC adapter
- Yamaha RX-V1071 receiver
If you need anything else, let me know. I looked through the log myself but I don't see any messages relating to a CEC process crashing or anything...
If it helps, this is how my CEC adapter shows up in dmesg:
Lsusb shows it, but anonymously:
From what I can see yours doesn't seem to be showing up.
Did you try different USB ports?
Get another Pi and use it as a Pi-Hole, I'd say?
Also, you could just have your router block any WAN requests from your LibreELEC setup(s). That's what I'd do for smart TV's etc.
It works just fine if you use the Chromium add-on and enable widevine in the settings. All configurable in the add-on's settings.
Thanks guys, going to test #1, lrusak, appreciate that as well, but I hope M4tt0's #1 works
I'll let you know.
My LibreELEC setups are set to an AZERTY keyboard layout, but the Chromium add-on does not pick up on this. Is there a way to have Chromium honour the keyboard layout used in Kodi?
It's been a while since I logged into the system directly (I think the SSH client's locale etc. override the server's when you connect over SSH?), but I recall it being AZERTY on the command line as well.
I read your OE 6.0.1 page, it makes me want to go out and pick up a BCM970015 card to replace my 970012... Even though I don't use my AppleTV anymore. Great work chewitt!
Happy to see you guys are getting along with Sam as well, that seemed different with OE and he does come across as a nice guy.
So that means the add-on repo works?
I saw some info about devs possibly moving things around some more before a beta release, which is why I'm still holding out.