Posts by popcornmix

I tested a 64-bit build of LibreELEC and it does improve VC-1 playback.

Hopefully LibreELEC (Orion) 12 will be 64-bit by default.

It's not in the 20.0-Nexus tag (it was the first commit after that tag...) which I believe current LE nightlies are using.

You need to wait for the next kodi bump from LE.

Opus is a common audio encoding and is supported.

The crash is in libass, so it's subtitle related.

Are you able to create a cutdown file that exhibits the crash?

It will obviously need to include the subtitle track.

(e.g. use ffmpeg to create a 2 minute cut of file, and confirm it still crashes).

I think this was fixed here

What are you doing at the time?

For me (with kodi not playing a video) user mempy is taking ~1% cpu and kernel memcpy is not making the list.

But the situation is likely to be very different when playing a video (and different with different codecs), copying files,

using ethernet, wifi or bluetooth, scanning library etc.

Try: delay=0, repeat=100, release=0

If you still get bouncing, increase "button press delay before repeating" in steps of 100.

Quote from tekno

I guess you did not read my post. Doing ANYTHING that so much as MENTIONS libreelec on the Kodi forums usually results in poster being attacked. No thanks. I use Libreelec only confirmed it on Kodi 20 on windows. My bug report STANDS as I will not post any Libreelec Bug on Kodi forum even if I confirm the same problem is in Kodi on Windows. I feel no need to be attacked neither here nor there

Please READ my post next time even if you are a dev that does not justify ignorance, as it was clearly stated in my OP.

Please READ my post.

Don't mention libreelec when reporting on the kodi forum an issue that affects kodi on windows.

Then the devs cannot attack you for using libreelec.

Quote from tekno

I installed Kodi 20/IPTV Simple on a Windows machine and found the exact same limited resolution playback (720p) so the Bug goes back to Kodi not LE. It is worth noting however if you ever post on the Kodi forum and so much as mention Libreelec you are likely to be attacked for trying to get support for LE on a Kodi forum, even if you have already found the same bug on Kodi (without LE). I therefore leave it in this forum's capable hands

If this is true, then why not report the Window form of the issue?

In general, to get the right developers to see an issue, report kodi issues on the kodi and libreelec issues on the libreelec forum.

2023-02-01 22:07:24.107 T:1143     INFO <general>: VideoPlayer: OnLostDisplay received

I suspect this message is hotplug related.

Not sure if a dodgy cable is causing spurious hotplug disconnects, or the TV is generating them for some reason.

With LE11, try adding (make sure you are using first hdmi connector - closest to power socket) :

video=HDMI-A-1:D

to the end of cmdline.txt (on same line).

If that doesn't work, try:

vc4.force_hotplug=1

instead.

I'm curious. What is the format of your 3d videos? e.g.

half-SBS

half-TAB

full-SBS

full-TAB

MVC

AV1 is a very new codec, and there is no hardware decode support for it on Pi400 (or any Pi models).

What you see is software decode, which won't handle full hd (1920x1080).

You may find lower resolution samples work okay (perhaps 1280x720@24), but that is probably the limit.

Quote from ciclista71

Didn't know, but I am using an headless raspberry, how can I show such debug info then? Sorry for my ignorance

I don't understand. How do you know "Video freezing whilst Audio continues" if you are running headless?

(headless means without a display, so no video to look at).

The debug info I'm suggestion is from kodi, while you are watching the video stream.

Player process info - Official Kodi Wiki

ctrl-shift-o shows useful debug info.

The "Player: a/v:0.01 forward 14.88MB 100%" line is pretty useful.

A/V is audio/video sync and should oscillate around 0 (usually not exeeding -0.1/+0.1

The forward and percentage numbers show how much data is encoded data is queued up - if that heads towards 0 you go into buffering mode and kodi doesn't handle that well.

Do you see video queue go down to zero before issues happen?

I think kodi just doesn't recover well when switching into and out of buffering where there isn't enough network bandwidth between the client and server.

I used to have issue like this when using a wifi connection, but it's been perfect since switching to wired.

It would be useful to confirm if the issue is reproducible from a recorded file (played through file interface of kodi).

If it is we can investigate the file.

Quote from @fterlife

Using your build I'm getting a picture here at boot without any workarounds.

Thanks for report. If anyone else can confirm it would be helpful.

The potential fix is not merged yet, and more positive reports would help it get merged.

You say LE9 used to work? Can you reproduce that now?

If it used to work and doesn't now, then it sounds like a hardware issue.

If the pi and cable can drive the PC monitor then it sounds like the issue is at TV end.

If there are multiple hdmi sockets on TV then try them all.