@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:

1. I need to choose 48 fps instead of 24 to keep the speed correct
2. The size of the file increases by 2 times
   3- Mobile safari doesn't support large files and the render just stops where previously I was able to work with longer files.
3. As the commenter before me wrote - the great video post effects remain inaccessible if you only use the LUT.

@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.