GH1 firmware research volunteers required

NURBS said:
Next test:
VA Bitrate adjustment 3: 3753 --change to--> 7506 (Can't write more 5sec.) - Frame rate : 23.947 fps wow :evil:

VA Bitrate adjustment 3: 3753 --change to--> 5000 (Can't write more 9sec.) - Frame rate : 25.191 fps wow :cheesy:

VA Bitrate adjustment 3: 3753 --change to--> 4000 - 3800 (Can't write more 28sec.) - Frame rate : 25.000 fps

VA Bitrate adjustment 3: 3753 --change to--> 2000 (Can't write flie)
Click to expand...

Can it write 720p with this settings?
It will be good to upload this short clips somethere.
 
Last edited:
Tester13 we are all behind you because

Tester13 we are all behind you because

when the 1080p is good its very very good, awesome in fact. If we had stable reliable footage it would truly rock.

Thanks T'side
 
Tameside said:
when the 1080p is good its very very good, awesome in fact. If we had stable reliable footage it would truly rock.
Click to expand...

You can see resolution charts shooting in this thread to understand sensor potential. Look at static 1920x1080 and loo at short video clip.
Of course, most degradatition is due to binning used.
 
NURBS said:
Testing new ptool ver.

Change only this mode.

VA 1920 frame height: 1080 -- change to --> 820 (result. camera can't record video and show text message: NO ADDITIONAL SELECTIONS CAN BE MADE).

VA 1920 frame height: 1080 -- change to --> 1180 (result. camera can't record video and show text message: NO ADDITIONAL SELECTIONS CAN BE MADE).

Testing more.
Click to expand...


tester13 said:
Try to use 816, not 820.
Anyway it looks we'll need to adjust this.
Click to expand...

If it becomes possible to shoot (and monitor on the LCD?) 4:3 @ 1920x1440 and 1.2:1 @ 1920x1600 my head will explode.. that'd be so perfect for scope shooting!
 
Ptool Updated (without version change)
Modified 1920 frame height patch (try to use 816 or 8 multiples), as both used numbers was wrong.
Also Bitrate Adjustment 3 completely changed, as we need to test how encoder perform under lowered bitrate, so set it to about 10.000.000 or even 6.000.000. I need such movies uploaded to analyze them at low level.
 
tester13 said:
Ptool Updated (without version change)
Modified 1920 frame height patch (try to use 816 or 8 multiples), as both used numbers was wrong.
Also Bitrate Adjustment 3 completely changed, as we need to test how encoder perform under lowered bitrate, so set it to about 10.000.000 or even 6.000.000. I need such movies uploaded to analyze them at low level.
Click to expand...

This is getting a little confusing. Should we test Bitrate Adjustment 3 while also changing the values of Bitrate Adjustment 1 and 2 or leave them at default? And what about "VA Bitrate Top Limit", etc.?
 
billy fattey said:
This is getting a little confusing. Should we test Bitrate Adjustment 3 while also changing the values of Bitrate Adjustment 1 and 2 or leave them at default? And what about "VA Bitrate Top Limit", etc.?
Click to expand...

Only this setting (VA Bitarete Adjustment 3) must be changed, and by lowering it, not upping. As described.
Do not touch anything else.
 
VA BITRATE ADJUSTMENT 3: 6000000
http://dl.dropbox.com/u/216574/00001.MTS

VA BITRATE ADJUSTMENT 3: 10000000
http://dl.dropbox.com/u/216574/00002.MTS

VA BITRATE ADJUSTMENT 3: 16000000 (default)
http://dl.dropbox.com/u/216574/00003.MTS

VA BITRATE ADJUSTMENT 3: 3000000
http://dl.dropbox.com/u/216574/00004.MTS

That last one is interesting in that it reduced the file size to 4.6MB where the other clips hover around 9MB. All clips are a 10 second static shot at same exposure. NTSC FHD 1080p.

VA BITRATE ADJUSTMENT 3: 1000000
http://dl.dropbox.com/u/216574/00005.MTS
 
Last edited:
Thanks, very useful, very.
16000000 file seems to be wrong.

If you can, try to do same things using 720 mode in maximum quality.
Also more graduated change between 6000000 and 1000000 is useful.
 
tester13: "It is hard to do anything with this hardware and such restrictions.
Best thing is to introduce 1080 film mode that removes all AVCHD restrictions and uses maximum possible bitrate." -- does this mean the only way forward for a good mod is to concentrate on the MJPEG mode? Or can AVCHD be sufficiently modded on here to be worthwhile in 1080p mode.
 
It means that you must clearly say customers that clips recoded in film mode won't play in some AVCHD players.
It is better try to adjust AVCHD.
720p30 MJPEG is already near its limit.
 
It's interesting to point out that a number of the "pro" digital cinema cameras record to JPEG. Cameras like the Vipre do JPEG(2k) at 23.98 as their primary capture with little other choices.
 
Svart said:
It's interesting to point out that a number of the "pro" digital cinema cameras record to JPEG. Cameras like the Vipre do JPEG(2k) at 23.98 as their primary capture with little other choices.
Click to expand...

Yes, propertly scaled down 1920x1080 24 JPEGS / second with low compression is very good. Unfortunately sensor can't full readout and scaling, hardware can't do such encode and write it to SD cards at such speeds (120-150Mbits).
 
Yes you are probably right. The Viper also cannot do anything higher than 30fps at 1080p. You can get 60fps at 720 though.

Obviously a limitation of processing speed as well.

I would personally be interested if the MJPEG on the GH1 could be changed to 1080 for research purposes and see what the maximum datarate it could handle is.
 
NEW Firmware ver.1.3 for DMC-GH1 !!!

NEW Firmware ver.1.3 for DMC-GH1 !!!


Firmware ver.1.3 for DMC-GH1
* Operation menu for image stabilizer will be added to the menu options when the LUMIX G VARIO 14-42 mm / F3.5-5.6 ASPH. / MEGA O.I.S. (H-FS014042) is attached.
* Availability of AF performance in FHD (full HD) movie recording mode with Four Thirds lenses that are compatible with contrast AF
* Improved AF performance in movie recording with LEICA DG MACRO-ELMARIT 45mm / F2.8 ASPH. / MEGA O.I.S. (H-ES045)
* Improved modulation accuracy of flash
* Improved AF (auto focus) performance with lenses of other manufacturer

According to engadget, the firmware will be released on May 10th, 2010.

I am not sure how this will affect the FANTASIC efforts of tester13 - will the hacks here still work???

http://www.engadget.com/2010/04/21/panasonics-dmc-gf1-gh1-g1-firmware-updates-improve-autofocu/


 
I think it will have no effect on tester13's patch. The patch will still work, but if it somehow does have ill effect on tester13's work, I have no intention to install ver1.3 firmware.

It would be interesting if Panasonic decides to be a good sport about all the works tester13 is putting in and decides to add descriptive comments to Gh1 firmware codes with this update. It could save a lot of time. Perhaps just wishful thinking.
 
Last edited:
Howto or Tutorial

Howto or Tutorial

Hello guys, I couldn't follow the development of this thread the past three weeks. Is there any how-to for reverse engineering the firmware. I thought of things like dumping and flashing the firmware and general information.
If not, I would like to encourage you guys to put up a wiki for this issue or at least some kind of tutorial to get more people on the boat. I would also offer putting up a wiki for this project, if there is any need. Maybe we should gather information about the firmware.
 
Last edited:
sirk said:
Hello guys, I couldn't follow the development of this thread the past three weeks. Is there any how-to for reverse engineering the firmware. I thought of things like dumping and flashing the firmware and general information.
If not, I would like to encourage you guys to put up a wiki for this issue or at least some kind of tutorial to get more people on the boat. I would also offer putting up a wiki for this project, if there is any need. Maybe we should gather information about the firmware.
Click to expand...

+1

Would be great if you put up a wicki which sums up everything. I just ordered a gh1 after following this thread for a while and would like to take part in the testing. A wicki would be very useful for all testers I guess.
 
You must log in or register to reply here.
Back
Top