The fact work was done on this, and a test build was provided and no one commented for over a month makes us believe this isn't a high priority issue. Effort can be better spent on issues where we get some response.
Posts by popcornmix
-
-
Also check output of dmesg for any kernel errors (e.g. allocation failed).
-
The strange thing here is that using the exact same hw configuration with le 9.2.8, plays flawlessly.
What have changed in le 10 that makes impossible to use tv server + client in the same machine ?I suspect the issue is at the tvheadend end, rather than the decoder end.
I don't know if you've tried using LE 10 on the Pi4 as the client, with the tvheadend server on a different device (either another Pi, or a different device).
If LE10 works when used as both client and server on separate Pi's, that would suggest there is a problem with the load when used on a single Pi, causing lost data.
If it still fails, then it would suggest something is worse on the server end - either tvheadend or the kernel driver for the tv device.
-
The sample file is corrupt (you can see complaints from VLC here).
Now how decoders cope with corrupt data is variable. In general software decoders have more ability to minimise visible artifacts (i.e. replace missing data with nearby data).
There is nothing that can be done about this, apart from not using the hardware decoder (which may have performance issues).
I don't believe LE 9.2.8 will play that sample file flawlessly.
-
Never seen a movie with 59.94 Hz ...
The NTSC standard is 29.97 interlaced frames per second, which when deinterlaced requires a framerate of 59.94Hz.
So in general live TV in America (and other countries) uses this, and so do many DVDs.
-
GUI with 50Hz is enough.
It is only neccessary to set 60 Hz, 50 Hz and 23.98 Hz in whitelist.
No you should set them all. Videos can be encoded with 59.94fps and 24fps and not allowing them in whitelist will mean occasional frame drops.
-
> Are there any bad ramifications to leaving it set to 128?
gpu_mem is unavailable for other uses, so when you are not playing 5.1 profile h264, it is wasted.
But it's unlikely to be noticeable (especially if you have 2GB or more RAM) in general.
-
Got sample and I can confirm it doesn't play.
I think I see the problem:
Format profile : [email protected]
Format settings : CABAC / 15 Ref Frames
The Pi only officially support profile 4.1 (BluRay).
This has far more reference frames than that supports (or is sensible to use).
Try adding gpu_mem=128 to /flash/config.txt and try again.
That allows enough memory for the high number of reference frames.
-
Should I attach the 30 second file here, or send it somewhere?
(I don't want to violate any rules, etc)Posting a 30 second sample file that demonstrates an issue is okay by rules here.
Google drive or dropbox and good examples of where to upload it (although there are many alternatives).
Post link (or DM it to me) and I check if it fail for me (and if it should play and doesn't I can get the right person to investigate).
-
Kind of "fixed" it by reducing the resolution (from something above 3000x) to 1920x1080.
Prehaps related to "upscaling"?
Check advice from here: https://wiki.libreelec.tv/configuration/4k-hdr#hdr
Using 1080p60 for GUI with 4k modes enabled is whitelist is recommended configuration. (You will get 4k resolution for video).
Running the GUI iat 4k is pointless (the skin texures are 1080p) and just makes kodi laggier.
-
No support for pirate add-ons.
If you have a file that fails to play, and can provide a sample (e.g. 1 minute cut) that shows the issue it can be investigated.
-
The easy solution is to use different SSID for 2.4GHz and 5GHz, and then connect to the 5GHz one.
On RPiOS I forced 5GHz by specifying the mac address of the 5GHz interface of router (with bssid=<mac addr>) in wpa_supplicant.conf
But my LE Pi is wired so I've not investigated how that handles wifi config.
-
> hi, in recordings they do not appear as green artifacts. anyway I will try to get a sample - more thinking where to share it.
google drive and dropbox are good options for sharing sample files (but there are many other options).
-
The low resolution suggests we can't read the edid (the tv's capabilities)
If you can get it to work once, then I'd suggest using getedid create to capture it to a file.
-
It could be a dodgy hdmi cable - have you tried swapping the cables around?
-
Do you see the artifacts in recordings? If so, can you provide a short sample file that shows the issue?
-
Your problem is probably that the TV is not forwarding certain buttons to the pi.
You can confirm this by enabling debug logging and checking which buttons produce a message,
or using the keymap editor.
If the buttons aren't forwarded at all that's down to the TV.
There may be hidden menus or button presses that can enable extra buttons (e.g. here).
-
I don't think it's possible without using another audio interface (e.g. hdmi, I2S, usb).
