I’m using a Pi 4B and my videos are are slightly sped up and thus the pitch is higher than normal.
My intended display is a CRT TV. Though I’ve tested this on 2 modern flatscreen TVs and the issue still persists. For these 3 tests I used the TRRS / RCA output.
I’ve played local media as well as media through add ons. This didn’t make difference either.
Here’s the debug:
[RPi4] Video playback out of sync / sped up
-
OatmealMan -
October 20, 2024 at 6:42 PM -
Thread is Unresolved
-
-
Settings -> Player -> Videos -> Sync playback to display
-
Settings -> Player -> Videos -> Sync playback to display
This did not change it.
-
If A/V is out-of-sync constantly with the same time difference, then you can adjust it manually.
-
How can I adjust it?
Ive tried moving the playback speed one step down to .90 but that is too slow.
Also syncing the playback to the display actually made it skip forward worse. Bad enough that I cannot tell if the A/V are in sync with each other. -
How can I adjust it?
Create an advancedsettings.xml file. You can adjust A/V in both directions.
-
Which tags should I be using / adjusting?
fps and refresh? -
-
The A/V are in sync but sped up.
-
The A/V are in sync but sped up.
I see, in-sync has a different meaning in my world. Reduce the <maxtempo> value then.
-
This add-on might be of interest: https://github.com/matthane/script.audiooffsetmanager
-
-
This might be a silly question but it says maxtempo has a range of 1.5-2.1 and 1.5 is the default. Can I really decrease it to say 1.3?
If 1.0 is default normal play speed and mine is running fast yet .90 is too slow I need somewhere around .95.
Also, how am I supposed to make sure that it is playing at the correct speed when I'm adjusting a fraction of a second? Is there really not a better way to fix this?
-
How exactly do add the file?
Enable SSH and login to the device over the network and use "nano" to create/edit text configuration files. You cannot read the EXT4 filesystem used for /storage on a Windows machine.
-
Your file content is missing a slash. It has to look like this:
Because the value range starts at 1.5, it probably doesn't work with lower values, and doesn't solve the problem.
Of course you can try other options, like playing with frame rates. Personally I would try the <fpsdetect> options next. Kodi is no professional video production software, so we don't have measurement for perfect playback speed. You have to experiment.
-
Hey, checking in on this thread to see if anyone has found a solution to this problem?
I'm in the same exact boat, using a RPi 4b (8gb) connected to a US CRT with a fresh install of Kodi 21 and Fen Light.
I came from a RPi 3b with the exact same setup with this issue not present, but as soon as I moved to the Pi 4 the issue showed up.
I've dug through every setting and forum post imaginable, and I was unable to find a solution. Any assistance would be greatly appreciated, as it's just barely annoying enough to cause frustration haha.