@Shaveblog It's odd that you would bury the lede like that. I clearly stated that I'm using the recommended card, and had no luck spanning. The first was a full card, so couldn't record another small clip, and the other tricks (record a short clip, turn off/on) didn't work either.

And then you say your play-back "may have to do with the fact" that you removed "Pasadena" (which is clearly not a standard step when installing the patch) almost as an aside. But if that is a way to get consistent (or in my case any) in-camera playback, it would appear to be a pertinent piece of information for @driftwood as those of us with external recording would likely accept lesser audio to sync with in exchange for the ability to review clips in the camera.

Thanks for the tip

@driftwood or anyone really "Subsequently, you get a finer low frequency matrix that strives to knock out artefacting at the expense of QP and higher bitrates." What does QP stand for?

Great tips guys - will try.

Quantization parameters QP

@babak I dnt know if this procedure will solve you problem. In order to disable pasadena, go to audio settings and uncheck all the options under it. By the way, shooting at 24p, I could not see the issues you described.

@marciocons thanks but the idea originated with @Shaveblog

@TATZU and @jebsly I was attempting to max-out the video bitrate with Moon T8 24H (wide-angle lens, lots of small moving elements in the image) and believe I did from looking at the stream parser results. I have since been able to get in-cam playback, with short clips at an average bitrate of about 50mbps (poorly lit, interior, shot with a Nikon 50mm). Perhaps it's only when you hit that max bitrate with the video that the audio settings make a difference for in-cam playback? I will try to replicate my treetop test today with just the audio settings reverted to stock, to see if I can playback the shot in-cam.

With that said, a quick look at the Moon T8 image does seem superior to T7, and the one quick shot of my skin tone (a light brown/beige) does seem subjectively more pleasing and more consistent than it did with T7, which was more than acceptable.

I shot a test clip with T8 on the 24p low setting and had an average bitrate of around 80mbps. Then I shot a few on the high setting and averaged around 73-75mbps. It is my understanding that this is a variable bitrate setting based on the results from my tests and the reported findings of other users. Larger file sizes of 140-150mbps do not concern me, in fact I have become accustomed to them by now. @driftwood Is there any possibility of releasing a more fixed bitrate version? I like to get as much encoded info as possible, it seems that a lot of bitrate is sacrificed with this patch. I however an not the expert so my opinion doesn't count for much, just my two cents. Thank you Driftwood for everything you have done so far!

@driftwood Further testing with both SanDisk Extreme 45MB/s and SanDisk Extreme Pro 90MB/s 64GB SD cards shows the same FCPX import error with 24H footage, but 24L footage has no issues with FCPX import at all.

The odd thing is this doesn't appear to be simply a matter of excessive bitrate with the 24H settings, as T8 seems no higher in terms of bitrate than your other all-I patches like T7 and IV2, which FCPX has never had problems rewrapping to H.264.

I confirmed that the importing errors occur whether I ask FCPX to import only (just H.264 rewrap) or to transcode to ProRes 422.

Hope this helps you, Nick, and thanks for the new Moon. So far it's your best looking patch IMO, with more natural skin tone and detail than T7 or IV2.

@driftwood thanks for clarifying! And thanks for t8! I notice i am getting pretty low bitrates with this hack does that mean the quality is less than t7? is there a way to make the bitrate equal or higher on average than t7 i have plenty of space on my sd cards and want the best quality possible out of my trusty old GH2 =D

@Shaveblog I agree with you except I enjoyed seeing the videos of what people created with Driftwood's work, even if they were post processed. It showed some of the potentialities of the hack regardless of processing or content.

Thanks so much @driftwood for your great work here. Here are some cropped stills from short clips I shot with T8 and Spizz T7 (taken from transferred footage in FCP7 timeline – footage shot on sandisk 95mbs 64gb, with canon fd 50mm f1.8 lens, aperture on 5.6). I have been specially looking at HBR qualities. There is an HUGE DIFFERENCE between HBR and 24H on T8 which is very surprising. The HBR footage looks very pixelated around the edges and very noisy, practically unusable. These differences were less extreme with Moon T7. With Spizz T7 the HBR footage looks much better than T8(bit rates: 71.3 & 68.5mbps). But unfortunately Spizz T7 doesn't span...

@babak Intra HBR 25p setting = just not enough power in the GH2 because its progressive structure is wrapped in a interlaced picture and HBR logarithms takes around twice the processing economics out of the codec than 720p. HBR30 being 3 GOP isn't as bad.

For HBR recordings try Spizz T7. I believe its the best looking HBR (3 GOP with B frames) and 720p (6 GOP with B frames) around at the moment.

DREWNET T10

Im just finalising the new DREWnet T10 'ClassiX' GOP (12 PAL/15NTSC), the 24p setting is using a newly developed 'Intravenus v3' matrix (4,4,4,127,4,4,4,127,etc...) which renders all recordings at a constant 80Mbps (the quanitser automatically changes dependent on the detail. This matrix is the finest (non coarse) hi/low frequency matrix ever implemented on the GH2.

Its extrememly powerful and can only be created on the DREWnet setting to achieve bottom QP of 14 on a 12/15 GOP (An Intra variation would cost around 280Mbps to achieve this so its impossible to implement on a GH2 - however, a frame /bitrate limited moon setting for close up/mid shot/ less detail shots is possible - requests accepted!). Skintones are breathtaking and grading is a pleasure. It'll be released soon.

Here's a picture of a 24p DREWnet T10 ClassiX render in Elecard Streameye.

@driftwood Are you seeing the same import error with FCPX and T8 I described or is it just me?