And now we can just hope that intel devlopers will find the cause of this and give us a proper fix.
They weren't able to before the massive layoffs across the company. One would think that they are now even less capable.
I wouldn't waste time interacting with Intel to try to solve this, as they couldn't even understand the concept that using only one AV receiver they will be able to reproduce the problem.
Is it then futile to try to achieve the goal of true Dolby Digital passthrough from a media player? If it is possible, kindly suggest a solution.
Believe it or not... the (lowly) latest FireTV 4K Stick running Android Kodi is capable of DV playback AND HD Audio passthru.
I'm not a big fan of low power android devices, but one can call it a better "solution" than any PC could ever dream to be.
CE does not use 12-bit for 4K/24. Intel does.
Oh well. Intel could at least point us which AVR it used for testing (if any). At the very least it would serve as a starting point for us to begin bothering Denon/Marantz about it.
I'm not convinced that this is an Intel issue. Looks to me that those affected AVRs (Denon?) are all using the same chipset which has some issue with 4K 12-bit modes.
It works correctly with some ARM box (Coreelec) in the same AVR. So what gives?
That fact and the long Intel tradition of having those types of issues make it very difficult rulling the possibility out.
My guess: Intel not being able to reproduce the issue is down to method, not knowing what to look for or simply not understanding the problem.
Jeez... the Intel guy can't reproduce the issue. How come.
Maybe it's a HDMI handshake thing that only happens with AVRs? Oh well, at least we have the script.
Thinking about it: How the Intel guy expects to test HD audio passtru without an AVR?
SD card issues appear to be resolved
Gave it a shot just for kicks and indeed the boot freeze is gone now.
Unfortunately HD audio pass-thru isn't working... and there is a lot of other minor issues (strange slowdowns, font rendering breaks after some use etc.). Maybe related to the breakage you mentioned... maybe not.
What do you mean? To the Internet?
If the gateway on eth0.1 them it will be the default route.
Mind if I ask you why are you using LibreElec as a router? It doesn't make a lot of sense as far network security and performance are concerned. Also, LibreElec raison d'être is it being purpose built to do media play stuff only. If you need more than that maybe other Linux distro will serve you better?
Any update on playing 4k60 files?
I was blissfully unaware that 4k60 HDR isn't working yet. I don't really need it... but now that I know it doesn't work I miss it. Heh.
I fiddled a bit in the configurations and different from RaspPIs there is nothing about HDMI SEC on input.
I'm willing to use even Yatse to control Kodi before buying something like the Pulse-eight CEC adapter, I just want to be sure it isn't just a matter of installing some program or addon.
Thanks!
Not running at the native framerate (23.976) means you won't be able to properly bit stream the audio; it will get decoded and passed along as PCM/LPCM
Yeah, that's what I thought would happen... but no. The AV Receiver still receives passthru audio as Dolby HD, undecoded as it should. It works even at 60hz as I latter discovered.
The only downside I'm having is that the Kodi interface must also be on 4k@24hz as the player won't use 24hz even if the res@refresh is whitelisted.
I wish I could change how the player chooses resolution/refresh output for a given resolution/refresh input. It seems that if isn't a perfect match it just gives up and use what the interface is using.
The only way I've gotten HD audio (TrueHD/DTS-HD/MA) to reliably stream without dropouts is to separate video & audio signals; This means you cannot have the AVR connected to your display ( otherwise libreelc will just 'clone' the signal out, causing the same issue) , and have to utilize both HDMI outs (one going directly to your display, the other going directly to your audio processor).
Yeah. I'm having the same issue with my Beelink EQ12... but just with TrueHD (not many DTSHD-MA 4k nowadays), and only on [email protected] videos. Seems to be a unsolved bug.
Strangely enough, using 4k@24Hz seems to "solve" the audio dropout problem. I'm still testing to be fully sure of it and understand the implications, if any.
But one can hope to just use one fast x86_64 device for all media.
My thoughts exactly. I'm pretty fed up with sluggish ARM boxes.
Just did a test run of you build on a just arrived Beelink N100 box (the DDR5 flavor one). So far, everything seems to work. Thanks!
The only way I've gotten HD audio (TrueHD/DTS-HD/MA) to reliably stream without dropouts is to separate video & audio signals; This means you cannot have the AVR connected to your display ( otherwise libreelc will just 'clone' the signal out, causing the same issue) , and have to utilize both HDMI outs (one going directly to your display, the other going directly to your audio processor).
Thinking about your issue... can't you use some kernel boot params in syslinux.cfg to force video output separated from audio (and avoid cloning) and thus maintain de video connected to the AVR?
I didn't test it on my current setup (I don't have 2 HDMIs) so I really don't know if it would work. Here is where I got the idea:
The only way I've gotten HD audio (TrueHD/DTS-HD/MA) to reliably stream without dropouts is to separate video & audio signals;
Thanks for replying. Even though your issue isn't too encouraging I guess I'll take a shot at the DDR5 version of the box.
I was also considering the alternatives (even Amlogic boxes) but I guess nothing beats the flexibility, convenience and power of a minipc. If everything goes wrong I can always use it as a router, heh.
Thought I'd report in that using a Beelink n100-based mini PC and the latest build posted in this thread I am getting proper HDR10/bt.2020 triggering on my setup: Pioneer AVR to LG C1 TV. It's looking great!
I've abandoned running video through my AVR as it had a lot of trouble 'locking on' to video mode changes / audio format changes (as well as intel's high resolution audio dropouts); luckily my device has dual HDMI outs.
I was thinking about getting a Beelink N100 myself due to the working BT.2020 triggering... but this HD audio bit got me worried. Isn't HD audio passthu working?
I have also been using the Beelink Mini S12 Pro with 16GB RAM and the 12th Gen N100 processor with no issues. They also seem to work well with the Wechip G20S and G40 remotes.
You can find both of these mini PCs on Amazon for less than the price of an Nvidia Shield Pro.
Indeed a very attractive alternative.
Does the Beelink S12 Pro you mentioned has any kind of issues with HDR switching, framerate switching, or any BT 2020 color space weirdness? I'm about to pull the trigger but just wanted to be sure about the capabilities of the box.
Reverting back to the factory image seems to be the pre-requisite.
Well, it makes sense, but I reverted the firmware to the original 2018 one (Android 6) and no... unfortunately that is not it.
While on the ¨"Community Edition¨¨¨" ROM. I just imaged the 1GB working SD one into a 16GB fast SD and it worked in the first time it booted. Having just booted, some ¨"storage device removed" notification appeared on the Kodi GUI and in the next boot it was again at the same non booting state.
The problem doesn't seem related to the ROM.
Just wanted to check in and say that I am one of those other users. I have exactly the same device, the same firmware (which I suspect is the culprit) and the same issue as the OP.
+1
Ok. I hopefully may be able to shed some light at this problem.
I tried several SDs. 2Gb, 8Gb, 16Gb. Slow ones and fast ones. In all of them I end up with the issues reported above. But... with an 1Gb SD it miraculously worked.
Maybe it is an issue with the partition resizer?
All of the SDs tested boot the horribly outdated Coreelec 9.2.8 normally, so it is not an issue with the SD cards.
