[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Looking for advice - ffmpeg-free and wf-recorder
From:       Neal Gompa <ngompa13 () gmail ! com>
Date:       2022-12-17 10:43:09
Message-ID: CAEg-Je9akTrYv0cFQ9SBvPVpAS8Cx7oPDRNUrEj+d2xL0NJVXQ () mail ! gmail ! com
[Download RAW message or body]

On Sat, Dec 17, 2022 at 12:29 AM Bob Hepple <bob.hepple@gmail.com> wrote:
> 
> I am the packager for wf-recorder (a wl-roots/wayland screen recorder) which \
> presently resides in rpmfusion - it uses proprietary ffmpeg codecs by default \
> (libx246). 
> Now that we have ffmpeg-free we have an opportunity to move wf-recorder to the \
> mainstream and change the default codec to the non-proprietary libopenh264. This \
> woud be in rawhide/f38 and on. 
> This all works fine in testing on f37. The fly in the ointment is that if \
> ffmpeg/rpmfusion is installed in place of ffmpeg-free, then wf-recorder can no \
> longer access libopenh264 and fails with an error. There is a workaround in the use \
> of the option -c libx264. 
> Several solutions occur to me and I'm looking for guidance on which path to take:
> 
> 0. leave wf-recorder where it is, in rpmfusion as in f37 and earlier.
> A. compile wf-recorder as shipped by upstream with the default libx264 - the '-c \
> libopenh264' workaround would be needed if ffmpeg-free is installed. This annoys \
> users who install stock fedora. B. compile wf-recorder with libopenh264 as the \
> default - the '-c libx264' workaround would be needed if ffmpeg/rpmfusion is \
> installed and would annoy those users. C. leave wf-recorder in rpmfusion and create \
> a wf-recorder-free package by analogy to ffmpeg (this might be obscure as it's not \
> likely to get much publicity - and annoy everyone sooner or later) D. the best \
> option might be to choose a codec common to both ffmpeg and ffmpeg-free. I'm not \
> terribly au fait with the various codecs so which would I choose? These codecs \
> appear to be in both packages: 

I suggest going with option D, and my suggestion is libvpx-vp9.

libvpx-vp9 is common to both and reasonably fast. I made a similar
change to O3DE some time ago for similar reasons:
https://github.com/o3de/o3de/commit/add4ad4ad42fe36b04e80b3ee4ab2358fe5fd35e




--
真実はいつも一つ！/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


[prev in list] [next in list] [prev in thread] [next in thread]