In usable lower iso Gh1 grade a way better and look like has more DR (For me) Same may say GM1 is more "cinematic":) but not for me. I compere them 2 cos M1 has low bitrate AVC but newer. GH1 miss just better iso performance:) but/and is wider! Both the same f1.7 500 iso200 standard all -2 straight from camera snaps from timeline

Also try this settings, tell me if you can see differences compare to previous settings.

@yskunto personally i don't like mud in shadows, on trees etc. You can see it on screenshots above compare to GM1. So i trying to solve it.

I don't like this ones, it appears even on static i-frames.

In my researches about GH1 previous patches, seeing streamparser screenshots, and comparing to the GH2 behavior, I perceived that in GH1 the I frames size can be very big and P frames size can be very small in size.

So, when increasing the datarate in GH1, the I frames size can become a problem for the frame buffer and frame limits, because they become too big. Also the GH1 options in PTool do not provide complete settings to tweak the frame limits and frame buffer as we can do in GH2.

The solution for this would be to tweak the GOP TABLES to keep the I frames size within something about 5:1 compression ratio which is pretty good quality for an I frame and this would keep the I frames size to be not too much big and the camera limits and buffer could work ok even with higher datarates. The GOP TABLES shares the data among the I and P frames and can make the I frames size bigger or smaller, when it increase I frame size it decrease P frame size, and when it decrease the I frame size it increase P frames size.

In my math calculations I perceived that 32Mbps with Overall 34 can probably be the maximum stable for the camera, after I found some informations about the maximum frame size which is possible for the GH1 to handle.

So finding the GOP TABLES in GH1 firmware and allow to tweak it in PTool can be very useful to achieve higher stable datarates. Also useful to get better noise and texture avoiding mud because bigger P frames are welcome to do this.

@humpman thanks for the streamparser screenshot. it shows and confirms what I was wondering to see: the average I frames size is about 8x the P frames size. This is useful information to create a patch which keeps the frames size under camera limits.

I developed a patch which has the gop and datarate tweaked to keep the I frames size under the constant values considering this 8x ratio between I and P. This patch is tweaked for 720p and 1080p, pal and ntsc, with custom matrix.

please give it a try, and remember to record more than 20 seconds in each take to get a better streamparser file reading:

Screen above i get with these settings, @apefos thx for organization of user.ini

I will do span test as its essential for me

@humpman @apefos I did quick test for spanning. And the results are:

setd: motion error quite often unless camera steady like rock on sandisk extrim 45mbs 32gb pictures attached

ip8x atrefacts over the place unless camera steady like rock 2 pictures attached -files can't be play by QT(black screen)

@humpman little lower please :)

@apefos just some another couple tables, seems that not affected on anything.

I did simple spanning test at night. Don't know about quality because its not stable.:)

ip8x_correct. patch seems to be ok 2 pics attached. biterate 34 Span test I switched off too soon 3.9gb in 30 minutes.

@humpman in gh2 there are some tables called "deblocking tables" it helps to avoid the diagonal rain problem and also minimizes macroblocking, did you see these tables in gh1 firmware? thanks.