CatxFish / obs-v4l2sink

obs studio output plugin for Video4Linux2 device
GNU General Public License v2.0
926 stars 97 forks source link

deb plugin is not installed in the correct directory #14

Open displague opened 4 years ago

displague commented 4 years ago

The released Debian package for the OBS plugin does not install the plugin in the correct directory (Ubuntu 19.10 / Eoan).

Work-around is:

cd /usr/lib/x86_64-linux-gnu/obs-plugins
sudo ln -s ../../obs-plugins/v4l2sink.so
Erudition commented 4 years ago

Ah! So that's why it wasn't showing up in OBS. Works now! Thanks

LDVSOFT commented 4 years ago

@displague May I ask you how you've build the plugin, it does not work for me? Sorry, worked now after clean retry.

3vi1 commented 4 years ago

Confirmed on Ubuntu 20.04 as well. Thanks for workaround.

alexfornuto commented 4 years ago

Or if you're using Fedora, symlink to ~/.config/obs-studio/plugins/v4l2sink/bin64.

:wave: @displague

motrengaw commented 4 years ago

On Debian Stretch: Have both linked and simply copied v4l2sink.so into /usr/lib/obs-plugins from /usr/lib/x86_64-linux-gnu/obs-plugins per the above. Still not seeing 'V4L2 Video Output' or anything like it in the tools pull-down of OBS. Built clones OBS 25.0.7. and this git. Where else can I put this so that OBS will find it??? Or do I need to refresh OBS plugins somehow?? Very frustrating.

alexfornuto commented 4 years ago

@motrengaw do you have a plugins directory in ~/.config/obs-studio/, as I noted for Fedora above?

pturmel commented 4 years ago

Using Ubuntu 18.04 LTS with the OBS PPA, this copy of the shared object is not required. The PPA expects OBS plugins to be in /usr/lib/obs-plugins/.

ppGodel commented 4 years ago

Or if you're using Fedora, symlink to ~/.config/obs-studio/plugins/v4l2sink/bin64.

wave @displague

for Fedora the correct path is ~/.config/obs-studio/plugins/v4l2sink/bin/64bit/

displague commented 4 years ago

https://github.com/CatxFish/obs-v4l2sink/pull/35 looks like the fix for this

prasket commented 3 years ago

35 looks like the fix for this

I agree and thank you for bringing this up, helped me out!

Should this issue be closed and pointed to #35