GH1 firmware research volunteers required

regarding AGC ( I imagine Auto Gain Control) it would be fantastic if we could turn this on/off because AGC is a brickwall limiter and pumps as hell...
 
Hi Vitaliy:

Just an FYI: The online magazine, Pro Video Coalition, today published my comments as an "inline" update to Allan Tepper's recent article on your PTool3 software. My comments were an attempt to diplomatically correct & expand upon Allan's original article:
http://provideocoalition.com/index....ibility_power_and_quality_into_the_lumix_gh1/

Concerning your quest to contact useful individuals at Panasonic, it's possible some of the regular contributors to PVC might be helpful. For example, one of the PVC's founders, Adam Wilt of Meets The Eye, is an engineer and seems to be a good guy. Adam appears to have good connections at Panasonic, although most of them may be with Panasonic's pro/broadcast products division. Gary Adcock of Studio 37 is another very knowledgeable contributor with many industry connections. The principal PVC writers are listed here:
http://provideocoalition.com/index.php/aboutus

See also:
http://www.meetstheeye.com
http://www.studio37.com

Anyway, I hope my addition to Allan's article and the above info is helpful, and thanks again for PTool!

- Peter
 
Hi Vitaliy:

Just an FYI: The online magazine, Pro Video Coalition, today published my comments as an "inline" update to Allan Tepper's recent article on your PTool3 software. My comments were an attempt to diplomatically correct & expand upon Allan's original article:
http://provideocoalition.com/index....ibility_power_and_quality_into_the_lumix_gh1/

Thanks. I'll try to use as much help as possible.
So, any people having some relations with Panasonic could be useful at this stage.
 
Small update on bracketing thing.

As I said initially this will be tought.
Bracketing menu have two selections - bracketing mode (from 3 1/3ev to 7 2/3ev) and
image sequence.
Main problem is that firmware use multiple memory areas copies (in separate tasks) and thus can reference same value using from 3(this is minimum) up to 9 different methods.
While I can change frames count (for example, from 7 to 3) at picture taking setup level, all else is not possible today.
EV steps and modes are hardcoded at some low shooting routines.
Any changes in such code are almost impossible to implement without introducing many bugs, this is btw main reason why we see so many cameras with similar functions.

Same thing in AVCHD encoder routines. You have menu selection code->video mode code->bitrate setting->transferred to encoder->comparisons->predefined settings inside video encoder. So, any settings adjustment at bitrate level won't directly affect encoder performance (is many cases). I really don't know how it is possible to write such code.
 
Last edited:
PTool 3.40d updated

Limiting bitrate patch and remove encoder limits patches removed.
All necessary things integrated in video bitrate patch.

"Manual movie modes" patch for GF1 improved.
Now movie mode changes have effect only in movie dial position.
Same as in GH1, but we still end up at P setting after power off or initial dial setting to movie position.
This is first patch made using gcc based IDE (as it small routine).
 
Last edited:
PTool 3.40d updated

"Manual movie modes" patch for GF1 improved.
Now movie mode changes have effect only in movie dial position.
Same as in GH1, but we still end up at P setting after power off or initial dial setting to movie position.

I've tested the new manual movie mode but rather like the previous one better.

In previous version (not sure which one as it also says 3.40d), I can enter correspondent manual movie mode from any dial mode (P,A,S,M) if I choose "M" mode in "Manual Exposure Mode" menu. Just dial into any mode and hit menu twice.

I also love the fact that I can see what f-stop/shutter speed camera choose when in S/A/P mode. This also happens only when I choose 'M' mode in menu.

In the new version I need to set it in menu every time when I want to change mode from M to P/A/S which require more button pushes and it always reset to P when dial is turned or power on.

Many Thanks!
 
Last edited:
I've tested the new manual movie mode but rather like the previous one better.

In previous version (not sure which one as it also says 3.40d), I can enter correspondent manual movie mode from any dial mode (P,A,S,M) if I choose "M" mode in "Manual Exposure Mode" menu. Just dial into any mode and hit menu twice.

