Things to consider. If the textbox is active then you need to respect the native key commands for the textbox.
You have the ability to cmd + c & cmd + v to copy & paste objects in the editor. So you need to most likely prevent the event key from propagating upwards inside keyUp within the textbox.
So you aren't wrong it's just one more thing to consider amongst the million other things.
I have a backlog and will knock these out all in one day easily :)
Yeah. I think this is a known bug. Most likely if you dont move the trimmer or try and trim the whole clip messes up the FFMPEG command.
Hasnt effected paying users yet, so it's lower priority, but will be addressed soon.
I am thinking about improving that UX. Instead of immediately prompting the user to trim. This will be in the toolbar as a "tool". So if you want to trim a podcast episode you can, that is the main use case, so it might make the most sense this way.
I slapped this in quickly because I was targeted podcasters for the first few customers and this was a critical tool to have.
Minor nit: hitting backspace to delete a clip (pretty common in editing apps) forces the browser to go back.
You might also want to catch other types 'leave page' events and ask for confirmation so that the user doesn't lose their work accidentally.