Linux browser obs studio

Arch Linux User Repository

Search Criteria

Package Details: obs-linuxbrowser 0.6.1-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/obs-linuxbrowser.git (read-only, click to copy)
Package Base:	obs-linuxbrowser
Description:	Browser source plugin for obs-studio based on CEF. Alternative to obs-qtwebkit.
Upstream URL:	https://github.com/bazukas/obs-linuxbrowser
Keywords:	browser obs obs-qtwebkit plugin
Licenses:	GPL
Conflicts:	obs-linuxbrowser-bin
Submitter:	NexAdn
Maintainer:	None
Last Packager:	NexAdn
Votes:	12
Popularity:	0.000320
First Submitted:	2017-04-01 14:55
Last Updated:	2019-04-06 16:57

Dependencies (14)

• atk (atk-git)
• gconf (gconf-gtk2)
• libxcomposite
• libxrandr (libxrandr-git)
• libxss
• nss (nss-hg)
• pango (pango-ubuntu, pango-minimal-git, pango-git)
• obs-studio>=21.1.2 (obs-studio-git, rpan-studio, obs-studio-rc, obs-studio-tytan652, obs-studio-browser, obs-studio-ftl, obs-hevc-vaapi-git)
• cef-minimal (cef-git, cef-standard, cef-minimal-obs-studio-browser-bin) (make)
• cmake (cmake-git) (make)
• git (git-git, git-vfs) (make)
• make (make3, make-git) (make)
• cef-minimal (cef-git, cef-standard, cef-minimal-obs-studio-browser-bin) (optional) – Up-to-date browser backend
• pepper-flash (pepper-flash-debug) (optional) – Flash support

Required by (0)

Sources (1)

Latest Comments

TrashDwellTroll commented on 2021-09-05 20:48

For some reason, I cannot install this. Edit: Seems like the main issue is missing native_blob.bin

GI_Jack commented on 2020-12-14 14:20

Does this REALLY need gconf as a dependency?

manouchk commented on 2020-10-09 04:55

cef-minimal 80.0.8-1 was installed but

Build failed with this errors

— Looking for Chromium Embedded Framework in /opt/cef — Found CEF: /opt/cef/Release/libcef.so
CMake Error at CMakeLists.txt:38 (file): file COPY cannot find «/opt/cef/Release/natives_blob.bin»: No such file or directory.

filiphanes commented on 2020-06-19 08:44

Using obs-studio-git I got working OBS Browser source. Even without cef-minimal-3770. obs-linuxbrowser-bin has conflicting files with obs-studio-git so I had to uninstall it before.

lorecast162 commented on 2020-05-03 17:17

@Leeo97one unfortunately they closed the bug with reason «Won’t implement»

Leeo97one commented on 2020-04-20 11:29

StormEngineer commented on 2020-04-08 12:03

The Github page for this says it’s archived because OBS ships with a source now that works on Linux, but this does not seem to be the case, I still don’t have browser source in OBS 25. So what? Can someone contact bazukas and let them know? I was unable to find a way to contact them.

cobaltspace commented on 2020-03-03 03:56

Git should not be a necessary tool to build this package. Download should probably be done using https://github.com/bazukas/obs-linuxbrowser/archive/$.tar.gz as source.

NexAdn commented on 2019-12-23 14:30

We are investigating issues if cef-minimal is installed on the system while obs-linuxbrowser is being used. This is however not an issue with the AUR package.

Also, this package is not outdated. It might contain bugs, but as I wan’t yet able to fix them, the newest version is still 0.6.1.

Mayravixx commented on 2019-03-13 15:08

Edit: This specific package does not work for me at all, however, obs-linuxbrowser-bin DOES work, streamlabs successfully tested my Twitch alerts inside OBS.

Copyright © 2004-2021 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Linux browser obs studio

Good news! Starting with version 25, OBS Studio ships with browser source that work on Linux. I recommend you to use that and report any issues at obs-browser repo and/or official discord community.

I will archive this repository from now on. I would like to say big thanks to all the users, testers and contributors. Special thanks to NexAdn who helped maintain this repository for most of the time!

