4 ms·
Did you try purging the dkms version and building the one in the post? I also spent an inordinate amount of time messing with it, but in the end the actual ste
by luxpir 7y ago
Did you try purging the dkms version and building the one in the post?
I also spent an inordinate amount of time messing with it, but in the end the actual steps that worked were simple. I couldn't get it to work with my flatpak version, and Debian stable is not fun trying to compile OBS (need more recent version of cmake).
But Ubuntu should be more straightforward... Did you get the option in the Tool menu yet? The other thing I got reading through all the GitHub issues was the need to sometimes change the YUV setting in that dialogue to YU2 (from memory).
Hope you get it cracked without much grief, and I can share what I can remember fwiw.
- joecot 7y agoI did attempt purge DKMS, and confirmed the kernel module is the one I've just compiled. I have it in the tool menu in OBS Studio. If I start the stream with RGB the camera doesn't work. If I start it with YUV32 as suggested in most guides, OBS just segfaults. switching it to YU2 was a helpful hint -- it just doesn't work as opposed to segfaulting.
- luxpir 7y agoAnother quick thought, did you check you're using the right device? In that tool menu dialogue you could switch it to 0 instead of 1 etc or try grepping for the device list... And can you view the device in VLC even when RGB? There are individual settings per input for RGB/YUV etc which I think default to the latter.
- joecot 7y agoI updated the top comment, but you got me looking closer at the device list. It seems that v4l2loopback and my webcam were interfering with each other. rmmod-ing v4l2loopback, running the mopprobe myself, unplugging my webcam and plugging it back in seemed to resolve it.
- luxpir 7y agoEyy, victory. Linux, the OS you love to hate. Wouldn't have it any other way.