You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of TurboWarp project creators like that you can increase the framerate and may want to create video projects with custom framerates out of the box. However, that can get a little tricky when the video player engine tries to adapt to the modified framerate, by changing the progress per frame so it runs the same speed as it would at 30 FPS. It should be easier to change the measurement unit so your video timeline can be measured in, say, 1/60ths of a second or any other unit instead. This is especially helpful for framerates like 44 FPS that don't divide nicely by 30 FPS ($30 / 44 = 0.68181818181…$).
With this, you'd also be able to measure time with units other than frames, such as seconds!
The text was updated successfully, but these errors were encountered:
#5 partially defeats the purpose of having nice round timestamps to measure against, though, but I might find a way for creators to choose to keep the current non-delta-timed behavior.
A lot of TurboWarp project creators like that you can increase the framerate and may want to create video projects with custom framerates out of the box. However, that can get a little tricky when the video player engine tries to adapt to the modified framerate, by changing the progress per frame so it runs the same speed as it would at 30 FPS. It should be easier to change the measurement unit so your video timeline can be measured in, say, 1/60ths of a second or any other unit instead. This is especially helpful for framerates like 44 FPS that don't divide nicely by 30 FPS ($30 / 44 = 0.68181818181…$ ).
With this, you'd also be able to measure time with units other than frames, such as seconds!
The text was updated successfully, but these errors were encountered: