PDA

View Full Version : The PTool Manual (WIP)



Tesselator
06-15-2010, 01:17 AM
This is the ongoing manual assembly project for the PTool version 3.40d (Wined Mac Version Here: PTool_Wined.app (http://tesselator.gpmod.com/PTool_Wined_app.zip)) for the GH1.

CAUTION CURRENTLY SOMEWHAT OUTMODED!

Any features you have information on please post them in this thread and I will add them. And remember to check back here often.

Thanks!

Part One

Feature Patch Name: Version Change
Function: Allows the GH1 to accept a firmware update by satisfying the camera's need for revision number iteration.
Usage:
Click the checkbox next to the feature,
Enter a value (negative numbers lower the version string, 0 maintains current, positive values increment),
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Related: Version Compare Patch
Tested: http://www.dvxuser.com/V6/showpost.php?p=2021799&postcount=21
Stable: Yes.
Notes:
No longer a requirement, this feature patch is only needed when overwriting firmware that the GH1 reports as being the same or higher version than the base firmware you customized.
First time customizers should probably use the "Version Compare Patch" instead - especially if you intend to try different settings at a later date.
See the notes for "Version Compare Patch".
Request For Information:



Feature Patch Name: Version Compare Patch
Function: Allows the GH1 to recognize any firmware version a viable "upgrade".
Usage:
Click the checkbox next to the feature,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Related: Version Change
Tested:
http://www.dvxuser.com/V6/showpost.php?p=2020402&postcount=2589
http://www.dvxuser.com/V6/showpost.php?p=2021799&postcount=21
Stable: Yes.
Notes:
For all intents and purposes this feature patch essentially set's the Camera's firmware to version 0.0 thereby allowing the GH1 to accept any firmware image file either Panasonic original or customized by PTool.
Request For Information:



Feature Patch Name: Third Party Battery
Function: Allows the GH1 to accept batteries manufactured by third party manufacturers regardless of authorization.
Usage:
Click the checkbox next to the feature,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: None.
Tested:
http://www.dvxuser.com/V6/showpost.php?p=1991715&postcount=1413
http://www.dvxuser.com/V6/showpost.php?p=1991891&postcount=1421
Stable: Yes
Notes:
Panasonic DMW-BLB13 lithium-ion batteries have three kinds of protection built into them: Protection from overcharging, protection from over current (voltage regulation), and protection from over or hyper discharge. See: http://panasonic.jp/support/global/cs/info/dsc_battery.html Panasonic has developed a way to identify authorized (or fully compliant?) batteries and the camera will refuse to operate if detection is not satisfied. This feature patch disables that identification routine thereby allowing the camera to operate with any battery of the proper form factor.
Some compliant 3rd party batteries do not need this patch in order to operate even though they are not officially authorized by Panasonic.
Request For Information:



Feature Patch Name: Interface Language
Function: Allows you to select the GH1's user interface language.
Usage:
Click the checkbox next to the feature,
Select the default language,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: None
Tested: http://www.dvxuser.com/V6/showpost.php?p=1987056&postcount=1211
Stable: Yes.
Notes:
This allows you to select between: English, Deutsch, French, Spanish, Italian, *Chinese Simp, *Chinese Trad, Russian, Polish, Czech, Hungarian, Dutch, Korean, Thai, Turkish, Portuguese, Classical Arabic, Modern Arabic, French2, Finnish, Danish, Swedish, Portuguese 2.
After applying this feature patch the GH1 will no longer allow multiple language selection if it did with the unmodified Panasonic firmware before. If the original language selection sets are desired simply uncheck this feature patch and reinstall.
* = Some characters seem to be missing.
Request For Information:
What are the differences between French and French2, Portuguese and Portuguese 2?
Need confirmation on Note 2.



Feature Patch Name: 30min. Limit Removal
Function: Allows recording of movie clips longer than 30min. in length - for PAL models of the GH1.
Usage:
Click the checkbox next to the feature,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: None
Tested:
http://www.dvxuser.com/V6/showpost.php?p=1973354&postcount=319
http://www.dvxuser.com/V6/showpost.php?p=1973427&postcount=355
Stable: Yes.
Notes:
In some regions of Europe devices capable of recording video footage longer than 30 minutes (take length) are subject to higher tax rates. In order to not penalize it's customers Panasonic opted to restrict the recording length of GH1 cameras destined for those regions. This affected PAL models of the GH1 camera. This feature patch removes that limitation.
Request For Information:



Feature Patch Name: Native 24p/25p
Function: Removes 60i/50i wrapper from FHD mode and enables writing native (from sensor) 24fps/25fps progressive stream to the MTS video file.
Usage:
Click the checkbox next to the feature name,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below)
Dependencies: None.
Tested: http://www.dvxuser.com/V6/showpost.php?p=2015009&postcount=2402
Stable: Yes, but using this feature patch results in the GH1 creating a non standard-compliant video file for those modes affected - See: Post #15 (http://www.dvxuser.com/V6/showpost.php?p=2019668&postcount=15) in this thread.
Notes:
Affects 1080p wrappered video only.
Normally the GH1's 24p (progressive) video recordings are stored in 60i (interlaced) "wrappers" (http://en.wikipedia.org/wiki/Container_format_(digital)) while 25p footage is stored in 50i wrappers. This patch removes the ability of the GH1 to use wrappers (or "containers") and allows the GH1 to encode video in it's 24p/25p native sensor formats directly. This can be a real time-saver when editing video on your computer.
24p video stream f-rame rate is reported at 23.971 fps instead of the NTSC standard 23.976 fps. This is not a concern for most players or NLEs (Non Linear Editors), however issues have been reported in FCP. NTSC standard compliance requires recompression. For details see: http://www.dvxuser.com/V6/showpost.php?p=2017542&postcount=424
Request For Information:



Feature Patch Name: PAL -> NTSC Conversion
Function: Changes the encoding system standards of the GH1 from PAL to NTSC.
Usage:
Click the checkbox next to the feature name,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below)
Dependencies: Only for PAL GH1 models.
Tested: Yes
Stable: Yes
Notes:
720p at 50fps becomes 720p at 60fps, 1080p at 25fps becomes 1080p at 24fps, etc.
You MUST clear all PAL footage from your SD card.
Request For Information:



Feature Patch Name: NTSC -> PAL Conversion
Function:Changes the encoding system standards of the GH1 from NTSC to PAL.
Usage:
Click the checkbox next to the feature name,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below)
Dependencies: Only for NTSC GH1 models.
Tested: Yes
Stable: Yes
Notes:
720p at 60fps becomes 720p at 50fps, 1080p at 24fps becomes 1080p at 25fps, etc.
You MUST clear all NTSC footage from your SD card.
Request For Information:



Feature Patch Name: MJPEG Encoder 30fps -> 24fps
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG Encoder 30fps -> XXfps
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor Mode 4
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 1
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 2
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 3
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 4
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 5
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 6
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 7sw
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Sensor m4 Adjustment 8sh
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG Size 1280m -> 1920m
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:




Manual Revision 0.1
For PTool 3.40d with GH1 ROMs

Tesselator
06-15-2010, 01:17 AM
Part Two

Feature Patch Name: MJPEG E1 Quality
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E1 Table
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E2 Quality
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E2 Table
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E3 Quality
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E3 Table
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E4 Quality
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: MJPEG E4 Table
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: 720p 59.94fps -> 29.97fps
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: 720p 50.00fps -> 25.00fps
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: AVCHD 1080p 24/25fps -> 720p 24/25
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Video Bitrate Adjustment FHD/SH Simplified
Function: Allows increased AVCHD codec bitrates thereby improving video quality for the GH1's FHD and SH rec. quality settings.
Usage:
Click the checkbox next to the feature,
Either Pick same tier of Ptool letter-grade (A,B,C as displayed in the PTool interface) settings for all three AVCHD patches; start at A and work your way up to C; or
If experimenting with your own numbers, make sure this value is lower than Overall Bitrate Adjustment.
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: Overall Bitrate Adjustment , Limiting Bitrate Adjustment
Tested: http://www.dvxuser.com/V6/showthread.php?t=213082
Stable: Can be with the recommended settings of 38000000 - see above link for "Tested".
Notes:
3 levels of recommended settings are displayed in the PTool interface for all 3 interdependent feature patches.
See page 106 of the printed manual.
Request For Information:
If you know of any good low-level AVCHD/MPEG analysis tools or in position to donate licensing or testing time on production systems (for select members of development team) please report details to AVCHD Testing thread in the Development forum. Currently Elecard StreamEye is commonly used, which is available on a 30-day trial.



Feature Patch Name: Video Bitrate Adjustment H
Function: Allows increased AVCHD codec bitrates thereby improving video quality for the GH1's H record quality setting.
Usage:
Click the checkbox next to the feature,
Either Pick same tier of Ptool letter-grade (A,B,C) settings for all three AVCHD patches or,
If experimenting with your own numbers, make sure this value is lower than Overall Bitrate Adjustment.
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: Overall Bitrate Adjustment , Limiting Bitrate Adjustment
Tested: Yes
Stable: Yes.
Notes: See Page 106 of the GH1's printed manual.
Request For Information:




Feature Patch Name: Video Bitrate Adjustment L
Function: Allows increased AVCHD codec bitrates thereby improving video quality for the GH1's L record quality setting.
Usage:
Click the checkbox next to the feature,
Either Pick same tier of Ptool letter-grade (A,B,C) settings for all three AVCHD patches or,
If experimenting with your own numbers, make sure this value is lower than Overall Bitrate Adjustment.
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: Overall Bitrate Adjustment , Limiting Bitrate Adjustment
Tested: Yes
Stable: Yes
Notes: See Page 106 of the GH1's printed manual.
Request For Information:




-------------
Feature Patch Name: Overall Bitrate Adjustment
Function: Allows increased overall AVCHD codec bitrates thereby improving video quality by reducing the amount of compression required.
Usage:
Click the checkbox next to the feature,
Either Pick same tier of Ptool letter-grade (A,B,C as displayed in the PTool interface) settings for all three AVCHD patches; start at A and work your way up to C; or
If experimenting with your own numbers, make sure this value is lower than Limiting Bitrate Adjustment.
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: Video Bitrate Adjustment Simplified, Limiting Bitrate Adjustment
Tested: http://www.dvxuser.com/V6/showthread.php?t=213082
Stable: Can be with the recommended settings of 40000000 - see above link for "Tested".
Notes: 3 levels of recommended settings are displayed in the PTool interface for all 3 interdependent feature patches.
Request For Information:



Feature Patch Name: Limiting Bitrate Adjustment
Function: Allows increased limiting (or maximum) AVCHD codec bitrates thereby improving video quality by reducing the amount of compression required.
Usage:
Click the checkbox next to the feature,
Either Pick same tier of Ptool letter-grade (A,B,C as displayed in the PTool interface) settings for all three AVCHD patches; start at A and work your way up to C; or
If experimenting with your own numbers, make sure this is the highest value of all three patches (see Dependancies).
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: Video Bitrate Adjustment Simplified, Overall Bitrate Adjustment
Tested: http://www.dvxuser.com/V6/showthread.php?t=213082
Stable: Can be with the recommended settings of 42000000 - see above link for "Tested".
Notes: 3 levels of recommended settings are displayed in the PTool interface for all 3 interdependent feature patches.
Request For Information:



Feature Patch Name: 720p50 GOP Size
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: 720p60 GOP Size
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: 1080p25 GOP Size
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: 1080p24 GOP Size
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:



Feature Patch Name: Audio Encoding BPS
Function: allows increasing bitrate for AC3 audio stream
Usage:
Click the checkbox next to the feature,
Select the desired bitrate from the list,
Click the checkbox of any other feature patches you would like to set,
Proceed to the Firmware Handling section (below).
Dependencies: None
Tested: Yes (no link)
Stable: No (see Notes 2 and 3).
Notes:
lpowell, an engineer at Dolby Labs, comments on the use of this adjustment: http://www.dvxuser.com/V6/showpost.php?p=1999254&postcount=1652
Applying this patch may allow the camera to record video clips which can not be played back in camera.
Attempting to play back clips recorded with this patch applied may cause the camera to freeze requiring momentary battery removal in order to continue camera operation.
Request For Information:



Feature Patch Name: Audio Sampling Rate
Function:
Usage:
Dependencies:
Tested:
Stable:
Notes:
Request For Information:





Manual Revision 0.1
For PTool 3.40d with GH1 ROMs


Currently: Inactive.



.

Tesselator
06-15-2010, 06:28 AM
Reserved for manual

Tesselator
06-15-2010, 07:55 AM
.



First time users:


Mac OS X Users:



