Re: [FFmpeg-user] CPU and GPU

I hope what the analogies below will help folks better understand the technology we use. Transistors are to logic gates as quarks are to electrons, protons, and neutrons. Logic gates come in 2 flavors: AND and OR, and it's from them alone that all other digital elements are made. Logic

Re: [FFmpeg-user] CPU and GPU

On 03/02/2020 11:14 AM, Carl Eugen Hoyos wrote: Am Mo., 2. März 2020 um 14:35 Uhr schrieb Mark Filipak : That is not what I meant. What I'm getting at is that it appears that the latest streaming protocols & methods are being developed via ffmpeg, then being tested-debugged-retested-etc. via

Re: [FFmpeg-user] CPU and GPU

Hi, > What is implemented in FPGAs is not solely so-called software-in-silicon. > Sometimes it is software-in-silicon -- marginal speedup -- but usually > software algorithms are realized as systems of FSMs (finite state machines) > -- huge speedup -- that simply mimic the original software

Re: [FFmpeg-user] CPU and GPU

Am Mo., 2. März 2020 um 14:35 Uhr schrieb Mark Filipak : > That is not what I meant. What I'm getting at is that it appears that > the latest streaming protocols & methods are being developed via ffmpeg, > then being tested-debugged-retested-etc. via ffmpeg users, then > implemented in FPGAs by

Re: [FFmpeg-user] CPU and GPU

On 03/02/2020 07:24 AM, Moritz Barsnick wrote: On Mon, Mar 02, 2020 at 04:57:23 -0500, Mark Filipak wrote: I used to work at Intel as a product line architect. I sat on 3 divisional planning councils, including graphics processors, and co-chaired one. [OT, sorry] OT, eh? Just like

Re: [FFmpeg-user] CPU and GPU

On Mon, Mar 02, 2020 at 04:57:23 -0500, Mark Filipak wrote: > I used to work at Intel as a product line architect. I sat on 3 > divisional planning councils, including graphics processors, and > co-chaired one. [OT, sorry] BTW, I have worked as Intel Corp. as well, incidentally both in graphics

Re: [FFmpeg-user] CPU and GPU

On 03/02/2020 05:12 AM, Carl Eugen Hoyos wrote: Am Mo., 2. März 2020 um 10:57 Uhr schrieb Mark Filipak : I used to work at Intel as a product line architect. I sat on 3 divisional planning councils, including graphics processors, and co-chaired one. Later, I represented Wyse Technology in

Re: [FFmpeg-user] CPU and GPU

Am Mo., 2. März 2020 um 10:57 Uhr schrieb Mark Filipak : > I used to work at Intel as a product line architect. I sat on 3 > divisional planning councils, including graphics processors, and > co-chaired one. Later, I represented Wyse Technology in industry > technology standards, engineering

Re: [FFmpeg-user] CPU and GPU

On 03/02/2020 03:56 AM, Carl Eugen Hoyos wrote: Am Mo., 2. März 2020 um 03:48 Uhr schrieb Mark Filipak : So codec engineering companies like NGCodec, MainConcept, Beamr and MulticoreWare turn open source-based, ffmpeg workflows into FPGAs that, when mature firmware implementations, chip

Re: [FFmpeg-user] CPU and GPU

Am Mo., 2. März 2020 um 03:48 Uhr schrieb Mark Filipak : > So codec engineering companies like NGCodec, MainConcept, Beamr and > MulticoreWare turn open source-based, ffmpeg workflows into FPGAs that, > when mature firmware implementations, chip companies like Intel & NVIDIA > turn into real

Re: [FFmpeg-user] CPU and GPU

On 03/01/2020 11:01 PM, Ted Park wrote: Hi, So codec engineering companies like NGCodec, MainConcept, Beamr and MulticoreWare turn open source-based, ffmpeg workflows into FPGAs that, when mature firmware implementations, chip companies like Intel & NVIDIA turn into real hardware: masked

Re: [FFmpeg-user] CPU and GPU

Hi, > So codec engineering companies like NGCodec, MainConcept, Beamr and > MulticoreWare turn open source-based, ffmpeg workflows into FPGAs that, when > mature firmware implementations, chip companies like Intel & NVIDIA turn into > real hardware: masked GPUs. Do I have that right? I think

Re: [FFmpeg-user] CPU and GPU

I'm not sure I'm hijacking this thread. The subject is actually quite related. Welcome to The Matrix. I had no idea. So codec engineering companies like NGCodec, MainConcept, Beamr and MulticoreWare turn open source-based, ffmpeg workflows into FPGAs that, when mature firmware

Re: [FFmpeg-user] CPU and GPU

> Am 02.03.2020 um 01:45 schrieb MediaMouth : > Part of the original reason for posting CPU vs GPU question in the first > place was just a curiosity about how FFmpeg was handling various workloads. > Already I use it in automated pipelines as a welcome alternative to Adobe > Media Encoder.

