As requested long ago by Nathan, Velvet Revolver has now support for h264 encoding. This is still experimental, but should work both for proxy generation and full-res copy creation. Reasons for such change are actually simple.
Technically, the suitable formats for editing are ProRes and MJPEG. This is especially true when you want to change the speed of those videos by using the “Speed control” effect in Blender’s Video Sequence Editor.
Second, my old recycled laptop computer, a Pentium M from 2005 (!), finally died. I was never able to edit videos on it, for obvious reasons. Last month, I bought myself a newer machine, an i5 ThinkPad from 2010. Video editing there seems promising with SSD, but asking for ProRes or MJPEG is simply too much because disk space there is an issue – the files are simply too big.
Used and older computers are great because you save some electronic waste and prove, at the same time, that 2D video can be achieved at lower cost machines, which can be crucial for activist groups. If you’re in the field, you need something fast, light and at hand, so h264 makes a hell lot of sense in this scenario.
Thanks Nathan for pointing that out in the first place and encouraging it, even though time has been short here and it took way longer than expected to have the peace of mind of implementing those changes.
Beware, though! Changes with the “Speed Control” effect may not render or work as expected since h264 is not an intra-frame codec. Test whatever you want to do before assuming things will go smooth with the 30′ documentary you have to deliver in the next 2 days.
Also: as computaholic pointed out at GitHub, Velvet Revolver was having issues when converting files down from 59.94fps to 29.97fps. When Blender 2.77 was released, direct access to the project’s FPS* seemed not to be working, so I changed the code to mimic the way Blender was supposedly calculating it. It turns out the old code is actually working now, so I raised the previous version from the dead and any problems should be fixed now.