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
When importing animated media from a format that supports storing the frame timing, to me there are two sensible ways of importing it. This distinction becomes important when the FPS of the video one is trying to import is different than the project FPS. Either:
1 video frame = 1 project frame. With this method, no frames are dropped or duplicated, but you lose the timing information. If rotoscoping, the resulting video will likely be too slow. If accompanying audio is imported, it will not be in sync.
1 second of video = 1 second in the project. With this method, the timing is preserved, but it may contain duplicated or drop frames from the imported video. Key poses the users might want to focus on could be removed. Duplicated frames could add bloat to the project's storage and memory requirements. In both cases, it becomes more difficult to retime the animation.
Actual Results
Currently, the Movie Video import uses method 2, while the Animated GIF (soon to be Animated Image) import and the Layers from Project file import both use method 1.
Expected Results
I think we should be importing animated media in a consistent way by default, and perhaps also offer the other way as an option before importing. I would like to hear thoughts on what we think the default should be, and how to best present this to the user as an option.
Developer Notes
Also of consideration is importing sources with variable frame rates. This is sometimes used in animated GIFs, and while I have never seen a video use it, technically most video formats support it. This may add additional complexity to implementing method 2.
Another issue with GIFs (and soon WebPs) occurs at higher frame rates/shorter frame durations. Browsers universally override short frame durations. So in such cases should they be treated as the file specifies, or as they would be displayed in a browser. And when they have different implementations, which browser?
The text was updated successfully, but these errors were encountered:
Issue Summary
When importing animated media from a format that supports storing the frame timing, to me there are two sensible ways of importing it. This distinction becomes important when the FPS of the video one is trying to import is different than the project FPS. Either:
Actual Results
Currently, the Movie Video import uses method 2, while the Animated GIF (soon to be Animated Image) import and the Layers from Project file import both use method 1.
Expected Results
I think we should be importing animated media in a consistent way by default, and perhaps also offer the other way as an option before importing. I would like to hear thoughts on what we think the default should be, and how to best present this to the user as an option.
Developer Notes
Also of consideration is importing sources with variable frame rates. This is sometimes used in animated GIFs, and while I have never seen a video use it, technically most video formats support it. This may add additional complexity to implementing method 2.
Another issue with GIFs (and soon WebPs) occurs at higher frame rates/shorter frame durations. Browsers universally override short frame durations. So in such cases should they be treated as the file specifies, or as they would be displayed in a browser. And when they have different implementations, which browser?
The text was updated successfully, but these errors were encountered: