Posts by Da Flex

Are you sure <pixelratio> belongs to advancedsettings.xml? I can't find that parameter at the docs.

The Kodi doc says about video calibration:

Quote from 3.2 Video calibration

Note: Always adjust the TV display settings first. Most issues are due to overscan and similar settings being enabled on the TV/monitor. Trying to adjust this setting in Kodi while these settings on the TV are enabled will have you running in circles and never being able to fix the issue.

So I think your issue is related to overscan settings. Read about overscan settings at config.txt (disable_overscan, overscan_scale etc.).

Yes, something like that works for many users with the same issue:

hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=16

Configure hdmi_group and hdmi_mode parameters as described at my above link.

PS: If you use hdmi_cvt instead, then hdmi_group and hdmi_mode are not needed.

Probably your connected hardware (AVR / TV) is the problem. You can enforce an HDMI mode at config.txt. Read here about editing.

Yes, the AVCHD specs say that USB 2.0 is too slow, and USB 3.0 is fine.

Try to rule out network errors:

Quote from kodi_crashlog_20200827114827.log

2020-08-27 08:20:46.316 T:1545593728 ERROR: Could not find 'nfs://192.168.0.109/export/nas/Music/Electronic/DnB and Dubstep/Pendulum/Pendulum - Albums & Singles/2006 - Pendulum Remixes/13-Moving Forward (Phetsta Remix) - T.wav' referenced in cue, case sensitivity issue?

Quote from Hansie

I have a ex-android box now running Coreelec (Sadly my libreelec box is a Rockchip one and audio passthrough totaly does not work on that ) with Kodi 18.8 and running the Jellyfin Addon in Addon mode.

We don't support CoreELEC. Sorry, I have to close this thread.

So I had a look at your add-on list. Bad news, you use Super Repo, which is illegal. No further support from us.

Your "JotunTV" add-on is the problem:

Sep 23 16:16:15 JotunTV kodi.sh[5141]: terminate called after throwing an instance of 'std::bad_alloc'
Sep 23 16:16:15 JotunTV kodi.sh[5141]:   what():  std::bad_alloc
Sep 23 16:17:10 JotunTV kernel: vchiq: 0: ignoring ERROR from callback to service 9d004
Sep 23 16:17:10 JotunTV kodi.sh[5141]: Aborted (core dumped)

You can use the update folder method to go back. Personally I would start from scratch with the latest LE (maybe on a different microSD), and find out step-by-step when playback goes out-of-sync.

Function calls are part of the script(s) you've been installed. Edit it.

Yeah, looks like a buffering issue, and the reason for that could be your latency setting at advancedsettings.xml:

<advancedsettings version="1.0">
    <video>
        <latency>
            <delay>166</delay>
        </latency>
    </video>
</advancedsettings>

Millman Read here. Post your kodi.log as a link (Pastebin as source for example).

earnie Maybe our showcase can help you.

Connect your HTPC directly to the TV, do the above EDID procedure, and then go back to the HTPC -> AVR -> TV hardware setup.

It's different hardware, which consumes more power on RPi 4, compared to his RPi 3. That's why I think the PSU is the issue here.

Quote from LibreINtoronto

The wifi does work, but I'm having buffer issues, if I'm hardwired, it works fine. That being said, my wifi access point is business class, I use an Aerohive AP wired to my Router. I do have a USB to ethernet adapter, but I really want that onboard port to work...my OCD will not allow any other solution..

I'm using a long Ethernet cable, too (around 40 feet), and it's working fine on my RPi 3B+. Maybe it helps to replace the cable, and use one with better shielding.

PS: After reading your latest post, your cable is probably OK. I don't think RPi 3 and RPi 4 use different Ethernet drivers. I suggest to use a stronger PSU, which will provide more power to the Ethernet port.

If the nightly built doesn't work, consider to buy an Ethernet to WiFi adapter. Because it's Ethernet-based, you will have no driver problems. Those adapter usually have 2.4 GHz only, not 5 GHz. If you can live with that, this could be your solution.

If you don't overclock, then it's probably a RAM issue:

Quote from kodi_crash.log

Backtrace stopped: Cannot access memory at address 0x10