GH1 firmware research volunteers required

PTool 3.36d released (development version for testing only)

http://www.pentax-hack.info/firmware/pan/ptool3d.zip

Added Version compare patch.
Short description: You need to set version increment as usual first time then using this patch. But since next upgrade you can omit increment at all, and leave this patch only.

This is risky patch, as can make body non-upgradable. Probability of this is very low. Bit it can happen, as it is untested patch. So, one brave tester is required.

Can you add the ability to load lower versions, such as the original Panasonic releases?
I know I keep bugging you with this, but I think it is doable. You may limit it to the same release group, such as 1.3x. This will then take care of your concerns regarding lens firmaware getting out of sync.

Thanks and good luck.
 
hi,

I have v1.2 firmware on my gh1. If i put a negative value say -15 on the version change i get the value of 0x0123 291. v1.32bin is 0x0 132 306. maybe its pure coincidence going by the numbers but would this make my firmware hack v1.23? This would then mean I can do 15 updates and still be able to revert to v1.32 original firmware if needed for warranty?

thanks.
 
so the latest untested Ptools 3.36d will let you update anytime to original 1.32 firmware and it will show as v1.32 on camera? If so that's brilliant!

thanks
 
Yes, but we've all gone chicken

Yes, but we've all gone chicken

so the latest untested Ptools 3.36d will let you update anytime to original 1.32 firmware and it will show as v1.32 on camera? If so that's brilliant!

thanks

Will give it whirl tonight
 
tester13, my question to you is -- is there any way you can optimize the bandwidth to prioritize the I-frame? I had one clip which had really bad "pulsing" -- too much detail for the I-frame, so every half-second it would "glitch" for a frame or two while the rest of the GoP "caught up".

I think that especially with the higher bitrates for the overall GoP that are being achieved, that we could really see some benefits from allocating more bandwidth to the I-frame so that the I-frames are cleaner. Is that possible?


For keyframe pulsing, you usually want lower bitrate allocation to the I-frame, and higher to P-frames. ie. you want to lower the I:P ratio (and lower the P:B ratio if it was using B-frames) . By having a lower ratio, the quality difference between P=>I frame transition is less, everything looks more even to the naked eye, and there is not as much as a quality jump.
 
Testing ptool 3.36d - well, I think it was me who asked for this so I guess I have to be the brave one! - wait for result...

Success, as far as I can see. Fuller report in next post.
 
Last edited:
What I did to test 3.36d -

