Package Details: obs-studio-browser 30.2.3-4

Git Clone URL: https://aur.archlinux.org/obs-studio-browser.git (read-only, click to copy)
Package Base: obs-studio-browser
Description: Free and open source software for video recording and live streaming. With everything except service integration
Upstream URL: https://github.com/obsproject/obs-studio
Licenses: GPL-2.0-or-later
Conflicts: libva-vdpau-driver, obs-browser, obs-linuxbrowser, obs-studio, obs-vst, obs-websocket
Provides: obs-browser, obs-studio, obs-vst, obs-websocket
Submitter: ashpie
Maintainer: tytan652
Last Packager: tytan652
Votes: 21
Popularity: 0.106985
First Submitted: 2020-11-05 09:36 (UTC)
Last Updated: 2024-11-12 09:58 (UTC)

Required by (144)

Sources (5)

Pinned Comments

tytan652 commented on 2023-01-13 07:52 (UTC) (edited on 2023-01-13 07:52 (UTC) by tytan652)

For those who might ask why libva-vdpau-driver was added to conflicts.

It is the only way at package level to prevent the user to have segfaults because of this driver. This will not be fixed on OBS side since this is not an OBS issue.

The driver is only loaded with Nvidia cards.

Try libva-nvidia-driver if you really need Nvidia decode through VAAPI.

tytan652 commented on 2022-07-08 06:02 (UTC)

This package have some dependencies with version check, it will allow you to rebuild the package only when your system is correctly updated. This feature is not enabled on Manjaro.

If you have any issue, please before commenting rebuild this package (a clean build) and try again to make sure it's not because of a library update.

Pamac has a messed up dependency checker, use another AUR helper for the first install.

This AUR package provide OBS with all the missing feature except Twitch, Restream and YouTube integrations.

More explaination here: https://ideas.obsproject.com/posts/1558/

It provide any dependency needed for Wayland support.

I'm quite active on OBS discord server (don't PM me directly).

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 13 Next › Last »

Sandwich commented on 2023-12-11 13:19 (UTC) (edited on 2023-12-11 13:19 (UTC) by Sandwich)

@tytan652 thank you for the short explanation.

I understand the desire for full self-compilation, but I'm puzzled by the conflicting dependencies—specifically, ffmpeg-obs and vlc-luajit. I've removed them and substituted CEF with the precompiled version. So far, I haven't encountered any segfaults or issues with the VAAPI and AV1 encoder, but my testing was brief.

Adding another obs-studio package to the AUR might be excessive, so I'm maintaining this fork locally. Perhaps we could seek a solution regarding "ffmpeg-obs and vlc-luajit," such as making them optional dependencies.

Personally, I'm not keen on replacing my ffmpeg and vlc with these alternatives. Unsure how others feel about it, but ill preference to stick with the original versions.

tytan652 commented on 2023-12-11 11:05 (UTC) (edited on 2023-12-11 11:06 (UTC) by tytan652)

@Sandwich

is there any reason why this Package compiles ffmpeg-obs?

Maybe the one listed in ffmpeg-obs PKGBUILD and pinned comments.

Is it also possible to include the cef binery?

NO and I don't want to make longer explanation.

Sandwich commented on 2023-12-11 10:42 (UTC)

Hallo, is there any reason why this Package compiles ffmpeg-obs?

The obs-studio-amf package is using the native one without any issues.

Is it also possible to include the cef binery? This would safe a lot of time and issues with the compilation! Also, I personally don't want to replace my system's FFmpeg with ffmpeg-obs

Adding CEF binary could be done like this:

source=(cef_binary_5060_linux64.tar.bz2::https://cdn-fastly.obsproject.com/downloads/cef_binary_5060_linux64.tar.bz2)

build() { ... cmake ... -DCEF_ROOT_DIR="../../cef_binary_5060_linux64" ... }

sikha commented on 2023-10-08 00:38 (UTC)

If your build is failing like below:

[ 55%] Linking C executable obs-x264-test
/usr/bin/ld: warning: libdav1d.so.6, needed by /usr/lib/libavcodec.so.60, not found (try using -rpath or -rpath-link)
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_default_settings'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_get_picture'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_version'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_data_wrap'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_send_data'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_flush'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_parse_sequence_header'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_data_unref'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_open'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_data_wrap_user_data'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_picture_unref'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_get_event_flags'
/usr/bin/ld: /usr/lib/libavcodec.so.60: undefined reference to `dav1d_close'
collect2: エラー: ld はステータス 1 で終了しました
make[2]: *** [plugins/obs-x264/CMakeFiles/obs-x264-test.dir/build.make:114: plugins/obs-x264/obs-x264-test] エラー 1
make[1]: *** [CMakeFiles/Makefile2:1622: plugins/obs-x264/CMakeFiles/obs-x264-test.dir/all] エラー 2

Rebuild ffmpeg-obs prior to updating this package. extra/dav1d received an update this week that bumped the .so version number.

AgentLoneStar007 commented on 2023-08-16 18:54 (UTC)

Package fails installation with the following output: https://gist.github.com/AgentLoneStar007/3b335dcbd0f352d17890fba655426cfd I've tried it with and without --noconfirm. Neither works.

tytan652 commented on 2023-05-04 09:42 (UTC)

The patch in question just got replaced, the sha256sum should be fine now.

Typology commented on 2023-05-04 09:33 (UTC)

shasum for the gcc patch is wrong. this is the correct one: 450cbf6df2b14ec8f9c43c1c7d44b06ab1b10c38eae6d1048eebffb4ca16e569 NOT 450cbf6df2b14ec8f9c43c1c7d4b06ab1b10c38eae6d1048eebffb4ca16e569 there's a missing 4 for some reason.

tytan652 commented on 2023-05-04 08:32 (UTC)

GCC 13 introduced some maybe-uninitialized warnings. Those should be fixed.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 13 Next › Last »