ffmpeg/libav default in Gentoo

Naib · Posted: Wed Feb 25, 2015 8:25 pm Post subject:

Besides locally the default?
Lobbying like minded developers, something that shouldn't be needed with this amount of technical reasons.

I wonder if a GLEP needs to be written to outline the rights and powers of the wider community, not to overrule developers but a 3rd prong alongside devs and the council
_________________
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;

Yggdrasil · Posted: Thu Feb 26, 2015 2:02 am Post subject:

steveL · Posted: Thu Feb 26, 2015 1:13 pm Post subject:

mcdebugger · Posted: Fri Feb 27, 2015 6:55 pm Post subject:

Politics in software. It's very sad. I don't see any reasons to switch to libav. FFMPEG works very well, don't break anything, devs are open: accepting patches from community, accepting work from libav and they don't do the f.. aggressive advertisment and PR of their work. Even if they are "deprecated" in some of distros, they are still living in my heart. The time will show everything but I can't say that being a parasite, making a fork and then discredit original project is something good. As in everywhere in politics we, the end users of the software, can't see hidden motivations and processes of the action, but we can have our point of view.

stephan-t · Tux's lil' helper Joined: 12 May 2014 Posts: 122

My recipe

Also work with mpd and mpv.

In make.conf

USE='-libav ffmpeg'

I remove the media-video/libav, media-sound/mpd and media-video/mpv and also remove the virtual/ffmpeg-9-r1

pull the latest virtual/ffmpeg-9-r1, media-video/mpd-0.19.6 and media-video/mpv-0.8.0 or media-video/ffmpeg-2.5.4

(probably i cannot install the 9999 version of mpv maybe, require the ffmpeg-9999)

After the compile work as pretty good and i happy with ffmpeg.

Let's check it with mplayer2 latest.

tld · Veteran Joined: 09 Dec 2003 Posts: 1850

Wow...I just got burned by this whole thing today. I've been really tied up with work and apparently picked the worst possible time to go a long stretch without updating. Got hit with the perl 5.20 and all sorts of crap at once. Worst list of blockers I've ever seen in 11 years of Gentoo.

Spent forever sorting out what I thought were perl issues...started thinking I was actually never going to get it...when it turned out it was ALL being triggered by the new default libav USE flag. Adding -libav cleared it all up.

I'd also been way to busy to follow any of this and have just been catching up. My position is simple: I know nothing of any advantages or disadvantages and couldn't care less. Forking a project like this and keeping the same library names as the libav project has done is a f***ing dick move plain and simple, and it should have been rejected as the default based on that alone.

Sorry for the harshness, but that move shows NO concern for end users and it already burned me badly. You can pry my -libav from my cold dead fingers shall we say.</pissed-off>

Tom

leifbk · Posted: Sat Mar 21, 2015 12:07 pm Post subject:

I switched from ffmpeg to libav in January 2013, when the announcement about the change first appeared on Planet Gentoo. I had to change from mplayer to mplayer2, as mplayer at the time didn't compile with libav. A couple of weeks ago I had a wtf moment when I saw that mplayer2 was masked as being defunct, and remembered the reason for installing it. I did a google search for "gentoo libav" and found this discussion. After reading it in its entirety, I decided to switch back to ffmpeg. The switch went well, apart from one little snag: In my package.use file I had this line "media-video/libav threads" which made portage insist on pulling in libav again. After changing that line to "media-video/ffmpeg threads" everything was ok.

I can't say that I've got any technical issues with libav, but, as for many others in this thread, the behaviour of the libav project worries me.
_________________
Grumpy old man

mrsaccess · n00b Joined: 03 Sep 2005 Posts: 30 Location: Greece

I am running on the testing amd64 branch. For the last 4 months there hasn't been an update for me that I didn't have to fix libav-libpostproc/ffmpeg issues.
I did everything suggested to switch to libav but still.

I haven't done enough research to support one or another, but what I do know is that Gentoo's quality has gotten significantly worse because of these issues.
_________________
Hardware: The parts of your pc you can kick.

juantxorena · Posted: Tue Mar 31, 2015 10:02 pm Post subject:

It seems that the common sense finally came to the people in charge: https://archives.gentoo.org/gentoo-dev/message/50c181372e098719b2573e7b16c74482.
I guess we will see ffmpeg as default in the following days.
_________________
I cannot write English very well. Please, correct any mistake so that I can improve.

Tony0945 · Posted: Tue Mar 31, 2015 10:45 pm Post subject:

juantxorena, from the link

danomac · Posted: Wed Apr 01, 2015 12:51 am Post subject:

About time. It makes more sense for the 6-8% of the userbase that use libav to deal with the portage headaches instead of the 90% that use ffmpeg.

juantxorena · Posted: Wed Apr 01, 2015 6:50 am Post subject:

augustin · Guru Joined: 23 Feb 2015 Posts: 318

leifbk · Posted: Wed Apr 01, 2015 10:36 am Post subject:

augustin · Guru Joined: 23 Feb 2015 Posts: 318

tld · Veteran Joined: 09 Dec 2003 Posts: 1850

WWWW · Tux's lil' helper Joined: 30 Nov 2014 Posts: 143

oh ok.

I just noticed the pesky libav USE flag incrusted into vlc that caused great havok on my system.

I was gonna ask what's the deal with this but upon reading the last post on this thread got the answer.

thanks!

ps: what about the postproc USE flag? Should I use it?

yngwin · Posted: Sat Apr 04, 2015 2:42 pm Post subject:

steveL · Posted: Sat Apr 04, 2015 6:43 pm Post subject:

augustin · Guru Joined: 23 Feb 2015 Posts: 318

yngwin · Posted: Mon Apr 06, 2015 4:39 am Post subject:

yngwin · Posted: Mon Apr 06, 2015 4:42 am Post subject:

steveL · Posted: Mon Apr 06, 2015 6:39 am Post subject: