GH1 firmware research volunteers required

Happens in playing back from the camera on an HDTV, happens when playing back from a blu-ray player. Has nothing to do with file conversion or computer software playback, at least as far as that clip I posted is concerned.

You are certainly correct that computer playback issues are behind a lot of the complaints about h.264 viewing, but I don't think we can chalk this particular artifact up to that.
 
Tester13, with the new tool(version compare)

Tester13, with the new tool(version compare)

I can go back to earlier version cool:laugh: but what do I do for a new version? tick version compare only or version increment and version compare and do I add an increment number. Finally what do I say the new version as? can I now use the 132 bin numbering, again and again and again?

Many thanks, am stuck.
 
Important notice.

I am temporary stopping participating in GH1 Firmware hack sub-forum.
As we moved from quite systematic research and development (big thanks to dracore and few other people) to uncontrollable flame.
Miriads of settings, databases. Manuals writtent by people who never used my tool.
You can contact me by PM, if you have important question, help or suggestion.
I'll need to set up proper place and infrastructure before we'll move back to speed.
Sorry, it was my error.

P.S. We have good temporary solution now - separate development forum (edited later).
 
Last edited:
One more notice.

We might find temporary solution to current situation with admins.

Good news.

I now have G2 firmware from undisclosed source. All seems pretty promising.
 
Joejitsu, Ptool is an evolving project which could really be thought of as beta test software. If you are concerned about using it, I wouldn't.

Almost all devices that can be firmware-upgraded will only accept a higher version number before they load the firmware. The latest Ptool makes the GH1 no longer check the version number. So you no longer have to worry about incrementing it.

As I said in another thread, you could now have a couple of small capacity cards, one with the original firmware on it, and one with your favourite firmware configuration on it, and load whichever one you want at any time. The GH1 will happily swap between them and will not care about version numbers if, using Ptool in the first place, you have told it not to check.
 
Hello everybody. I've been following this thread for some days and the work of Vitaliy is really outstanding so it were these discussions that inspired me to buy the GH1 with Transcend 16GB 10Class card. I hope that I will manage to patch it successfully like everybody else but the thing I wish to say is that if it is necessary to make healthy working condition for Vitaliys project then maybe there could be a buffer zone made of closer friends or older forum participants to act like messengers between him and the public so that only useful information goes thru. In that way he would not have to spend his precious time following threads of all sorts but get only the filtered ones that contribute to the improving of the hack.
Maybe this is just happening and sorry if I missed something since this is my first post.
Regards
 
So... here is the basic laydown... I think Vitaliy and I have come to a solution that will hopefully serve the growing gh13 community, as well as the actual development effort of the firmware hack and any associated tools, etc. We not only have to accommodate the growing community, but we also all should have an interest in insuring that the increased foot traffic does not hinder development efforts...

The GH13 hack has become enormously popular very quickly. This is not without it's pains...

b/c it is getting so popular and has generated a lot of excitement, it's generated a lot of discussion... here and elsewhere... This is good, and encouraged by us. However, it is a bit conflicting with what was originally Vitaliy, his firmware hack, and a core group of folks who were rooted in the process of development, testing, etc..

As a result, threads intended for specific discussion get noisy, off topic, questions get repeated, etc...

Well, Vitaliy needs a place where he and his cohorts can work on development of his firmware, testing, etc, etc in a controlled, and noise-free environment.

Everyone else, needs a place for the more open and casual discussion, and a place that is accommodating to those less-experienced and/or less-involved in the actual development process of the project. Moving forward, that's where this current sub-forum comes in... The place for general info (which folks are working on organizing and compiling into more navigable structure) and questions and discussion, etc as it relates to the gh13 hack in any way...

All development and testing stuff... will move to a gh13 development sub-forum. it will be accessible by all to read (and to enlist if they are serious), but will be intended for use by those who are actually seriously involved in the development and testing of the gh13 hack. There will be strict posting guidelines in order to keep this development section on point and free of noise, so that the people who are actually working on the stuff can do so in a noise-free environment. Everyone else can read without interrupting. It's still a public process, but the actual posting in that section will be only directly relevant to ongoing development and testing.

all other discussion takes place in this current sub-forum which will be managed as the rest of dvxuser. the development area will be for development, and will be maintained to provide a noise-free atmosphere for those people actually involved in the development and testing process, etc.
 
The goal, more than anything, is to let Vitaliy focus on developing the software, rather than answering questions and fielding requests and moderating threads and doing all those other miscellaneous tasks.

With a core group of dedicated, committed testers, he should be able to get back to doing what he does best, shaking up the whole DSLR world!
 
So... here is the basic laydown... I think Vitaliy and I have come to a solution that will hopefully serve the growing gh13 community, as well as the actual development effort of the firmware hack and any associated tools, etc. We not only have to accommodate the growing community, but we also all should have an interest in insuring that the increased foot traffic does not hinder development efforts...


Awesome work to you Jason & Vitaliy for figuring out a game plan to making this development effort work and proceed......


Pappas
 
Thanks and a :thumbsup: to Vitaliy for doing great work that is as close to unique as any I've seen! It's rare that one person can impact so many and lift us out of our rut. He is testimony to the concept that anything is possible with creativity, drive, and hard work! Here's to 'ya... :beer:

And also big :thumbsup: to Jason for creating an environment where members can keep in touch with what's going on and simultaneously allowing key members to drive this project forward. Brilliant! :) :) :)

Regards,

Dan.

p.s., I'm a software developer. One of the most critical and least-appreciated things about being a software developer is the need to limit interruptions when they're working. While no one appreciates interruptions, for most people it's a matter of the wasted time and energy while responding to the interruption. That applies to software developers too. BUT there's one other problem...

When they are working through an thorny issue, they may spend hours, days, or even weeks wracking their brain to find a solution. And then, just as they've cracked that "nut" and defined an awesome solution... Just when that "Eureka!" moment comes... Someone interrupts them with a stupid question or just wants to chit-chat!!! :furious3:

So they courteously spend 5 minutes answering the question and then try to get back to true gem they just found designed. But it's gone! The train of thought has been derailed. And then they may spend hours or days getting back "on track". Or maybe it never comes back! It's gone!!! Arrrgh!!!! And you wonder why they get PO'd?!?

p.p.s. I know all of this because I've been there, done that. Many times! I once worked on a dev team with 22 developers where the project management team thought it was reasonable to have a 1/2 hour meeting every day and a 2 hour meeting ever week. Then they wondered why the project was going down the tubes and way behind schedule!
 
Vitaly, Thank you for your work on the GH1 firmware! Unfortunately the dvxuser community lacks your understanding of the GH1 firmware. Nor does it understand the hypotheses that you are evaluating as as you pore through the firmware. As a result, recent testing efforts have been not been helpful to you. With that in mind, I'd like to make a suggestion that may help your efforts.

When you post a new ptool, please also list all the patch combinations that you want to be tested in the scenarios you want them tested (eg., detailed scene with panning on tripd, detailed scene without panning, etc.,) . Assign each combination a unique identifier. Then we can try all those combinations for you in the scenarios you want them tested and post our results and our footage if necessary. It's a little more work for you up front, to list the exact combinations that you want tested, but it's more likely to give you the information you need to rapidly and conclusively confirm or refute your hypotheses.
 
Last edited:
Our goal today is to return to sensor m4 mode constants testing.
One by one with extensive documentation and grabs from footage or photos of LCD screen if grabs are not available.
 
Last edited:
I encountered a possible problem today with the 'Version compare' patch and I'll report it here - please delete/move/ignore as appropriate.

I've only started testing AVCHD settings today. My initial chief interest is to see whether widely recommended settings make a difference that's worthwhile to me personally. Selfish, but I will try to move on to general testing very soon.

I prepared two class 6 cards newly formatted in the GH1.

Card 'A' had firmware with only 'version compare' patch ticked. This was intended to enable me to revert to an unpatched state for comparison.

Card 'B' had 'version compare' patch ticked, together with

Native 24/25p
Video bitrate adjustment 38000000
Overall bitrate adjustment 40000000
Limiting bitrate adjustment 42000000

So first I inserted card 'A', did firmware upgrade, took test shots.

Then inserted card 'B', did firmware upgrade, took test shots.

Then inserted card 'A' again, tried to do firmware upgrade, but the GH1 froze needing the battery to be taken out.

The only way to get it to do the firmware upgrade (after I had stopped panicking) was to record five seconds of video on that card 'A' - using therefore the firmware still running on the camera, firmware which came from card 'B' - and that made it possible to do the card 'A' firmware upgrade, then continue testing onto that card.

The same thing happened when I then inserted card 'B' and tried the firmware upgrade. Camera froze, and would not do the upgrade until I had recorded something on it using the firmware sill installed on it which came from card 'A'.

Now I know what to do, it's not a big deal, but I wonder whether it points to a problem which could be fixed in Ptool in due course, enabling firmware swapping without freezes.

What might do the trick meanwhile would be to carry a couple of other cards, with only the firmware on them (one version on one card and the other version on the other card, which I would not use for recording tests but just for swapping firmware.

Results of actual tests to follow when I've played them back.
 
This is quite emotional report :-)

Lets make it step by step thing.
What you did on each step, camera state, freeze moment etc.
Check same thing having only incremented firmware.
 
Back
Top