GH1 firmware research volunteers required

Thanks a lot for the much improved version.

I have a problem though: writing the patched firmware seems to be impossible for me - whatever filename I use (for example "GF1__123.bin" [two underscores]... also tried lowercase and different numbers) - I always get the error "Wrong filename, camera won't be able to read such file" ... and nothing is written. Never had that before with any previous ptool-version.

Solution found:
The problem was, that I had renamed my original fimrware file to GF1__122.orig.bin to avoid accidental overwrites etc.

Ptool did load the renamed firmware and accepted it 100%, presenting me with alle the change options, but would not allow me to save a patched version under any name, because it considered my renamed source-firmware-file not to be valid.
I guess this should be changed to having this check announced while loading the firmware with the "invalid"/unwanted filename, maybe with a warning: "Strange filename! Should be exactly 'GF1_122.bin' or 'GH1__132.bin' - is this really an original firmware-file? - yes/no".

Anyway... renaming my original source firmware-file back to 'GF1__122.bin' allowed me to later easily save a patched version.

Hope this helps anybody faced with similar difficulties.

Greetings,
Niklas
 
Unfortunately due to fact that I need to write all necessary tools myself progress will be quite slow.
Other than optimist PM messages I see no help from any developers.

Here is screenshot of one of small tools I am working today:

1278473215.jpg


Shows some of 1bpp resources.
 
Last edited:
Vitaliy,

Thanks for the great update. I wish I could help you with the project but I am not a developer. Instead I will just keep donating money.

I do have one request though. A lot of people really want to be able to try 1080p @ 24 FPS on the GF1. Is it possible to add that option to the GF1 firmware? I noticed you can change the GH1 to 720p @ 30 FPS so it seemed like it would be possible to have that option for the GF1.

Have you received the GF1 yet? If not what is causing the delay? Maybe we can help with that. If we are not developers is there anything else we can do to help besides donating money?

Anyway, thank you for your efforts and everyone elses hard work. You have really made this an outstanding product.
 
PTool 3.40d Updated

Please note that from this time version will change only if changes ahd been made to End users patches. All testers related changes will have same version number.

Updates:
Added "Preset Bitrate" and "Preset Bitrate 2" patches for AVCHD.
I hope that they'll improve encoder behaviour.
Added "Shutter press change" patch to start our low level keys related patches section.

Addition. Made few more tests on GF1.
Shutter press change leaves shutter closed as it looks not like key, but rather a shutter mode code :-)
Preset bitrate also works not as initially expected.
Early testing patches :-).
 
Last edited:
PTool 3.40d Updated

Updates:
Added "Preset Bitrate" and "Preset Bitrate 2" patches for AVCHD.

any hints about these, i got freeze while shooting the "star" chart less than 3 seconds no matter increase or decrease the value to 480 and 200. Compare to default setting having over 20s with my class 10 card.
 
any hints about these, i got freeze while shooting the "star" chart less than 3 seconds no matter increase or decrease the value to 480 and 200. Compare to default setting having over 20s with my class 10 card.

Sorry, such report is unusable.
Decrease to 200 is not a decrease, as default is 168.
Plus all other bitrate settings must be adjusted, else you'll get freeze.
Always start by decreasing value significantly.
 
Gotta love that new PTools interface. Testers get pirate icons in their section and some of the experimental patches look interesting in sensor section. Nice job Vitaliy, playing with the patches now.
 
Last edited:
It is imprtant to return to service mode now.
As we need to know how key press processing works.
And big three char menus inside service mode have KEY item.
 
As for 1080p24 on GF1, is it impossible thing. Sensor can't do it.
I have GF1 and few specific patches will be coming with time.

Sorry, to ask again but your sentence was unclear. Did you mean "it is an impossible thing"? So the sensor in the GF1 won't record true 1920x1080 no matter what firmware settings you use?

If that is true then I will just have to buy the GH1. Thanks for the information. You are doing a great job.
 
So, I am back to graphics things.

Here is another small tool that allow you to render any string exactly as camera make it.

1278652048.jpg


Same thing in Japanese

1278652481.jpg
 
Last edited:
I'd help out with some coding but i am swamped with work to do. I keep refreshing this thread every day though :)

Any chance to share WinGraph sources?
As we have some C++ developers and progress can be faster.
It really needs some facelift and AA suppor too.
 
No problem. I can put the source somewhere. I was able to get the AGG library to somewhat run with wingraph... but I ran into a problem where the paint event wipes out whatever I draw on the screen due to paint flickering. I haven't had more time to find a workaround for it.
 
No problem. I can put the source somewhere. I was able to get the AGG library to somewhat run with wingraph... but I ran into a problem where the paint event wipes out whatever I draw on the screen due to paint flickering. I haven't had more time to find a workaround for it.

OK, thanks, repost this problem detailed description to Wingraph thread.
I suggest you to paint in separate TBitmap (make it at runtime) and use
Canvas.Draw in Form OnPaint event handler to make actual draw from this bitmap. Seems pretty easy.
Some form of double buffering. :-)

Place link to archive (with AGC library, please) to WIngrath thread also.
I'll move to to gh1-hack.info.
 
Sorry, such report is unusable.
Decrease to 200 is not a decrease, as default is 168.
Plus all other bitrate settings must be adjusted, else you'll get freeze.
Always start by decreasing value significantly.

I changed my video bitrate to 23-25-27 to fit preset bitrate “234”, and H-30, L-24.

Native 25p
F23-H30-L24-25-27-p-234
Shooting the chart – FHD-write error, SH-ok, H&L-freeze with press record.
Normal shooting – FHD-ok, SH-ok, H&L-freeze with press record.

The setting above with interlace 50i
F23-H30-L24-25-27-i-234
Shooting the chart – FHD & SH – ok, H&L-freeze with press record.
Normal shooting – FHD-ok, SH-ok, H&L-freeze with press record.

F35-H40-L30-56-60-p-350
Shooting the chart - FHD-write error, H- freeze with press record, L-ok

F50-H44-L33-56-60-p-default
Shooting the chart – FHD-write error, SH & H & L –ok
Normal shooting – FHD & SH & H & L –ok

F50-H44-L33-56-60-p-500
Shooting the chart – FHD & SH - INSTANT write error

F50-H44-L33-56-60-p-80
Shooting the chart – FHD - write error over 20s, SH - ok

F50-H44-L33-56-60-i-default
Shooting the chart – FHD & SH & H & L –ok
Normal shooting – FHD & SH & H & L –ok

My 0.2 cents
Once clicked preset bitrate, it affect only the H and L mode.
The write error depends on the native or not.
 
Back
Top