We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now recordChild does not trigger a timeupdate event for the first frame of each multi render.
This means you might have single frames every x % of your video, which are just incorrect.
Currently, I have hackily fixed this by adding:
await new Promise((accept) => setTimeout(accept, 25)); await page.evaluate(`scene.emit("timeupdate", { currentTime: ${time} })`); await new Promise((accept) => setTimeout(accept, 25));
after await page.evaluate(timeFunction as any);
await page.evaluate(timeFunction as any);
in the recordChild method in child.ts.
recordChild
child.ts
but i am sure there is a better way to implement this fix
The text was updated successfully, but these errors were encountered:
@mhaddon
Does the media exist in the scene?
Sorry, something went wrong.
What version of Scene.js is it?
latest scenejs and latest scenejs render, it is only the first frame that each "multi" generates.
its when you try to make your own render logic using the timeupdate event, the normal css rendering is working as expected
Are you using "timeupdate" in your scene?
If so, how about using "animate" instead of "timeupdate"?
The animate event will fire whenever setTime is called.
No branches or pull requests
Right now recordChild does not trigger a timeupdate event for the first frame of each multi render.
This means you might have single frames every x % of your video, which are just incorrect.
Currently, I have hackily fixed this by adding:
after
await page.evaluate(timeFunction as any);
in the
recordChild
method inchild.ts
.but i am sure there is a better way to implement this fix
The text was updated successfully, but these errors were encountered: