@1agh/maude 1.0.8 → 1.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -237,7 +237,18 @@ try {
|
|
|
237
237
|
// no renderMediaOnWeb container support (and no audio need); an artboard with
|
|
238
238
|
// no registered comp (ordinary/CSS) has nothing for renderMediaOnWeb to render
|
|
239
239
|
// — both fall through to the frame-step path below.
|
|
240
|
-
|
|
240
|
+
//
|
|
241
|
+
// MAUDE_RENDER_SKIP_WHOLE_COMP=1 forces the frame-step path even for a
|
|
242
|
+
// registered comp. @remotion/web-renderer's renderMediaOnWeb never RESOLVES on
|
|
243
|
+
// the headless Linux render worker (measured on the cloud fleet AND CI — even
|
|
244
|
+
// a 12-frame comp and even muted; WebCodecs itself works, per the caps probe,
|
|
245
|
+
// so it is something in web-renderer's whole-comp pipeline that wedges). On
|
|
246
|
+
// that host it only ever burned the renderMediaOnWeb timeout and then fell to
|
|
247
|
+
// frame-step anyway — so the worker skips it and goes straight to the path
|
|
248
|
+
// that WORKS, reclaiming those minutes for the actual (muted) render. The
|
|
249
|
+
// desktop, where renderMediaOnWeb works and carries audio, leaves it on.
|
|
250
|
+
const skipWholeComp = process.env.MAUDE_RENDER_SKIP_WHOLE_COMP === '1';
|
|
251
|
+
const useRenderer = !skipWholeComp && !!renderLib && format !== 'gif' && !!compId;
|
|
241
252
|
|
|
242
253
|
// When the whole-comp renderer path throws we DON'T fail the export. The most
|
|
243
254
|
// common cause is a `RangeError: Maximum call stack size exceeded` from
|