4 ms·
Decoding sure, but I was saying about encoding, my Macbook mid 2015 comes with "Intel Iris Pro 1536 MB" and takes 25% cpu to capture screen with Quicktime, whil
by alfonsodev 7y ago
Decoding sure, but I was saying about encoding, my Macbook mid 2015 comes with "Intel Iris Pro 1536 MB" and takes 25% cpu to capture screen with Quicktime, while newer MacBooks >=2016 come with HEVC, which after some searches I found out is also called H.256[1][2], and is not just in Macs[3]
[1] https://support.apple.com/en-us/HT208238 https://support.apple.com/en-us/HT208238
[2] https://www.macrumors.com/guide/hevc-video-macos-high-sierra-ios-11/ https://www.macrumors.com/guide/hevc-video-macos-high-sierra...
[3]https://www.techspot.com/article/1131-hevc-h256-enconding-playback/ https://www.techspot.com/article/1131-hevc-h256-enconding-pl...
EDIT: I see now the label 2016, so opening question didn't make sense :) sorry.
- kalleboo 7y agoThey also have encoding. The software might not be using it properly though. https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video I think screen recording is slow not due to the video encoding but since it defeats standard GPU acceleration of the GUI in order to be able to capture the contents
- namibj 7y agoIt really shouldn't. You just feed the framebuffer both into the DMA output, and in the H.26x encoder. If needed, use another framebuffer space if the encoder is slow, so you don't _have_ to recycle the buffer after this frame, and risk the encoder not being done yet.