Jump to content

Hardware Acceleration with NVIDIA under FreeBSD?


martijnk

Recommended Posts

martijnk

Hi all,

 

Been a long time Plex user for 3-4 years now, but I don't like the way where it's going so I'm looking for alternatives and people recommended Emby. Now I've noticed that with Emby 4.0 hardware acceleration got a big improvement.

 

I have a Quadro P2000 and with Plex it supports only decoding under FreeBSD not encoding which is forcing me to use Windows which is not an option as my entire library is on a ZFS and I don't want to change it.

 

Long story short, does Emby fully support the Quadro P2000 under FreeBSD or is the same with Plex, so only Intel Quick Sync?

 

Thanks!

 

Link to comment
Share on other sites

Hi, we have not tested Nvidia on FreeBSD yet. It is possible for the future though.

 

In the meantime, if you can manage to get Nvidia drivers installed on FreeBSD, then you can always try it. There's nothing in Emby preventing it from working on FreeBSD, we just don't know yet if it actually will.

 

Thanks.

  • Like 1
Link to comment
Share on other sites

unhooked

nvidia linux drivers (which is what we get) only support encoding for now, you have to use quickstep still for decoding so libva/drm kernel modules and such. But whenever I try to enable it in emby, the ui just spins forever because it's not getting results from something.

 

Could also be my hardware though as my newest running freebsd is a 4th gen i5 and I just started playing with that stuff again after migrating my desktop last week.

Link to comment
Share on other sites

martijnk

if plex uses ffmpeg that uses the nvidia freebsd driver to utilize encoding i don't see why emby should have problems. :D

 

Plex says they are using an older implementation of ffmpeg.

Link to comment
Share on other sites

makarai

I am by far not an expert on this but I think ffmpeg just needs to support nvenc in order to support the hardware part, and I am quite sure that the newer versions will have that.

 

Why don't you just give it a try? I'd do it but I don't have any hard for it :(

Link to comment
Share on other sites

makarai

No it's more than that. Drivers are also needed.

 

yeah thats what i wrote in the comment before. And the nvidia driver in freebsd are quite established. https://www.nvidia.com/object/freebsd-x64-archive.html and if plex manages to achieve hardware transcoding on freebsd i don't see why emby would not

Edited by makarai
Link to comment
Share on other sites

unhooked

Can you provide a server log? I'm curious to see that. Thanks !

I'll dig for it next time it happens, but I think the timeouts happen when changing the transcode space to something that doesn't exist /tmp/emby instead of /tmp. The other options don't seem to trigger it.

Link to comment
Share on other sites

unhooked

yeah thats what i wrote in the comment before. And the nvidia driver in freebsd are quite established. https://www.nvidia.com/object/freebsd-x64-archive.html and if plex manages to achieve hardware transcoding on freebsd i don't see why emby would not

encode isn't the problem, the nvidia drivers don't support decoding yet. You have to use intel quicksync for that (via the drm kmod).

Link to comment
Share on other sites

I'll dig for it next time it happens, but I think the timeouts happen when changing the transcode space to something that doesn't exist /tmp/emby instead of /tmp. The other options don't seem to trigger it.

 

No, the server will create the transcoding temp folder if it doesn't already exist. Best thing to do is attach the server log and then we don't have to guess anymore :)

Link to comment
Share on other sites

unhooked

No, the server will create the transcoding temp folder if it doesn't already exist. Best thing to do is attach the server log and then we don't have to guess anymore :)

That doesn't seem to be the case, setting transcode space to /tmp is fine and setting save, if I set them to /tmp/emby and click save I get the spins.

 

This is all that's in the logs:

2019-01-25 18:38:21.548 Info HttpServer: HTTP GET http://192.168.0.10:8096/emby/System/Configuration/encoding. UserAgent: Mozilla/5.0 (X11; FreeBSD amd64; rv:64.0) Gecko/20100101 Firefox/64.0

2019-01-25 18:38:21.549 Info HttpServer: HTTP Response 200 to 192.168.0.10. Time: 1ms. http://192.168.0.10:8096/emby/System/Configuration/encoding

2019-01-25 18:38:21.553 Info HttpServer: HTTP POST http://192.168.0.10:8096/emby/System/Configuration/encoding. UserAgent: Mozilla/5.0 (X11; FreeBSD amd64; rv:64.0) Gecko/20100101 Firefox/64.0

2019-01-25 18:38:21.559 Info HttpServer: HTTP Response 404 to 192.168.0.10. Time: 6ms. http://192.168.0.10:8096/emby/System/Configuration/encoding

 

Link to comment
Share on other sites

It's really hard to say. I don't see much evidence there of a problem relating to the temporary transcoding path.

Link to comment
Share on other sites

unhooked

Yeah I know, it's not tossing up any errors.

Default saves fine ( but I don't want to transcode to my ssd).

/tmp saves fine. (and encoding.xml is created)

/tmp/emby (just sits there spinning)

if I make /tmp/emby2 it saves fine (but that will never exist between reboots -tmpfs)

/Shared/emby (times out unless I create the directory first - zfs pool).

/mnt/Shared/emby (times out -nfs share)

 

When it fails it seems to spit out a 404, but that looks the same as a 200.

2019-01-25 21:51:41.150 Info HttpServer: HTTP Response 404 to 192.168.0.10. Time: 1ms. http://192.168.0.10:8096/emby/System/Configuration/encoding
 

and that's with debug turned on.

Link to comment
Share on other sites

unhooked

This one?

 

equesting url without automatic networking: http://192.168.0.10:8096/emby/Encod
ing/CodecConfiguration/Defaults apiclient.js:1:12885   
This site appears to use a scroll-linked positioning effect. This may not work w
ell with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Pe
rformance/ScrollLinkedEffects for further details and to join the discussion on
related tools and features! index.html
Requesting url without automatic networking: http://192.168.0.10:8096/emby/Syste
m/Configuration/encoding apiclient.js:1:12885
Requesting url without automatic networking: http://192.168.0.10:8096/emby/Syste
m/Configuration/encoding apiclient.js:1:12885
Unexpected value NaN parsing y1 attribute. markup.js:336:6
Unexpected value NaN parsing y2 attribute. markup.js:336:6
Unexpected value NaN parsing x1 attribute. markup.js:336:6
Unexpected value NaN parsing x2 attribute. markup.js:336:6
Unexpected value NaN parsing y1 attribute. markup.js:336:6
Unexpected value NaN parsing y2 attribute. markup.js:336:6
Unexpected value NaN parsing x1 attribute. markup.js:336:6
Unexpected value NaN parsing x2 attribute. markup.js:336:6
Unexpected value NaN parsing y1 attribute. markup.js:336:6
Unexpected value NaN parsing y2 attribute. markup.js:336:6
Unexpected value NaN parsing x1 attribute. markup.js:336:6
Unexpected value NaN parsing x2 attribute. markup.js:336:6
Unexpected value NaN parsing y1 attribute. markup.js:336:6
Unexpected value NaN parsing y2 attribute. markup.js:336:6
Unexpected value NaN parsing y1 attribute. markup.js:336:6
Unexpected value NaN parsing y2 attribute. markup.js:336:6
Unexpected value NaN parsing x1 attribute. markup.js:336:6
Unexpected value NaN parsing x2 attribute. markup.js:336:6
Unexpected value NaN parsing y1 attribute. markup.js:336:6
Unexpected value NaN parsing y2 attribute. markup.js:336:6
app is hidden apphost.js:1:5166
 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...