@piotremanuel After using IQ=20, Q = 8 on new Orion patch, I completely agree with this idea that AQ2 which samples around the Q = 10 mark that AQ2 could be the sweetspot. I have found that the AQ processing is perhaps a bit more taxing than finding the sweetspot Q whcih will still get you where you want to be in terms of quality. In many cases using AQ3 or 4 delivers only a few lines of macroblocks at the lowest Q (2 to 6). So its best to try and get most the picture where you can around the same mean average Q.

It wouldn't suprise me if motion benefits from this.

@stonebat Without the proper matrices I am getting lowered bit rate and visible macro blocking with the new ptool and firmware. I am trying to marry the Driftwood's Dark Matter with cbrandin 66 but it takes lots of testing and time. There is so much more to it than just mixing settings randomly... Besides, since 25p is inferior to 24p quality wise, I am not in a rush to jump exclusively to v1.1. And another thing, I feel AQ2 yields better results, but it's subjective.

@cbrandin 66Mbps on v1.0 firmware. I still haven't been able to achieve the matching quality with firmware v1.1. Comments welcome.

See the modified versions of @cbrandin's 44Mbps and 66Mbps settings.

Basically I removed all settings for testers only. Frankly I don't know much about all those complex settings. But I recall that @cbrandin's original intention was using only end user settings only. But the irregular cadence issue required more tweaking for hacked firmware 1.0. Now it's firmware 1.1.

The 44Mbps settings worked for all modes. The settings doubled default bitrates and have AQ4. No crash so far. This is my default settings.

The 66Mbps settings tripled default video bitrates and have AQ3 instead of AQ2. 24p and 60p modes worked fine, but HBR mode failed. See the stream parser captures. Sometimes in-camera playback didn't work. Hopefully more advanced testers can fix it.

Could do with your skills tomoz, we need another GH2 cameraman for Turin Brakes gig in Brighton.

@Nameless Great stuff, well filmed mate.

@driftwood A friend recommended the @cbrandin 44M settings and they are the only ones I have tried. I am not a tester type, finding all the necessary information and understanding how to hack my gh2 was difficult enough for me. The initial test went well so I didn't feel a need to change anything else ...until I checked the real life footage out.

I have to say I admire you guys for the immense work it takes for perfecting the settings.

I got V frames on 27 out of 123 files, almost all of those 123 have been cut in camera, and I think all of the 27 files have been cut in camera. @cbrandin said „StreamParser identifies frames as V frames when there is something wrong with a header and what type of video frame it is can't be identified by looking at transport stream header data.„ Using any software that allows .mts cutting results in stream parser almost always showing V frames. I thought it was bad so i decided to cut in camera since when testing I got no V frames on in camera cut footage.

So is there really anything to be worried about? The footage looks nice and the chart full of V frames looks just as any other chart only without colors ; )

@driftwood I'll assume “the encoder goes skewifth” means It's not working properly ; ) Any idea why?

Is it time to hack my GH2 with some other settings? Would you recommend some rock solid ones that would work on a class 6 card and keep the file size within reason? Of course „maximum quality” ; )

@paglez

No way I'll be able to finish porting this weekend.

@piotremanuel Thanks for the report mate. Yeah seaquake Quantum, etc... all should be good. These are highly measured settings and shouldn't ever go wrong.

I have a question about @cbranidin 44M

I used it with Pretec 32GB class 10 cards, actually more like class 6 cards. I shoot everything 24p. I did some tests and everything looked as it should (first screen)

I went on a vacation and my oh my, real life footage doesn't seem so perfect in stream parser. Where is the bitrate, where is the consistency?

Some of it was cut in camera, but I did some tests for in camera cutting and it looked in stremparser exactly the same as before cutting.

Is it the compression adapting itself to different conditions, or is there something wrong?

Help will be very much appreciated.

It's my first post here so if there's a better place to post this question please tell me.

@driftwood Oh, I didn't find any mention of it anywhere.. I think it should be spelt out for those who have write problems with cbrandin patch.

@driftwood The iso tick problem with the latest ptool applies to Chris's patch. Without it ticked it spans, goes on for over half an hour and doesn't give any card errors. I haven't experimented with yours in this way yet but it's a good hint, thanks. Unfortunately the current weather is not permitting the "moon test" where I had the problems.