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.
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.
Some you may have missed, popular articles from the last month:
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
17 comments
Excellent. I like how they are quick with the new Ubuntu releases.
0 Likes
i really dont get whats that nvenc thing? that was possible long time with OBS
0 Likes
Great to see ALSA support, I can finally purge my system of pulseaudio. :D
Last edited by N30N on 25 April 2016 at 2:25 pm UTC
i 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
1 Likes, Who?
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.
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.
0 Likes
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.
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 D34VA_ on 25 April 2016 at 5:22 pm UTC
1 Likes, Who?
*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.
2 Likes, Who?
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.
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.)
0 Likes
*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.
0 Likes
For archlinux users please note the latest opencv package did broke obs dependency.
0 Likes
Nah. My comment/joke was in reference to Gentoo's portage package manager, which in my experience is much closer to BSD's ports than pacman.*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.
0 Likes
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:...
Yeah, that's what I'm afraid of. I'm using the OBS PPA, so its 'obs-studio', but my issue is that my build of ffmpeg doesn't include the '-dev' bits, so:
$ sudo apt-get build-dep obs-studio
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help resolve the situation:
The following packages have unmet dependencies:
builddeps:obs-studio : Depends: libavformat-ffmpeg-dev but it is not installable
Depends: libswscale-ffmpeg-dev but it is not installable
Depends: libswresample-ffmpeg-dev but it is not installable
Depends: libavdevice-ffmpeg-dev but it is not installable
Depends: libavfilter-ffmpeg-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
There's a *pile* of headers and things in the build trees for each of those in my ffmpeg folder... I just need to figure out how to tell debuild / dpkg-buildpackage to bundle them up as the above *-dev packages, too, and I should be able to get going. I'll keep hacking at it a bit. :p
0 Likes
Wait, I'm being dumb - it made the packages, but called them e.g. libavformat-dev instead of libavformat-ffmpeg-dev... I'm assuming I need to make a virtual package (kind of like a dpkg symlink?) from the latter to the former. Almost!
0 Likes
Wait, I'm being dumb - it made the packages, but called them e.g. libavformat-dev instead of libavformat-ffmpeg-dev... I'm assuming I need to make a virtual package (kind of like a dpkg symlink?) from the latter to the former. Almost!
Okay. Forced grabbing the obs-studio sources. Realised that this is a name change thing from Debian's move from the Libav fork back to FFmpeg proper. obs-studio is looking for the transitional packages that no longer exist in Xenial / 16.04.
Quick find-and-replace on obs-studio-0.14.1.1/debian/control to get rid of the superfluous '-ffmpeg' on the Build-Depends: line... and now debuild is running! :D If this works, I'll try to post together a quick Howto on how the heck I managed to get this to build on 16.04.
1 Likes, Who?
Really quick and dirty and horrible, but here's a quick HOWTO of how I got it finally working on my system (Xubuntu 16.04):
OBS with NVENC for Ubuntu 16.04
OBS with NVENC for Ubuntu 16.04
2 Likes, Who?
For archlinux users please note the latest opencv package did broke obs dependency.Not really you just need to rebuild deps that depend on opencv. In this case you probably use ffmpeg-full-nvenc. You need to rebuild it otherwise applications that depend on ffmpeg will crash just like OBS or MPV.
ldd /usr/bin/obs | grep opencv
libopencv_imgproc.so.3.1 => /usr/lib/libopencv_imgproc.so.3.1 (0x00007f3d0b189000)
libopencv_core.so.3.1 => /usr/lib/libopencv_core.so.3.1 (0x00007f3d0a479000)
ldd /usr/bin/mpv | grep opencv
libopencv_imgproc.so.3.1 => /usr/lib/libopencv_imgproc.so.3.1 (0x00007fba9b1a1000)
libopencv_core.so.3.1 => /usr/lib/libopencv_core.so.3.1 (0x00007fba9a491000)
Last edited by Commander on 26 April 2016 at 1:48 pm UTC
0 Likes
Really quick and dirty and horrible, but here's a quick HOWTO of how I got it finally working on my system (Xubuntu 16.04):
OBS with NVENC for Ubuntu 16.04
Congratulations on your success, and thank you for sharing the build instructions!
1 Likes, Who?
You're right ! I totally forgot to rebuild ffmpeg +nvenc after the opencv update. Thank you.For archlinux users please note the latest opencv package did broke obs dependency.Not really you just need to rebuild deps that depend on opencv. In this case you probably use ffmpeg-full-nvenc. You need to rebuild it otherwise applications that depend on ffmpeg will crash just like OBS or MPV.
ldd /usr/bin/obs | grep opencv
libopencv_imgproc.so.3.1 => /usr/lib/libopencv_imgproc.so.3.1 (0x00007f3d0b189000)
libopencv_core.so.3.1 => /usr/lib/libopencv_core.so.3.1 (0x00007f3d0a479000)
ldd /usr/bin/mpv | grep opencv
libopencv_imgproc.so.3.1 => /usr/lib/libopencv_imgproc.so.3.1 (0x00007fba9b1a1000)
libopencv_core.so.3.1 => /usr/lib/libopencv_core.so.3.1 (0x00007fba9a491000)
0 Likes
See more from me