I also love the fact that I can see what f-stop/shutter speed camera choose when in S/A/P mode. This also happens only when I choose 'M' mode in menu.

In the new version I need to set it in menu every time when I want to change mode from M to P/A/S which require more button pushes and it always reset to P when dial is turned or power on.

Many Thanks!

I tried out the new bracketing menu option. It is kind of cool. If gives you the choice of whether you want to take the next bracket picture or not. If you are satisfied with the previous one you can just cancel the rest of the sequence. Now if you can get it to do in camera HDR I will be a believer.

I have to agree about reverting back to the old way of doing manual movie settings. I liked it better the old way. It gave us the option to choose when we wanted to use manual movie mode. I liked saving the custom “C2-3” and “C2-2” settings with manual movie mode with different options.

Could you change the manual movie options back in the next release?

+1 on some sort of incremental numbering even for maintenance releases.

Just curious as to why the 1080p AVC-HD is “just for fun” right now? That is the one option that everyone with a GF1 would love to have. From my testing it looks like it actually does work. It records 1080i at 29.97 FPS or 25 FPS. The static on the top seems to be related to shutter speed but I am sure we could figure out what is going on with some testing.

Did you say that we shouldn’t test it because you don’t think it will ever work or because you think the other options are more important?
 
PTool 3.40d updated

Limiting bitrate patch and remove encoder limits patches removed.
All necessary things integrated in video bitrate patch.

Okay, I have time to do some test-series this evening as promised - I guess I should be testing the "Overall bitrate 2" setting as Vitaliy asked.

My normally used AVCHD settings are:
Video Bitrate FHD/SH: 50.000.000 (H: 32.000.000 L: 22.000.000)
Overall Bitrate: 52.000.000

My question is:
What settings-series should I test for "Overall Bitrate 2"?
(the default setting in ptool is 9.000.000)
Should I go for 5.000.000 to 15.000.000 in steps of 1.000.000 or should I rather test something around 52.000.000 (as its the value of the old "Overall bitrate")?

Hope I am not acting completely dumb here, but the relation of "Overal Bitrate 2" and "Overall bitrate" is still unclear to me.
 
As for old Manual Modes behaviour.
I'll try to add it to testers section in one of the next releases.
Problem with old approach is that it affects many things and is not suitable for normal people unaware of all consequences.

Overall bitrate and Overall bitrate 2 are used together in reality, one is two times larger then other.
Without detailed and systematic testing we won't know how they work exactly.
 
Did some testing of "overall bitrate" and "overall bitrate 2" today. It was my
first try at systematic test runs... so I have a bit to learn and much to
improve.

I did shoot gras as that is famous for producing AVCHD bitrate-peaks. The
problem with this is that even on a tripod the filesize sometimes seemed to have
quite a lot to do with how much the wind blew and thus how much the gras moved
:-)
So I will want to do another testrun tomorrow with a more static motiv -
suggestions for suitable motives very welcome!

The two conclusions that I would dare to make right now are:
- using "overall bitrate 2" with a value of "overall bitrate"/2 improves the
files bitrate (sometimes quite dramatically)
- having a "video bitrate" very close to the "overall bitrate" is inferior to
having a "video bitrate" well below "overall bitrate" (most of shots with "H"
are way bigger than with "SH" in my tests)

...hope this helps a bit... suggestions for further tests welcome! (I would play around with values for overlalbitrate2 in configuration G next if nothing else is suggested.)


Here are the test-results:

all tests shot with:
- GF1 (AVCHD 720p)
- 1/100s shutter, f4, ISO 100, on 50mm/1.4 Nikkor manual lens via manual movie mode
- all exactly 60 seconds in duration
- besides AVCHD-bitrate-patches only manual movie mode, 3rd party battery and
language patch checked to rule out any other interferences

(bitrate-patch values in million)

