> 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).
Posts by popcornmix
-
-
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).
-
If your TV supports 4kp60 then the best setup is to add "hdmi_enable_4kp60=1" to config.txt.
Set the resolution to 1920x1080@60 in settings/system/video, and enable the whitelist for any resolution/refresh rate combinations you care about (probably 1080p23/1080p24/1080p50/1080p59/1080p60/4kp23/4kp24/4kp50/4kp59/4kp60).
You will then have a fluid gui at 1080p60, and kodi will switch to 4k when required (i.e. video is 4k).
-
Does this only occur with timeshift, and not when watching live tv or recordings?
Do you believe issue is not present with Matrix builds?
If not, any idea when it appeared in nightlies?
-
I'd guess you are not returning the video frames to v4l2, so they are just consuming all of (cma) memory.
-
One reason for USB devices getting reinitialised is insufficient power supply. If you have a powered USB hub, try connecting to it through that.
-
HiassofT downloaded the file for me.
I've watched the first 5 minutes and it seems fine (given the approximate nature of checking a dubbed program for lip-sync).
A better sample would help, as well as a description of exactly what's wrong (e.g. at timecode 2m30 character X is seen speaking 2 seconds before audio is heard). But really need a non-dubbed example file.
-
Might be geo-blocked. I'm in UK and still get Access Denied.
-
So I give it another try:
Link gives access denied.
-
A sample file would be https://rodlzdf-a.akamaihd.net/dach/zdf/21/12/211221_2015_sendung_iat/5/211221_2015_sendung_iat_a1a2_3360k_p36v15.mp4
It is an episode of a german tv series "In 80 Tagen um die Welt" and can be downloaded for free from the mediathek of ZDF.
The delay immediately starts at the beginning of the file.
A link would be useful for someone who doesn't speak German and knows nothing of mediathek of ZDF.
-
I have an ArgonPi One Case (first one with still having two microHDMI instead of regular HDMI), and everything works fine when using LE 9.2.7 (even before with LE 8.X with the same TV, but that might also have been my former RPi3). So I doubt that the issue is hardware (case) related for me, but a kernel / software topic.
Can you confirm if issue still exists when not using the Argon case?
-
TomTom you log doesn't include the kodi.log or crashlog.
Can you try uploading again, with debug logging enabled, after the crash (and without rebooting).
-
I suppose it's a Tvheadend / Timeshift issue (currently using addon Tvheadend Server 4.3 (Alpha) 10.80.4.103 but the same with 4.2)
Can you run tvheadend server on a different device and connect tvh client to it over network.
That should narrow down if the issue is in the client or server end.
-
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).
