Open tsuza opened 5 months ago
Yes because it stops on what your seeing, meaning that the input/output points are valid when the frame is loaded.
I don't think that's a desired outcome, though. That's not how it works in any other video editing software ( e.g. Davinci ). It just creates annoyances when you're trying to trim a video.
To add to this, if you try to change the duration from the right ( I genuinely don't know how it's called... the right bracket for trimming, I hope you get it ), the video completely hangs and you can't interact with it anymore ( neither watching it nor trimming it ). Manually editing the values works fine though.
If you scroll through the timeline slightly too fast, the timeline will reset to the previous position ( most of the time, otherwise it'll reset to the last ""recorded"" position while you were scrolling ). It'll work fine if you do it slow though.
Here below I've provided a GIF to visually show what I mean:
I assume that the application is setting the timeline's position variable way too slowly, which creates this inconsistency compared to what I'm actually seeing.