I used that version of ptool to add add two increment to the version number (this being only my second use of ptool). I also ticked the "version compare" patch. I also ticked "native 24/25p" as this is so far the only extra feature I definitely want (so if I was stuck on that version I'd at least have that.

I then saved that as GH1__134.bin, inserted card in camera, upgraded firmware as usual. Took one short video. I noticed that the first frame was a bit blurry which seems to be the result of native 24/25p, so the upgrade appeared to be working. And certainly the camera was not bricked.

Then I took out the card, and deleted GH1__134.bin from it, and replaced it with the original Panasonic firmware GH1__132.bin - crossed my fingers and put the card in the camera and pressed play. Eureka, it asked if I wanted to upgrade, I confirmed, it displayed the progress bar as normal, and completed. I then took a short video shot. Replaying that did not have a slightly blurred first frame, so it appears on that basis to have gone back to the official firmware.

I'm going to bed for the night in about ten minutes, so any immediate questions or checks you want me to do will have to be asked right away - otherwise, see you in about 7 hours!

BTW this is a PAL camera in case it makes the slightest difference.

Edit - further confirmation that it works now obtained - replaying the first of the two clips mentioned above (25pN) is reported by Nero as progressive. Playing the second (original firmware, (25p in 50i wrapper)) is reported as interlaced.

This would appear to mean that by carrying two (small capacity) cards, one with original firmware and one with modified firmware, one can now swap at will, or have a couple of configurations of modified firmware and swap according to requirements. Brilliant.

(Having taken that risk, am I now absolved from donating?! Only joking, I will donate soon).
 
Last edited:
Awesome again Tester13!

Awesome again Tester13!

this gets better and better, the ability to go back is really cool.

Ozpeter, do you feel there are big improvements from native 25p over original 50iwrapper, as a PAL user? or is it removing a step in your workflow?

ps, thanks from everyone for trying this first, am going to give it a whirl tonight.
 
Ozpeter, do you feel there are big improvements from native 25p over original 50iwrapper, as a PAL user? or is it removing a step in your workflow?

I'm still evaluating what difference the native 25p makes to certain problems I've encountered with editing software.

BTW version number in camera now shows body 1.3, lens 1.2
 
Last edited:
I guess having gone back to the original firmware, which would have the ability to go back to earlier versions not permitted, I couldn't now go back to an even earlier official version without first using ptool again to change the firmware to permit that? So if anyone wanted (for some reason) to go back to pre-1.3, you'd have to use 3.36d to only remove the version comparison feature, then after that, go back to the earlier firmware. Or load that earlier firmware into ptool with nothing ticked except the new 'remove version comparison' box. I suspect a crystal clear FAQ entry is required on this else there will be loads of questions.
 
I guess having gone back to the original firmware, which would have the ability to go back to earlier versions not permitted, I couldn't now go back to an even earlier official version without first using ptool again to change the firmware to permit that? So if anyone wanted (for some reason) to go back to pre-1.3, you'd have to use 3.36d to only remove the version comparison feature, then after that, go back to the earlier firmware. Or load that earlier firmware into ptool with nothing ticked except the new 'remove version comparison' box. I suspect a crystal clear FAQ entry is required on this else there will be loads of questions.

I do not recommend to go to earlear firmware (I mean really earlear - 1.22, etc, not unpatched 1.32). It can be risky , as many settings are stored at eeprom, plus some lens related things reside inside.
 
For keyframe pulsing, you usually want lower bitrate allocation to the I-frame, and higher to P-frames. ie. you want to lower the I:P ratio (and lower the P:B ratio if it was using B-frames) . By having a lower ratio, the quality difference between P=>I frame transition is less, everything looks more even to the naked eye, and there is not as much as a quality jump.
This doesn't make any sense to me. At all.

The i-frame is clearly nowhere up to the task of properly representing the image. As you look at the footage, it's obvious that the I-frame starts out mushy and blocky, then the first P-frame improves on it significantly, then the next P-frame brings it up to standard, and it stays that way throughout the GoP. Then, at the start of the next GoP, SLAM -- there's a huge quality drop as the inadequate I-frame starts the cycle over again.

Whereas if more was allocated to the I-frame, it'd look better in the first place, and you wouldn't need as much bandwidth allocated to the P-frames because they wouldn't have to work as hard to bring the bad I-frame up to snuff.
 
Greetings all,

I had been using pTools 3.35 and missed 3.36 so I tried 3.36b. My settings were identical to the wiki's except I checked "version compare" and "Native 24p/25p", upversion GH1__134 to GH1__135. It updated and when I checked the version number it was "body firmware Ver. 0.0", "lens fiirmware 1.2". Holy Crap! My GH1 is now a freakin' virgin!

I am using a Sandisk Extreme III class6 and it's too slow. All my class6 cards are too slow. MJPEG still would record only a second at HD. AVCHD at 24p would record but would not play back but instead of crashing it just gave me a screen saying it wasn't going to play that file. Hit play again and I'm back out.

Wondering if I could still update I decided to change some values: DO NOT USE THESE VALUES!!!

Video buffer 50,000,000
Video Bitrate Adjustment 50,000,000
Video Bitrate Adjustment Simplified 50,000,000
Overall Bitrate adjustment 34,000,000
Limiting Bitrate adjustment 40,000,000

Upversion to GH1__136 and it worked! Body version number is still 0.0. I discover that it is impossible to to trip the shutter. Press and it doesn't freeze but becomes totally unresponsive and turning it off will not reset, gotta remove the battery.

Removed card and replaced GH1__136.bin with GH1__133.bin, just drag and drop. Replaced card and the sucker did a downversion! Checked the version and now body is showing 1.3 and everything works.

Great job Tester13. Imo send you some cheddar.
 
This doesn't make any sense to me. At all.

The i-frame is clearly nowhere up to the task of properly representing the image. As you look at the footage, it's obvious that the I-frame starts out mushy and blocky, then the first P-frame improves on it significantly, then the next P-frame brings it up to standard, and it stays that way throughout the GoP. Then, at the start of the next GoP, SLAM -- there's a huge quality drop as the inadequate I-frame starts the cycle over again.

Whereas if more was allocated to the I-frame, it'd look better in the first place, and you wouldn't need as much bandwidth allocated to the P-frames because they wouldn't have to work as hard to bring the bad I-frame up to snuff.

What sample where you looking at ? Perhaps you are desribing something else, not keyframe pulsing ?

Were you looking at coded order, or display order?

What you are saying doesn't quite make sense , because in theory a P-frame cannot be higher quality than the I-frame it's using as reference. (That P-frame is coding the difference between the IDR reference frame)
 
Last edited:
Back
Top