For playback you can disable buffering (local and network) on advancedsettings.xml:
Code
<advancedsettings>
<cache>
<buffermode>3</buffermode>
</cache>
</advancedsettings>Posts by Da Flex
-
-
Not a helpful report, because you don't name the scraper add-on.
-
Sorry for the inconvenience. Of course we are still maintaining our project.
* I go to the RPi3 link and it shows me the download for RPi2 (maybe they both share the same, but if so it could have been presented better).
That's correct, you can use that image for your RPi3, too. I'm using it myself on RPi3B+, so I know it's working.
* Ok.. back to the download page, I click on the instructions for the app link, and it redirects me to a 404 page.
We recently switched to a new Wiki, the link you are searching is here.
* I google around, and find links to the wiki, but clicking on them, libreelec.tv isn't even resolving
Same solution as above, use our new Wiki.
-
Maybe you have the ability to update the firmware of the sound card. I'm not familiar with that, try at your own risk.
-
I have a problem with an AOIDE DIGI Pro soundcard (DIGI+ PRo clone card) wich is working fine on pi3B.
Thanks for the kodi.log. Your soundcard doesn't appear at the output device list. I think HiassofT is right, and the card is not detected by the kernel.
Our RPi4B users have no problems to use original HiFiBerry cards. So your problem is that you are using a clone. That's why the HiFiBerry support forum will not help you.
Your clone is compatible to RPi3B, but incompatible to RPi4B. Buy the original from HiFiBerry, and everything will work.
-
og13 This is beyond the current topic. Open a new thread at General Support, describe your issue and add a link to a complete kodi.log.
-
og13 You can comment out dtparam=i2c_arm=on and dtparam=i2s=on.
-
og13 It's just dtoverlay=hifiberry-digi. After next boot you should see a new audio output device on the settings.
-
To get better and 5.1 sounds with my home cinema amplifier, i bought a DIGI+PRO soundcard. After many tests and reading topics, it's not posible to use these soundcards with PI4. I seems to be an issue from the driver. We have to wait for ...
Did you set the right config.txt option?
-
Great! The trick is to go to the forum's main page first, and then press the magnifier icon. Search results will include all sub-forums that way.
-
Yes, use our search function, and you can find this.
-
Other people had the same (good) idea on this forum. The answer is still no. LE / Kodi development is miles away to do such things. Use an HDMI audio extractor instead.
-
It's probably due to a bug from a long outdated build.
I hope you don't try to sneak in with an OpenELEC question. Stone age is over.
-
It's a GPU thing, not CPU. The GPU provides hardware acceleration for video playback. On the other hand, the GPU has to work hard (non-accelerated) when displaying EGL graphics, which is used by the GUI. I think your RPi is responding normally.
-
The MPD add-on is probably just compiled to deliver IP port binding.
-
Code
Nov 09 16:57 : exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address already in useUsually 127.0.0.1 is the right address for local host.
-
You can also change the firmware on LE, but it's easier on Raspbian. After changing the firmware, you can insert your LE card and instantly use it (firmware is at the chip).
-
At the 2GB variant, this result was expected. I guess the data bus is too slow for 60Hz plus AAC audio at the moment. Wait for optimization updates.
