@pwc That excel file is great and I sure appreciate it and would appreciate your continued updating... Al Edit: Any reason you did not add lpowell and EOSHD mjpeg settings?
@aljimenez In the July 23 LPowell post the link to the ini file of the 100Mbps GH2 Low Light MJPEG 1080p Patch is missing. As for EOSHD I couldn't find any posted ini files.
Just load @LPowell's ini and change 480p width to 1440 and 480p height to 1080 and use that VGA MJPEG mode in-camera for anamorphic shooting. With new PTools it works great.
A question for @Vitaliy_Kiselev - why is MJPEG resolution currently restricted to max 1920 and 1080? Going further produces no improvement in resolution? Or just too unreliable?
I'd also be interested to test MJPEG resolutions beyond 1920x1080. While that was the maximum practical resolution on the GH1, the GH2 is clearly capable of recording reliably at significantly higher MJPEG bitrates and resolutions.
1920x1080 is only a little smaller than DCI 2K 16:9 resolution: 2048x1152. This frame size can be easily cropped to 2048x1080, the delivery resolution for digital cinema format. Shooting at 2048x1152 would also make it more convenient to intercut GH2 MJPEG footage with Red 2K footage.
If you used a 1.33X anamorphic lens with a 2560x1080 MJPEG frame size, the GH2 would produce native widescreen video files that would not require post-production stretching.
hacked my GH2 tonight in 10 minutes tops! Thanks Vitaliy, and all the testers! Just used the 42000000 and 35000000 recommended settings for 24H and 24L, Went smoothly, very easy. I'm waiting for a Ciecio7 FD to M4/3 adaptor. Once that comes, I'll get Vimeo+ and start in on some high quality stuff! (Eager to try out the short GOP stuff).
@Vitaily so how does this work? will there be subsequent versions of PTools as the hacking progresses?
@chrimsbroome Do it now! Stable is here :) I'm using the settings from this post: http://www.personal-view.com/talks/discussion/comment/7646#Comment_7646 . They are conservative - a moderate but substantial increase in video quality - but appear totally stable. I have cannot find a scene that will crash the codec with these settings. Just did an evening of shooting while sailing with these settings - lots of shots of water and wake and no problems, and they pass my "codec death speaker grille shooting" test.
+1, do it now. It's easy, and quick, and there's enough stable stuff even if you just up the bit rate to 42, its still worth it. And that way, you'll have gone through the process a couple times by the time there's something you REALLY want to try.
Thanks for the great work Vitaly! I've been using the "stable" (42/35) 24H setting on a fiction project and getting lovely pictures (even at 3200ASA!), but wanted to report that the sound is 2 frames out of sync (ahead of picture). My shoot is all double-system with a slate, so it's no big deal (Just means the editor can't be lazy and use Plural Eyes), but I wanted to report this in case no one had before.
@bdegazio I believe Mr. V has stated that AVCHD optimization is first priority, and for the most part, it seems as if this is exactly how he's going about things. He'll crack that first, then move on to the next important thing after, I'm sure.
Hi Vitaly and all -- congrats on getting so far on this great project! One thing I have not been able to find in the forums is whether the hack affects the photographic side of the camera at all, and also, whether it is reversible. If you load the hack, are you able to go back to original programing should you wish? Thanks in advance.
Hey everybody, I wanted to know if the hack allows 60i on PAL GH2. I am going to buy one soon while I'm here in shanghai, and I need 60i when I go back to the USA.
@sSTEV. Yes - the hack enables you to switch back and forwards between PAL (24P, 720p50, 1080i50) and NTSC (24P, 720p60, 1080i60). It also allows the language to be changed.
@Madhatter. I believe you would simply reload the original GH2__V10.bin firmware into PTool and not check any checkboxes except "Version increment". (Note the version doesn't actually increment on the camera - it stays at 1.0)