It is nice to hear that the attempt to revive GH1 is making a progress. I hope @humpman 's findings soon can be port to the old GF1 and G2. If I could only find a cheap GH1, then I will join the party soon.

very interesting things.

would it be possible to enable in the user section all the scalling tables for GH1 as we have in the GH2 ?

how did you find the values for the tables?, are they from the original firmware or are they your own tables?

can you develop a tutorial how to create the user settings? it seems you need to put the user ini file in same folder of ptool and then the ptool load it

the "codec profile high" can be better maybe, how to force the camera to use it?

the min qp in gh2 on my patches vary from 12 to 16. I think 16 can be a good number for the qp min on GH1 due to bitrate is lower than gh2.

I think the max qp need to be 51 so the camera decides how much to increase it.

how to create scalling tables for B frames? it would be useful for 24p, because the GH1 cannot increase datarate so much, so using IPB is good idea. Also, are these scalling tables in your user ini file for all recording modes?

I did a look in the user ini file in notepad and the scalling tables design is different from gh2. ingh2 all numbers start with "0x" then there are the two hex numbers: 0x1111 in hex = 0x1717 in decimal on the gh2. the gh2 have 48 numbers separate with comma and space, 16 for Y, 16 for Cr, 16 for Cb. How is this design in GH1 numbers?, it seems there is only one 0x in beginning and then all numbers comes together...

thanks.

@humpman thanks for answers!

if the default original is codec profile high, so it seems to be better to keep it as is...

if the camera can vary qp from 0 to 51 so it seems to be good also. vary from 16 to 51 maybe can help to save datarate for other image areas because avoid camera to use from 0 to 16. the range 16to51 works pretty good on gh2.

it would be interesting to enable the scalling I, P and fallback for 720p50, 720p60 and 1080p24 (I think the camera records native 24p when we check this option). If you enable them I can prepare some tables for you to try.

Are you sure the GH1 camera does not have B frames when recording native 1080p24 ? Did you take a look on it using StreamParser software?

Remember: I do not own the GH1 so all things I am doing is based on my previous GH2 knowledge.

thanks again.

thanks for answer

please, give a try on the sete and setf in last post of this link below to perceive if they can be stable, I used my gh2 knowledge to try to get stable progressive on gh1 with a 48Mbps datarate which is good enough for reasonable quality:

http://personal-view.com/talks/discussion/13045/gh1-how-many-people-are-using-it-these-days-is-the-gh1-woth-the-effort-to-improve-the-hackpatch#Item_10

thanks

@humpman is right.

Actual GH1 improvements require more research of encoder code and developing new patches as he did, not changing few numbers.

@konjow settings that dated May 4 are pretty stable but it's interlace. Anyway i don't see problem on it, you can easily deinterlace it in post.

@humpman your post dated May 4 show very impressive detail from your settings. I wish QP and I-P scaling can also be ported to the other old Lumix e.g. GF1 or G2.

Here is. One new patch that helps on stability. Added new settings. In this settings i tried to get very high quality in low light.

I did a careful read in all the topic since page 1 first post and compared to my previous GH2 knowledge:

it seems that codec profile is better to keep original so we can use scalling tables.

in GH2 I got good results using QP min = 16 and QP max = 51 (I perceived that lowering QP min to less than 16 is pointless if you do not have enough datarate as GH1 is and keep the QP min = 16 maybe can save camera processor power and allow smaller QP for other image areas because camera will not low it so much anymore).

about scalling tables I have some ideas based on my previous GH2 development, also considering the lower datarate on GH1, but I do not have GH1 to do tests so better not suggest values now, but if you ask me I would try these because they are the best for GH2 even in lower datarate, in good or low light, in low or high iso, for both 1080 and 720:

Scalling I=0x606, 0x909, 0x909, 0xC0C, 0xF0F, 0xC0C, 0x1212, 0x1515, 0x1515, 0x1212, 0x1818, 0x1B1B, 0x1818, 0x1E1E, 0x1E1E, 0x2424, 0x606, 0x909, 0x909, 0xC0C, 0xF0F, 0xC0C, 0x1212, 0x1515, 0x1515, 0x1212, 0x7272, 0x7878, 0x7272, 0x7E7E, 0x7E7E, 0x9C9C, 0x606, 0x909, 0x909, 0xC0C, 0xF0F, 0xC0C, 0x1212, 0x1515, 0x1515, 0x1212, 0x7272, 0x7878, 0x7272, 0x7E7E, 0x7E7E, 0x9C9C

