highest possible careful tweaked settings for very high image quality with enough stability for short takes up to 5 - 8 minutes.

Improved for best low light noise and textures in all modes, perfect for high iso, and excelent image texture in good light.

Arri Alexa image quality inside the GH2, (just missing the Alexa dynamic range of course)

default version:

*SH and H slots are better for good light in low iso and for more detailed scenes in good light

*SH slot is higher quality and more stable with manual focus legacy lenses

*H slot more stable with native lenses with electronic contacts

*H slot also better for use with image stabilization

*hbr is better in good light than in low light

*default version is more stable in SH and H 720p and in HBR than the boson version

*24p 24H and 24L are the same of boson

*great quality in all modes

boson version:

*SH slot improved for low light textures and noise

*H slot better for good light in low iso, better for more complex details scenes in good light

*H slot is more stable for native lenses

*HBR does the low light / good light balance automaticaly for better noise in low light or better detail in good light

*24p has same noise quality in both good light or low light for constant image texture this keeps same random noise in all light conditions, good for intercut with SH

*a little less stable in 720p and HBR than the default version

*best quality in all modes

seta = workhorse default

setb = workhorse boson

setc = workhorse default lower datarate in SH and H for more stability in 720p and hbr

setd = workhorse boson lower datarate in SH and H for more stability in 720p and hbr

sete = same as seta, but the 24H and 24L are optimized to deliver sharpest image for steady complex detail scenes, it does the automatic adaptation in 24p for low light noise or good light steady complex detail scenes

setf = same as setc, but the 24H and 24L are optimized to deliver sharpest image for steady complex detail scenes, it does the automatic adaptation in 24p for low light noise or good light steady complex detail scenes

all tests performed in NTSC with the Sandisk 32GB SDHC Class 10 U1 45Mbps card.

transcode the original mts files to Apple ProRes 422 full range using the 5DtoRGB free software before editing to avoid the diagonal pattern rain problem. Try the ProRes HQ, normal and LT versions to perceive the best balance between quality/file size.

as of september 05 2014 all versions are modified flowmotion 2.02 with extensive careful tweaking

please donate to www.personal-view.com

I did some research in the forum about PTools settings but I did not find the answers I need...

What happens is:

Only GOP which works good for 720p 60p are GOP 30 and GOP 3, all other GOP gives diagonal pattern (rain) in computer monitor. But the GOP 3 in 720p always stops recording and it seems the card is not the problem, I am using Sandisk 45mbps and other people says the Sandisk 95mbps also stops recording in 720p hacks... The GOP 6, 12 and 15 works for some shoots, but they are unstable (sometimes stops recording) and gives diagonal pattern (rain) in computer monitor. GOP 3 stops recording all the time, no matter the bitrate (I tested GOP 3 from 40 to 200mbps). So GOP 30 is the only option.

Problem is: when using the GOP 30 the camera encoder always keeps the bitrate very low when the camera is quiet, when there is no motion in the image, and this gives lots of macroblocking and texture lost in low light. Even when I set the bitrate to 48mbps or 64mbps in PTools the camera does not record 48mbps or 64mbps, StreamParser shows only around 23mbps... (for static low light shoots)

The auto quantizer all to motion or all to details did not make any difference. So I did some try to change settings in TESTER options of PTools. I fount the TOP and BOTTOM bitrate limits and I enabled it with 48000 and 42000 for top and bottom 720p, but this makes no effects in encoding, bitrate is still very low for static shots no matter the bitrate I type in PTools...

Only thing I found to make the bitrate encoding keep high is the GOP 3, but camera stops recording in all 720p shoots, the GOP 3 just works for 1080p.

So I am wondering if there is a way to keep the bitrate high using GOP 30 in 720p...

Any suggestion welcome, thanks.

I've been quite impressed by the great image detail the all-new 4:4:4 hacks produce, but I still have problems with their RELIABILITY, colors don't look that great for me and I also have to deal with HORIZONTAL WAVES that destroy the image. Unfortunately, I'm also quite new to hacking and don't really know which patch to choose.

Is there anyone who could recommend a patch with a bitrate around 40MBPS and INTENSE COLORS (e. g. similar to Canon 5D Mark III or GoPro Hero Silver Edition) and that could be used BOTH WITH a LUMIX G Vario 14-140MM and a SLR MAGIC HYPERPRIME 12MM?

Thanks in advance. Simon

==MY TEST==

I went on a shoot this weekend, and was using Sandisk Extreme 16gb 30mb/s cards. I wanted to ensure both spanning and playback in camera for the shoot, so I went with driftwoods "spanmybitchup" patch. I did just a few short preliminary tests: the test I did was to shoot the papasarts star chart (which I've attached--I also attached the more extreme codec test chart v2 2010), and let it run. I waved my hand around in the frame from time to time and also had some talking to get audio. Everything seemed good: I was getting spanning and smooth playback in camera with audio. (EDIT: also attaching Stray's death charts with color information!)

==MY SHOOT==

So during the shoot, after a few shots, I was getting the message "motion image cannot be played" for all my clips (or something like that I don't remember exactly)--my heart sunk! An actor asked me to check to see if we recorded something on a previous take, I had to say that "yes it was" without checking. I was worried about requests for playback--and this was only with one actor: imagine this on shoot with clients! For certain shots, I wanted to be sure that something was recorded since I wasn't at the camera, and I couldn't do this. The scene I was shooting was an actor in a car at night--he was lit and most everything else was dark. That's when I got the messages. I put in a new Sandisk card, and formatted it. Reshot the same scene and I was getting the same error.

==LESSONS==

1) In camera playback is important at least for some of us, and for some, like me, it is even more important than low gop. For me, I am willing to forego a very very high quality low GOP setting (awesome work driftwood!!) that doesn't have playback in camera on good SD cards for an improved long GOP with ultra reliable in camera playback. I'm NOT saying that everyone wants this or should want it (especially if you have the cash for more super high end SD cards or for extra harddrive space). But I'm guessing some people are in my situation as well.

2) It seems there's a relatively standard procedure for patch development (using streamparser, tweaking settings incrementally, etc etc). BUT there seems to be no standard procedure for testing spanning and in-camera playback. You might not think that makes a difference, but it seems that it does: it seems to matter what you shoot when you are testing things like spanning and in-camera playback. Or, at least the number of clips you shoot or the ISO you shoot at makes a difference: otherwise, I don't know how to explain the divergence between my pre-shoot tests and what happened on the shoot. I welcome some constructive thinking about standardizing spanning and camera playback tests.

==DESIRES==

The ideal for me would be to get a hack that improves quality over the stock settings, that has very very reliable spanning and in-camera playback with audio, and works on good quality cards like the Sandisck 30 mb/s (16gb). I know some people are getting the SandDisk extreme pro 64gb cards... but a lot of people (like me) already have a stash of good quality cards and don't want to fork over even more money to get these super high end cards.

I did test w/ @cbrandin 's (Chris's) 66M patch. We know that this doesn't span (but getting around 10 or 11 minutes is okay for me, although I'd love spanning). But what I did notice is that I couldn't get in camera playback with this either. I'm going to try the 44M patch.

Thoughts?