This is a browser source plugin for obs-studio based on Chromium Embedded Framework. This plugin is Linux only.

Unfortunately, I was not able to make obsproject/obs-browser work on Linux, so I decided to create a separate plugin using the same engine, so both plugins should have feature parity in terms of browser capabilities.

Installing (binary release)

• Download the latest release from the releases page. Make sure the release version matches obs-studio version on your system [1].
• mkdir -p $HOME/.config/obs-studio/plugins
• Untar, e.g.: tar -zxvf linuxbrowser0.6.1-obs23.0.2-64bit.tgz -C $HOME/.config/obs-studio/plugins/
• Install the dependencies (see Dependencies section)

Arch Linux users can install obs-linuxbrowser from the official AUR packages obs-linuxbrowser or obs-linuxbrowser-bin.

You don’t need to build the plugin if you’ve downloaded a binary release, instructions below are for people who want to compile the plugin themselves.

[1] Every binary release has the version number of OBS contained as part of the file name, e.g. “linuxbrowser0.6.1-obs23.0.2-64bit.tgz” refers to obs-linuxbrowser version 0.6.1 with OBS version 23.0.2.

Building from source

The following steps are NOT necessary, if you have already installed a binary release of obs-linuxbrowser!

• Download CEF minimal or standard binary release from http://opensource.spotify.com/cefbuilds/index.html [2]
• Extract and cd into folder
• Run cmake ./ && make libcef_dll_wrapper

[2] Due to unknown reasons certain CEF versions do not work properly with OBS-Studio. See issue #63 for a list of versions which have been confirmed to be working and to track progress on this issue.

Make sure you have obs-studio installed.

• cd obs-linuxbrowser
• mkdir build
• cd build
• cmake -DCEF_ROOT_DIR=

.. (don’t forget the two dots at the end!) [3]

make

[3] If you’ve installed OBS under an installation prefix other than /usr (meaning include files aren’t located at /usr/include/obs and library files aren’t located at /usr/lib ), you need to set OBS_ROOT_DIR to reflect the actual installation prefix. If you don’t know your installation prefix, you can also set OBS_INCLUDE_SEARCH_DIR to the location of your OBS installation’s header files and OBS_LIBRARY_SEARCH_DIR to the location of your OBS installation’s library (.so) files. In most cases, though, this is NOT required at all.

Info: If you intend to install obs-linuxbrowser system wide (though the OBS developers don’t recommend that), you can add -DINSTALL_SYSTEMWIDE=true to the CMake call. obs-linuxbrowser will then be installed to /usr/lib/obs-plugins (binaries) and /usr/share/obs/obs-plugins/obs-linuxbrowser (data).

Installing compiled sources

• Run make install to install all plugin binaries to $HOME/.config/obs-studio/plugins .
• Make sure to have all dependencies installed on your system

You can enable flash by providing the path to your installed pepper flash library file and its version. Some distributions provide packages with the plugin, but you can also extract one from google chrome installation. The Flash version can be found in manifest.json that is usually found in same directory as .so file.

obs-linuxbrowser provides some JS bindings that are working the same way as the ones from obs-browser do. Additionally, a constant window.obsstudio.linuxbrowser = true has been introduced to allow the distinction between obs-browser and obs-linuxbrowser on the website.

All off the following bindings are children of window.obsstudio .

• onActiveChange(bool isActive) – called whenever the source becomes activated or deactivated
• onVisibilityChange(bool isVisible) – called whenever the source is shown or hidden

• linuxbrowser = true – Indicates obs-linuxbrowser is being used
• pluginVersion – A string containing the plugin’s version

obs-linuxbrowser does not compile with recent versions of CEF

Due to changes of the CEF API, recent versions of CEF are no longer compatible with obs-linuxbrowser. An attempt to solve this issue has been made and can be tried out by checking out the fix-new-cef-api-108-110 branch. Unfortunately, this branch hasn’t been merged to master yet due to the problems described in #121.

OBS snap installation crashing when trying to create a Linuxbrowser object

obs-linuxbrowser does not support Snap installations as these have some known restrictions that make our plugin crash. Please install OBS your distribution’s standard way (e.g. via APT, RPM, etc.).

