Open andrasferenczi opened 1 week ago
Thanks for reporting!
Objects are being passed between browser and Node.js and there is no useful way of undoing serialization of classes. We'll fix this by updating the docs to explicitly disallow non-JSON-serializable values.
To still improve it, in the next version the serialization will be consistent and in the Studio it will also turn into an object, to catch this earlier in the developer journey.
Makes sense, thanks. Based on your comments I got a better understanding of how Remotion works.
Couple minor doc comments I feel is missing from calculateMetadata
is that:
concurrency
defined in renderMedia
)selectComposition
is called
Bug Report π
I created the following composition:
Key points from this example:
calculateMetadata
returns a non-serializableclass
,Vector2
Vector2 [X: 10, Y: 10]
[object Object]
, which means it is no longer theVector2
classI think this is a bug, because:
calculateMetadata
does not mention any restrictions regarding non-serializable objectsinputProps
according to the docs, but this is no longer theinputProps
Is there a way to undo this serialization?
Thank you!