From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] lavfi AVOption redundancy, ffmpeg code cleanup [GSoC] Date: Tue, 1 Mar 2022 14:34:30 +0100 Message-ID: <CAPYw7P5aBKDCMNxj+azcB0uLTiH1qaCXBvMRDEFtsBXetvOVOg@mail.gmail.com> (raw) In-Reply-To: <20220301142823.GB102752@xor.haasn.dev> On Tue, Mar 1, 2022 at 2:28 PM Niklas Haas <ffmpeg@haasn.xyz> wrote: > Hi, > > There was some discussion recently about the possibility of reducing the > amount of ad-hoc file loading in filters by introducing common syntax > for loading AV_OPT_TYPE_BINARY options from files. (vf_libvmaf, > vf_frei0r, vf_libplacebo, vf_vidstabtransform, ...) > > Another source of redundancy currently is the code is redundancy of > colorspace configuration options. (vf_colorspace, vf_vectorscope, > vf_libplacebo, vf_setparams, vf_zscale(?)) These could also benefit > from being unified somehow. > > The idea was raised to gather more such cleanup work and turn it into a > GSoC project. But I don't think these two tasks alone are enough to fill > the 50-100 hours needed for a project. Does anybody have additional > ideas for low-hanging fruit type cleanup / redundancy elimination work > that needs to be done? > Rewrite it so various warnings while compiling are finally gone? > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-03-01 13:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-01 13:28 Niklas Haas 2022-03-01 13:34 ` Paul B Mahol [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAPYw7P5aBKDCMNxj+azcB0uLTiH1qaCXBvMRDEFtsBXetvOVOg@mail.gmail.com \ --to=onemda@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git