Actually the /storage sub-folder doesn't matter, because it's all about the way to include the libs at the Python script. Do this:
import sys
sys.path.append('/storage/.kodi/userdata/<PATH-TO-YOUR-PYTHON-LIB-FOLDER>')The benefit of the /storage/.kodi/userdata folder is that it's part of the LE backup strategy.
LE uses add-ons by default, so search at the repos first. Other package managers are not available by design. However, some users install docker packages. Maybe that's an option for you.
Please describe your hardware, your LE version and your goal.
Activate debugging at GUI (HUD will appear on top), try to start a video, login by SSH and call pastekodi. Post the resulting link here.
Hey jazzl!
What happens if you do this on SSH: amixer -c 0 set Digital 80%?
This line has been taken from the official HiFiBerry doc, so it's actually common knowledge for all HiFiBerry users.
Can I just delete advancedsettings.xml with no problem?
Yes.
I think your changes at config.txt and advancedsettings.xml don't solve the problem, so I suggest to remove both.
You have two choices now:
a) Update to the latest LE nightly as often as you can, and hope for HD audio improvements.
b) Re-rip your videos to non-HD audio.
I had a look at your latest log. It says you are using dtsHD:
2021-02-16 16:10:06.544 T:473310064 INFO: CAEStreamParser::SyncDTS - dtsHD (core) stream detected (6 channels, 48000Hz, 16bit BE, period: 512, syncword: 0x41a29547, target rate: 0x18, framesize 2080))Because HD audio isn't highly optimized on LE yet, I think you have to wait for an LE update with better HD audio implementation. Keep using the latest LE nightly, if you wish.
If you re-rip to a non-HD audio format, it could solve it.
I did notice something I haven’t seen. When trying to play the John Adams HBO Mini Series MKV rips and even some of the Enterprise episodes I have tested with in the past it causes LibreElec to reboot and go back to the load screen. Never seen that before. Once it boots back up I click on them again and they play as normal. What could be causing this?
If your current advancedsettings.xml solves the original issue, disable (comment out) force_turbo=1 at config.txt.
If the reboot issue persists after this, open a new thread and provide a log file (pastekodi link) with debugging enabled on GUI.
Is buffer underrun related to what you referred to as the network buffer and the underrun in my log?
Yes, that's what I get from your log level 0 file. You can increase the log level, if you activate logging at GUI, and then use pastekodi.
Anyway, tell me the results of your new settings first. This should do something. 
config.txt doesn't exists on x86 hardware. You have to create a custom EDID file instead.
Sorry, for playing local files you need this (buffer mode 1):
<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 ) :
<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.