Why does rendering a work range with GStreamer produce the wrong frames in Silhouette?

Updated March 17, 2026 14:48

Silhouette may render incorrect frames when using GStreamer to render a defined work range. This is a known limitation in the Silhouette GStreamer rendering workflow.

Articles in this section

Why are ProRes files imported as 16-bpc in Silhouette?
Why can’t I connect multiple Silhouette plug-ins in a chain?
Why do alpha channels with soft edges appear smaller in Premiere Pro when using the Silhouette plug-in?
Why does DaVinci Resolve limit Silhouette plug-ins to a single input?
Why does rendering a work range with GStreamer produce the wrong frames in Silhouette?
Why does sequence numbering start at 0 in Silhouette when using Flame?
Why does Silhouette not support rendering interlaced movie files?
Why does the PowerMesh Warp node in Silhouette produce different results than Mocha Pro?
Why doesn’t the image match in Particle Illusion or the Flare Editor when using OpenColorIO in Silhouette?
Why is copying and pasting Silhouette plug-in projects in an OFX host not allowed?