From: Mondain <mondain@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Add enhanced rtmp codec vp8 to flv format
Date: Tue, 6 Aug 2024 09:29:07 -0700
Message-ID: <CAHQq8Q+VaR79OsV-dxqGRcbmqRvCY4s3o+3VOt7jrZ0sf-bXyg@mail.gmail.com> (raw)
In-Reply-To: <20f34271-8c9f-4b24-b672-53e25b03ac81@rothenpieler.org>
Just a curiosity thing; why would the spec need to be out of alpha, yet the
other codecs are already in ffmpeg? Just no preference for VP8 itself,
while its still in-spec for tech like WebRTC? Again, just seems odd that
I've run into this type of messaging before.
Best Regards,
Paul
On Mon, Aug 5, 2024 at 12:55 PM Timo Rothenpieler <timo@rothenpieler.org>
wrote:
> On 05.08.2024 16:01, Mondain wrote:
> > Fixes: Reading and writing of VP8 media in FLV files, to match
> > existing enhanced codecs
>
> This will be part of the already finished enhanced rtmp v2 patch set,
> but the spec needs to be out of alpha first.
> VP8 is in fact missing, since I didn't think anyone would care about it
> specifically.
> If you like, send it as PR to
> https://github.com/BtbN/FFmpeg/blob/enhanced-flv
> _______________________________________________
> 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".
>
--
<https://about.me/mondain?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
Paul Gregoire
about.me/mondain
<https://about.me/mondain?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
_______________________________________________
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".
next prev parent reply other threads:[~2024-08-06 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 14:01 Mondain
2024-08-05 19:55 ` Timo Rothenpieler
2024-08-06 16:29 ` Mondain [this message]
2024-08-06 16:37 ` Mondain
2024-08-06 16:39 ` Timo Rothenpieler
2024-08-06 17:17 ` Mondain
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=CAHQq8Q+VaR79OsV-dxqGRcbmqRvCY4s3o+3VOt7jrZ0sf-bXyg@mail.gmail.com \
--to=mondain@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