From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg at NAB 2024
Date: Sun, 31 Mar 2024 12:48:49 +0100
Message-ID: <b0d8fdfe-a22d-4ed2-924b-92b0f1d10c85@gmail.com> (raw)
In-Reply-To: <d1fff69c-de53-4c63-97e8-1412cc1be2b7@gmail.com>
On 11/1/2023 9:25 PM, Derek Buitenhuis wrote:
> This is certainly interesting considering we just had a giant thread about not using
> or using SPI, with multiple people accused of having corporate interests.
Adding to the list of wtf NAB things:
https://twitter.com/JanetGrecoBP/status/1773342135514779700
I will be with #GPAC on the #FFMPEG stand #W4232 during #NABShow, from 13-17th
April in Las Vegas. If you're interested in cutting-edge #openSource #ultramedia
video streaming & next-gen multimedia transcoding, packaging & delivery software,
do stop by or DM to meet! @wearegpac
(Janet does PR/markey and stuff for Motion Spell, GPAC's commercial arm.)
I am sure this email will continue the long trend of emails in this thread being
routed to Thilo's /dev/null.
- Derek
_______________________________________________
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-03-31 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 20:37 Thilo Borgmann via ffmpeg-devel
2023-11-01 21:25 ` Derek Buitenhuis
2023-11-19 14:05 ` Derek Buitenhuis
2023-11-19 14:19 ` Derek Buitenhuis
2023-11-19 14:20 ` Derek Buitenhuis
2023-11-19 14:26 ` Kieran Kunhya via ffmpeg-devel
2023-11-19 21:46 ` Michael Niedermayer
2023-11-19 23:49 ` Kieran Kunhya via ffmpeg-devel
2024-03-31 11:48 ` Derek Buitenhuis [this message]
2023-11-01 21:25 ` Kieran Kunhya
2023-11-02 7:58 ` Rémi Denis-Courmont
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=b0d8fdfe-a22d-4ed2-924b-92b0f1d10c85@gmail.com \
--to=derek.buitenhuis@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