Good morning, good night! There is a problem with an FFMPEG build option that comes native in slackware current. With the option: aac="--disable-encoder=aac" disabled it ends up "breaking" the Simple screen recorder and OBS-studio. I'll explain what happens.

I know that obs is not by default in Slackware but in slackbuilds, but here's the thing. The audio of the simple screen recorder (native in slackware) and OBS (Not native in slackware) end up showing on the graph (obs and ssr) that they are activated and work, but in the recording ends that the video is "WITHOUT AUDIO".

And when trying to see the logs of both programs ends up not "showing" the real reason. Until after much exploring I saw that when activating this option in ffmpeg in the compilation without (aac="--disable-encoder=aac") does not work the audio on the recording. Again this seems to be an invisible error, and that can cause some users to lose their hair.

There are few reports on the internet but I ended up by chance finding another user with this problem: https://obsproject.com/forum/threads...urrent.140908/

To really work, then we have to recompile FFMPEG with the option aac="--disable-encoder=aac" (ON) And everything works normally. I do not know if it is possible to activate this option by (default) in ffmpeg, if it is not possible my report is for those who face something like that!



I know it's software that not everyone uses, but I use it to work recording/streaming for my classes etc..

I'm pretty sure that ffmpeg has some built-in aac stuff, because (and I could be wrong) I seem to remember that fdk-aac is no longer required but my build.log was still reporting aac getting used. I would have to check my logs to be sure (not gonna be around that computer for a few days though).

But there is the other concern, legal issues. I'm not sure again here, but I don't think that aac is exactly legal here in the US.

You are probably just going to have to rebuild ffmpeg for yourself with that and --enable-nonfree.

you can also test installing a prebuilt ffmpeg with AAC support from here and see if it solves your issue

https://slackware.nl/people/alien/re...pkg64/current/

Doesn't Alien Bob maintain a "non-restrictive" ffmpeg package?

http://slackware.uk/people/alien/res...pkg64/current/

1 members found this post helpful.

On one machine I took the official ffmpeg Slackware slackbuild from a mirror and tweaked it so I have things like aac. The optional dependencies can be found on Slackbuilds.org and it is easy to change the slackbuild to enable them.

the link you posted actually points to the same packages of the one I posted (just hosted elsewhere), the restricted versions: "restricted" means that should not be redistributed in the States because of the license with which some of the codecs they support are distributed by their vendors.

the non-restricted ffmpeg packages from Alien Bob don't contain support for AAC (the AAC redistribution license is one of the reasons of the existance of those packages).

1 members found this post helpful.

That non restrictive package may explain why some time ago the ability to stream from sling.com stopped working. It kind of works in Firefox now but not well. It doesn't work at all in Chrome but it used to. I see references to ffmpeg in the console window but googling the errors gives little help.