It's OK to wish senseless things, but you have to find the guy who does it for free. Good luck!
Posts by Da Flex
-
-
Is every release perfect?
No. If you want to know whether it's usable for most RPi 4 owners, you have to read the forum anyway. If you have to be here to get such stability info, I don't get the point about update info.
-
Why don't you just switch to auto-update?
-
Understand. Then you should enable logging, reproduce the error and give a link to kodi.log. That's the way to find out what happens.
-
Your RPi informs you about available updates. That's the perfect spot, and much better than all the social media crab.
-
I can only guess that USB speed went down since LE 9.2.4, and as a result your USB DAC stopped working.
If you have another microSD to play with, try this LE mod.
-
I have a media center to do the ripping on my MEDIA CENTER, NOT MY COMPUTER!
Your "media center" isn't a computer? What is it?
-
Sounds good. If you need an instant solution, buy an HDMI audio extractor.
-
EDIT: or are you suggesting trying to move to balenaOS?
Whatever OS compiles fine at 64 bit mode will be a benefit for us. We don't compile that way at the moment. Feel free to share your progress here.
-
dmrlawson Did you read my link to balena.io? It provides some fixes and workarounds.
-
I'm pretty sure it's a software bug. LE updates the RPi firmware, but you can install different firmware for testing. If you have audio pass-through enabled, disable it for another test.
After you did both tests, write a complete bug report.
PS: I was just reading that RPi 4 users get an LE 9.2.5 hot fix, which contains new firmware: click. So try this first.
-
Thanks for reply. The reason to run LE in docker is to make the box serving as HTPC and full Linux server at the same time.
Maybe it's a better approach to run Docker inside LE. You can find cool Docker projects in our showcase section.
-
I just had a short dev conversation. We need a complete kodi.log (link, like you did before, log level 2). Thanks!
PS: Use local media for testing. Streaming has some additional unknown factors.
-
My point is that both options could be same. I don't think that a display refresh rate can vary all the time, so "hdmiclocksync" probably means "sync playback to display", not vice versa.
If so, it could be a bug. Maybe the corresponding GUI setting has been overwritten by a wrong compiler flag. When "sync playback to display" is always active, it can result in frame drops.
PS: I have been informed the devs. Stay cool.
-
hdmiclocksync is "Adjust display refresh rate to match video", not "sync playback to display".
Are you sure you have both options, not just "sync playback to display"?
-
Quote from kodi.log
2020-07-16 16:40:29.111 T:1390015360 DEBUG: COMXVideo::Open - decoder_component(0x0x5d414ba8), input_port(0x82), output_port(0x83) hdmiclocksync 1
vs.
Quote from @chewittDo not "sync playback to display" as that will force everything to be resampled and ARM devices are rubbish at that.
-
Yes, I know how de-interlacers work. It's not relevant to this discussion, and neither is overclocking as the issue is not related to CPU load.
Did you verified normal CPU load by using top or similar programs?
-
That is not correct at all, it de-interlaces it to 1080p50 depending on the de-interlacer setting. But there are a lot of different things going on when playing back such content, less video bandwidth for starters.
I'm at least partially correct. Here is the reference I mentioned: click.
