From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Hardware purchase request: AVX512-capable laptop
Date: Sat, 6 Jan 2024 19:26:42 +0100
Message-ID: <20240106182642.GK6420@pb2> (raw)
In-Reply-To: <1786204.uqgHB7WpJ2@basile.remlab.net>
[-- Attachment #1.1: Type: text/plain, Size: 1977 bytes --]
On Sat, Jan 06, 2024 at 08:11:51PM +0200, Rémi Denis-Courmont wrote:
> Le lauantaina 6. tammikuuta 2024, 18.21.00 EET Lynne a écrit :
> > As for whether this is a lifestyle choice, we generally pay for anything
> > that involves conferences, from train tickets, planes, parking, and
> > sometimes for location/stand rent.
>
> I would personally agree that representing FFmpeg at (non-FFmpeg-specific)
> conferences is a choice of life style. But it is normal to refund reasonable
> expenses made to represent the project.
>
> > I'm asking for a useful bit of permanent hardware.
>
> I don't question that providing you with one development system with the
> relevant Vulkan hardware support and AVX-512 is (or was) justified. If you do
> all the work for free (or paid by some other entity than FFmpeg), that's
> indeed excellent ROI.
>
> But the "business" case for a *second* system with all the disadvantages of a
> laptop is frankly not so clear.
I think some kind of remotely usable system does make sense for every volunteer
who wants to work. It simply results in more available time for that work.
Even i (who doesnt travel volunteerly around) have needed and used my notebook
for FFmpeg away from my desktop system many times.
When ive spend some time in appartments of other familiy members, when i had to
change my own apartment due to very noisy neighbors and so forth
Maybe a compromise would be a cheap laptop that is just used to login and
access the more powerfull hardware via SSH ?
But IMO having _nothing_ to work on FFmpeg when one wants to work on FFmpeg
seems a kind of bad setup for FFmpeg.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Breaking DRM is a little like attempting to break through a door even
though the window is wide open and the only thing in the house is a bunch
of things you dont want and which you would get tomorrow for free anyway
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-01-06 18:26 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 0:56 Lynne
2024-01-03 1:22 ` James Almer
2024-01-03 3:04 ` Lynne
2024-01-03 13:46 ` Michael Niedermayer
2024-01-05 17:36 ` James Almer
[not found] ` <NnCGm7x--3-9@lynne.ee-NnCGqE2----9>
2024-01-03 3:30 ` Lynne
2024-01-03 5:28 ` Kieran Kunhya
[not found] ` <NnCMnsG--3-9@lynne.ee-NnCMrYP--J-9>
2024-01-09 18:57 ` Lynne
[not found] ` <Nnj2jS_--3-9@lynne.ee-Nnj_bOo--3-9>
2024-01-14 17:23 ` Lynne
2024-01-15 8:57 ` Kieran Kunhya
2024-01-15 14:06 ` Paul B Mahol
2024-01-15 16:01 ` Rémi Denis-Courmont
2024-01-15 16:07 ` Paul B Mahol
2024-01-15 16:10 ` Nicolas George
2024-01-15 17:30 ` Michael Niedermayer
2024-01-15 14:59 ` Lynne
2024-01-15 16:01 ` Rémi Denis-Courmont
2024-01-15 17:36 ` Lynne
2024-01-15 18:50 ` Kieran Kunhya
2024-01-15 21:47 ` Michael Niedermayer
2024-01-16 0:03 ` Lynne
2024-01-16 10:05 ` Kieran Kunhya
2024-01-16 11:50 ` Paul B Mahol
2024-01-16 11:54 ` Kieran Kunhya
2024-01-16 14:59 ` Lynne
2024-01-17 13:37 ` Michael Niedermayer
2024-01-17 15:39 ` Lynne
2024-01-18 3:28 ` Michael Niedermayer
2024-01-18 4:07 ` Lynne
2024-01-18 8:42 ` Steve Williams via ffmpeg-devel
2024-01-18 9:52 ` Kieran Kunhya
2024-01-18 9:54 ` Paul B Mahol
2024-01-18 9:57 ` Kieran Kunhya
2024-01-18 17:19 ` Paul B Mahol
2024-01-18 22:59 ` Michael Niedermayer
[not found] ` <25e0763a-4b07-4328-ba93-354d23c8e591@advance-software.com-NoQj7Fn----9>
2024-01-18 15:37 ` Lynne
[not found] ` <NoPk9Ny--3-9@lynne.ee-NoPkD07----9>
2024-01-18 12:32 ` Lynne
2024-01-05 17:24 ` Rémi Denis-Courmont
2024-01-05 17:31 ` Kieran Kunhya
2024-01-06 10:38 ` Lynne
2024-01-06 11:09 ` Rémi Denis-Courmont
2024-01-06 16:13 ` Lynne
2024-01-06 17:57 ` Rémi Denis-Courmont
2024-01-06 18:01 ` Lynne
[not found] ` <NnUYG5V--3-9@lynne.ee-NnUYKEn----9>
2024-01-06 16:21 ` Lynne
2024-01-06 18:11 ` Rémi Denis-Courmont
2024-01-06 18:26 ` Michael Niedermayer [this message]
2024-01-06 20:15 ` Rémi Denis-Courmont
2024-01-06 21:06 ` Lynne
2024-01-06 23:36 ` Kieran Kunhya
2024-01-07 0:00 ` Lynne
2024-01-07 0:40 ` Kieran Kunhya
2024-01-07 1:55 ` Lynne
2024-01-07 3:14 ` Kieran Kunhya
2024-01-06 17:59 ` Michael Niedermayer
2024-01-06 18:21 ` Rémi Denis-Courmont
2024-01-06 18:28 ` Lynne
2024-01-06 17:42 ` Michael Niedermayer
2024-01-10 2:31 ` Michael Niedermayer
2024-01-10 2:56 ` Lynne
2024-01-10 13:06 ` Paul B Mahol
2024-01-10 17:58 ` Michael Niedermayer
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=20240106182642.GK6420@pb2 \
--to=michael@niedermayer.cc \
--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