Econaut

Blimey... I tried probably a dozen times before on different days, all failed. Randomly tried again after posting this and it worked.

Whenever I do, the page just reloads and Stable is still selected. This is a new install with key (not trial). Maybe related maybe not but plugin updating also seems to be having trouble all of a sudden. Worked for a while and now nothing.

mkvpropedit isn't used and not necessary, at least 90% of the time. I think maybe a few plugins use it but if in doubt, yours probably arent.

Is there AMD GPU support? I have an R9 390x I would like to use. I don't think it does H.265 or 4k for that matter but locally with handbrake using AMD VCE, it does 1080p H.264 like a champ.

I did also install that plugin though I thought it wasn't necessary above 6.10. Glad you got it working.

I can share what I remember: Use official Emby docker. Put this in the config: I recall it just working essentially. If it's not for you, share some of your details and I can compare.

Would be great if UNRAID would include SPICE support natively for VMs. The VNC remote viewer is super buggy and copy-paste doesn't even really work.

Working great for me so far.

Seeing same issue myself, haven't touched config in months and it's been working but now it seems nothing is connecting and I cannot view web UI. Edit: Rebooted Unraid, left this docker stopped, did a force update, then started again watching logs and now it's got an accessible web GUI again. Very odd but can't say the force update definitively helped it or was just coincidence.

Thanks - my mistake, I had an IP conflict. br0 does not know how to draw from the existing DHCP pool or something.

Can this be used with a custom bridge interface (own DHCP IP) ? None of the IP:Port combinations give me the web UI. Log shows this repeating: Start Logitech Media Server... Can't call method "log" on an undefined value at /usr/share/squeezeboxserver/CPAN/Log/Log4perl/Appender.pm line 189. [21-12-05 04:43:39.1733] main::init (390) Starting Logitech Media Server (v8.2.1, 1634705759, Wed Oct 20 07:17:47 CEST 2021) perl 5.030000 - x86_64-linux-gnu-thread-multi [21-12-05 04:43:39.3731] Slim::Utils::SQLiteHelper::postConnect (377) Optimizing DB because of missing or empty sqlite_stat1 table [21-12-05 04:43:39.4102] Slim::Schema::forceCommit (2177) Warning: Trying to commit transactions before DB is initialized! [21-12-05 04:43:39.5122] Slim::Utils::SQLiteHelper::postConnect (377) Optimizing DB because of missing or empty sqlite_stat1 table [21-12-05 04:43:39.5244] Slim::Schema::forceCommit (2177) Warning: Trying to commit transactions before DB is initialized! [21-12-05 04:43:39.9491] Slim::Utils::SQLiteHelper::postConnect (377) Optimizing DB because of missing or empty sqlite_stat1 table [21-12-05 04:43:39.9547] Slim::Schema::forceCommit (2177) Warning: Trying to commit transactions before DB is initialized! Are there prerequisites?

Is this plugin necessary/beneficial for 6.10 ?

Neat - how long until that gets into Plex official docker I wonder...

Worked for me with xx:2202/ubooquity/opds-comics/ but from what I can tell the Kuboo app is just awful and you have to force close it when changing server to get it to refresh. Even when adding multiple directories (books & comics for instance) you still have to manually switch your active server and do this force close nonsense - pretty lame. Once you get past that, it's decent.

What are the known issues? What can be done safely? Reading the most recent comments, this seems to have compatibility issues with the 6.10.0-rc1 version? Any way to view the progress as it's backing up?

Also interested in this info.

Yup that one worked for me. Also used the Emby docker (official) and used the same Device passthrough /dev/dri - select VAAPI in server config. Both worked great for me. Using a 5700G. Tried with official Plex docker and that was a failure.

I have an AMD APU that I can pass through to Jellyfin or Emby docker containers but it seems like I cannot pass it through to both at once. Can anyone else confirm if this is supposed to work or if it's possible to share the same GPU with multiple docker containers for hardware acceleration?

Might be a nice addition to default these values (at least specifying the Network interface as tun0):

Gotcha - thanks for the reminder - it was probably the audio. Yeah the 2 discrete GPUs are bound to VFIO (still can't get passthrough working for them but they are bound anyway). Ok cool, good to know how that would manifest otherwise, thanks!

Yes I did read that and installed & set that up. At first there was huge CPU usage which could have just been something else... and very minimal GPU usage but then the CPU usage settled after a while and the GPU usage continued low. Looks like it's working great 👍 Was hoping Jellyfin may be more definitive on it's own (I am using hardware vs software for instance). I do actually have 3 AMD GPUs plugged into this system (one integrated, two discrete) I don't suppose /dev/dri specifies one over another or if maybe just the primary is selected?

Yes indeed - at first I was unable to log in to your container perhaps because I already had the binhex container. Seems like it was a port conflict and changing the port allowed it to work. Dumb question... but how can I differentiate between cpu & gpu transcode?

I am not sure how to check but the binhex jellyfin docker does not work with the device passthrough as such. Probably missing the sufficient mesa version?: https://jellyfin.org/docs/general/administration/hardware-acceleration.html Seems like AMF may be on the horizon for support here but maybe not until it's available through the open source amdgpu driver module.

Noticed there's an AMD AMF option for transcoding - is that usable on certain hardware?

Yes I am on 6.10.0-rc1 - does that mean I don't need to add the modprobe line to the /boot/config/go file? If I add the same parameter as is in your docker config to other docker containers (Device with value /dev/dri ) that will allow the other containers to use the hardware? (I guess just Emby additionally maybe)? You may be right, Plex has this posted in their article: