GH1 firmware research volunteers required

JerryB said:
Although it may have been said somewhere in the 193 pages of this forum, could you please clarify...
Why do think 720/24p Mjpeg will probably not be possible?
Click to expand...

We have encoder setting (here we can do that we want).
And we have sensor settings. This is much tougher.
Sensor seem to have constant read speed without interruptions.
Each setting have many parameters. And without sensor documentation it is almost impossible to change something to get useful picture.
And preset settings allow only resolutions that we already have.
May be scaling down from 1920 to 1280 can be made.
This is why it is interesting to know how 848 is implemented.
 
Will be testing soon.

Will be testing soon.

Howdy all. I have been quietly following this thread for quite awhile now and am very interested in what I've seen. I definately plan to join the tester ranks in addition to donating, in the near future. The dilemma I'm faced with before I do so is whether or not I might exchange my newly purchased GH1 for another one within the next week or so.

I have the GH1 video banding issue staring me at the face and with all the talks on other threads/forums of people with a higher degree of issue with this then others... and on the flip side people whos GH1s supposedly suffer very little from this... I'm trying to decide which of these catagories mine falls into and if there might be merit to attempting to exchange it for a new one. Thus, I obviously don't want to mess with firmware changes until I'm sure I will not be returning the camera or otherwise I get the replacement.

In relation to the breakdown of the cameras functions discussed in this thread, I notice that video noise and banding is largely supressed by some sort of post camera filtering that doesn't initiate until after the record button is pressed. I wonder how much this process might task the cameras processors and whether or not that had any bearing on there being no HDMI preview on the device. Whether it be a lack of processing resources or just fear of tasking and overheating the system.
 
banding has been discussed in at least a dozen threads. it's a hit a miss really. i've dealt with two different gh1'1, one american version and another japanese and neither had banding unless i was pushing the iso or shooting in dim light scenes. others have said it went away after it "burned" in, but I personally think that's a bunch of farce. in regards to your camera, it's kind of up to you, no clear answer.
 
Banding is really nature of Panasonic LiveMOS chips (CMOS also have similar thing).
In photo they use smart algorithms with dark frame (viewefinder goes dark for this reason?) or something similar.
My Panasonic camcorder have same banding.
Other camcorder is 3CCD and do not have such issues.
In fantazy land they could allow user to make camera profile using gray cards and running through various resolutions and sensor temperatures. Such thing and simple processing can reduce banding very much.
 
That pretty much what I figured.. it's really a hard thing to substantiate.. and I've been through ALL the the threads. It's not so much that I'm horrified with the camera performance or anything.. it's just the nagging possibility that an exchange might produce a better working model for me.

Should anyone have time to spare... at max (+3) exposure comp, shutter priority (1/30) and 1600 ISO the banding is clearly visible while recording with the lens cap on. If anyone cares to tell me if they get the same, less, or more visible/recorded banding at that setting, here's a quick clip of what I get.....

http://www.jerseyforged.com/sampleclips/banding_1600iso_maxexpcomp.zip

Also, on still mode "s" at the same settings the banding is extreme (again with lens cap on) and red colored until the record button is hit (the previously mentioned filtering). Those are obviously crap settings, but it's the best way I can think of to easily compare my banding levels to someone elses.

In any case, I have another week to return the camera and if I don't I'll begin running any needed tests next week.
 
dracore said:
Double click on a node. Most likely it won't switch to IDA. Post me the contents of the wingraph32.log file that it creates
Click to expand...

Switch working now (but going to function not workingm I believe it must be ok at this testing stage).
If you can identify window by calling process (process that calls WinGraph) it'll be better, as I have many IDA windows sometimes.
 
GrgurMG said:
That pretty much what I figured.. it's really a hard thing to substantiate.. and I've been through ALL the the threads. It's not so much that I'm horrified with the camera performance or anything.. it's just the nagging possibility that an exchange might produce a better working model for me.
Click to expand...

Please, make other thread for this.
 
Well, I figured since I plan to donate my time and money to this effort.. and we already have very thorough testers on this very active thread... I'd bring it up here. But I relent.
 
tester13 said:
Switch working now (but going to function not workingm I believe it must be ok at this testing stage).
If you can identify window by calling process (process that calls WinGraph) it'll be better, as I have many IDA windows sometimes.
Click to expand...

Can you post the wingraph32.log file? I want to see specifically why the going to function is stopping.
 
dracore said:
hmm.. that's it?

just curious... but is there a .log file? :)
Click to expand...

It is up to you to know.
I don't see any log file.
I really suggest you to see examples on the web, as task is quite typical (plus as far as I know you need separate DLL to send keystrockes to application).
 
Yes, I was just surprised that it stopped there. Didn't even get to send any keyboard events...

OK, I need a screenshot in wingraph32 of the node that you are double clicking on
 
dracore said:
Yes, I was just surprised that it stopped there. Didn't even get to send any keyboard events...

OK, I need a screenshot in wingraph32 of the node that you are double clicking on
Click to expand...

It happens on any node :)
I tried many-many various graphs.
You better contact me by PM or email, af this have no interest for others.
 
The more I work on this project the more I see GH1 potential.
Today we are like blind kittens.
In reality we need either debug firmware build or object files (they won't provide sources anyway). Speed will be much faster and results will be better.

We must build small team with sole purpose to reach necessary people in Panasonic Lunix division development department.
Under this I mean information digging, many calls via cheap international Skype, etc. to get necessary persons and talk to them.
I do not mean any useless petitions, etc
Contact me by email and PM if you want to become member of such team.
I specially invite people from Japan.
 
You must log in or register to reply here.
Back
Top