Ptool Advisory

P

Park Edwards

Veteran
If you can't figure out how to load the ptool based off the information provided, it's probably best you didn't load the ptool.
 
While I laughed at this myself... you gotta' admit that each version of PTools changes something. Compound that with the people that are having problems (usually through user-error... admitted, not-admitted, or not realized)... and your bound to have some anxiety around the issue.

How many people were freaked out about "that clunking noise"?

While I agree that people who can't figure out how to load the PTool (based on the info given) probably shouldn't do it... the fact is that it's not rocket science... I'd rather say;

If you can't make a peanut butter'n'jelly sandwich unless the peanut butter'n'jelly are in the same jar... you maybe shouldn't load the ptool.

If you can't walk and chew gum at the same time... you maybe shouldn't load the ptool.

etc. etc.

The thing is that there is a LOT of experimenting with each incarnation of the PTool... and then you can read a lot of advice about settings and variables that many people who found this forum may never get into... or... they'll get into all that later. So then these guys find a thread that says you gotta' click this or do that... and if they get the latest 3.37D PTool... they won't even have to bother... or even think about it (initially, or maybe ever).

I think a protective CYA statement at the beginning of the instructions... something stating the obvious about the product, it's development, and the LACK of any contract plus use at your own risk... ...should then be followed by just a couple sentences clarifying "who" the following instructions are for...

Something like, "So you've been reading about the amazing GH13 and you're ready to change the firmware on your brand new GH1, if this is your and your cam's FIRST experience with the PTool firmware patch, follow these instructions exactly..."

Then... rather then have a step stating "apply patches"... maybe add something like "the most stable AVCHD patch for 1080p as of 7/08/10 is the C setting, so: patches for end users>AVCHD movie mode>AVCHD Compression then check the boxes for Video Bitrate FHD/SH, Overall Bitrate, and Limiting Bitrate... then click C at the bottom of the window... and if you want native 24p you can click that box, found under "wrapper"... finally click the big green button that says "save firmware" and be sure to name your new bin file one number higher... such as GH1__133... or GH1__134... etc."

There are a couple of very helpful threads... where each thread leaves out something that yes, SHOULD, be obvious... but you can't blame people for feeling a little anxiety about potentially bricking* their cam... even though it's actually butt-simple to do the firmware patch.

*The potentially "bricking" part... as I understand it... comes in with user-error... not using the fully charged battery during the firmware update... mis-naming the file, etc.
 
Wait till they see version 4!

Wait till they see version 4!

Car3o said:
If you can't figure out how to load the ptool based off the information provided, it's probably best you didn't load the ptool.
Click to expand...

It has a pirate symbol for goodness sake, outstanding, LOL:kali::badputer:
 
MattinSTL said:
While I laughed at this myself... you gotta' admit that each version of PTools changes something. Compound that with the people that are having problems (usually through user-error... admitted, not-admitted, or not realized)... and your bound to have some anxiety around the issue.

How many people were freaked out about "that clunking noise"?

While I agree that people who can't figure out how to load the PTool (based on the info given) probably shouldn't do it... the fact is that it's not rocket science... I'd rather say;

If you can't make a peanut butter'n'jelly sandwich unless the peanut butter'n'jelly are in the same jar... you maybe shouldn't load the ptool.

If you can't walk and chew gum at the same time... you maybe shouldn't load the ptool.

etc. etc.

The thing is that there is a LOT of experimenting with each incarnation of the PTool... and then you can read a lot of advice about settings and variables that many people who found this forum may never get into... or... they'll get into all that later. So then these guys find a thread that says you gotta' click this or do that... and if they get the latest 3.37D PTool... they won't even have to bother... or even think about it (initially, or maybe ever).

I think a protective CYA statement at the beginning of the instructions... something stating the obvious about the product, it's development, and the LACK of any contract plus use at your own risk... ...should then be followed by just a couple sentences clarifying "who" the following instructions are for...

Something like, "So you've been reading about the amazing GH13 and you're ready to change the firmware on your brand new GH1, if this is your and your cam's FIRST experience with the PTool firmware patch, follow these instructions exactly..."

Then... rather then have a step stating "apply patches"... maybe add something like "the most stable AVCHD patch for 1080p as of 7/08/10 is the C setting, so: patches for end users>AVCHD movie mode>AVCHD Compression then check the boxes for Video Bitrate FHD/SH, Overall Bitrate, and Limiting Bitrate... then click C at the bottom of the window... and if you want native 24p you can click that box, found under "wrapper"... finally click the big green button that says "save firmware" and be sure to name your new bin file one number higher... such as GH1__133... or GH1__134... etc."

There are a couple of very helpful threads... where each thread leaves out something that yes, SHOULD, be obvious... but you can't blame people for feeling a little anxiety about potentially bricking* their cam... even though it's actually butt-simple to do the firmware patch.

*The potentially "bricking" part... as I understand it... comes in with user-error... not using the fully charged battery during the firmware update... mis-naming the file, etc.
Click to expand...


+1

Well said Matt!

This phenomenon has grown to such exponential proportion, I've even had to step away from it for a bit. I was there from day one...like the third post in the "Research volunteers required" thread, (I was actually knocking tester13 b/c I thought he was being crabby towards another member...turned out it was a language barrier thing- I digressed and have since removed the post)- I have a huge amount of respect for Vitaliy Kiselev formerly known as Tester13 and trusty band of coherts...the early-on crew i.e. Nurbs, Chibs, Car3o to name a few. I was happy to be a part of something that felt....well...like something.

Anyhow the point being, I'm no programmer, can't write code, but consider myself to be technically inclined- so using the ptool for the first time was a little daunting- not knowing what was going to come out of the other side. There was a time when you could just follow the one thread and as long as you kept up on a daily,(and sometimes hourly), basis, you would be up to snuff on what was the latest and greatest--do's and don'ts of the hack. Now there's entire sections, stickies, threads upon threads of info- it's overwhelming for sure. So any first timer walking in here is definitely not going to know which way to look for absolutely ALL the information.
I have still yet to try the new 3.40 ptool, I think I'm still running 3.37 ptool with 'jobless' 'old D' settings which was changed at one point to 'C' settings .....who knows....it works great for me though. One of these days I'll get up to snuff again......so much info...so little time argh!!
 
Think it just prudent to feel compassion to those like us who are excited but still confused.It is natural that a lot will have anxieties since the whole ptool series came out. Patience is a virtue that will gain strength thru numbers, patience is a quality that will multiply for as long as those that knows more will extend their hands and not simply flaunt their arrogance to those that have faint of hearts but are willing to jump to the bandwagon and try their hand on the new Formula1 car around the tracks.Teach them how to drive the car and encourage them despite their grade 1 ways.Be magnanimous rather than exclusive, share with the masses rather than for a few.It will only take you 2 minutes of your time to answer one silly stupid repetitive questions. Lastly and most important, be kind and forgiving.
 
I want to stress that I really appreciate all the hard work and time that people are putting into this... and I know as well as anybody how tiring it can be to answer the exact same question over and over.

The opening statement is correct... that all the needed info is there to do the hack, but I think in some threads there are suggestions of choices, or "pick any number you want", or "no that setting didn't work for me so I changed it to this"... and all that can be intimidating to the first-time hack.

The thing to do (in my very humble opinion) is to not get a crap card... get a class 10 if possible (you can get an 8gb class 10 Panasonic gold card from J&R for only $30)... then follow the very clear tutorial that Car3o has done... and once you're in PTools... just click the basic stuff (at least for the first firmware run)... I ticked video bit rate, overall bit rate, and limiting bit rate, then I clicked "c" at the bottom window to load up the default C settings... finally I ticked 24pn and saved the file as GH1__133... and everything went smooth as silk (knock on wood)... as best I can tell it was just that simple.

I'm as new to the GH13 as anybody else here... so for better or worse, I'm still speaking as a newbie to the hack... and I'm sure I'll have more to report as I get out and use the cam.
 
easy to a point

easy to a point

It's easy to download the hack and make the changes and save the file, but that's where the instructions end. Then what? Drag the new 133 file WHERE on the Class 10 or 6 card--put it in WHICH folder? Then put it in the camera and do WHAT next? Need basic instructions beyond just making a new file.
 
Those parts are very simple chrisccw! Put it on any card in the root. Put card in cam. Press "playback" button on back of cam. Follow instructions.
 
I've said this in a few threads now... the "root" means NOT in any FOLDER... it's on the main part of the card! If you put the formatted card in your PC then open the card (in the PC) you'll see a window with 3 folders in it... the "root" is the "open space" of the window, NOT a folder... you drag and drop to THERE.
 
chrisccw said:
It's easy to download the hack and make the changes and save the file, but that's where the instructions end. Then what? Drag the new 133 file WHERE on the Class 10 or 6 card--put it in WHICH folder? Then put it in the camera and do WHAT next? Need basic instructions beyond just making a new file.
Click to expand...

from there you follow the update procedure on the panasonic website. The instructions are there, you just have to look for them.

I remember this being asked when this first started so the information is there.

Not everything can be packaged neatly with a bow on top for everyone. You have to remember that this is a TEST, it's not a product, it's not a service, it's a continuing test of HACKS that may or may not work. All of these instructions and sharing of data/information is purely a friendly exchange of courtesy. When people start complaining that stuff is not complete, well, that's when things are at the point of people feeling entitled to this stuff, and that's not good at all.
 
It goes straight into a folder when I drag it over and try to leave it in the open space below Private, goes straight into top folder, the DCIM one--Misc is in between. I've tried to follow your threads of instructions and avoid operator error, but things are not responding in exactly that way on my PC. Frustrating to no end!
 
Thanks so much to everyone for your patience. Very sorry to have sounded entitled, just needed help with that one root thing. It worked that time after numerous attempts to keep it OUT of the DCIM folder. It went there on it's own, and worked. Have a great Sunday and happy testing. Sorry to bother. But thank you.
 
chrisccw said:
It goes straight into a folder when I drag it over and try to leave it in the open space below Private, goes straight into top folder, the DCIM one--Misc is in between.
Click to expand...

:shocked: Sorry!
Before you drop the file - slowly and cautiously move your cursor away from the DCIM folder until it is not highlighted than take a deep breath and drop the file. If it still goes into a folder make the Explorer window (you can't be on a Mac) as large as possible and drop the file on the lower part of the window. Good luck!

1278863354.gif



EDIT: Oh I see you've figured it out. Congratulations!
 
blues said:
Think it just prudent to feel compassion to those like us who are excited but still confused.It is natural that a lot will have anxieties since the whole ptool series came out. Patience is a virtue that will gain strength thru numbers, patience is a quality that will multiply for as long as those that knows more will extend their hands and not simply flaunt their arrogance to those that have faint of hearts but are willing to jump to the bandwagon and try their hand on the new Formula1 car around the tracks.Teach them how to drive the car and encourage them despite their grade 1 ways.Be magnanimous rather than exclusive, share with the masses rather than for a few.It will only take you 2 minutes of your time to answer one silly stupid repetitive questions. Lastly and most important, be kind and forgiving.
Click to expand...

IMHO, lastly and most important, have a sense of humor, don't take everything so seriously, make an effort to "know what you don't know", read the documentation again & again until you "get it" or until you can ask a better-quality question, make an effort to appreciate how many times others here have previously answered questions -- even if they don't answer yours, say "hello" and "thank you" more often, and have a nice day. ;-)
 
loading tester's hacked FW into the camera is no different than loading panasonics. if you're having trouble updating your FW, stay away from the ptool.
 
You must log in or register to reply here.
Back
Top