lordtangent
2007 September 21st, 04:44
I was thinking about the long shutter speeds and it occurred to me that of course, when you shoot with a shutter speed like 1/6 of a second you are by necessity shooting at 6 frames per second. It's pretty obvious, but I got excited anyway once I understood the ramifications. It's a very easy way to "under crank" the camera! The only side effect is since the HV20 only record 24 or 60 distinct images per second, you get that "steppy" effect where it duplicates the frames to fill the time. No problem... frames are easy to throw away...
I came up with an AVISynth script which uses the FDecimate plug-in to automatically remove the extra frames and re-time the clip to 23.976 FPS. It works great. Of course the end result produces frames that have what amounts to a 360 deg shutter. For under cranked effects it looks pretty cool though, at least IMHO.
One thing I figured out, which I'm not sure anyone else has mentioned explicitly, is that if you use a 1/30th of a second shutter speed the HV20 effectively produces "30p" also. Again, the shutter time is an "unnaturally long" 360 deg and some people might not like the look. But at least to my eye it looks much nicer than 60i. And of course, the 1/30th sec shutter speed is also an entire stop of exposure more than 1/60th. One stop is a lot when you need it. I'd rather have a 360deg shutter and sort of long-ish motion blur than have to resort to using gain any day. But I'm thinking I might shoot in this "30p" mode under regular circumstances. It's a nice way to split the difference between 24p (and all the hassles involved) and 60i (with it's not too filmic field based structure) I'm going to do more tests.
Here is an unprocessed .mt2 clip at "30p"
http://hv20.info/yopu/30p.m2t
It's a little shaky because it was so freaking windy when I shot it my light little tripod was actually shaking!
Here are some shots done at 1/6th sec and then processed to remove the extra frames from the .m2t stream.
http://hv20.info/yopu/24p_from_6p_1.mp4
http://hv20.info/yopu/24p_from_6p_2.mp4
http://hv20.info/yopu/24p_from_6p_1_QT_encoded.mp4
I encoded them with AVIdemux to h.264. A buddy of mine raised a flag that Quicktime chokes on my AVIdemux encoded frames. I'm not too wild about Quicktimes encoder (more on this later) so if you want to watch my clips I suggest you try Mplayer or Media Player Classic. Trust me, you'll like them. They both happily play stuff both Quicktime and Windows Media Player choke on and being Free Software, neither is used as a front end to sell you "iTunes" or other crap like that.
I also encoded clip #1 with Quicktime. For anyone who already has Mplayer I urge you to compare the QT compressed and the x264 (via AVIdemux) encoded files. QT totally mutilates the color. This is a good example of what I mentioned in one of my other threads regarding "video" color space vs. full range. QT seems to assume you WANT the blacks padded and there does not seem to be any way to turn that behavior off. AVIdemux, on the other hand, encodes what you hand to it without messing with the color too much. (not only that but it's much more flexible and tweakble in other areas)
Comments? I'm really interested to learn any other tricks people have figured out with the HV20 and also what other people are using for encoding their final output.
I came up with an AVISynth script which uses the FDecimate plug-in to automatically remove the extra frames and re-time the clip to 23.976 FPS. It works great. Of course the end result produces frames that have what amounts to a 360 deg shutter. For under cranked effects it looks pretty cool though, at least IMHO.
One thing I figured out, which I'm not sure anyone else has mentioned explicitly, is that if you use a 1/30th of a second shutter speed the HV20 effectively produces "30p" also. Again, the shutter time is an "unnaturally long" 360 deg and some people might not like the look. But at least to my eye it looks much nicer than 60i. And of course, the 1/30th sec shutter speed is also an entire stop of exposure more than 1/60th. One stop is a lot when you need it. I'd rather have a 360deg shutter and sort of long-ish motion blur than have to resort to using gain any day. But I'm thinking I might shoot in this "30p" mode under regular circumstances. It's a nice way to split the difference between 24p (and all the hassles involved) and 60i (with it's not too filmic field based structure) I'm going to do more tests.
Here is an unprocessed .mt2 clip at "30p"
http://hv20.info/yopu/30p.m2t
It's a little shaky because it was so freaking windy when I shot it my light little tripod was actually shaking!
Here are some shots done at 1/6th sec and then processed to remove the extra frames from the .m2t stream.
http://hv20.info/yopu/24p_from_6p_1.mp4
http://hv20.info/yopu/24p_from_6p_2.mp4
http://hv20.info/yopu/24p_from_6p_1_QT_encoded.mp4
I encoded them with AVIdemux to h.264. A buddy of mine raised a flag that Quicktime chokes on my AVIdemux encoded frames. I'm not too wild about Quicktimes encoder (more on this later) so if you want to watch my clips I suggest you try Mplayer or Media Player Classic. Trust me, you'll like them. They both happily play stuff both Quicktime and Windows Media Player choke on and being Free Software, neither is used as a front end to sell you "iTunes" or other crap like that.
I also encoded clip #1 with Quicktime. For anyone who already has Mplayer I urge you to compare the QT compressed and the x264 (via AVIdemux) encoded files. QT totally mutilates the color. This is a good example of what I mentioned in one of my other threads regarding "video" color space vs. full range. QT seems to assume you WANT the blacks padded and there does not seem to be any way to turn that behavior off. AVIdemux, on the other hand, encodes what you hand to it without messing with the color too much. (not only that but it's much more flexible and tweakble in other areas)
Comments? I'm really interested to learn any other tricks people have figured out with the HV20 and also what other people are using for encoding their final output.