Originally posted by osv it is a tough scene, but 25Mbps should have been enough... what you really need a good two-pass encoder that does h.264.
the way to test your settings/encoder quality is to put a text or graphic overlay over some of the video... if it's not fairly sharp on the edges after the youtube upload, you know that the encoding job that was done on the upload was not up to par, because the graphic is not relevant to motion in the video.
if anything, since the graphic doesn't change in the frame, it leaves more bits to be allocated to the video footage itself.
i would also compare the youtube upload results both with and without the warp stabilizer, at the same upload bitrate settings for both... my prediction is that the non-warped upload will look cleaner, depending on how bad the footage was to begin with.
This is part of my archiving script, otherwise I'd need a ton of new hard drives...
avs2yuv "%%~nA.avs" -o - | x264-10b-r2377-1ca7bb9.exe --preset placebo --tune film --qcomp 0.65 --aq-mode=2 --crf 20.5 --fps 25 --input-res 1920x1080 --output "%%~nA.264" - --demuxer y4m
I'm using the latest 10 bit version of x264, at the very highest setting. Constant quality rather than VBR, cause some scenes can easily get away at 2 Mbps, while others need 25 (usually I get 6-8, though that also depends on the lens. The 50mm usually gets smaller files). Only setting the bitrate doesn't make sense to me. I do a color denoise prior to encoding on all files (pretty much like what Lightroom does per default), and a mild denoise in general. If you have any suggestion on where to upload the file I uploaded to YouTube I will do so.
I have attached 2 screen grabs, one from the original and one from the h264 file. I think the 2 star 60 Mbps MJPEG setting wasn't enough for a scene like that, sadly I didn't bring enough memory along to shoot at the highest quality setting all the time. In situations like that it'd be nice to have h264... which the K-3 does, but sadly it's the only format it supports. Rather than MJPEG they could let us shoot h264 at really high bitrates. Say 50-80 Mbps. Or have the encoder be more open ended, so if the scene needs it it can give much higher bitrates. The Sony a57 simply warns you that you shoot at a bitrate/setting that isn't Bluray compatible... why can't Pentax do something like that? Simply do a here be dragons pop up when you set something that CAN have downsides, such as very high bitrates. Say it needs to be processed, cause the bitrate is too high for any standard medium. Say, when selecting mechanical SR, that it can introduce noise in the audio track, and that it is advisable to shoot with a microphone that is isolated from the camera. And that it reduces battery life.
The warped footage looks pretty clean to me. There is a slight loss in resolution, but since there wasn't much to correct for - just a bit of jitter mostly - it didn't crop much. I think something like 10%?
@TomGarn: You can always convert the old footage to something more acceptable for Premiere, and since the resolution is so low you can go for something lossless like Huffyuv or better yet Lagarith.
As for the flow stopping here and there... either it's the low frame rate that you are talking about, or I have simply maxed out the range of the SR system when walking fast (I can't get stable video while running, for that you really need at least a glidecam). My dream would have been for the K-3 to cover the entire full frame area, and of course for it to do video SR. With such a range (and more rotational adjustments) you would be able to get ridiculously stable video... and to bracket a full frame photo at high resolution (i.e. the sensor would move to the top left, shoot, top right, shoot, bottom left, shoot, bottom right, shoot). That could be loaded into any stitching software and voila you have a very high res full frame image. Landscapers and architectural photographers rejoice! Alas that never happened...
I also looked at the Vimeo preset in Premiere, and saw 5 Mbps (!). The YouTube preset gives you 8 Mbps... still too low, but since YouTube will process the video anyway, and won't do such a good job at it (not surprisingly, encoding takes a lot of CPU power at high settings, and decoding those files is also quite challenging, so YouTube just does a quick and dirty encode job... they just have too many files to encode).
The GH3 is really popular for film making because it a) has ridiculously high bitrates when hacked and b) cause it does pixel binning... it takes ALL the pixels and scales them down to Full HD resolution. No aliasing, much higher light sensitivity, sharp video... it's I think the only camera that does that, perhaps other sensors aren't capable of reading out all pixels 25, 30, 50 times a second.
However there are people doing great work with Pentaxes... like this guy who is also on PF:
I have also seen Film Riot using a Pentax K-5 or K-7 several times, though mostly they will shoot a 7D or 5D it seems, and occasionally a RED. On the review of several glidecam-a-likes they've done a few months back you can see them use the Pentax. I wonder if they left the SR on for that extra bit of stability (just in case some bumps do get through).