The PTool Manual (WIP)

Thanks for the help Barry. I tried doing another upgrade but I encountered more issues...:

1) the camera doesn't recognize the bin file and doesn't prompt for upgrade when I press play. I increased the number when I save the bin file everytime, although I did try to re-save a bin file of the same number when the card wasn't recognized and I thought I didn't save the file properly

2) when I inserted another card with videos on it, the camera locks up as soon as I press the play button; only way to unfreeze it is to remove the battery, the on/off button doesn't work

3) I tried another card for this but file not recognized by the camera again
4) Without being able to view the video in-camera, I played it with VLC on the iMac, didn't really see a quality improvement, and there seems to be even more
 
oops, pressed the wrong button...

please ignore #4, it seems to be a problem with VLC, didn't see any problems with iMovie
 
You should start another thread for these. This thread is about building a manual and trying to understand the features in order to do so. ;)

Maybe if there's Mod with some free time he can do it for you... Or you can Modify->Delete and start one yourself. :)


.
 
Last edited:
OK, done.

That look about right?


And thank you!
I actually saw that quote a few days ago but spaced off adding it in. I'm in the middle of modifying three EOS AF lenses to bring the aperture control external. It's slightly brain racking as they're for a paying customer - so I have to make it dust-proof / waterproof, and something I feel will last at least one lifetime of abuse. :)
 
Last edited:
Tesselator said:
OK, done.

That look about right?
Click to expand...
Looks good. Also, when you have time please update native patch information with the following.
http://www.dvxuser.com/V6/showpost.php?p=2029598&postcount=58

I'm in the middle of modifying three EOS AF lenses to bring the aperture control external. It's slightly brain racking as they're for a paying customer - so I have to make it dust-proof / waterproof, and something I feel will last at least one lifetime of abuse. :)
Click to expand...
Sounds great, any chance of an all electronic Panasonic-Canon interface thingy? ;)
 
svecher said:
Looks good. Also, when you have time please update native patch information with the following.
http://www.dvxuser.com/V6/showpost.php?p=2029598&postcount=58
Click to expand...

Aren't these troubles only related card age,speed,feature though? It seems to me that it is. So I currently dunno weather to put "use a good card" or something else. I tested the C and D settings with A-Data class 10 cheepys (but brand new!) and didn't have any troubles shooting the star-chart thingy. It's also not just wrapper removal slash convenience. My first recordings without any hack produced actual interlaced footage. I could see the A and B field interlace lines on almost any movement - even when played back in the camera. With the Native 24p option checked the frames are indeed progressive. So, in all, I'm unsure what I should add.


Sounds great, any chance of an all electronic Panasonic-Canon interface thingy? ;)
Click to expand...

Is there a chip for that yet? Gawd, if there is I'm wasting my time and messing up these people's lenses. :zombie_smiley: I saw one that allows focus confirmation or something but I've not seen one that allows driving the aperture, nor focus motors. Do you have other information?

Edit: I guess I could do it if I had a panasonic lens to cannibalize and then just fit into the EOS lens. :)
 
Last edited:
Tesselator said:
Aren't these troubles only related card age,speed,feature though? It seems to me that it is. So I currently dunno weather to put "use a good card" or something else. I tested the C and D settings with A-Data class 10 cheepys (but brand new!) and didn't have any troubles shooting the star-chart thingy. It's also not just wrapper removal slash convenience. My first recordings without any hack produced actual interlaced footage. I could see the A and B field interlace lines on almost any movement - even when played back in the camera. With the Native 24p option checked the frames are indeed progressive. So, in all, I'm unsure what I should add.
Click to expand...
Well, card in use is one of the variables, however it is not a causative one. The causative issue is application of native 24p/25p patch. For example, as I reported here (http://www.dvxuser.com/V6/showpost.php?p=2023389&postcount=6) one can shoot exact same scene with exact same settings and have no issues. Change only one thing (apply native patch) and you get either card speed errors or complete camera lockup.

With that said, having this patch listed as "stable" is not accurate IMHO. I don't know how else to explain this better, perhaps someone can distill the contents of that thread again or write it better. In the end, the user has to decide.
 
In the spirit of discussion and discovery: Then we really can't call any of the patches that allow variables "stable". I mean someone could enter twenty billion as a bitrate for example and the camera would not work. So far I feel likewise about the Native 24p/25p switch. It's only under mistaken circumstances that it doesn't work. To me, for something like a camera firmware patching utility, this falls under the category of pilot error.

I do agree that we need to document the conditions under witch failure is probable tho.
 
Last edited:
Tesselator said:
In the spirit of discussion and discovery: Then we really can't call any of the patches that allow variables "stable". I mean someone could enter twenty billion as a bitrate for example and the camera would not work. So far I feel likewise about the Native 24p/25p switch. It's only under mistaken circumstances that it doesn't work. To me, for something like a camera firmware patching utility, this falls under the category of pilot error.

I do agree that we need to document the conditions under witch failure is probable tho.
Click to expand...
Well, for patches that have variables (AVCHD bitrate adjustment ones) we have notes that imply stability for only "standard" settings, as in "C" settings, which have been shown to be stable through testing. There are no variables for native patch, however. With a non-stellar performing card you will get card speed errors with only native patch enabled. The patch itself is a variable :)
 
svecher said:
Well, for patches that have variables (AVCHD bitrate adjustment ones) we have notes that imply stability for only "standard" settings, as in "C" settings, which have been shown to be stable through testing. There are no variables for native patch, however. With a non-stellar performing card you will get card speed errors with only native patch enabled. The patch itself is a variable :)
Click to expand...

Hi- As i brought up in another post, I've found at least 3 different bitrate combinations all called "C" settings. It adds a bit to the confusion.
 
mitchell1074 said:
Hi- As i brought up in another post, I've found at least 3 different bitrate combinations all called "C" settings. It adds a bit to the confusion.
Click to expand...
Yes, indeed. I always refer to PTool's "C" Settings. If referring to other ones, I usually specify Jobless's "C" Settings, etc.
 
svecher said:
Yes, indeed. I always refer to PTool's "C" Settings. If referring to other ones, I usually specify Jobless's "C" Settings, etc.
Click to expand...

so it looks like v 1.37d PTool's "C" settings (well, as of 8:00am PST 6-30-2010) are 50/52/60
I assume 40/46/50 were Jobless' "C" settings?

Sorry to jump right into another issue, but:

Here's a contender for stoopid question of the day award, do you always have to load an untouched Panasonic firmware version (in this case 1.32) into Ptools?

I just tried loading the "GH1__1.32.bin" file which I patched and saved (as "GH1__1.32.bin", I just overwrote the original panasonic file) into Ptools 3.36 and it gave me the error message:

"Wrong file or already patched"
 
Last edited:
Tesselator, now that patches have been split off into "End User" and "Tester" sections I think we should mirror the same format in the manual.
 
Yes. Agreed.

I'll get on it in the next day or two. Sorry I'm being kinda slow with the updates lately.

I sorta wanna wait till V has finalized a theme - it keeps changing so fast. :)
 
Last edited:
Yes, sorry about that. I've been unusually swamped lately with lens modification and repair requests. Good for me but the thread suffered a little. I'll be back on it in about a week - it looks like.
 
You must log in or register to reply here.
Back
Top