Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [REFUND-REQUEST] Vulkan F2F travel
Date: Mon, 29 Apr 2024 20:22:23 +0200 (CEST)
Message-ID: <Nwewo2r--3-9@lynne.ee> (raw)
In-Reply-To: <CAPBf_On45ejfShMCxuxK94eSnUETYRyV5L=gRJCnguycztzwSQ@mail.gmail.com>

Apr 29, 2024, 19:30 by gseanmcg@gmail.com:

> Hi,
>
> On Mon, Apr 29, 2024 at 12:58 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
>
>>
>> Hi
>>
>> On Sat, Apr 27, 2024 at 02:16:36PM +0200, Lynne wrote:
>> > Hi,
>> >
>> > I'm requesting a reimbursement for attending the Khronos F2F
>> > event in Brussels on 2024-04-26, where I gave a talk about the
>> > current status of Vulkan Video integration into FFmpeg:
>> >  - Currently implemented decoding features
>> >  - What we would like to be improved (stability, speed and testing from all vendors)
>> >  - Currently implemented WIP encoding features
>> >  - What we would need to implement in order to match nvenc in terms of quality on most vendors
>> >
>> > Also, I collaborated on future extensions to the standard,
>> > and discussed AV1 issues recently found in the specifications
>> > and how we could fix them.
>> >
>> > 95 GBP: Eurostar to Bruxelle-Midi
>> > 95 GBP: Eurostar from Bruxelle-Midi
>> > Total: 190 GBP
>>
>> LGTM
>>
>> PS: maybe we should make a page on trac that links to all talks from all FFmpeg developers
>>
>
> Is there video/audio from this talk? I would like to watch/listen if so.
>

Unfortunately, Khronos doesn't really publish them.
But if you want, I can explain what is lacking somewhere.
_______________________________________________
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:[~2024-04-29 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27 12:16 Lynne
2024-04-29 16:58 ` Michael Niedermayer
2024-04-29 17:29   ` Sean McGovern
2024-04-29 18:22     ` Lynne [this message]
2024-05-04 15:37 ` Stefano Sabatini

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=Nwewo2r--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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