saarg

It will be available when it's available. Asking when it's released won't make it appear any faster. We have a life also and it's not all of us that does the compiling.

As far as I remember, Q35 is needed to get the AMD audio driver to still work after the first reboot after the driver install. The workaround I used was to install the windows audio driver, but that only supports 2 channel audio. I didn't try this myself as the server was occupied most of the time and then had a breakdown. New hardware don't play nice with the RX480, so had to install a nvidia card. Still have one RX480 in the server that I can test with if I get the time tomorrow. However, I feel it's a little bit too drastic to remove it from being able to select.

Seeing that this is all windows CVE except one that affects linux and also need local user access, it's not a high risk of being attacked. Unless you have shady friends visiting Edit: Didn't flip the page to see the other guys already answering... Too little beers!

You don't need vt-d or vt-x support for this plugin to work. It still passes the GPU to the container.

The list in system devices is just a lspci, so it should be listed. Probably best to post a diagnostic and also the output of running lspci manually.

I'm not sure about that. Let me test it and come back to you.

Isn't it better to switch the servers? Copy from the unraid vm to the bare metal one? That way the writing happens on the supported unraid.

No need to apologize 🙂 I didn't remember that @tidusjar was here.

This is a question for the developers, not us.

I don't think you have to worry about which version it is, as there will be a hundred posts asking when our image will get updated to it 😆 I don't think we have any intention to post specific versions here. I do think the specific version will be available on the tag page on dockerhub. The new buildsystem will build the new version when it's available and (as far as I know) tag the specific version.

We don't know the limits of the cards, so this is something you have to figure out yourself. The cards doesn't have unlimited power. It also depends on what you transcode.

You should not need to restart every few days.

The vaapi errors might have something to do with it. Might be something in binhexs emby container. You don't pass through an igpu? Can you test installing the original emby container and see if that works?

Your screenshot clearly said that you did not have a Emby premier subscription. Yes I can read Danish. Did you restart emby after adding the subscription? I don't see --runtime=nvidia added in the extra parameters field.

Your screenshot from Emby clearly says you need an active Emby premier subscription for hardware acceleration to work.