See #105 for details.

Old version of OBS not starting with new version of obs-linuxbrowser installed

Using obs-linuxbrowser with an older OBS version than the one which has been used for compilation makes OBS break. Compile obs-linuxbrowser with the same OBS version you are going to use for streaming/recording or select a binary release whose OBS version matches the same version as yours. If you’ve compiled obs-linuxbrowser yourself, recompile it with the older version of OBS.

OBS-Linuxbrowser not displaying any content with certain versions of CEF

Some builds of CEF seem to be not working with obs-linuxbrowser. We weren’t able to figure out the exact cause of this, but we assume that it’s a CEF-related issue we can’t fix. Check issue #63 for information about CEF versions that are known to be working. This issue seems to have been resolved. If it occurs again, please open a new issue.

Problems might also occur when updating CEF withouth recompiling obs-linuxbrowser afterwards. Please make sure to recompile obs-linuxbrowser before opening issues concerning problems with certain CEF versions.

Transparency not working correctly: Transparent white browser content appears gray on white scene background.

As stated in issue #58, there is a limitation in CEF, making it unable to detect the background of the OBS scenes. Instead, premultiplied alpha values are used, which somehow make transparent white colors appear gray (every color on the grayscale is a bit darker than normal when using transparency). With a black background, transparency seems to be working out quite fine.

This issue cannot be fixed.

OBS-Linuxbrowser not compiling, complaining about having to use ISO C++11 standard (old compiler versions)

See #88 for details. Some older compiler versions seem to have trouble with our current CMake setup. Using newer versions (e.g. GCC 8.x) should work. This issue should’ve been resolved with versions 0.5.3 and above.

OBS-Linuxbrowser crashing when using amdgpu

See #89 for details. obs-linuxbrowser seems to crash on machines using amdgpu drivers. Unfortunately, this issue cannot be fixed.

Источник

Install Instructions

If you want to develop for OBS, please visit our Discord and get to know the devs or have questions answered!

Also, if there is something in this guide you want to change/improve on, it is recommended that you talk about it with the devs in Discord or IRC first.

Please note that any install directions/packages for Linux/FreeBSD distributions listed as Unofficial means that they are community provided, and any support for those packages should be directed at the appropriate distro/package maintainers.

Table of Contents:

Windows

Windows Install Directions:

The full .exe installer and .zip contains OBS Studio 32bit, 64bit, Browser Source, and Intel® RealSense™ plugin. You will be prompted during install for the Browser Source and RealSense plugin to be installed if using the .exe installer, otherwise the components are included in the .zip.

The small .exe installer contains the base OBS Studio 32bit, 64bit, Intel® RealSense™ plugin, but does not contain the Browser Source plugin.

NOTE: If using the .zip method for either the full or small install and installing to a non-standard program location (i.e. outside Program Files), you will need to add the security group ALL APPLICATION PACKAGES to have full control over the main OBS Studio directory and sub-directories. Certain features may not function properly without these security rights (primarily, the ability to use game capture on UWP apps).

Windows Build Directions:

Requirements for building OBS on Windows

• Development packages of FFmpeg , x264 , cURL , and mbedTLS .
  • Pre-built versions of these dependencies for VS2019 on Windows can be found here:
    • VS2019: https://obsproject.com/downloads/dependencies2019.zip
• Qt5 (Grab the MSVC package for your version of Visual Studio)
  • We currently deploy with Qt 5.15.2
    • Qt 5.15.2 Windows
• CEF Wrapper 3770 (x64, x86)
• Windows version of CMake (3.16 or higher, latest preferred)
• Windows version of Git (Git binaries must exist in path)
• Visual Studio 2019
  • Windows 10 SDK (minimum 10.0.20348.0). Latest SDK

Installation Procedure

Clone the repository and submodules:

If you do not know what submodules are, or you are not using Git from the command line, PLEASE make sure to fetch the submodules too.

Create one or more of the following subdirectories within the cloned repository for building: release , debug , and build (suffixed with or without 32/64 to specify architecture). They are excluded from the repo in .gitignore for the sake of building, so they are safe to create and use within the repository base directory.

Run cmake-gui, and set the following fields:

• In «where is the source code», enter in the repo directory (example: D:/obs).
• In «where to build the binaries», enter the repo directory path with the ‘build’ subdirectory (example: D:/obs/build).

Set the following variables. You can set them in cmake-gui, or you can set them as Windows Environment Variables to persist across configurations.

Required

DepsPath is the path to the folder containing the dependencies, not including Qt. Set this to the win32 or win64 directory from the Pre-built dependencies package that you downloaded earlier.
For example, if you extracted the dependencies .zip to C:\obs-deps, DepsPath should be one of these:

If you want to specify both 32 and 64 bit dependencies to avoid changing the variable between builds, you can instead set DepsPath32 and DepsPath64 like so:

• DepsPath32 : C:\obs-deps\win32
• DepsPath64 : C:\obs-deps\win64

QTDIR is the path to the Qt install directory. The OBS UI is built by default, which requires Qt. Set the CMake boolean variable DISABLE_UI to TRUE if you don’t want the GUI and this is no longer required. Can be optionally suffixed with 32 or 64 to specify target arch.

NOTE: Make sure to download Qt prebuilt components for your version of MSVC (32 or 64 bit).

Example Qt directories you would use if you installed Qt to D:\Qt would usually look something like this:

• QTDIR32=D:\Qt\5.15.2\msvc2019 (32-bit)
• QTDIR64=D:\Qt\5.15.2\msvc2019_64 (64-bit)

CEF_ROOT_DIR is the path to an extracted CEF Wrapper. We provide a custom prebuilt wrapper to simplify the build process. This custom build includes access to hardware acceleration and additional codecs. This enables Browser Source and Custom Browser Docks.

Be sure to also enable the CMake flag BUILD_BROWSER otherwise this will do nothing

Optional

• VIRTUALCAM_GUID — Set to any random GUID value. This must be set to build the Virtual Camera features.

(If these components below share the same directory as DepsPath, they do not need to be individually specified.)

• FFmpegPath — Path to just FFmpeg include directory.
• x264Path — Path to just x264 include directory.
• curlPath — Path to just cURL include directory.

INFORMATIONAL NOTE: Search paths and search order for base dependency library/binary files, relative to their include directories:

In cmake-gui, press ‘Configure’ and select the generator that fits to your installed VS Version:
Visual Studio 16 2019, or their 64bit equivalents if you want to build the 64bit version of OBS

• NOTE: If you need to change your dependencies from a build already configured, you will need to uncheck COPIED_DEPENDENCIES and run Configure again.

If you did not set up Environment Variables earlier you can now configure the DepsPath and if necessary the x264, FFmpeg and cUrl path in the cmake-gui.

In cmake-gui, press ‘Generate’ to generate Visual Studio project files in the ‘build’ subdirectory.

Open obs-studio.sln from the subdirectory you specified under «where to build the binaries» (e.g. D:/obs/build) in Visual Studio (or click the «Open Project» button from within cmake-gui).

The project should now be ready to build and run. All required dependencies should be copied on compile and it should be a fully functional build environment. The output is built in the ‘rundir/[build type]’ directory of your ‘build’ subdirectory.

The PACKAGE target uses Wix Installer and seems to be obsolete. Discussion on discord indicates that the current installer uses NSIS, but the process seems not to be fully documented.

If you want to use the Virtual Camera from this build, you will need to run its install script. If you already have a standard OBS Studio installation, you will need to uninstall its Virtual Camera first.

To uninstall an OBS Virtual Camera:

1. Close any applications that were using the OBS Virtual Camera.
2. In the obs-studio installation directory, run data\obs-plugins\win-dshow\virtualcam-uninstall.bat as administrator.

To install an OBS Virtual Camera:

1. In the obs-studio installation directory (for Visual Studio builds, this is ‘[build dir]/rundir/[build type]’), run data\obs-plugins\win-dshow\virtualcam-install.bat as administrator.

Don’t forget to uninstall your build’s virtual camera before cleaning/deleting your build files.

Integrating clang-format into Visual Studio

• clang-format is required for pull requests, and our CI uses a specific version that may not match the one VS2019 ships with.
• Download and install LLVM 10.0.0. LLVM 11+ currently introduces extra clang-format changes that we do not want to handle at this time.
• Run VS, and go to Tools -> Options.
  • Text Editor -> C/C++ -> Code Style -> Formatting -> General
    • Enable «Use custom clang-format.exe» and enter the file name. For example:
      • C:\Program Files\LLVM\bin\clang-format.exe
• The default command for formatting a document (Edit.FormatDocument) is Ctrl+K, Ctrl+D.

macOS

macOS Install Directions

Simply run the installer and follow the on-screen directions to install OBS Studio.

macOS Build Directions

Clone the repository and submodules:

If you do not know what submodules are, or you are not using Git from the command line, PLEASE make sure to fetch the submodules too.

macOS Full Build Script

To get a self-built OBS up and running, a default build and packaging script is provided. This script only requires Homebrew (https://brew.sh) to be installed on the build system already:

• To build OBS as-is with full browser-source support, simply run ./CI/full-build-macos.sh from the checkout directory (The script will take care of downloading all necessary dependencies).
• To create an app-bundle after building OBS, run the script with the -b flag: ./CI/full-build-macos.sh -b
• To create a disk image after building OBS, run the script with the -p flag: ./CI/full-build-macos.sh -b -p
• To notarize an app-bundle after building and bundling OBS, run the script with the -n flag: ./CI/full-build-macos.sh -b -n
• To create an app-bundle without building OBS again, run the script with the -s flag: ./CI/full-build-macos.sh -s -b

The last option is helpful if custom cmake flags have been used, but a proper app bundle is desired.

macOS Custom Builds

Custom build configurations require a set of dependencies to be installed on the build system. Some dependencies need to be installed via Homebrew (https://brew.sh):

If you need SRT support, either use FFmpeg provided by obs-deps or install FFmpeg from a custom tap instead of the default homebrew FFmpeg:

Pre-Built Dependencies

These dependencies are also available via obs-deps (https://github.com/obsproject/obs-deps) as pre-compiled binaries, which are assured to be compatible with current OBS code (as OBS is built against specific versions of some packages while Homebrew delivers most recent stable builds).

When using obs-deps, extract both archives from the macOS release to /tmp/obsdeps to assure compatibility with app bundling later (due to the way dylib s are identified and linked).

Create a build directory inside the obs-studio directory, change to it, then configure the project via cmake :

Build OBS by running make .

Configuring and Building

If not already handled by the Homebrew installation, install a current macOS platform SDK (only macOS High Sierra 10.13.4 or later is supported): xcode-select —install

Create a build directory inside the obs-studio directory, change to it, then configure the project via cmake :

NOTE: cmake might require additional parameters to find Qt5 libraries present on this system, this can either be provided via -DQTDIR=»/usr/local/opt/qt» or setting an environment variable, e.g.: export QTDIR=/usr/local/opt/qt

Build OBS by running make

Run OBS from the /rundir/RelWithDebInfo/bin directory in your build directory, by running ./obs from a Terminal

NOTE: If you are running via command prompt, you must be in the ‘bin’ directory specified above, otherwise it will not be able to find its files relative to the binary.

macOS Xcode Project

To create an Xcode project for OBS, cmake must be run with additional flags. Follow the build instructions above to create a working configuration setup, then add -G Xcode to the cmake command, e.g.:

This will create an obs-studio.xcodeproj project file in the build directory as well as Xcode project files for all build dependencies. To build a full macOS build, the build target ALL_BUILD can be used, but must be configured first:

• Select ALL_BUILD from available build schemes in Xcode, then press CMD+B to build the project at least once
• Then select Edit Scheme. from the same menu.
• Under the Info tab, click on the dropdown for Executable , then click on other .
• Navigate to the /rundir/debug/bin bin folder that the previous Xcode build process should have created and select the obs binary found there.
• Next, switch to the Options tab and check the box to Use custom working directory and select the same /rundir/debug/bin directory in your Xcode build directory.

NOTE: When running OBS directly from Xcode be aware that browser sources will not be available (as CEF requires to be run as part of an application bundle in macOS) and accessing the webcam will lead to a crash (as macOS requires a permission prompt text set in an application bundle’s Info.plist which is, of course, not available).

To debug OBS on macOS with all plugins and modules loaded, follow these steps:

• Build (but do not run) OBS with Xcode.
• Run BUILD_DIR=»YOUR_XCODE_BUILD_DIR» BUILD_CONFIG=»Debug» ../CI/full-build-macos.sh -d -s -b to bundle OBS build by Xcode, replace YOUR_XCODE_BUILD_DIR with the directory where you ran cmake to create the Xcode project.
• Next, create a new Xcode project, select macOS as platform and Framework as type.
• Give your project any arbitrary name and place it in any folder you like.
• With the new project open, click on your current build scheme in Xcode and select Edit Scheme. .
• For the Run step, go to the Info tab and select Other. in the dropdown for Executable .
• Browse to your OBS Xcode build directory and select the OBS.app application bundle created by the script.

You can now run OBS with Xcode directly attached as debugger. You can debug the visual stack as well as trace crashes and set breakpoints.

NOTE: Breakpoints set in the actual Xcode project do not carry over to this «helper» project and vice versa.

Linux

Any installation directions marked Unofficial are not maintained by the OBS Studio author and may not provide all the features and/or be up to date or stable.

NOTE: OpenGL 3.3 or later is required to use OBS Studio on Linux. You can check what version of OpenGL is supported by your system by typing glxinfo | grep «OpenGL» on Terminal.

Linux Install Directions

Ubuntu/Mint Installation

Please note that OBS Studio is not fully working on Chrome OS and features like Screen and Window Capture do not work.

xserver-xorg version 1.18.4 or newer is recommended to avoid potential performance issues with certain features in OBS, such as the fullscreen projector.

FFmpeg is required. If you do not have the FFmpeg installed (if you’re not sure, then you probably don’t have it), you can get it with the following commands:

If you want virtual camera support you need v4l2loopback-dkms installed. You can install it with the following command :

Make sure you enabled the multiverse repo in Ubuntu’s software center (NOTE: On newer versions of Ubuntu, adding a repository automatically apt updates.) Then you can install OBS with the following commands:

Arch Linux Installation (Unofficial)

• «Release» version is available on the community repository:
• Some AUR packages are also available.

Manjaro Installation (Unofficial)

• Graphical: search «obs-studio» on Pamac Manager or Octopi
• Command-line: install it via pacman with the following command:
• Some AUR packages are also available.

Fedora Installation (Unofficial)

OBS Studio is included in RPM Fusion. If you do not have it configured (if you’re not sure, then you probably don’t have it), you can do so with the following command:

Then you can install OBS with the following command (this pulls all dependencies, including NVENC-enabled FFmpeg):

For NVIDIA Hardware accelerated encoding, make sure you have CUDA installed:

If you have an older card, use this command instead:

OpenMandriva Installation (Unofficial)

• OBS Studio is included in OpenMandriva Lx3 non-free repository and in restricted repository for upcoming Lx4 release — available now as Cooker.

For OpenMandriva Lx3

Graphical: search and install «obs-studio» on «OpenMandriva Install and Remove Software» (Rpmdrake)

Command-line: install it as root (su or sudo) via terminal/konsole with the following command:

For OpenMandriva Lx4

Graphical: search and install «obs-studio» on «OpenMandriva Software Management» (dnfdragora)

Command-line: install it as root (su or sudo) via terminal/konsole with the following command:

Solus Installation (Unofficial)

• Graphical: search obs-studio in Software Center
• Command-line: install it as root (su or sudo) via terminal/konsole with the following command:

openSUSE Installation (Unofficial)

The Packman repository contains the obs-studio package since it requires the fuller version of FFmpeg which is in Packman for legal reasons. If you do not already have the Packman repository add it as shown below.

• For openSUSE Tumbleweed:

• For openSUSE Leap 15.2 (If you’re using a derivative of Leap, replace $releasever by your leap release number) :

The Packman version of FFmpeg should be used for full codec support. To
ensure any existing codec packages are switched to Packman versions
execute the following before installing obs-studio.

Install the obs-studio package.

Gentoo Installation (Unofficial)

Command-line: can be installed using portage by the following command:

NixOS Installation (Unofficial)

Command-line: can be installed by the following command:

See https://nixos.org/wiki/OBS for further instructions

UOS/Deepin Installation (Unofficial)

UOS/Deepin 20 or newer is required.

First, make sure you have everything up-to-date.

FFmpeg is required. If you do not have the FFmpeg installed (if you’re not sure, then you probably don’t have it), you can get it with the following command (or compile it yourself):

Finally, install OBS Studio.

Debian/LMDE Installation (Unofficial)

Debian 9.0 or newer is required.
Please note that OBS Studio is not fully working on Chrome OS and features like Screen and Window Capture do not work.

Also note that as of 2021-06-13, this package is the outdated 0.0.1 version. It should still work, but won’t have all new improvements. Build from source to get the newest version.

First, make sure you have everything up-to-date.

FFmpeg is required. If you do not have the FFmpeg installed (if you’re not sure, then you probably don’t have it), you can get it with the following command (or compile it yourself):

Finally, install OBS Studio.

Void Installation (Unofficial)

First make sure your repositories are up-to-date. OBS is available on the multilib repos if you need the 32-bit build.

Then install OBS Studio. Any missing dependencies will be installed automatically.

• If it refuses to install, try running sudo xbps-install -Su to update everything first.

snappy Installation (Unofficial)

If you haven’t already, install snapd (ignore the Support Overview which is outdated).

Install OBS Studio.

Linux Build Directions

Note: as of May 1, 2019, Facebook live now mandates the use of RTMPS. That functionality requires your distro’s mbed TLS package, which obs-studio/cmake/Modules/FindMbedTLS.cmake script searches for at compile time.

Note: Do not use the GitHub source .tar as it does not include all the required source files. Always use the appropriate Git tag with the associated submodules.

Red Hat-based Build Directions

Get RPM Fusion at http://rpmfusion.org/Configuration/ (Nux Desktop is an alternative that may include better packages for RHEL/CentOS 7)

Get the required packages:

• If speexdsp-devel is not available, it can be built from source (https://gitlab.xiph.org/xiph/speexdsp)

Building and installing OBS:

If building with browser source:

If building without browser source:

By default OBS installs libraries in /usr/local/lib. To make sure that the loader can find them there, create a file /etc/ld.so.conf.d/local.conf with the single line

Fedora Build Directions

Building and installing OBS:

If building with browser source:

If building without browser source:

Debian-based Build Directions

Get the required packages:

Building and installing OBS:

If you have configured your environment with a umask 077 or a noexec home dir you may
want to change your CMAKE_INSTALL_PREFIX , as it is reported /usr may change permissions on /usr/bin and /usr/lib .

If building with browser source:

If you have checkinstall use this instead of make install

If building without browser source:

If you have checkinstall use this instead of make install

openSUSE Build Directions

See openSUSE installation instructions (above) for details on adding Packman repository.

Install build dependencies:

Building and installing OBS:

If building with browser source:

If building without browser source:

Linux portable mode (all distros)

Please note that you need to install the build dependencies for your distribution before following this steps. See above.

You can build in portable mode on Linux, which installs all the files to an isolated directory.

If building with browser source:

If building without browser source:

After that, you should have a portable install in

/obs-studio-portable . Change to bin/64bit or bin/32bit and then simply run: ./obs

FreeBSD

FreeBSD Installation (Unofficial)

Install OBS Studio:

FreeBSD Build Directions

The easiest way to build OBS Studio from source is to use the FreeBSD Ports and modify the multimedia/obs-studio port to suit your needs.

First you have to set up the ports infrastructure on your system. See the related chapter in the FreeBSD Handbook.

Once you’ve got your ports tree at /usr/ports you may edit the multimedia/obs-studio port to your liking. Then, you may build and install the port with:

Guides/Info

Install Instructions

© 2012 — 2021. OBS and OBS Studio are created and maintained by Jim. Development by OBS Studio Contributors.
Website designed and created by Warchamp7, powered by Kirby CMS. Downloads powered by Fastly.

Источник