Read everything on this page (http://www.dvxuser.com/V6/showpost.php?p=1958384&postcount=1) first!


In the camera menus select: MENU/SET --> SETUP --> RESET --> YES --> YES, in order to reset the camera to it's factory defaults.


Either

download and install WineBottler from the links supplied in step 1 (just above) and save the "bottled" file to your desktop as "PTool_Mac.app", or
download the Mac ready self-contained "bottled" version supplied here (http://tesselator.gpmod.com/PTool_Wined_app.zip) or at the top of this thread (they are one and the same) and unzip it to your desktop.



Place the "GH1__132.bin" file you downloaded from the page you read in step 1 (above), onto your desktop.


Load and execute PTool_Mac.app by double clicking on it.


Click the "Load Firmware" button (bottom left), navigate to your Desktop folder, and select the "GH1__132.bin" firmware file you downloaded from Panasonic's website in step one (above).


Navigate the tree structure of Available Patches and make the desired changes.

You must click both on the Patch Name and also on the Patch's checkbox in order to activate, change, or enter values!
(this is not a bug but is a result of how multitasking works by default in OS X.)
Read the manual (this thread) and the PTool_Mac's hot-help in order to understand how to set what you wish to set.
If there is conflict between the information presented in this manual and that displayed in the hot-help then the hot-help takes precedence. The manual here is an an open project compiled by PTool users while the hot-help is from the PTool developer directly.
If this is your very first firmware upgrade and the camera is running v1.31 or earlier then all you need to click of the versioning management options, is the "Prevent version compare". This actually jives with the hot-help as the developer is addressing users already at version 1.32 or higher.



When all of the desired settings are entered correctly wait a few minutes and then go back over everything to double-check for correctness.


Insert a healthy, freshly camera formatted SDHC memory card into your card reader or connected camera and wait for it to mount.


Click "Save Firmware" in the PTool interface (bottom right), navigate to the root folder of your inserted memory card, and save as "GH1__132.bin"
notice the two "_" (underbar) characters, all uppercase filename with a lowercase ".bin" extension.



Eject the mounted memory card volume.


Turn off your camera.


Make sure the memory card is inserted correctly in the camera and then turn on the camera.

!CAUTION! Use only a freshly charged battery! If the battery isn't at 90% or higher capacity the camera will refuse to perform the firmware update.



After the camera is powered up and cleaning + initialization is complete (usually takes about 4 seconds) press the camera's "Display" button and follow the camera's on-screen instructions.


After the firmware update is complete be sure to format the card once again before using the camera.


Done.








Windows Users:



Due to political reasons regarding the Gates Foundation I don't wish to even turn on any of my windows machines until I can get everything to do with MicroSoft off of the drives (and then it won't be a windows machine any longer. :P) . As such I need a windows user to write up this section for us. Some of it may be similar enough to the OS X that you can just paste it and change a few terms.








.

svecher
06-15-2010, 08:34 AM
Now, if I can just everyone who visits this thread to offer 1 entry this is going to be easy!





Feature Patch Name: Native 24p/25p

Function: Removes 60i/50i wrapper from FHD mode and enables writing native (to sensor) 24fps/25fps progressive stream to MTS file.
Dependencies: None
Tested: http://www.dvxuser.com/V6/showpost.php?p=2015009&postcount=2402
Stable: Works, but not standard-compliant.
Notes: 24p video stream f-rame rate is reported at 23.971 fps instead of the NTSC standard 23.976 fps. This is not a concern for most players or NLEs, however issues have been reported in FCP. NTSC standard compliance requires recompression. For details see this post http://www.dvxuser.com/V6/showpost.php?p=2017542&postcount=424

svecher
06-15-2010, 08:44 AM
Remove the following patches, as they are no longer in PTool 3.36 (Rev. 20100615)

Feature Patch Name: Video buffer (seems to have not had any effect)
Feature Patch Name: Video Bitrate Adjustment (replaced by VBA Simplified)
Feature Patch Name: MJPEG Encoder 1280m -> 1920m (part of MJPEG Size 1280m -> 1290m patch)

Tesselator
06-15-2010, 09:55 AM
Awesome guys! Thanks!

Keep'm coming.

BTW, I know a lot of this info is embedded in the PTool itself but I guess there will be many who won't ever get that far without reading a document like this one first. I know I didn't. :D I always want to know what's going to happen before I try it. :)

Vitaliy Kiselev
06-15-2010, 10:46 AM
Problem with such manuals is that they can be confusing sometimes.

I really did not get anything about version change description here.
As current version have two patches related to this thing.
23.971 thing is also very confusing, as actual rate is exact 23,976 and no recompression is required.
Some NLE still have troubles with AVCHD footage, but it do not mean that any recompression is required in normal software.

I believe that Tesselator do not use firmware today?
If this is the case and no one want to maintain this manual I'll shut it down temporary before he'll try every patch he describe here personally.

Isaac_Brody
06-15-2010, 11:29 AM
I think a manual even if confusing is better than none. As long as a lot of tester's contribute to this it could be very helpful for a lot of users.

Vitaliy Kiselev
06-15-2010, 11:38 AM
I think a manual even if confusing is better than none. As long as a lot of tester's contribute to this it could be very helpful for a lot of users.

I do not agree here.
Manual must be written by someone who know things and tried all this settings.
This is not the case here, as I understand.

Isaac_Brody
06-15-2010, 11:41 AM
He is collecting information, and testers are giving input. At the moment the information on this project is spread out in about five threads, and it will get harder to follow results and get definitive answers as each thread grows. As long as the thread is updated based on current tester information it will be useful. With the collective input and eyes of many there will be less chance for error.

svecher
06-15-2010, 12:55 PM
Problem with such manuals is that they can be confusing sometimes.

Tesselator is employing a very structured approach to aggregating information in principle very similar to peer review. Such efforts typically reduce confusion levels, especially when the alternative is status quo.


I really did not get anything about version change description here.
Well, since you know best how it works please feel free to make corrections, if you have time.


23.971 thing is also very confusing, as actual rate is exact 23,976 and no recompression is required.
Confusing indeed. I wrote up that description based both on my own testing and what others reported (I refered to the post). Analysing my own footage as well as examples posted by others with StreamEye reveals that the actual rate is 23,971 fps (see attachment). There seem to be no issues playing such native footage back on a computer, posting on Vimeo or on BD players. But the rate is clearly a little off NTSC standard, so there might be issues when using footage in a broadcast environment. We just don't know at the moment.


I believe that Tesselator do not use firmware today?
If this is the case and no one want to maintain this manual I'll shut it down temporary before he'll try every patch he describe here personally.
He said he'll maintain it. I'm sure he is not making stuff up, as majority of descriptions are still blank. In addition, he is adding information from other testers. If something is wrong, then please offer corrections. It's an open project, like the patch project itself. Why talk about shutting things down?

Tesselator
06-16-2010, 03:41 AM
Yup, I'll maintain it for at least a few years (health permitting - currently healthy as a horse!). At first my updates will be almost every day. Then when we all (and that includes Tester13 [Vitaliy Kiselev] - primarily!) feel generally satisfied I'll start revisiting (updating) it with each new release of PTool and as new information is posted in this thread or in some way comes to my attention.

Anyone with the privileges to do so please also feel free to enter or correct information in post #1 and #2 in this thread!

Also BTW, I am trying stuff as I go. At first I am only going as far as PTool use without actually burning the firmware on the camera! As soon as revision iterations are confirmed to no longer be an issue of any kind I will be burning and testing most functions as well.

As far as qualification goes I've written several manuals - probably the most famous among computerists would be the Lightwave 3D manual where I wrote one of the three books that ships with the NewTek product. I believe it's about 900 pages if memory serves. But I also helped to engineer that product. Tester13 [Vitaliy Kiselev] is right about it being very helpful to know the product well! If allowed to continue I'll do my best though and maintain a special diligence in being very meticulous about correctness.

I of course need help though. Especially from the Mods and from Tester13 [Vitaliy Kiselev] whenever they have or if they have, the time.

--
Thanks!
Jim

Chris Light
06-16-2010, 03:55 AM
Tess...with credentials like that, your comittment to this project will be valued and appreciated.

svecher
06-16-2010, 08:09 AM
Feature Patch Name: Video Bitrate Adjustment Simplified

Function: Allows increasing AVCHD codec bitrate to improve footage quality.
Usage: Either 1) Pick same tier of Ptool letter-grade (A,B,C) settings for all three AVCHD patches; start at A and work your way up to C; or 2) If experimenting with your own numbers, make sure this value is lower than Overall Bitrate Adjustment
Dependencies: Overall Bitrate Adjustment , Limiting Bitrate Adjustment
Tested: http://www.dvxuser.com/V6/showthread.php?t=213082
Stable: Jobless's recommended settings (38000000)
http://www.dvxuser.com/V6/showpost.php?p=2012634&postcount=1
Notes: If you know of any good low-level AVCHD/MPEG analysis tools or in position to donate licensing or testing time on production systems (for select members of development team) please report details to AVCHD Testing thread in the Development forum. Currently Elecard StreamEye is commonly used, which is available on a 30-day trial.
Request For Information:
Feature Patch Name: Overall Bitrate Adjustment

Function: Allows increasing overall AVCHD codec bitrate to improve footage quality.
Usage: Either 1) Pick same tier of Ptool letter-grade (A,B,C) settings for all three AVCHD patches; start at A and work your way up to C; or 2) If experimenting with your own numbers, make sure this value is lower than Limiting Bitrate Adjustment
Dependencies: Video Bitrate Adjustment Simplified, Limiting Bitrate Adjustment
Tested: see Video Bitrate Adjustment Simplified
Stable: Jobless's recommended settings (40000000)
Notes:
Request For Information:
Feature Patch Name: Limiting Bitrate Adjustment

Function: Allows increasing limiting AVCHD codec bitrate to improve footage quality.
Usage: Either 1) Pick same tier of Ptool letter-grade (A,B,C) settings for all three AVCHD patches; start at A and work your way up to C; or 2) If experimenting with your own numbers this is should be the highest value of all three patches.
Dependencies: Video Bitrate Adjustment Simplified, Overall Bitrate Adjustment
Tested: see Video Bitrate Adjustment Simplified
Stable: Jobless's recommended settings (42000000)
Notes:
Request For Information:

Tesselator
06-16-2010, 07:03 PM
Awesome svecher! Thanks man!

AdrianF
06-17-2010, 12:53 AM
Thanks for the mammoth effort guys. Between you and those who are posting footage and settings, it's going to help everybody find what is workable.

Tesselator
06-17-2010, 03:36 AM
Well, I couldn't stand waiting any longer and burnt me a GH13 custom firmware upgrade in order to find out how the reversioning (entry #1 and #2) actually work. It's actually completely logical and I have no idea what my problem was. :D I guess I had to see it to understand it.

Anyway basically it goes like this:

It your current firmware is anything less than 1.32 (like mine was 1.0 official!) then you do NOT need to use "Version Change" at all no matter what. Hacked, Official, it doesn't matter because you're writing a higher version when you write either the official or the hacked 1.32 for the first time. This was always the case I guess - peroid.

If you intend to test many different settings AND your current firmware is less than 1.32 then all you need to use is the "Compare Version Patch" switch - and you should use it everytime you write a custom firmware. You never need to use the "Version Change" under these circumstances.

Now, if you're trying to upgrade a camera that's already at 1.32 or higher then you need the Version Change iteration. But if the "Version Compare Patch" is set then after that image in burned you will never need to use the "Version Change" switch again. Assuming you always set the Version Compare ever after.

Once you have an image written with the Version Compare Patch installed you can also restore the camera to any of Panasonic's official patch releases. But of course you should only use 1.32 or later because of the different variables different firmware images store.

If you want to install or reinstall a GH13 custom image over the official 1.32 you then need to use the Version Change so that the camera recognizes the ROM image file as being an "upgrade" (new version). Although if you set the Version Compare Patch then you don't need the Version Change when you write it again after this.

The caveat? With the "Version Compare Patch" installed the GH1's "Version Display" screen reports a BODY FIRMWARE version of 0.0

No biggy, who cares about a version string?


Hehehe, what a fun manual entry! :Drogar-Kriz(DBG):

arknox
06-17-2010, 06:18 AM
You had me thinking yes this is exactly the feature needed... up until:


The caveat? With the "Version Compare Patch" installed the GH1's "Version Display" screen reports a BODY FIRMWARE version of 0.0

So what is the body firmware version number before applying the version compare patch, and is there any way to have the ptool maintain the body firmware version number instead of it reporting 0.0?

I'm thinking purely from a "camera goes tits up" mentality and needs serviced and Panasonic take one look at it and say "what's this 0.0 number, we aint fixing your camera".

Tesselator
06-17-2010, 06:58 AM
You had me thinking yes this is exactly the feature needed... up until:

:)




So what is the body firmware version number before applying the version compare patch,

It could be anything. 1.0, 1.45, just anything. Mine happened to be 1.0 the first time through.


and is there any way to have the ptool maintain the body firmware version number instead of it reporting 0.0?

You have two options with a Version Compare Patched camera reading out 0.0:

1) Place Panasonic's original unmodified firmware image on the card and update to that,
2) Use PTool's "Version Change" without the "Version Compare Patch" and call it anything you like. The Camera's "Version Display" screen will then display whatever you entered - as the BODY FIRMWARE version.


I'm thinking purely from a "camera goes tits up" mentality and needs serviced and Panasonic take one look at it and say "what's this 0.0 number, we aint fixing your camera".

Yup, that's what had me going too and why I thought I would wait till it was all sussed out before I tried the firmware. IMHO, this is as safe as it will ever get. As long as the camera can read the card you can now ALWAYS restore to an unmodified original Panasonic release. And that's a load off my mind in a very big way. :) Well, in a $400 way anyway... :P

svecher
06-17-2010, 07:16 AM
If you intend to test many different settings AND your current firmware is less than 1.32 then all you need to use is the "Compare Version Patch" switch - and you should use it everytime you write a custom firmware. You never need to use the "Version Change" under these circumstances.

Interesting, because when I tested two days ago (http://www.dvxuser.com/V6/showpost.php?p=2020219&postcount=3) and tried loading firmware with only "Compare Version Patch" checked off (and AVCHD patches that I wanted to test) with version-agnostic firrmware already running on the camera the version up process would fail after starting (message displayed "please turn off the camera") and corrupt the firmware file on the card. Couldn't delete the file either. After reformating the card I found that "Version Change" patch must always be checked in conjunction with "Compare Version Patch." It just didn't matter what increment number I put in.

EDIT: Could not repeat this in testing two days later http://www.dvxuser.com/V6/showpost.php?p=2022740&postcount=36, when patch worked the way descirbed in the manual.

Tesselator
06-17-2010, 07:28 AM
My first guess would be a bad memory card. <shrug> I have no idea. All I know is what it did for me.

I do follow some simple basic rules whenever downloading any firmware images to any cameras tho:

1) Reset all user setting on a freshly powered up camera.
2) Turn the camera off and then on again.
3) Use only a freshly camera formatted card with ONLY the firmware image on it.
4) Always use the AC Adaptor.
5) Reset all User settings again after the image download.
6) Format the card immediately after
7) Power down and up the camera before using it and/or restoring my defaults.

Try it again to see if it wasn't just a fluke?

svecher
06-17-2010, 08:20 AM
The card is Sandisk Extreme 30Mb/s Class 10. It is one of the better cards out there (as far as reviews are concerned) and it has never given me problems. I doubt it is the problem.

However, thanks for posting your upgrade procedures. Yours are definately more thorough, as for example, I normally don't do steps 1), 3), 5), 6). I'm starting to recall a recommendation (from Vitaliy IIRC) to reset user settings, so maybe that's the issue. I'll try again tonight.

Isaac_Brody
06-17-2010, 08:31 AM
My first guess would be a bad memory card. <shrug> I have no idea. All I know is what it did for me.

I do follow some simple basic rules whenever downloading any firmware images to any cameras tho:

1) Reset all user setting on a freshly powered up camera.
2) Turn the camera off and then on again.
3) Use only a freshly camera formatted card with ONLY the firmware image on it.
4) Always use the AC Adaptor.
5) Reset all User settings again after the image download.
6) Format the card immediately after
7) Power down and up the camera before using it and/or restoring my defaults.

Try it again to see if it wasn't just a fluke?


I've heard that it's dangerous to do firmware updates with AC adaptor and it should only be done with a fully charged battery.

UncleBenji1977
06-17-2010, 08:49 AM
Ok... Maybe I'm missing something.... I'm learning.... But I used this tutorial to do my first hack: http://wiki.eoshd.com/index.php/Beginners_GH1_Custom_Firmware_Guide

It worked... but after reading these boards I realized I wanted to do more. I went in, made more changes, and when saving the file added one number up, loaded the card, and then the cam wouldn't update. What did I do wrong? I also deleted the original hacked file... Was that a bad move? Someone help please. Thanks.

UncleBenji1977
06-17-2010, 08:58 AM
Forget what I wrote... Figured out the problem.

svecher
06-17-2010, 09:01 AM
I've heard that it's dangerous to do firmware updates with AC adaptor and it should only be done with a fully charged battery.
Well, if you loose power during the upgrade there is a probability of firmware corruption in camera, with subsequent inability to operate it or finish the upgrade. If such an event is a concern, you can always plug into a UPS. I think most people will already protect their computer equipment if such concerns are not very minor.
It should be noted, that GH1 manual lists AC adapter as a valid option for upgrading, so if anything goes wrong it will be only fair to make that fact known when speaking to the warranty department. Perhaps then future products will be designed with DC in port. I'm not sure why this wasn't done in the first place and instead we got this fake-battery-thingy.

Tesselator
06-17-2010, 09:36 AM
I've heard that it's dangerous to do firmware updates with AC adaptor and it should only be done with a fully charged battery.

Yeah, I followed that thread as well. I guess it's somewhat of a personal choice and knowing the stability factor of the AC at your location. In my case I'm completely off the public electrical grid and about the only way the AC could go out is if some stinker cut the wires or something. :)

Tesselator
06-17-2010, 09:41 AM
The card is Sandisk Extreme 30Mb/s Class 10. It is one of the better cards out there (as far as reviews are concerned) and it has never given me problems. I doubt it is the problem.

However, thanks for posting your upgrade procedures. Yours are definately more thorough, as for example, I normally don't do steps 1), 3), 5), 6). I'm starting to recall a recommendation (from Vitaliy IIRC) to reset user settings, so maybe that's the issue. I'll try again tonight.

I think 1 and 3 are important - especially 3. 5 and 6 are probably just me being anal. :Drogar-BigGrin(DBG)

So, did you try it again? I'm dying to know how it went...

If you're right it means both Tester and I are wrong and I need to document it in the manual.

I tried mine 3 more times now and for me it works as I described. Are you on a GF1 or a GH1 btw?

svecher
06-17-2010, 11:01 AM
So, did you try it again? I'm dying to know how it went...

I tried mine 3 more times now and for me it works as I described. Are you on a GF1 or a GH1 btw?
Neither, I have GH13 :2vrolijk_08:

No experiments while at work (for another 4 hrs or so).

Tesselator
06-17-2010, 11:06 AM
Neither, I have GH13 :2vrolijk_08:

No experiments while at work (for another 4 hrs or so).

OK, kewl! I'll be patient. :undecided

tyampel
06-17-2010, 06:40 PM
Well, I couldn't stand waiting any longer and burnt me a GH13 custom firmware upgrade in order to find out how the reversioning (entry #1 and #2) actually work. It's actually completely logical and I have no idea what my problem was. :D I guess I had to see it to understand it.

Anyway basically it goes like this:

It your current firmware is anything less than 1.32 (like mine was 1.0 official!) then you do NOT need to use "Version Change" at all no matter what. Hacked, Official, it doesn't matter because you're writing a higher version when you write either the official or the hacked 1.32 for the first time. This was always the case I guess - peroid.

If you intend to test many different settings AND your current firmware is less than 1.32 then all you need to use is the "Compare Version Patch" switch - and you should use it everytime you write a custom firmware. You never need to use the "Version Change" under these circumstances.

Now, if you're trying to upgrade a camera that's already at 1.32 or higher then you need the Version Change iteration. But if the "Version Compare Patch" is set then after that image in burned you will never need to use the "Version Change" switch again. Assuming you always set the Version Compare ever after.

Once you have an image written with the Version Compare Patch installed you can also restore the camera to any of Panasonic's official patch releases. But of course you should only use 1.32 or later because of the different variables different firmware images store.

If you want to install or reinstall a GH13 custom image over the official 1.32 you then need to use the Version Change so that the camera recognizes the ROM image file as being an "upgrade" (new version). Although if you set the Version Compare Patch then you don't need the Version Change when you write it again after this.

The caveat? With the "Version Compare Patch" installed the GH1's "Version Display" screen reports a BODY FIRMWARE version of 0.0

No biggy, who cares about a version string?


Hehehe, what a fun manual entry! :Drogar-Kriz(DBG):

I would like to add that the version change feature allows testers the flexibility to test various options by carrying two SD cards - one with modified settings, the other with the original Panasonic version. Now it is easy to switch between versions to compare the before and after effects.

Thanks for your efforts in producing the manual.

svecher
06-17-2010, 07:27 PM
OK, kewl! I'll be patient. :undecided
I just tested the "old" way (i.e. without formatting card etc.) in Release 3.37d and happy to report that "Version Check" works flawlessly. I blame "operator error".

svecher
06-17-2010, 07:52 PM
Feature Patch Name: Audio Encoding BPS

Function: allows increasing bitrate for AC3 audio stream
Usage: from 192,000 (default) to 448,000 bps.
Dependencies: None
Tested:
Stable: Camera will record, but not playback footage. Files will playback on computer.
Notes: lpowell, who is an engineer at Dolby Labs recommends to leave audio bitrate at default http://www.dvxuser.com/V6/showpost.php?p=1999254&postcount=1652
Request For Information:

Tesselator
06-18-2010, 03:27 AM
I just tested the "old" way (i.e. without formatting card etc.) in Release 3.37d and happy to report that "Version Check" works flawlessly. I blame "operator error".

OK, Awesome dooderz! Much appreciated! So I'll keep the current manual description. Also since there is currently such a large volume of conflicting info in these threads it might be a good idea to go back and click the edit button on old posts and add a quicky note - something to this affect.


Feature Patch Name: Audio Encoding BPS

Function: allows increasing bitrate for AC3 audio stream
Usage: from 192,000 (default) to 448,000 bps.
Dependencies: None
Tested:
Stable: Camera will record, but not playback footage. Files will playback on computer.
Notes: lpowell, who is an engineer at Dolby Labs recommends to leave audio bitrate at default http://www.dvxuser.com/V6/showpost.php?p=1999254&postcount=1652
Request For Information:


Awesome! Another entry too! You ROCK! man! Thanks!

svecher
06-18-2010, 07:18 AM
OK, Awesome dooderz! Much appreciated! So I'll keep the current manual description. Also since there is currently such a large volume of conflicting info in these threads it might be a good idea to go back and click the edit button on old posts and add a quicky note - something to this affect.

Good idea, I added the note to my post in this thread.

