Package Details: obs-v4l2sink 0.1.0-4

Git Clone URL: https://aur.archlinux.org/obs-v4l2sink.git (read-only, click to copy)
Package Base: obs-v4l2sink
Description: v4l2 output for obs-studio
Upstream URL: https://github.com/CatxFish/obs-v4l2sink
Licenses: GPL
Submitter: skystrife
Maintainer: luzifer
Last Packager: luzifer
Votes: 5
Popularity: 1.22
First Submitted: 2018-09-17 21:48
Last Updated: 2020-05-19 19:00

Pinned Comments

ekce commented on 2020-07-20 01:36

Just some remarks about using this.

  1. You need to have v4l2loopback-dkms installed (and linux kernel headers as well).

  2. Run sudo modprobe v4l2loopback, this will load the kernel module and create a new video device like /dev/video0 but the number may vary, like it may be /dev/video1 or something (use ls -l /dev/video* to see which device was created when you ran that command)

  3. In OBS-Studio click on Tools and go to the v4l2sink option. Make sure you select the newly created video device to loopback into (if you pick the wrong number you might get an error saying format unsupported or something).

  4. After the loopback starts you should be able to see it as a new dummy camera device or something like that in your other programs (eg. you can set it as your camera in Zoom).

Latest Comments

1 2 Next › Last »

skerit commented on 2020-08-01 08:53

I no longer get the v4l2sink option in the OBS tools menu, even though the v4l2loopback has been loaded successfully.

Edit: I had the flatpak version installed of OBS. And even though I used to be able to separately open the flatpak & the AUR version, since the last gnome upgrade this doesn't seem to be the case anymore. I just removed the flatpak version & reinstalled obs, and it's working now!

luzifer commented on 2020-07-20 10:16

@ekce: Thanks for writing this short introduction how to use the plugin! I've pinned your comment so it won't just vanish…

ekce commented on 2020-07-20 01:36

Just some remarks about using this.

  1. You need to have v4l2loopback-dkms installed (and linux kernel headers as well).

  2. Run sudo modprobe v4l2loopback, this will load the kernel module and create a new video device like /dev/video0 but the number may vary, like it may be /dev/video1 or something (use ls -l /dev/video* to see which device was created when you ran that command)

  3. In OBS-Studio click on Tools and go to the v4l2sink option. Make sure you select the newly created video device to loopback into (if you pick the wrong number you might get an error saying format unsupported or something).

  4. After the loopback starts you should be able to see it as a new dummy camera device or something like that in your other programs (eg. you can set it as your camera in Zoom).

luzifer commented on 2020-05-19 18:59

Thanks for the heads-up! There was a missing step in the updater-script… This is now fixed and should be in here within a minute…

Ricky_cezar commented on 2020-05-19 18:56

The checksum hash for the second file is wrong. This is the right list of checksums:

sha256sums=('83e9bb104dcc3840acd17ebc0810de30c8de27545d4ef181d58f8a375dba06d4'
            'ef1179c23256c312212e3dce9083d4fa67751db05c3001ad824e2b6995943941'
            '617e017562ab3ca85fffa86c869fa778e26ee0694e0ae8dd1b8b110bff1bb6cc')

dack commented on 2020-05-19 18:55

Just a heads up - with the latest PKGBUILD update, I think you have missed updating the sha256sum for the OBS source. You've got obsver=25.0.8, but the hash matches the obs 25.0.4 source.

Thanks for maintaining this package!

kIERO commented on 2020-04-24 19:10

Thank you @0xrayn that worked for me too.

luzifer commented on 2020-04-20 18:45

@dack already created an orphan-request with the same intention :D

dack commented on 2020-04-20 18:44

@benoliver999 A patch could be included in AUR, to address the v4l2device_close issue until such time as upstream decides to merge the change. I wouldn't hold my breath waiting for upstream, since they haven't had a commit in 2 years.

@skystrife Are you still interested in maintaing this AUR package? If not, I'd be willing to take it over.

benoliver999 commented on 2020-04-07 11:23

Thank you @0xrayn that worked for me.

@skystrife there is nothing that can be done about the upstream fix needed, a pull request has been submitted.

However, the PKGBUILD should be updated to keep in sync with the current arch version of OBS - 25.0.4 right now.