[SOLVED] Anyone got obs-studio working on slackware current?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anyone got obs-studio working on slackware current?
Hi,
I am trying to get obs-studio to work on slackware64 current, but when I start it up I get the messages:
Code:
error: Output ID 'rtmp_output' not found
error: Failed to create output 'simple_stream'!
info: output 'simple_stream' (rtmp_output) created
error: Encoder ID 'obs_x264' not found
info: encoder 'simple_h264_stream' (obs_x264) created
error: Failed to get properties for encoder '' (ffmpeg_aac)
error: Could not enumerate any AAC encoder bitrates
info: encoder 'simple_h264_stream' destroyed
info: output 'simple_stream' destroyed
error: Failed to create aac streaming encoder (simple output)
and a popup window saying "Failed to create aac streaming encoder (simple output)"
I compiled obs-studio from the slackbuild from slackbuilds.org. I also compiled x264 and ffmpeg using slackbuilds.org too. When building ffmpeg I used the options:
FAAC=yes LAME=yes OPENSSL=yes PULSEAUDIO=yes RTMP=yes X264=yes XVID=yes
I tried with obs-studio 0.12.3, and also changed the slackbuild to compile 0.14.1. Same problem with both.
My graphics card is an nvidia GTX560Ti using the proprietary drivers (also installed from slackbuilds.org)
In slackbuilds current It requires qt5 and the qt5 in Slackbuilds breaks many other programs that you build down the road. I have been working on this for over a year. I suggest use a alternate program. I really did not care much for it.
If you build it using alien bobs kde5 you will run in to other issues. because alien bobs still using qt4 enable to run many of the programs from slackware current.
As of right now qt5 build in slackbuilds breaks kdenlive and many other qt4 programs . As for your answer Yes it builds and runs just fine on my qt5 only system. git clone https://github.com/jp9000/obs-studio.git it and create your own package.
as for running on slackware current with qt5 it will but remember it will break other things. You can get around this by heavily editing your /etc/ld.so.conf take a look at how ubuntu handles ld.so.conf then set up per program.
As for contacting any one at slackbuilds maintainers. In my years of emailing the addresses I have only had one person return the email.
You may do better handle it through the github. and place it on one of their commits. So everyone can see it.
At one time we had an alternate install of qt5 that made this issue a little more simple to deal with. But as of now qt5 blob is dropped right in the middle of /usr/lib-arch
and again it was handle through /etc/profile.d and /etc/ld.so.conf
My biggest hate of this program is it wants to control your desktop and I do not like that.
I didn't think of emailing the maintainer since it built OK so assumed it was a problem with obs and not the SlackBuild.
I should have mentioned that I do also have qt5 installed at the moment - but yes I remember having to remove that before because it caused problems.
I just downloaded it with git like you suggested and built a portable version following the instructions on their install page and that seems to work OK (it starts up the GUI at least)
Code:
$ git clone https://github.com/jp9000/obs-studio.git
$ cd obs-studio
$ mkdir build && cd build
$ cmake -DUNIX_STRUCTURE=0 -DCMAKE_INSTALL_PREFIX="${HOME}/obs-studio-portable" ..
$ make -j4 && make install
waiting for the maintainer to have a look at it, I fixed obs-studio in my git branch (while I was there I also version-bumped it): you can check modifications there, they will go in the master branch at the next merge.
Quote:
Originally Posted by Drakeo
As of right now qt5 build in slackbuilds breaks kdenlive and many other qt4 programs .
well, I have qt5 installed and kdenlive works fine here. just for curiosity I've tried also rebuilding it (still with qt5 installed) and it hasn't broke.
which are these "many other qt4 programs"? can you please post the errors they give you?
Quote:
as for running on slackware current with qt5 it will but remember it will break other things.
again, which ones?
could be useful if you report them here, maybe we can fix them (if there's something to fix).
I had a reply from the maintainer of the SlackBuild and the problem is that cmake ignores the -DLIB_SUFFIX=${LIBDIRSUFFIX} so the libs are getting installed in /usr/lib on slackware64. The SlackBuild then moves all the libs into /usr/lib64 and when obs starts up it can't find them anymore because it is looking in /usr/lib. Removing the following lines from the SlackBuild "fixes" it by leaving the 64bit libs in /usr/lib:
Code:
if [ "$ARCH" = "x86_64" ]; then
mv $PKG/usr/lib $PKG/usr/lib${LIBDIRSUFFIX}
fi
you most probably missed the post above your last: I fixed that in my git branch using -DOBS_MULTIARCH_SUFFIX="$LIBDIRSUFFIX".
this way libraries are installed under the correct arch-dependant directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.