Join us on our own very special Reddit on /r/Linuxers.
Good news for anyone doing livestreaming or recording their gameplay, as OBS Studio 0.14 (and .1 hotfix) are now available.

A few major new features and some useful fixes. With some Linux-specific stuff like:
- Added an option "Use alpha-less texture format" option to window capture that helps capturing certain windows with mesa drivers
- Added an ALSA sound input source (currently added like any other source, will be accessible via audio settings as well in the future)

Apart from the Linux specific stuff, here's some highlights:
- NVIDIA NVENC encoder support. To use NVENC on linux, you must compile or get a version of FFmpeg with NVENC support
- Deinterlacing support
- Added a 'slide' transition
- Added a 'fade to color' transition

See the full changelog here.

It's a really great bit of software, and I'm pretty pleased they have fixed issues that I came across, like filters/properties windows crashing the entire app when closed. That will make livestreaming a bit easier for me to have a much more stable application.

Myself and Samsai use OBS Studio for all of our livestreams (every week!), so you know it's useful stuff.

If you're on Ubuntu, you can simply use this PPA. You can also just use this source code package. Article taken from GamingOnLinux.com.
0 Likes
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG and Humble Store. See more here.
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
18 comments
Page: 1/2»
  Go to:

NovenTheHero 25 Apr, 2016
Excellent. I like how they are quick with the new Ubuntu releases.
Xpander 25 Apr, 2016
i really dont get whats that nvenc thing? that was possible long time with OBS
N30N 25 Apr, 2016
Great to see ALSA support, I can finally purge my system of pulseaudio. :D

Quoting: Xpanderi really dont get whats that nvenc thing? that was possible long time with OBS
"full support" means you can now use it for streaming, not just recording (as was previously available).


Last edited by N30N on 25 April 2016 at 2:25 pm UTC
stan 25 Apr, 2016
ALSA sound input is awesome, but I wonder if it will only work on chipsets with hardware support, or if OBS automatically takes care of setting up ALSA so it works everywhere…
Kithop 25 Apr, 2016
I'm still trying to get the NVENC support to work. Rather, to detect. Managed to hackily build a .deb for Ubuntu 16.04 off the master tree for ffmpeg with --enable-nonfree and --enable-nvenc tacked on the end. Have the required toolkit installed from nVidia, headers symlinked in /usr/local/include ... a bit of futzing around later with it not detecting libva properly (maybe just an issue from when I cloned master?), and I have working ffmpeg .debs!

I installed them! 'ffmpeg --codecs' shows nvenc in the list!

OBS still mocks me with 'Software (x264)' as the only encoder drop down. :( So now I'm thinking, great, do I have to actually build OBS from source too, so it detects my new custom build of ffmpeg? Oh, right, I need all the -dev packages that OBS depends on if I want to bui-

*fliptable* I'm not a developer, but a SysAdmin. This is one time I will say: BSD's ports system makes this so much easier. You pick your poison at configure time, and it always rebuilds from source.

If anyone figures it out, I'd love to know... and no, I can't redistribute the .deb files legally - hence the requirement for non-free. ;/ This is why we can't have nice things, like a PPA with NVENC-enabled ffmpeg builds, unless nVidia relicenses the required libraries.

95%+ sure that my next card (and potentially my next CPU!) are going to be AMD, so here's hoping for some love in the form of, say, AMD VCE support in OBS Studio? ^.^ Especially if it's exposed through the new-and-upcoming open source AMDGPU drivers. I'm so, so sick of binary blobs and stupid license incompatibility issues.
ST34MF0X 25 Apr, 2016
Quoting: KithopI'm still trying to get the NVENC support to work. Rather, to detect. Managed to hackily build a .deb for Ubuntu 16.04 off the master tree for ffmpeg with --enable-nonfree and --enable-nvenc tacked on the end. Have the required toolkit installed from nVidia, headers symlinked in /usr/local/include ... a bit of futzing around later with it not detecting libva properly (maybe just an issue from when I cloned master?), and I have working ffmpeg .debs!

I installed them! 'ffmpeg --codecs' shows nvenc in the list!

OBS still mocks me with 'Software (x264)' as the only encoder drop down. :( So now I'm thinking, great, do I have to actually build OBS from source too, so it detects my new custom build of ffmpeg? Oh, right, I need all the -dev packages that OBS depends on if I want to bui-

*fliptable* I'm not a developer, but a SysAdmin. This is one time I will say: BSD's ports system makes this so much easier. You pick your poison at configure time, and it always rebuilds from source.

If anyone figures it out, I'd love to know... and no, I can't redistribute the .deb files legally - hence the requirement for non-free. ;/ This is why we can't have nice things, like a PPA with NVENC-enabled ffmpeg builds, unless nVidia relicenses the required libraries.

95%+ sure that my next card (and potentially my next CPU!) are going to be AMD, so here's hoping for some love in the form of, say, AMD VCE support in OBS Studio? ^.^ Especially if it's exposed through the new-and-upcoming open source AMDGPU drivers. I'm so, so sick of binary blobs and stupid license incompatibility issues.

Yes, that is exactly the case. You have to compile both. And if you follow their instructions, you have to do the checkinstall bit twice. Otherwise, OBS will bitch about not being able to get OpenGL context. It's annoying.


Last edited by ST34MF0X on 25 April 2016 at 5:22 pm UTC
tuubi 25 Apr, 2016
Quoting: aFoxNamedMorris*fliptable* I'm not a developer, but a SysAdmin. This is one time I will say: BSD's ports system makes this so much easier. You pick your poison at configure time, and it always rebuilds from source.
aFoxNamedMorris, please meet Gentoo. Gentoo, this is aFoxNamedMorris.

And they lived happily ever after.
MajGuano 25 Apr, 2016
Quoting: KithopI'm still trying to get the NVENC support to work. Rather, to detect. Managed to hackily build a .deb for Ubuntu 16.04 off the master tree for ffmpeg with --enable-nonfree and --enable-nvenc tacked on the end. Have the required toolkit installed from nVidia, headers symlinked in /usr/local/include ... a bit of futzing around later with it not detecting libva properly (maybe just an issue from when I cloned master?), and I have working ffmpeg .debs!

I installed them! 'ffmpeg --codecs' shows nvenc in the list!

OBS still mocks me with 'Software (x264)' as the only encoder drop down. :( So now I'm thinking, great, do I have to actually build OBS from source too, so it detects my new custom build of ffmpeg? Oh, right, I need all the -dev packages that OBS depends on if I want to bui-

*fliptable* I'm not a developer, but a SysAdmin. This is one time I will say: BSD's ports system makes this so much easier. You pick your poison at configure time, and it always rebuilds from source.

If anyone figures it out, I'd love to know... and no, I can't redistribute the .deb files legally - hence the requirement for non-free. ;/ This is why we can't have nice things, like a PPA with NVENC-enabled ffmpeg builds, unless nVidia relicenses the required libraries.

95%+ sure that my next card (and potentially my next CPU!) are going to be AMD, so here's hoping for some love in the form of, say, AMD VCE support in OBS Studio? ^.^ Especially if it's exposed through the new-and-upcoming open source AMDGPU drivers. I'm so, so sick of binary blobs and stupid license incompatibility issues.

You many need to rebuild OBS. If you have the OBS ppa set up, make sure you have build-essential and debhelper packages installed, then try:
apt-get build-dep obs
This may replace your custom ffmpeg. If it does, reinstall your custom ffmpeg deb package.
apt-get source obs
I don't remember if this will unpack the source tarball for you. If not, unpack it.
Then, navigate to the directory where you just downloaded the OBS source.
dpkg-buildpackage
Assuming all goes well, you should find a .deb package in the source code's parent directory. Install it.

If this doesn't work, you probably need to rebuild ffmpeg, with the "--enable-shared" option. Good luck! If you rebuild ffmpeg, you may need to rebuild OBS, too.

I had this working previously, but after some recent upgrades, everything broke. Rather than fix it, I just switched to Arch, where all the necessary goodies were in the AUR, and it built and compiled effortlessly. I'm serious. Switching to Arch was actually less hassle for me than getting it working on Ubuntu.

(NOTE: I'm not interested in getting involved in any distro wars. They're both good distros, with their own strengths and weaknesses, and I use each of them regularly. Manjaro is a nice compromise. It feels like reminiscent of Mint, but it's a rolling release and uses Arch's package management.)
chrisq 25 Apr, 2016
Quoting: tuubi
Quoting: aFoxNamedMorris*fliptable* I'm not a developer, but a SysAdmin. This is one time I will say: BSD's ports system makes this so much easier. You pick your poison at configure time, and it always rebuilds from source.
aFoxNamedMorris, please meet Gentoo. Gentoo, this is aFoxNamedMorris.

And they lived happily ever after.

Or Arch.
Snowdrake 25 Apr, 2016
For archlinux users please note the latest opencv package did broke obs dependency.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: Liberapay or PayPal.

This ensures all of our main content remains totally free for everyone with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.