That will be put in the new release info once we make a new "release" here
soon.
On Wed, Sep 27, 2017, 9:31 AM Svantoviit wrote:
> I would appreciate an announcement that Sabayon has switched back go
> ffmpeg.
>
> --
> SvantoViit
>
>
I would appreciate an announcement that Sabayon has switched back go
ffmpeg.
--
SvantoViit
"Our users" or "our user base" are very vague categories.
Although it has been stated, that Sabayon is not a democracy,
as one of the users I can say I am happy with libav ;)
--
SvantoViit
Silence here, so let me share the status: it's still undecided, and the
discussion can continue when /some guy/ can fully participate (goes from
semi-away which is due to technical problems).
Thanks for clearing that up.
So it appears that getting the support of upstream to work on packages
would be a great amount causing user base to be "stuck". I wasn't aware
that there was so many packages and our manpower is too low to impact
upstream. I believe debian went back to ffmpeg a year
11.9 is the latest patch release on the 11.x branch, 12.0 is also in
portage but not marked stable. Neither provides the same versions of the
component libraries as ffmpeg even as old as ffmpeg 3.0.x (bearing in mind
ffmpeg is already u pto 3.3 branch, 3.0.x is already quite old). There may
be
Wasn't libav 11.9 released last month?
On Mon, May 1, 2017 at 9:43 AM, Ben Roberts
wrote:
> Let's bear in mind the problem is not just that there are packages that
> don't have direct support for libav. The problem is also partly that there
> is not a libav release
Let's bear in mind the problem is not just that there are packages that
don't have direct support for libav. The problem is also partly that there
is not a libav release that provides all the same component library
versions that are available in ffmpeg; libav is definitively behind ffmpeg
at the
Can we get a list of every application in portage that DOES NOT support
libav and requires ffmpeg?
I would volunteer to attempt filing bugs for each application requesting
libav support.
On Mon, May 1, 2017 at 9:31 AM KJS wrote:
> I have to agree with Ettore
>
> On Mon, May
I have to agree with Ettore
On Mon, May 1, 2017 at 6:02 AM, Sławomir Nizio
wrote:
> > We are one of the few distributions (actually i'm not aware of others)
> > that support libav out of the box, and i'm proud of it. What i would
> > propose instead is trying to push
> We are one of the few distributions (actually i'm not aware of others)
> that support libav out of the box, and i'm proud of it. What i would
> propose instead is trying to push upstream projects that misses libav
> support and/or helping libav providing support to them.
Volunteers? :)
One of
Just a heads up, right now we're thinking of working to get libav working
upstream. We are still in talks and it's not set in stone yet.
On Fri, Apr 28, 2017, 2:13 PM Sławomir Nizio
wrote:
> Joost expressed on IRC he would be OK with the switch.
>
> Ettore - ?
>
> It would be awesome for the users to have the choice, actually. ,-)
It could be useful only in limited number of cases I think, and neither
Debian, Gentoo nor Arch do it, from what I can see.
(Gentoo provides the choice, but they can't co-exist, and switching
requires rebuilding many
On Wed, Apr 26, 2017 at 01:02:20AM +0200, Joost Ruis wrote:
>What matters to me is what works best for our users.
It would be awesome for the users to have the choice, actually. ,-)
--
Nicolas Sebrecht
> The fact that https://gpo.zugaina.org/media-video/obs-studio has a hard
> dep on ffmpeg could be because the Gentoo maintainer isn't aware of the
> virtual package.
I read it really does not compile with libav.
> I'm not technically up to date, but if libav is indeed
> breaking away with
> As long as we're not updating ffmpeg every chance we get and wait for
> ffmpeg releases to prove their stability etc, I think we may be fine.
I believe only ffmpeg with the stable keyword would be used.
What matters to me is what works best for our users.
The fact that https://gpo.zugaina.org/media-video/obs-studio has a hard dep
on ffmpeg could be because the Gentoo maintainer isn't aware of the virtual
package. I'm not technically up to date, but if libav is indeed breaking
away with ffmpeg
Interesting. LibAV is supposedly cleaner, harder code, but much of libAV
ends up in ffmpeg anyway from what I'm reading and ffmpeg has more support
for most other applications etc. Their problem is ffmpeg tends to be more
bloated and risky about adopting patches and code? As long as we're not
Hello,
The libav project has served Sabayon well, and the fact it appeared and
has been actively developed might have made great impact on the world of
audio/video libraries. However, this may be a good time to switch back
to ffmpeg. There are references on IRC that it's wanted by users because
19 matches
Mail list logo