When recording movies, savestates are primordial to the process, because in tool-assisted speedruns you want to go back and optmize as much as you want and need.
I tested current v0.4.0 release and the most recent build and when you're recording a movie you can savestate, but when you loadstate the movie unfortunately ends recording. Would be a nice feature being able to go back and retry your inputs.
Another suggestion is having savestate naming using the movie file name, so your normal ("movie-less") savestates aren't loaded when you're recording a movie of the same game and vice-versa, for example:
Normal gameplay Super Mario World save states:
Super Mario World_1.mss
Super Mario World_2.mss
etc
Super Mario World movie save states:
moviename_1.mss
moviename_2.mss
etc
with them being completely different, based on what the played did. So when you're playing normally it would only save/load Super Mario World_X.mss saves, and while recording/playingback movies it would only save/load moviename_X.mss saves.
When recording movies, savestates are primordial to the process, because in tool-assisted speedruns you want to go back and optmize as much as you want and need. I tested current v0.4.0 release and the most recent build and when you're recording a movie you can savestate, but when you loadstate the movie unfortunately ends recording. Would be a nice feature being able to go back and retry your inputs.
Another suggestion is having savestate naming using the movie file name, so your normal ("movie-less") savestates aren't loaded when you're recording a movie of the same game and vice-versa, for example:
Normal gameplay Super Mario World save states:
Super Mario World movie save states:
with them being completely different, based on what the played did. So when you're playing normally it would only save/load
Super Mario World_X.msssaves, and while recording/playingback movies it would only save/loadmoviename_X.msssaves.