config.txt doesn't exists on x86 hardware. You have to create a custom EDID file instead.
Posts by Da Flex
-
-
Sorry, for playing local files you need this (buffer mode 1):
Code<advancedsettings version="1.0"> <cache> <memorysize>2000000000</memorysize> <!-- 2GB buffer size --> <buffermode>1</buffermode> <!-- buffer all filesystems --> <readfactor>8.0</readfactor> <!-- doubles the default readfactor --> </cache> </advancedsettings>I think audio stutter can indicate a buffer underrun, especially because your video slows down a bit, too. 2GB buffer is a lot, but no problem for your 8GB device. Try it!
-
Thanks for the log! The log says "CAESinkPi:AddPackets Underrun (delay:0.00 frames:512)". This could mean that your network buffer runs empty. To avoid this, try this: Click!
-
Your config.txt is OK, changes will have effect after reboot. If you enable debugging at GUI, you should see clock speed (I guess).
-
Buffer mode 3 was no buffering. Next we should try to increase buffer size and read factor (details here: advancedsettings.xml ) :
Code<advancedsettings version="1.0"> <cache> <memorysize>2000000000</memorysize> <!-- 2GB buffer size --> <buffermode>4</buffermode> <!-- buffer all network filesystems --> <readfactor>8.0</readfactor> <!-- doubles the default readfactor --> </cache> </advancedsettings> -
Probably not the HDMI cable then.
Do you have pass-through enabled at the LE audio settings? If yes, disable it for the non-working mini PC.
-
Should I also adjust GPU memory?
No. The current test is just about clock stepping.
-
Also, another question. Do I need version="1.0"> in my XML file at the top or does it matter?
That's for parsing XML. Kodi will parse fine without that version attribute. Your choice.
-
You have disabled buffering with buffer mode 3. A minimum of necessary data still goes into RAM. With memory size 0 you will use microSD instead of RAM. To avoid an early death of your microSD, use memory size 0 just for testing, not for permanent usage.
What's the result of your overclocking test?
Which LE version do you use for testing?
Does pastekodi show any unusual output when you get audio errors? If yes, post the link.
-
PS: Another hint, not related to config.txt. /storage/.kodi/userdata/advancedsettings.xml should look like this to avoid buffering:
Code<advancedsettings version="1.0"> <cache> <memorysize>0</memorysize> <buffermode>3</buffermode> </cache> </advancedsettings> -
So force turbo is a form of overclocking, but not going all the way with voltage changes, etc?
Yes.
So I don't lose my warranty?
Yes.
And I suppose if I don't want to force turbo 1 I can just add a # to that line in the config file and it will ignore my force turbo additional line?
Yes.
-
1. Where is the config.txt located?
2. You're just saying add force_turbo=1, nothing else? Am I overclocking? What would you recommend for the settings for RPI 4B 8 GB RAM?
Yes, that's all you need, and it fits for your device. It's no real overclocking, the RPi just stays at max regular clock level.
3. Where do I add this in the txt file?
Location doesn't matter, just make it the last line of config.txt.
4. Can this be undone?
Yes, just remove the line again. You will not lose your guarantee by using that option.
5. Should I re-rip first?
No, try overclocking first. If it doesn't work, remove overclocking and re-rip.
-
Create this /storage/.kodi/userdata/advancedsettings.xml:
Code<advancedsettings version="1.0"> <cache> <buffermode>3</buffermode> </cache> </advancedsettings> -
I'm using the "Joyn" (and "DAZN") add-on from the KodiNerds repo without the need of VPN. Eventually you have to update to the latest LE nightly to make it work.
The Netflix links of your initial post are useless spam. I had to remove them. Maybe those links have been created by the forum formater.
-
The fix I used was to increase the minimum clock frequency for both the ARM and the GPU by adding entries in config.txt
What do you think of this?It's worth to try. I would add force_turbo=1 to config.txt. The SoC's clock frequency will stay constantly at max then. So if it's a SoC frequency issue while playing video (speed down -> speed up...), this should fix it.
Re-ripping is also a good idea.
-
If you "Chinese TV" has a higher resolution than your Samsung TV, then the HDMI cable could be the weak part. For a 4K TV you need an HDMI 2.0 or 2.1 cable to transfer higher data rates.
-
Maybe because YT is running on a lower resolution. Set your default LE resolution lower (video settings). This reduces HDMI data rate, and maybe creates enough free data rate for audio.
-
OK, thanks for testing. The next trick sounds weird, but I know it solved audio issues for some users. When playing a video stream and pressing "OK", the status bar appears. On the bottom right you'll see a gear wheel, which contains a setting for de-interlacing. On my RPi nightly build this setting is grayed out, but you maybe have it. Deactivate de-interlacing, if you can.