Re: [FFmpeg-user] CPU and GPU

> On Mar 1, 2020, at 2:28 PM, Dennis Mungai wrote: > > On Sun, 1 Mar 2020, 19:55 Carl Eugen Hoyos, > wrote: > >> Am So., 1. März 2020 um 14:11 Uhr schrieb Ted Park >> : >>> FFmpeg's videotoolbox implementation is missing ProRes support. >>> >>> Oh, I never

Re: [FFmpeg-user] CPU and GPU

On Sun, 1 Mar 2020, 19:55 Carl Eugen Hoyos, wrote: > Am So., 1. März 2020 um 14:11 Uhr schrieb Ted Park >: > > > > > FFmpeg's videotoolbox implementation is missing ProRes support. > > > > Oh, I never noticed that. It shouldn’t be too difficult right? > > Hopefully not. > > > Though I’m

Re: [FFmpeg-user] CPU and GPU

Am So., 1. März 2020 um 14:11 Uhr schrieb Ted Park : > > > FFmpeg's videotoolbox implementation is missing ProRes support. > > Oh, I never noticed that. It shouldn’t be too difficult right? Hopefully not. > Though I’m guessing the decoder would be of limited use for the command line > tools.

Re: [FFmpeg-user] CPU and GPU

> FFmpeg's videotoolbox implementation is missing ProRes support. Oh, I never noticed that. It shouldn’t be too difficult right? Though I’m guessing the decoder would be of limited use for the command line tools. I think I will try comparing them on cpu, I was going through the docs and

Re: [FFmpeg-user] CPU and GPU

> On Wed, Feb 26, 2020 at 5:34 PM Carl Eugen Hoyos wrote: > >> Am Mi., 26. Feb. 2020 um 17:15 Uhr schrieb Carl Zwanzig : >>> >>> On 2/26/2020 5:01 AM, Carl Eugen Hoyos wrote: Am Mi., 26. Feb. 2020 um 07:31 Uhr schrieb Ted Park < >> kumowoon1...@gmail.com>: > Just for completeness,

Re: [FFmpeg-user] CPU and GPU

curious, why are you dying to get prores ? qt has at best 8 bits h264 encoding, you're just resampble colours to 10 bits. may be nvenc's lossless 10 bits h264 coud fit your needs as well, i'd go ~16x real time... On Wed, Feb 26, 2020 at 5:34 PM Carl Eugen Hoyos wrote: > Am Mi., 26. Feb. 2020 um

Re: [FFmpeg-user] CPU and GPU

Am Mi., 26. Feb. 2020 um 17:15 Uhr schrieb Carl Zwanzig : > > On 2/26/2020 5:01 AM, Carl Eugen Hoyos wrote: > > Am Mi., 26. Feb. 2020 um 07:31 Uhr schrieb Ted Park > > : > >> Just for completeness, there is now the Afterburner card dedicated to > >> ProRes decode and render (not a GPU), but a Mac

Re: [FFmpeg-user] CPU and GPU

On 2/26/2020 5:01 AM, Carl Eugen Hoyos wrote: Am Mi., 26. Feb. 2020 um 07:31 Uhr schrieb Ted Park : Just for completeness, there is now the Afterburner card dedicated to ProRes decode and render (not a GPU), but a Mac Pro is the only platform that supports it and if you have that setup,

Re: [FFmpeg-user] CPU and GPU

Am Mi., 26. Feb. 2020 um 07:31 Uhr schrieb Ted Park : > > > As long as no hardware manufacturer supports ProRes (and this seems > > unlikely) > > no "GPU" ProRes transcoding support will be available. > > Just for completeness, there is now the Afterburner card dedicated to ProRes > decode and

Re: [FFmpeg-user] CPU and GPU

> As long as no hardware manufacturer supports ProRes (and this seems unlikely) > no "GPU" ProRes transcoding support will be available. Hi, Just for completeness, there is now the Afterburner card dedicated to ProRes decode and render (not a GPU), but a Mac Pro is the only platform that

Re: [FFmpeg-user] CPU and GPU

> "GPU encoding / decoding" nowadays means using a specific piece of > hardware inside > the GPU (but unrelated to any of its other usages) which is made to > support a particular > codec. As long as no hardware manufacturer supports ProRes (and this > seems unlikely) > no "GPU" ProRes

Re: [FFmpeg-user] CPU and GPU

Am Mo., 24. Feb. 2020 um 00:00 Uhr schrieb MediaMouth : > Is there something about transcoding to ProRes that makes GPU processing not > an option? "GPU encoding / decoding" nowadays means using a specific piece of hardware inside the GPU (but unrelated to any of its other usages) which is made

[FFmpeg-user] CPU and GPU

I'm watching ffmpeg crank out a ProRes from an older format QT at about 3 - 4x real time I'm on a 8-core machine, and it's using all of them + hyper-threading. It's really impressive. Also been converting to mp4 using GPU which is faster still -- mind-blowingly fast. My impression from