GH1 firmware research volunteers required

Try to shoot longer clip (1/2 second clip for 1/2 shutter is a joke).
If you can shoot some timer (watches, etc) it'll be especilally good.
From this clip I see completely weird encoder behaviour making GOP=2, and encoder can not maintain normal P frame allocation (P frame low size-I frame-P frame with 2x I frame size-etc).
But I don't see fps changing, as timer settings for frames are normal and all frames are the same.
 
tester13 said:
It'll be tough.
Try to use present 720p50->720p25 patch (requires PAL patch, of course, also) to see if it produces suitable results. Bitrate drops accordingly to framerate, but individual frame quality is not worse.
Click to expand...

The thing is: I'd like to try NTSC->PAL, then 720p50->720p25 patch,
but does this exclude 720p60 from the menu?

What is involved in adding multiple frame rates to a 720p menu? Is a new user interface necessary?

Thanks so much for everyone's hard work.
 
DanDOF said:
The thing is: I'd like to try NTSC->PAL, then 720p50->720p25 patch,
but does this exclude 720p60 from the menu?

What is involved in adding multiple frame rates to a 720p menu? Is a new user interface necessary?
Click to expand...

Being able to specify parameters for the useless H and L settings in Req Quality would be useful here.

Unfortunately I can't test the custom firmware until I know it will work with my custom battery pack: :cry:



http://imageshack.us
 
Last edited:
why exactly do you need the TZ5? are you sure, that you can learn of it's firmware, or what is the plan?
 
DanDOF said:
The thing is: I'd like to try NTSC->PAL, then 720p50->720p25 patch,
but does this exclude 720p60 from the menu?

What is involved in adding multiple frame rates to a 720p menu? Is a new user interface necessary?
Click to expand...

Yes 720p60 won't be present.
May be at much later stages we'll be able to replace 720p60 H and L to different bitrates. But it requires massive changes.
 
1/2 shutter files are very weird.
Multiple doubling frames, strage GOP, strange P frames, sometimes almost skipping P frames, strange time codes for frames.
To be short - it is all one big encoder bug.
They must either fix codec parameters and behaviour or remove such shutter speeds.
 
DanDOF said:
Also, it seems this wiki can't be edited, since I can't join. IDK I've never worked on a wiki page before.

I wanted to add a section of links to uploaded files, categorized into which patch version was used.
Click to expand...

Click "create an account" at the top right. tester13 said, he wont participate. I guess it doesn't make lot of sense then, but it surely would be easier to report test and such on the wiki.

gh1.wikidot.com guys
 
While wiki's are useful, one thing they lack is any kind of interaction or personality. It's kind of fun and a rite of passage to discover this thread and read through all 111 pages of it.

Actually, I'm not even sure how much help a wiki can be. Take the Magic Lantern wiki as an example. I find it hard to find anything definite or detailed about what's going on. Whereas you can pop in here and ask a question and get an answer in twenty minutes.
 
Ya i'm actually fine with this thread too. So can someone explain what the Native 24p patch does exactly? Is it for 1080p24 only?
 
DanDOF said:
Ya i'm actually fine with this thread too. So can someone explain what the Native 24p patch does exactly? Is it for 1080p24 only?
Click to expand...


When you shoot FHD 1080p you wind up with a 24fps .mts file instead of a 60i file that then has to have the pulldown removed to get to an actual 24fps file. Plus side: one less step to do before you can edit footage. Down side: the camera can't play the clips.

I don't honestly know if it affects anything else besides 1080p24.
 
tester13, I think you might have mentioned it somewhere but were you looking for someone to do some C/C++/C# stuff? I might be able to lend a hand
 
dracore said:
tester13, I think you might have mentioned it somewhere but were you looking for someone to do some C/C++/C# stuff? I might be able to lend a hand
Click to expand...

Try to improve this tool
http://www.hex-rays.com/idapro/freefiles/wingraph32_src.zip

We need:
1. Ability to change maximum depth from root node (using input field in toolbar).
2. Realtime filtration (you type part of function name and it hides all functions that do not contain this part).
3. If you click on a node program must switch back to Ida Pro (without closing) and go to function name mentioned in this node.
4. Make it run faster and produce better looking graphs (may be use colors for different subrgaphs).

You can also use any of open source graph visualization packages to improve visuals.
 
Last edited:
You must log in or register to reply here.
Back
Top