I see that you are splitting patches up in between two posts. How about putting tested and "production-ready" patches in the first one and research and experimental ones (a majority of them, which also don't have descriptions ATM) in the second?

Tesselator
06-18-2010, 09:27 AM
That would be a good idea but they change all the time. As it is they follow the order presented in PTool's GUI listview. This makes it easy for me to find and I'm hoping easy for others to locate the entry more easily.

Tesselator
06-18-2010, 05:39 PM
How about color coding them?

RED = Not stable yet or can cause real problems.
YELLOW = Can be stable but use with caution.
GREEN = Good to go, no worries.

What do you think?

svecher
06-18-2010, 06:19 PM
How about color coding them?

RED = Not stable yet or can cause real problems.
YELLOW = Can be stable but use with caution.
GREEN = Good to go, no worries.

What do you think?
Sounds good, I think this will quickly give an idea to those not familiar with latest developments a quick reference on what's safe to touch and what's not.

Tesselator
06-18-2010, 08:07 PM
So... I guess go by Tester's own tagging?

WORKING = GREEN
TESTED / PARTIALLY TESTED = YELLOW
UNTESTED / EXPERIMENTAL = RED

Does that sound about right? Did I leave out anything?

Tesselator
06-20-2010, 11:15 AM
Or actually... :D with 42 total (current) features color tags are going consume too much of the 2000 character (per message) limit.
]color=green[]/color[ = 21 characters x 42 functions = 882 characters or 441 per message. :(

How about special characters? What do you see below?

☼ <-- 8 pointed star
✰ <-- Drop shadowed 5 pointed star
❍ <-- Drop shadowed circle
❑ <-- Drop shadowed square
☯ <-- Ying yang
✔ <-- Check mark
✓ <-- Check mark 2
☒ <-- Boxed X
☑ <-- Boxed check mark
☠ <-- Skull and bones
⚠ <-- Caution
▣ <-- Boxed filled box
▇ <-- Filled box?
⌧ <-- X'ed box
▢ <-- Box
⤴ <-- Turn up
⤵ <-- Turn down
⤶ <-- Turn back
⦻ <-- X'ed circle
⦸ <-- Crossed circle
⦵ <-- Striked circle
⦿ <-- Circled filled circle
⨸ <-- Circled divide
⨷ <-- Double circled multiply
⑴ <-- Parenthesized 1
<-- Half
<-- Quarter
Ⓐ <-- Circled A
Ⓒ <-- Circled C
Ⓕ <-- Circled F

Does anyone not see those? Which ones don't render properly for you?

Or, my Request for information could go white and equal it out?

Or is there a better way yet? Trying to conserve on the character count here. Or how about the mods up the limit (for this thread/author)? Anything?

Martti Ekstrand
06-20-2010, 11:49 AM
I see all special characters as you describe them with Safari and Chrome on OSX.

You are doing a great job here with the manual.

savagess
06-20-2010, 03:42 PM
Great idea with listing features. Wish I could help and add, but don;t know enough.

Waiting for the MJPEG settings!..
One thing, could you add if the settings for what ever hack are changed if it's still playable on the camera or not, this I think would be handy to know.
It's really one of the main thnings stopping me changing video settings if it stops the ability to play back on the camera...
Cheers

svecher
06-21-2010, 08:12 AM
Great idea with listing features. Wish I could help and add, but don;t know enough.

It's really one of the main thnings stopping me changing video settings if it stops the ability to play back on the camera...
Cheers
In the manual such information is noted under "Stable" field. The only patch known to cause camera not to be able to play footage is audio bitrate adjustments. AVCHD adjustments are fine. There are some issues with native patch (23.971 frame rate and Upper Dominance field causing issues in FCP as well as possibility of camera freezing when shooting detailed static scenes). I haven't experimented with MJPEG patches myself, but I don't recall any issues with playability. Use settings from "Stable MJPEG settings" sticky until somebody does the entry for Manual.

EDIT: Tesselator, I noticed that audio bitrate adjustment patch is missing a warning about not being able to play back footage in camera. Please add. Thanks.

rundavids
06-21-2010, 08:47 AM
Hi, Tesselator. Great manual so far. They need to make this thread a sticky.

I also have a question "version compare patch". My gh1 firmware is 1.2 and if I use this patch, my gh1 would then become 0.0 and can test settings repeatedly as long as this patch is checked everytime?
And I could return my gh1 to it's former self with official panasonic firmware?

svecher
06-21-2010, 09:10 AM
Hi, Tesselator. Great manual so far. They need to make this thread a sticky.

Hopefully Isaac can work this (and character limit) out. I asked him about that earlier this morning.



I also have a question "version compare patch". My gh1 firmware is 1.2 and if I use this patch, my gh1 would then become 0.0 and can test settings repeatedly as long as this patch is checked everytime?
And I could return my gh1 to it's former self with official panasonic firmware?
Yes, I tested exactly this scenario and it works. However, since PTool is based on stock version 1.32, if you do go back to stock firmware version it is highly recommended that you revert back to stock v.1.32 (because of lens version updates).

jokari
06-21-2010, 10:29 AM
very helpful job, many thanks!

Isaac_Brody
06-21-2010, 11:33 AM
Character limit was raised for this thread.

svecher
06-21-2010, 12:56 PM
Character limit was raised for this thread.
Awesome, thanks very much Isaac!

So, we should have enough space for additional features and color coding as discussed.

Tesselator
06-21-2010, 07:38 PM
Character limit was raised for this thread.

Excellent! Thanks Brody!

Heh, what a cool name!

:Drogar-BigGrin(DBG)

rundavids
06-22-2010, 12:33 AM
Thanks for reply svecher. I'm gonna upgrde to gh13 soon.

Tesselator
06-23-2010, 05:06 AM
Thanks for reply svecher. I'm gonna upgrde to gh13 soon.

It think I've now tried just about every feature of the camera and the changes I made with PTool seems to have caused no negative affects other than the body version string reporting 0.0.

I'm not sure I set it at all correctly though. I set:


Version Compare Patch (never used Version Change - ever)
3rd party Battery (though I only have just the one Panny battery anyway :D)
Interface Language: English.
Native 24p/25p
MJPEG 4:2:2
Bitrate Adjustment FHD/SH Simplified: 40,000,000
Bitrate Adjustment H Added: 38,000,000
Bitrate Adjustment L Added: 36,000,000
Overall Bitrate: 44,000,000
Limiting Bitrate: 48,000,000


But as you see below the bit-rates didn't increase much or at all:

http://tesselator.gpmod.com/Images/Temporary/PlexSnapz_005.jpg
http://tesselator.gpmod.com/Images/Temporary/PlexSnapz_004.jpg
http://tesselator.gpmod.com/Images/Temporary/PlexSnapz_003.jpg
http://tesselator.gpmod.com/Images/Temporary/PlexSnapz_002.jpg

So, the first 5 settings there are probably right but I'm wondering if the last ones don't also depend on something else I'm not doing.

Anyway, with those settings everything about the camera works perfectly. So I think it's completely safe to mod at this point.

svecher
06-23-2010, 07:34 AM
It think I've now tried just about every feature of the camera and the changes I made with PTool seems to have caused no negative affects other than the body version string reporting 0.0.

I'm not sure I set it at all correctly though. I set:


Version Compare Patch (never used Version Change - ever)
3rd party Battery (though I only have just the one Panny battery anyway :D)
Interface Language: English.
Native 24p/25p
MJPEG 4:2:2
Bitrate Adjustment FHD/SH Simplified: 40,000,000
Bitrate Adjustment H Added: 38,000,000
Bitrate Adjustment L Added: 36,000,000
Overall Bitrate: 44,000,000
Limiting Bitrate: 48,000,000
But as you see below the bit-rates didn't increase much or at all:
So, the first 5 settings there are probably right but I'm wondering if the last ones don't also depend on something else I'm not doing.


AVCHD bitrate adjustment settings are standalone (6-10) as a group. The likely reason you are seeing low bitrates is because of shooting relatively low-detail scenes. Shoot something like a star chart http://www.bealecorner.org/red/test-patterns/star-chart-bars-full-600dpi.png and they will get up there. Or a field of flowers ;)

Patch #5 is probably meaningless without applying other MJPEG related patches.

Patch #4. There is discussion in this thread, linking native patch to some breakage in footage, rogue I/P frames and camera freezing when using high bitrates.
http://www.dvxuser.com/V6/showthread.php?t=213908
The manual entry needs a little revision under testing notes for this entry.

rundavids
06-23-2010, 11:17 AM
Thanks for the information tesselator. I'm definitely will upgrade soon. Promise :)

Tesselator
06-23-2010, 12:57 PM
I recently answered a PM and thought it might be useful to also post it here for consideration and comment:



Hello Tesselator,

I have been reading everything I can about the GH1 hack and need some clarification using the newer "Version Compare Patch"...

http://www.dvxuser.com/V6/showpost.php?p=2021799&postcount=18


Do you still save the new firmware name file by '1' increment?

No. [see the post linked above]



When I want to make additional changes/tweaks to the firmware, do I always work off the original 1.32 file

Yes.


Lastly, if I want to re-install the original Panasonic 1.32 firmware will the camera still read 0.0 in the 'Body Firmware' version display?

No.


I think it would help a lot of people if the instructions on the first-post sticky pages were updated (especially screenshots) - thanks for the work you have done ;)

I probably will not add screen shots (I dunno yet) but the first few "Manual" messages in this thread are actively being updated. There's a slight lull (a few days) in updates as the author says he is revising the layout of Ptool and may also be consolidating some feature patches. It will get a large update shortly after that is released - likely very soon now!

Tesselator
06-23-2010, 01:07 PM
AVCHD bitrate adjustment settings are standalone (6-10) as a group. The likely reason you are seeing low bitrates is because of shooting relatively low-detail scenes. Shoot something like a star chart http://www.bealecorner.org/red/test-patterns/star-chart-bars-full-600dpi.png and they will get up there. Or a field of flowers ;)

I thought my tests were heavy but OK, I'll try and weight them down with more detail... Thanks!



Patch #5 is probably meaningless without applying other MJPEG related patches.

But it does give me 422. Color resolution like 420/422/etc. is typically only noticeable when compositing or when up-scaling the footage. Since I my want to composite something (sometime) I would like to just always use 422. It's not really that much bigger. I think it adds something like 10% to the relative file size - typically (on average).



Patch #4. There is discussion in this thread, linking native patch to some breakage in footage, rogue I/P frames and camera freezing when using high bitrates.
http://www.dvxuser.com/V6/showthread.php?t=213908
The manual entry needs a little revision under testing notes for this entry.

OK, which posts were you referring to specifically?

Tesselator
06-24-2010, 08:08 AM
BTW, Just to update a little: I shot the "star-chart-bars-full-600dpi" on the LCD yesterday and yup, sure enough, it jumped right up to 39.8 mbits and stayed between 36 and 39.x the entire time the "star-chart-bars-full-600dpi" was in view (about 3 min. clip test time). ;)

