I find out that the problem only exists with some video files. One of the "bad" files has this parameter:
A sample (e.g. 2 minutes) of that file, assuming it still shows the issue may be useful.
I can't see anything obvious in the codec options.
Only strange thing is the problematic file was 50fps, and the converted file was 29.754fps.
I don't know if you specifically chose that in encode options, or if that was auto detected (which may suggest an issue with timestamps of frames).
Try without the argon case.
A debug log when it happens may be useful.
Identifying the exact nightly build it started would be very useful.
I have an Pi4 with LE9.2.8 and LE10.0.1.
Same TV , same settings.
Do you have any custom hdmi settings in config.txt?
I've been looking at hello_drmprime on GitHub, and it looks like it uses DRM planes instead of drawing to a surface. Should I rewrite my program to match the output process used in hello_drmprime, or is there something else I'm missing?
Outputting directly to a DRM frame is far more efficient and I'd say necessary for 4K performance.
I'd suggest you ask ThePiHut. Personally I'd be surprised if it just works.
All models of RPi2 are 1GB, so I think they will be fine.
Only the Pi0, Pi1 and Pi0 2 have less ram, and so aren't recommended for kodi.
Vimes can you confirm if the black screen shortly after boot issue only occurs with the nightly builds (which use kernel 5.15), or if they also occur with Matrix builds (using kernel 5.10).
I believe I've seen a similar issue on 5.15 kernel, but never on 5.10.
I've set up a LE nightly build to auto-reboot every 2 minutes and unfortunately it ran all day yesterday without showing the issue.
Any info on what makes it occur more often would be useful.
e.g. any non-default config.txt settings, display resolution and refresh rate. Whether it happens on a clean install, or only after libraries/addons are set up.
> Using a local USB HDD (3TB 7200rpm drive), when I jump forward 40min after starting the movie it takes 15 seconds to catch up.
What is the format of the file? For indexed files like mkv, I'd expect this to be much faster.
I typically seek around files with a 1 or 2 second delay (Pi4 using nfs, but I'd expect directly attached disk to typically be better than any network interface).
Non-indexed files (m2ts, dvd/bluray iso or folder structure) can be a lot slower to seek.
Work has just started on optimising VC-1. If anyone wants to provide a sample file (e.g. 1 minute section cut from a currently problematic file), then that will be checked when determining when performance is good enough.
Ideally a harder section from a BluRay (e.g. where bitrate peaks, or we lose audio sync fastest).
Technically this could be implemented by anyone. All relevant code is open source.
But the number of people who are willing and able is small.
so I noticed that if I turn on the TV first and then the PI, Kodi always starts properly. But as soon as I leave the TV off and start the PI, it doesn't work. The Pi then starts the TV via CEC and there is only the white writing at the top left with Libreelec 10....
Some displays don't allow resolutions supported (edid) to be read when powered off, or to determine the device is connected (hotplug). Some do.
You can use "getedid create" from wiki to store the edid to a file, and allow TV/Pi to be powered in either order.
Can you ssh in when it is working normally?
Can you ssh in when it boots with blank screen?
If so, the output of dmesg would be useful.
How does one enable AAC to AC3 transcoding on the RPi4 LibreElec Nightlies? The option is not apparent. Do I need to install a plugin?
There is even a bug report on github with no response from the devs. It seems that they are not able to fix it unfortunately..
It's almost impossible to fix something without being able to reproduce it.
I watch videos on Pi4 every day, and sync is always prefect.
There's something in:
files being played
settings used
AVR or TV
A clean install of LE10 on an sdcard, and playing a standard file would be useful to rule out the first two of these.
There was a recent fix that affected seeking.
It may (or may not) help your issue.
It's been backported to Matrix, but isn't in LE yet.
It should be in LE nightly builds if you wanted to test (ideally on a spare sdcard).
Whre can i ndo this: i.e. can you adjust audio offset then "set as default for all files" ?
It's not out of sync for me.
Does it occur with all files or just "harder" ones? Provide mediainfo of a file with this issue.
Is it always the same offset (i.e. can you adjust audio offset then "set as default for all files" to make everything in sync) or does it vary?
