Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: [FFmpeg-devel] FFmpeg at NAB 2024
Date: Wed, 1 Nov 2023 21:37:04 +0100
Message-ID: <e30c8506-33f4-e85c-1c64-d9c987190905@mail.de> (raw)

Hi,

FFmpeg will have a booth at the next NAB from April 14th to 17th 2024 in Las 
Vegas [1]!

We reiceived an anonymous corporate sponsorship for the booth, so there are no 
costs for the FFmpeg project to it (and no obligations, of course).

Any FFmpeg developer is welcome to join in and man the booth with me, especially 
any developers based in the US or other american countries!

Share with us your broken workflows, unfulfilled requirements, ideas for 
enhancements and after show drinks at W4232 [2]!

-Thilo

[1] https://cloud.e.nabshow.com/2024/
[2] https://nab24.mapyourshow.com/8_0/exhview/?hallID=W&selectedBooth=W4232
_______________________________________________
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".

             reply	other threads:[~2023-11-01 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 20:37 Thilo Borgmann via ffmpeg-devel [this message]
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
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=e30c8506-33f4-e85c-1c64-d9c987190905@mail.de \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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