Thanks svecher! (yet again!) :)

svecher
06-24-2010, 03:41 PM
OK, which posts were you referring to specifically?
The thought process has been evolving throughout, so I might as well resummarize. Basically, applying a native patch has been linked to appearance of "rogue" I/P frames (usually last P frame in a GOP or standalone I frames that are several times larger than average) in AVCHD stream files. Depending on 1) SD Card used, 2) Amount of detail in the scene (high detail pushes average bitrate up) and 3) Bitrate settings chosen for AVCHD mode, one can experience either good performance, stopped recording with "card too slow" errors or complete freezing of the camera (requires pulling battery and loosing footage). There are no generally agreed upon "safe settings" yet, but a good Class 10 card (Sandisk, Panasonic or equivalent) with PTool's "C" settings has been reported to be least problem-prone. Native patch is mostly about convenience - not having to deal with removal of 60i wrapper. The one functional exception confirmed by Barry Green is true progressive color sampling, which is closer to "real" colors than interlaced sampling. It is therefore recommended that this patch is only applied by users who clearly need the optimized workflow and fully understand the risks associated with use.

pepperidge
06-25-2010, 11:24 AM
Hi, I'm new to the forum, led by the link to PTools as reviewed on luminous landscape.

I just tried a few patches with the latest 3.37d version, including:

Version Compare Patch
3rd party Battery
Interface Language: English.
Native 24p/25p
Audio bit rate

After the firmware "upgrade", I wasn't able to playback videos on the camera anymore. Were there any settings I should be doing? I tried searching on the thread by couldn't find anything...

Hope I have screwed anything up!

Appreciate any help.

Barry_Green
06-25-2010, 11:27 AM
The audio bitrate patch is th eone that makes it not able to playback in-camera. Next time you upgrade, don't check that, and you'll be fine.

pepperidge
06-25-2010, 09:11 PM
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

pepperidge
06-25-2010, 09:25 PM
oops, pressed the wrong button...

please ignore #4, it seems to be a problem with VLC, didn't see any problems with iMovie

Tesselator
06-27-2010, 01:29 PM
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. :)


.

timbook2
06-27-2010, 01:41 PM
The audio bitrate patch is th eone that makes it not able to playback in-camera. Next time you upgrade, don't check that, and you'll be fine.

This note should make it into the next PTools version, its a trap many of us ran into!

Tesselator
06-28-2010, 04:28 AM
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. :)

svecher
06-28-2010, 06:36 AM
OK, done.

That look about right?

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. :)
Sounds great, any chance of an all electronic Panasonic-Canon interface thingy? ;)

Tesselator
06-28-2010, 08:31 AM
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

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? ;)

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. :)

svecher
06-28-2010, 10:23 AM
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.

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.

Tesselator
06-29-2010, 01:38 PM
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.

svecher
06-29-2010, 01:54 PM
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.
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 :)

mitchell1074
06-30-2010, 07:31 AM
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 :)

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.

svecher
06-30-2010, 07:46 AM
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.
Yes, indeed. I always refer to PTool's "C" Settings. If referring to other ones, I usually specify Jobless's "C" Settings, etc.

mitchell1074
06-30-2010, 08:02 AM
Yes, indeed. I always refer to PTool's "C" Settings. If referring to other ones, I usually specify Jobless's "C" Settings, etc.

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"

svecher
07-01-2010, 01:15 PM
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?

Correct. http://www.dvxuser.com/V6/showpost.php?p=2024463&postcount=2



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?

yes

svecher
07-13-2010, 05:58 PM
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.

Tesselator
07-14-2010, 07:08 AM
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. :)

Vitaliy Kiselev
08-02-2010, 09:20 PM
I unsticked this thread as updates are slow.

Tesselator
08-03-2010, 05:48 PM
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.