Code:
Configuration A)
plain vanilla GF1 AVCHD  - no AVCHD codec bitrate patches:
     filesize    filename
SH 65654784    00035.MTS
H  60948480    00036.MTS
L  56616960    00037.MTS

Configuration B)
Video Bitrate SH:34 H:28 L:22
Overall Bitrate:    36
Overall Bitrate 2:  - (not checked)
     filesize    filename
SH 60936192    00038.MTS
H  63043584    00039.MTS
L  68167680    00040.MTS

Configuration C)
Video Bitrate SH:34 H:28 L:22
Overall Bitrate:    36
Overall Bitrate 2:  18
     filesize    filename
SH 66840576    00042.MTS
H  57108480    00043.MTS
L  66226176    00044.MTS

Configuration D)
Video Bitrate SH:36 H:32 L:22
Overall Bitrate:    36
Overall Bitrate 2:  - (not checked)
     filesize    filename
SH 72222720    00045.MTS
H  66471936    00046.MTS
L  64862208    00047.MTS

Configuration E)
Video Bitrate SH:36 H:32 L:22
Overall Bitrate:    36
Overall Bitrate 2:  18
     filesize    filename
SH 78348288    00048.MTS
H 131260416    00049.MTS
L  81887232    00050.MTS

Configuration F)
Video Bitrate SH:50 H:32 L:22
Overall Bitrate:    56
Overall Bitrate 2:  - (not checked)
     filesize    filename
SH 64991232    00051.MTS
H 100675584    00052.MTS
L  83558400    00053.MTS

Configuration G)
Video Bitrate SH:50 H:32 L:22
Overall Bitrate:    56
Overall Bitrate 2:  28
     filesize    filename
SH 118886400    00054.MTS
H  153169920    00055.MTS
L  128643072    00056.MTS

 
So, overall bitrate is time related thing (as 90000 is one second time).
May be it defines window length for bitrate measurement and adjustment?
How it behaves with original values - 18.000.000 and 9.000.000 and high bitrate ?
I see many values changingt through testings while we need to change only one value.
It is interesting to see original overall bitrate (not checked at all) and increasing video bitrate step by step.
Next same thing with OB and OB2 set to 56m and 28m.


Guys, please repost your reports to AVCHD research thread - it is much better suited for this. OK?
 
Very interesting results. StreamParser suggests an Overall Bitrate setting. Actually, this is a suggested minimum because among other things it causes a buffer to be allocated. I have found that if I don't set Overall Bitrate to at least this value I get buffer overrun errors in FHD mode when 24pN is checked(the check file feature will detect these). Obviously, though, Overall Bitrate does more than just allocate buffers.

Chris
 
Just like to report that with the FHD option checked, my GF1 is unable to get AF lock when shooting video in FHD with my ME45 lens. It will simply rack back and forth.

UPDATE 2/8/10: Tested FHD mode with the 20/1.7 and encountered the same issue. Camera will AF before starting a recording, but once shooting a FHD video, AF will fail to lock on.

Camera firmware 1.22 with 3.40d hack, lens firmwares all up to date. Test carried out in AF-S and single point AF.
 
Last edited:
I cleaned thread a bit removing discussion about oscillators as it have no reality ground(participants are free to make thread outside development).
 
Our first target must be IDE development.
Notepad++ while being good editor is not suitable for our task.
Cygwin must be also shaved as much as possible.
If anyone could port compilers for C and assembler under MinGW it'll be very good.
 
I cleaned thread a bit removing discussion about oscillators as it have no reality ground(participants are free to make thread outside development).

Fair enough, but my original question was if anyone has more info on the main IC such as pinouts, or a diagram of the main PCB? If so please PM me, thanks.
 
Thank you for your great works.

I found a problem after hacked the firmware by using 3.40d: after hacked the firmware, language option not work for original Japanese GH1 model, as no language menu appeared in menu setting and the langauage can only be shown in Japanese.

Thank you
 
Back
Top