Reply to thread

Message

<blockquote data-quote="LopeDeAguirre" data-source="post: 1887043" data-attributes="member: 408334">I think my computer is fine, thanks.I did some testing and found the following. Hardware seems to be assigned to a task at Apple's discretion. With ffmpeg one can transcodeffmpeg -i x.mkv -c:v h264_videotoolbox y.mkvIn the example, the videotoolbox seems to use Quicksync. At least the execution is quite fast and the &quot;GFX AVG&quot; goes up to 0.15, so I assume it is Quicksync, which I think is running on integrated GPU hardware. [Fun fact: Trying insteadffmpeg -i x.mkv -c:v hevc_videotoolbox y.mkvshows &quot;GFX AVG = 0,00&quot;, but it is still very fast. It seems to use not Quicksync on the iGPU but the T2 instead, because it features hardware hevc compression.]Seems the hardware selection is transparent to the user and (of course) dependent on what is available, which makes sense.Ok, at least the GPU hardware on the CPU can be made use of via libraries - maybe it happens also elsewhere.</blockquote>

[QUOTE="LopeDeAguirre, post: 1887043, member: 408334"] I think my computer is fine, thanks. I did some testing and found the following. Hardware seems to be assigned to a task at Apple's discretion. With ffmpeg one can transcode ffmpeg -i x.mkv -c:v h264_videotoolbox y.mkv In the example, the videotoolbox seems to use Quicksync. At least the execution is quite fast and the "GFX AVG" goes up to 0.15, so I assume it is Quicksync, which I think is running on integrated GPU hardware. [Fun fact: Trying instead ffmpeg -i x.mkv -c:v hevc_videotoolbox y.mkv shows "GFX AVG = 0,00", but it is still very fast. It seems to use not Quicksync on the iGPU but the T2 instead, because it features hardware hevc compression.] Seems the hardware selection is transparent to the user and (of course) dependent on what is available, which makes sense. Ok, at least the GPU hardware on the CPU can be made use of via libraries - maybe it happens also elsewhere. [/QUOTE]

Verification

Name this item. 🍎