Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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: Wed, 10 Jan 2024 18:58:24 +0100
Message-ID: <20240110175824.GU6420@pb2> (raw)
In-Reply-To: <NnlI9YX--3-9@lynne.ee>


[-- Attachment #1.1: Type: text/plain, Size: 3156 bytes --]

On Wed, Jan 10, 2024 at 03:56:22AM +0100, Lynne wrote:
> Jan 10, 2024, 03:31 by michael@niedermayer.cc:
> 
> > On Sat, Jan 06, 2024 at 06:42:40PM +0100, Michael Niedermayer wrote:
> >
> >> Hi
> >>
> >> On Wed, Jan 03, 2024 at 01:56:12AM +0100, Lynne wrote:
> >> > As some of you know, my laptop died nearly 2 years ago, and
> >>
> >> Why/how did the laptop die ?
> >> is it unrepearable ?
> >>
> >
> > ping
> >
> 
> It was a 4th gen Thinkpad X1 Carbon. A few drops of water got in
> between the caps lock before I noticed, by the time I did, it was too late.
> Battery circuitry is dead so it only runs on AC, frequency controller is
> dying so it runs at fixed Pentium II 350Mhz speeds, keyboard controller
> sees keys pressed all the time, touchpad is dead, USB is dead.
> The motherboard crammed essential components on the periphery
> and non-essential replaceable components like wifi and 4g modem
> right next to the CPU, so it was not great engineering.
> It did live a long life for 7 years, but only the shell remains mostly usable.
> I may not be able to put it back together as it was, since I lost some screws,
> as I kept working on it for months.

Sounds like corrosion, did you inspect it for signs of corrosion ?
I guess it would need a new mainboard. and maybe other parts
But it honestly doesnt sound like a few drops of water, you shure it was
a few drops only and only water ? ;)

I dumped a whole glass of water through my HP notebook once and after
drying it still worked just with some occasional artifacts on screen

Anyway iam not against buying you a new notebook from SPI-FFmpeg money
But you need to find some consensus with the community, its not my
decission its the decission of the community.
I do think though a cheap notebook would be aggreed to by the people
easier
in case you dont know, theres:
https://geizhals.eu/?cat=nb
you can select the features you want and it will show you whats available
for example with OLED and Zen 4 the cheapest is 799€
https://geizhals.eu/acer-swift-go-sfg14-42-r6vl-pure-silver-nx-kleeg-003-a2999043.html?hloc=at&hloc=de
or if you dont like acer
Theres a lenovo for 999 with oled and zen 4
https://geizhals.eu/lenovo-yoga-slim-6-14apu8-misty-grey-a3040258.html?hloc=at&hloc=de

or with IPS instead of OLED theres
https://geizhals.eu/lenovo-ideapad-pro-5-14aph8-arctic-grey-83amcto1wwat1-83amcto1wwde1-a3051616.html?hloc=at&hloc=de

again, i know neither so they may be bad choices, i have HP and acer notebooks here
all sub 1k €
also i dont know what you need exactly. Maybe a remote zen 4 is fine?
I did generally use my notebooks with FFmpeg by doing stuff remotely on a bigger box.
Even if you have a rather powerfull notebook, some high end desktop is going to build and
run tests much faster

PS: also dont forget to look at the screen size, a 17inch notebook and a 14inch differ in useability and
portability

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you think the mosad wants you dead since a long time then you are either
wrong or dead since a long time.

[-- 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".

      parent reply	other threads:[~2024-01-10 17:58 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
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 [this message]

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=20240110175824.GU6420@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