Scalling P=0x606, 0x909, 0x909, 0xC0C, 0xF0F, 0xC0C, 0x1212, 0x1515, 0x1515, 0x1212, 0x1818, 0x1B1B, 0x1818, 0x1E1E, 0x1E1E, 0x2424, 0x606, 0x909, 0x909, 0xC0C, 0xF0F, 0xC0C, 0x1212, 0x1515, 0x1515, 0x1212, 0x7272, 0x7878, 0x7272, 0x7E7E, 0x7E7E, 0x9C9C, 0x606, 0x909, 0x909, 0xC0C, 0xF0F, 0xC0C, 0x1212, 0x1515, 0x1515, 0x1212, 0x7272, 0x7878, 0x7272, 0x7E7E, 0x7E7E, 0x9C9C

Scaling Fallback=0x909, 0xC0C, 0xC0C, 0xF0F, 0x1212, 0xF0F, 0x1212, 0x1818, 0x1818, 0x1212, 0x1B1B, 0x2121, 0x1B1B, 0x2424, 0x2424, 0x3636, 0xC0C, 0xF0F, 0xF0F, 0x1212, 0x1515, 0x1212, 0x1515, 0x1818, 0x1818, 0x1515, 0xB4B4, 0xC6C6, 0xB4B4, 0xD8D8, 0xD8D8, 0xFCFC, 0xC0C, 0xF0F, 0xF0F, 0x1212, 0x1515, 0x1212, 0x1515, 0x1818, 0x1818, 0x1515, 0xB4B4, 0xC6C6, 0xB4B4, 0xD8D8, 0xD8D8, 0xFCFC

these scalling above also have the benefits of same inter frame and intra frame values which is better for low camera processor usage, same I and P tables which gave excelent results in my tests with values in perfect point between lower and higher quantization in the matrix avoiding artifacts and improving quality. In my tests I found that using higher matrix quantization in P frames does not help quality and increase artifacts. These conclusions are for GH2 but maybe can be useful for GH1.

about "limit setting", if it is the same behavior as GH2 it will mean each frame maximum size, this value must be a little higher than the maximum frame size that you see in streamparser, it seems that this value tells to the camera what kind of maximum frame size to handle. If this value is lower than the maximum frame size the camera will freeze. See the maximum i-frame size in streamparser and set this value to 20% more, this works ok on GH2. Use values which can be divided by 8. You need to know if it is using bit or byte values to do the type correctly.

I believe that if we can get perfect settings combination using all patches maybe we can stabilize the Native 24p, try it!

try to use the patches I developed in last post of my GH1 topic as a base for your user settings, they can be useful to pursue stability, after stability you can try raise datarate, this is what I did with GH2. I recommend the latest setA that I did as a base for your user settings. Try the others also from last post in my GH1 topic.

about the "constant for 720p = 3456000" and "constant for 1080p = 777600" it seems that it means the frame buffer size, (or maybe the maximum frame limit). uncompressed 4:2:0 720p frame is 1382400 and uncompressed 4:2:0 1080p frame is 3110400. Doing the maths you will perceive that the camera allows a 4:1 compression ratio for the frames size. I believe that the original values are enough to raise datarate to 42Mbps or 32Mbps but you can try to raise these values to 3:1 compression ratio: "constant for 720p = 460800", "constant for 1080p = 1036800" (Or value less than 999999 for the 1080p)

Problem now is: I do not own the GH1 !!!

Good Luck !!!

@apefos you forgot that i did user settings only for interlace mode, so if you check the Native 24p, that settings won't work. You can't stabilize native 24p with actual patches. GH2 has different encoder, so it's another story. I just can't understand what a problem on using interlace. Progressive and interlace on GH1 actually have same quality on this area.

@apefos i understand your desire to help. Anyway, i think we forgot one most important thing, we just need to shoot something :=)

@apefos ok, i added seperate user.ini for progressive mode in case if somone wish to develop and test new settings. Remember that it affects on both 1080p and 720p modes.