Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ich777

Community Developer
  • Joined

  1. ich777 changed their profile photo
  2. I don't see anything suspicious in your Diagnostics. How did you test if transcoding is working, did you force a transcode, if yes on which client (iOS, Android, Browser), did you made sure that this is a media file without burnt in subtitles (since these are nutritious to cause the CPU go wild in combination with Plex), also do note that audio transcoding is done on the CPU not GPU (just if audio needs to be transcoded). Please do also note that Plex transcodes in chunks so to speak, it will transcode, then pause the transcode, transcode, pause to transcode and so on. Do you also have the capabilities variable in your Docker template as pointed out in the second thread.
  3. I'm not familiar what Viseron is. However if everything is now working, glad that it's solved. :)
  4. Sorry but I'm not into modding, I assume the container would support that but I'm not too sure about that. You can copy whatever you like and add startup parameters to the template, maybe that will help you. I can only give support for the container if something isn't working and the container in general is working. :D
  5. These are Kernel Panics, not sure if the Module causes that or Frigate: ``` Jun 13 19:13:20 tower-one kernel: WARNING: CPU: 2 PID: 12957 at ./include/linux/rwsem.h:80 find_vma+0x28/0x60 ``` I would recommend that you ask in the Frigate support thread.
  6. Only Diagnostics would give me a full picture. However, is something not working?
  7. IIRC SotF needs a public IP so to speak a direct accessible connection from outside to work properly, I think there is no LAN only switch for that game.
  8. Okay, about what container are we talking about?
  9. Wrong support thread since the driver is meant to be not used if you are using the card in a VM: Please create a post in the General Subforums.
  10. This is really strange, however please do note that I deprecated TheLounge over a year ago, if possible, please switch over to the container from Linuxserver.io if possible. However if the container was running up until now I assume that something in appdata got corrupted or isn't there where it should be. Maybe look if everything is okay with your appdata directory since the deprecation won't affect the function from the container.
  11. No, this is just when you get the message in your logs. Nothing that I can do about that since this is related to steamcmd and not the container.
  12. Please do the following: Stop the container Delete the steamapps folder from your rust directory Start the container
  13. The GitHub page says it supports up to Kernel 6.14 (Open Source) and the script that they've linked includes only their closed source drivers, not the open source ones from GitHub. Download the script and see for yourself, the script downloads a tar archive from their site.
  14. Where did you test the transcoding? Did you test that in the WebPlayer, the WebPlayer is known to have issues when switching quality, have you yet tried it with a native App (Android/iOS). Please also do keep in mind that if you have burnt in subtitles in the media file that this will use a lot of CPU when playing back the file. Did you tried it with different media files? EDIT: I don't see anything wrong in your Diagnostics.
  15. Sorry, I'm not a huge fan from what you are proposing since this indeed could work but please also do note that this could go horribly wrong. I would rather see that this gets actually mode upstream since I really don't know if that's the way to go.
  16. It seems that this is some kind of new hardware revision, if you search for your dmesg output from above you'll find several posts online with similar issues but all with other card ID's I'm not too sure what's going on here.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.