Posts by Da Flex

Quote from mcaron1234

It appears that a mod deleted the xrandr instructions posted above, is that because they were incorrect?

I've reactivated that post now. sudo doesn't exist, so we were thinking about copy & paste chat bots.

Quote

2023-04-01 21:28:09.986 T:12386 critical <general>: [script.module.inputstreamhelper] ['ldd', '/storage/.kodi/cdm/libwidevinecdm.so'] cmd failed.

Re-install InputStream Helper.

You can try those two points:

• disable DRM Prime
• in case you are using x86 Generic, switch to x86 Generic-legacy (update folder method)

The screen shot mentions a loop device, that can't be detached. Maybe you have to unmount or delete a loop device.

Here is a documentation for Linux loop devices: Click!

Try the Generic-legacy image. You can use the update folder method to switch among Generic and Generic-legacy.

Works fine here (LE 11.0.1 / RPi 3B+).

PS: I'm using the DAZN add-on from KodiNerds repo. Maybe that makes a difference.

Disable DRM Prime.

Thanks. The shutdown procedure at kodi.old.log looks good to me.

Can you say something about your hardware drives, especially about /flash?

My current theory is that LE's installation drive has errors. There are free hardware diagnostic tools, which can run from USB stick. So I would run one of those tools, and check all drives.

Stay with the passive approach, and use external WiFi. You will have no driver issues with this, because it uses the Ethernet plug:

https://www.amazon.com/dp/B07Z1SGWL5

Looks like LE can't unmount all drives. kodi.old.log contains more info about the last faulty shutdown.

• activate log level 1 by creating an advancedsettings.xml file
• reboot
• replicate the issue by shutting down
• reboot
• login by SSH
• open kodi.old.log by using the editor: nano /storage/.kodi/temp/kodi.old.log
  
• copy and paste the content to PasteBin
• post the resulting URL, so we can have a look
• close the editor by Strg + X

I had a short conversation with developers. Nobody knows the cause of the color errors. The error I mentioned is very likely not the cause. So all I can say is, stay with Generic-legacy, until the next LE update appears. Switching between Generic and Generic-legacy should work, because all hardware drivers are the same.

Quote from dsy4711

here the log.

in both streams from Netflix - wrong black level and the flickering

http://ix.io/4rZZ

Thanks. Maybe an FFMPEG issue. A developer should have a look:

2023-03-27 21:37:28.221 T:965     debug <general>: CDVDVideoCodecFFmpeg - Updated codec: ff-h264-vaapi
2023-03-27 21:37:28.225 T:889      info <general>: CActiveAESink::OpenSink - initialize sink
2023-03-27 21:37:28.232 T:965     error <general>: ffmpeg[0x542d0c0]: [h264] mmco: unref short failure

Quote from thedogg

Please have a look at that one. I have updated libreelec to its latest version and the problem occurs.

http://ix.io/4s2q

DRM Prime problem:

2023-03-28 12:06:16.459 T:1323    error <general>: CDVDVideoCodecDRMPRIME::AddData - send packet failed: End of file (-541478725)
2023-03-28 12:06:16.460 T:1268     info <general>: Skipped 7 duplicate messages..

You can use the usb-devices command, but I don't think it's helpful. There are not too many device classes in the keymaps folder, so I would trial-and-error to find the right XML.

Quote from Ainuke

Where do I locate the .xml for the volume knob?

You have to create a key mapping file. LE has default key mapping files.Those files are located at /usr/share/kodi/system/keymaps,

They are read-only. You can overwrite any of these files by creating your own version at /storage/.kodi/userdata/keymaps.

Read about key mapping details here: Click!

Quote from dsy4711

I can confirm the behavior with Generic. Legacy runs normally

For me it looks like all DRM streams are affected (Netflix , Amazon..).

Sometimes a stream starts normally without the flickering. After stop and start from the beginning the same stream flickers.

Sometimes the black level is also wrong (black is gray).

Newer hardware does not solve the problem (Intel I3 12.th Gen)

If you want to help to find the bug, give us a log file.

The window manager also handles video output, so the story makes sense to me.

Link to error message doesn't work. Please edit your post.