Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardware acceleration support? #67

Closed
DX37 opened this issue Aug 4, 2022 · 7 comments · Fixed by #69
Closed

Hardware acceleration support? #67

DX37 opened this issue Aug 4, 2022 · 7 comments · Fixed by #69
Labels
question Further information is requested

Comments

@DX37
Copy link

DX37 commented Aug 4, 2022

Hello there! Using Neko recently, figured how to pass render devices through to docker image and enabled NEKO_HWENC for better stream encoding performance.

But in neko-rooms I don't see such options or fields to specify it manually, only NEKO_HWENC: true, which cause created room to collapse due to lack of render devices.

Can it be implemented? Is there temporary solution alongside using Neko without rooms?

@m1k1o
Copy link
Owner

m1k1o commented Aug 4, 2022

You should be able to set NEKO_HWENC=VAAPI env variable, add /dev/dri to mounts whitelist and mount it as public path. That should be enough, to get it working.

@m1k1o m1k1o added the question Further information is requested label Aug 4, 2022
@DX37
Copy link
Author

DX37 commented Aug 4, 2022

You should be able to set NEKO_HWENC=VAAPI env variable, add /dev/dri to mounts whitelist and mount it as public path. That should be enough, to get it working.

Nope, that didn't worked. Created room-container falling in fatal state, saying no vaapivp8enc element or no vaapih264enc element. I tested hardware encoding separately, without rooms and with devices, and it's working on my PC.

@DX37
Copy link
Author

DX37 commented Aug 4, 2022

That's weird, because with mounting and without setting NEKO_HWENC=VAAPI I can see /dev/dri or any other dirs mounted.

изображение

@DX37
Copy link
Author

DX37 commented Aug 4, 2022

Hey, can it be because of different groups of card0 and renderD128? This is from Neko without rooms.

изображение

@m1k1o
Copy link
Owner

m1k1o commented Aug 4, 2022

I don't have such GPU, so I cannot help further. Here is original PR m1k1o/neko#151 for that, maybe the author can help you with that

@DX37
Copy link
Author

DX37 commented Aug 5, 2022

I don't have such GPU, so I cannot help further. Here is original PR m1k1o/neko#151 for that, maybe the author can help you with that

I'm not asking for help with GPU support, I asking is there a way to add option for adding docker-compose devices string for rooms creating, if simple mount not working? Like these:

devices:
- /dev/dri/renderD128:/dev/dri/renderD128
- /dev/dri/card0:/dev/dri/card0

@m1k1o
Copy link
Owner

m1k1o commented Aug 5, 2022

No, that is not possible with neko-rooms yet. This is how it could look like: 35d2958 Or alternatively just implementing gpu: enum for room and it mounts correct devices/sets correct env.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants