It's basically the same answer we already gave you in your other thread:
Posts by Da Flex
-
-
What did you installed exactly? LE x86-64 legacy? What are your hardware specs?
-
It’d be great if this info was highlighted a bit more in the docs, because most newcomers won’t even think to dig into cmdline.txt.
Most newcomers don't even know what composite is. So the conclusion is: If someone needs composite, then it's a nerd, who can deal with config files. Anyway, you can write into our Wiki, if you want.
-
Quote from chewitt , who explained it to me in the background:
QuoteDisplay Morefeel free to mess with compile flags AND disabling hardware decoding
the latter is important, because when you enable hardware decoding (on most hardware) Kodi is trying to use a zero-copy path
zero-copy basically means no opportunity to mess with the stream (as that requires copying)
most hardware cannot CPU decode and process high-bitrate 4K UHD media
the example given of low-latency DJ tools being able to stretch audio is correct, but ignores the reality of 4K UHD video being 10x the data size of an mp3 file
all that data needs to be moved in/out of memory multiple times once you mess with it
and at that point all the whizzy ideas are dead in the water
-
Maybe time stretching helps to normalize playback speed. Seems like it's actually possible with FFmpeg:
Timestretch Audio and Video Using 'Rubberband' Filter - FFmpeg By ExampleThe following command will be a video that plays at half speed with audio that's both slowed down and pitched down by an octave. Note: To enable compilation…ffmpegbyexample.comchewitt Do we use the rubber band flag for FFmpeg compilation?
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
The getedid script solves a single and specific problem; the TV not being powered on before the RPi starts.
That could have an impact for CEC connection, so I would give it a shot.
-
LE probably still uses the old CEC route for HDMI port 3. So run getedid create from SSH while being connected to HDMI port 2.
-
I don't think it's an LE problem. The easiest solution is to solder the LED off, and use an LED connected to GPIO.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Try without any HiFiBerry entries at config.txt. There is a chance that it's detected automatically in newer LE versions, and explicit activation leads to a setup mismatch.
-
I've been using Libreelec9.x on a Raspi3.
...
Now I've updated to Libreelec12.2 (complete reinstallation and also reconfiguration of the system).
Do you mean an installation from scratch? That's the officially suggested way to "update" from LE 9.x to LE 10+.
Background: If you're using an outdated settings file internally, then something like your audio issue can happen.
-
Double-post:
Audio Profiles (for Kodi 18 and later)
Closed, because the dev is at Kodi forum, not here.
-
Understood. I guess you can connect the fan directly to other GPIO pins. Then the fan is always on, and you don't need a script.
-
Damn, what now?
Throw the Argon One case into the trash. It's the source of several issues on this forum (use the search function for evidence).
-
Da Flex that's not an appropriate comment/rebuke because XR819 is an Allwinner own-brand WiFi chip found on some older Allwinner boards. The specific device/OEM is irrelevant due to the not-supported state of the chip.
It's relevant for users, who don't know, which chips they have inside of their devices. Many of them only know the device name.
-
sghenkks Be more precise next time. You didn't mentioned your device, and you didn't mentioned the manufacturer of the WiFi chip.
-
Closed, because this thread is pointless.
