[photawe]

Thanks!

1. I already have this - in my app, it's called "Static Video" - you select the "static video" tool, click where you want do set it, and drag for as long as you want.

2. I have this as well - I do need to test it a bit more, but it's there (as long as the audio + video are synchronized, which is the default) -> this works

3. This - I've added to my TODO list. About the audio - that makes sense too (also added to my TODO list).

A bit more details on 3. - I want to implement also something called a "lock" - basically, when you click it, you tell my app - I'm not gonna modify this anymore, so you can do whatever mojo you want, to optimize as much as possible. Will (in theory :D) work wonders on time remapping (which is what I'm working on right now).

^Does that make sense?

[gus_massa]

In some brig (15 minutes :) ) projects, I made two passes.

In the first pass I made a lot of small fixes to cover typos, drop down menus of the interface, sometimes the mouse, a transparent frame to have nice borders, ... but I didn't modify the timeline.

In the second pass I cut dead time, error that were erased, and other similar stuff that modify the timeline.

The first pass takes like x4 the length of the video, but the second pass only take x1/2 of the length of the video. (I had to fix a few details in the first pass, so I rendered it like 3 times.)

[photawe]

Assuming that is your workflow, I believe I should be able to cut that 4-5 times. Namely, I would cut down on your first time probably 3 fold, by making it waaay faster - I already have instant preview everywhere as you hover something with the mouse (I'm working on making this even faster).

Cutting down (trimming) videos is simply insanely easy and fast, so I assume I would cut that process in half also.

There might be some bugs to iron out, but if you'd like to try it out (the app), we can go from there.