New Feedback
After updating the application and adding a context window with a question about frame rate before rendering, a problem appeared: although the application correctly detects 24 fps, I get a file with a length 2 times longer than the original one, and 1:2 frame skip. The audio track ends exactly in the middle. I attach the raw file and the render results. When doubling the frame rate when rendering to 48 the problem is partially solved, but the video is actually rendered in 48 fps and this increases the resulting file size.
The bug is being reproduced on both macbook pro m1 and iPhone 15 pro.
Previously there was no such problem and the render worked perfectly. I realize that the renderer is not a core feature of your product, but it is very useful for me to quickly work with apple-log right on my phone. Thanks in advance.
1.Use h.265 apple log file (attached)
2.Export
3.Render
4.Application correctly detects 24 fps
5.x2 longer video file and 1:2 frame skip :(
Hi @alex728 - looks like the video can not be decoded properly on a frame-by-frame basis which is what the current experimental implementation is trying to do. I'm aware of these issues and know why this is happening but I don't have time to prioritize video rendering right now which is why the feature will remain behind the experimental flag for now.
@monokee This is definitely a priority feature! I cant get halation or grain the same a different way. Really hope you can fix this soon, its one of my favorite and needed features
@monokee Perhaps, as a temporary solution until this bug is fixed, you could revert back to the previous version of the render engine? After all, everything was working correctly before the window with the FPS question appeared. Or add a switch to temporarily select the old render version rather than the new "experimental" version?
Why this is so important to me.
I now can't render my apple-log videos directly on my phone:
3- Mobile safari doesn't support large files and the render just stops where previously I was able to work with longer files.
@alex728 @osoloso unfortunately there is no new experimental version of the render engine I could roll back.
The reason this entire feature is experimental is because I have zero control over video decoding and encoding right now because it's entirely handled by the browser engine. When the browser or any of the decoders/encoders that ship with the browser engine change, so does the implementation in Color.io.
If you've seen any changes in the rendering behaviour, your browser has updated because I haven't touched this code path in over 4 months and I'm developing this by myself.
There are other ways to handle video rendering entirely on the app side without relying on the browser but this is not something I have been able to allocate time to yet as it's a massive undertaking and I'm working on other updates right now.
the render skip bug is back for me as well !
Merged in a post: