🎥 Make videos programmatically with React
Clarify screenshot encoding overhead
Jonny Burger1039f19d3bd5
diff --git a/packages/docs/docs/shared-memory-chromium-patch.mdx b/packages/docs/docs/shared-memory-chromium-patch.mdxindex 14ad4f7c4d..4d9cc684b4 100644--- a/packages/docs/docs/shared-memory-chromium-patch.mdx+++ b/packages/docs/docs/shared-memory-chromium-patch.mdx@@ -8,7 +8,7 @@ crumb: 'Rendering'Traditionally, screenshots of webpages are captured using the [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/), then encoded as either JPEG or PNG. Which one is used is determined by the [Video Image Format](/docs/renderer/render-media#imageformat) option.-FFmpeg later decodes these images back into bitmaps before encoding the video. This compression and decompression adds work, and JPEG can reduce image quality before video encoding begins.+Encoding these images is pure overhead, since FFmpeg later decodes them back into bitmaps. JPEG compression can also reduce image quality.From v4.0.534, Remotion uses a special version of Chromium to optimize rendering in some cases. Instead of compressing each image, the bitmap is shared directly with Remotion's FFmpeg binary, which encodes it into a video.