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
This behavior is intentional. In V2, we replaced the event-based rendering system—which only updated the composition in response to changes—with a periodic update approach. During playback, the composition updates at the target frame rate (30 FPS), and when playback is stopped, it updates every 200ms.
The primary reason for this change is to better support automated video editing, which requires handling a large number of editing operations efficiently. In V1, the event-driven update system caused excessive GPU load due to frequent event propagations. By switching to periodic updates, we have decoupled GPU pressure from the number of editing operations, resulting in better performance and scalability.
I am using version 2.0.2, and I noticed that:
Steps to Reproduce
Environment
Version: 2.0.2 (bug exists) / 1.6.0 (working correctly)
Framework/Platform: Angular
Browser/OS: Chrome 132/Windows 11
The text was updated successfully, but these errors were encountered: