GH1 firmware research volunteers required

Next test:

MJPEG mode sensor test.
(turn on: MJPEG Encoder 30fps -> Xfps: - 25)

Setting:

Sensor mode 4: 4 -> 6
Sensor m4 adju 1: 856 -> 880
Sensor m4 adju 2: 870 -> 912
Sensor m4 adju 3: 10 -> 11
Sensor m4 adju 4: 838 -> 848
Sensor m4 adju 5: 52 -> 54

Result below on the picture
Video link: http://rapidshare.com/files/396777560/P1010138.MOV
 

Attachments

  • P1010138.jpg
    P1010138.jpg
    26.6 KB · Views: 0
Use jDownloader.
http://jdownloader.org/
It will retry automatically
I believe that RapidShare has switched to limit 10 downloads per file some time ago for free accounts. It is best then for most people to refrain from the urge to pixel-peep these test files to make sure that those who really need to see them (tester13) actually do get to see them. Or buy a paid rapidshare account for Nurbs since he is so involved with testing.
 
If you split your files up into 50MB segments with something like 7zip, Skydrive has 25GB free storage with no limits on downloads.
 
Ok, here is the first test for me:
Settings were changed for an attempt at AVHCD quality improvement

This is the only thing I changed except 'native' 24p setting set

Video Buffer : 25xxxxxx
Video Bitrate Adjustment: 22xxxxxxx
Overall Bitrate Adjustment: 24xxxxxxx

Good:
Camera Zoom worked

Bad:
Camera would not record video after an attempt to record was tried.
Picture Images could not be taken either after the video attempt.

Result:
I am re-verting to a non-edited bitrate firmware right now. Maybe others will have better luck?
 
Special note.

Any discussion of Andrew related stuff will be removed from this thread.
This especially concerns Andrew himself under different nicknames.
 
Next test:
Setting:
Sensor mode 4: 4 -> 6
Sensor m4 adju 1: 856 -> 880

Please do not touch Sensor mode 4 patch.
As it makes all other adjustments useless.
Change one thing at a time.
As for 800sh constants you can go from about 600 to about 1300.
Try to start from sw and sh patches (last two).
 
Last edited:
AVCHD mud explained

Look at this strange picture:
1276064182.jpg


It shows block types and motion vectors for P frame.
Scene is specially very simple, overexposed and out of focus for easy viewing.
On simple scene and careful motion you have enough interframe blocks and some intraframe blocks (things with small divisions).
Lets look at high detail scene. Without motion, interframe blocks are able to maintain quality of I frame. But as soon as motion kicks in, you have almost only intraframe blocks.
As P frame size hits limitation, intraframe blocks compression became insane (3x-6x more size reduction). So, you have something like overcompressed I frame than P frame.
 
Ok, here is the first test for me:
Settings were changed for an attempt at AVHCD quality improvement


It's due to too high Video Bitrate Adjustment value.
More than 20xxxxxxx value will crash the camera.
My bitrates combination for AVCHD is 40xxxxxxx:20xxxxxxx:24xxxxxxx.
And if you are able to review the pictures, I mean to avoid freezing the body when touching the Play button, make sure the first shot is a picture, not an AVCHD movie.
 
Last edited by a moderator:
Why would they do it like this?

Why would they do it like this?

AVCHD mud explained
It shows block types and motion vectors for P frame.
...
As P frame size hits limitation, intraframe blocks compression became insane (3x-6x more size reduction). So, you have something like overcompressed I frame than P frame.

Dont Panasonic know what they are doing?
 
Last edited by a moderator:
Mayor breakthrough coming. Stay tuned.

As for Panasonic. No, they don't know. How they can make P frame size larger than I frame and have worse quality? This is kind of the hint to that's coming.
 
PTool 3.35 released

Limiting bitrate patch added. Now you can adjust AVCHD bitrate (with use of other three patches that we have already).

Tested settings:

Code:
Video buffer                 - a) 33.500.000 b) 40.000.000
Video bitrate adjustment     - a) 22.000.000 b) 32.000.000
Overall bitrate adjustment   - a) 24.000.000 b) 35.000.000
Limiting bitrate adjustment  - a) 26.000.000 b) 40.000.000

a) Gives you 22Mbit bitrate with some spikes up to 24Mbit.
b) Gives you 32Mbit bitrate with some spikes up to 34Mbit.

For 720p60 actual bitrate can be slightly lower (I get 27Mbit at b) ).

Top bitrate and best settings will be found by testers later.
Possibility is it can be as high as MJPEG top bitrate for FullHD mode.

Q: Such high bitrate clips are playable on camera?
A: Yes, no problems during my limited testing. All plays fine.
 
My battery is on charge, have to give this one a go. Tester13 you are incredibe if you solve this, thank you for keeping the faith with avc.
 
Adjustable bitrate AVCHD? Playback in camera? This is awesome news. Wish I was at home rather than at work so I could try this right now.

I hope everyone who is so far benefiting from these updates is also donating :).
 
PTool 3.35 released

Limiting bitrate patch added. Now you can adjust AVCHD bitrate (with use of other three patches that we have already).

Tested settings:

Code:
Video buffer                 - a) 33.500.000 b) 40.000.000
Video bitrate adjustment     - a) 22.000.000 b) 32.000.000
Overall bitrate adjustment   - a) 24.000.000 b) 35.000.000
Limiting bitrate adjustment  - a) 26.000.000 b) 40.000.000

a) Gives you 22Mbit bitrate with some spikes up to 24Mbit.
b) Gives you 32Mbit bitrate with some spikes up to 34Mbit.

For 720p60 actual bitrate can be slightly lower (I get 27Mbit at b) ).

Top bitrate and best settings will be found by testers later.
Possibility is it can be as high as MJPEG top bitrate for FullHD mode.

Q: Such high bitrate clips are playable on camera?
A: Yes, no problems during my limited testing. All plays fine.

I confirm. MUD free image with b settings !!!
I'll upload the test footage in a moment...

update:
download link:
http://www.nikolicnemanja.com/test4.rar
I started panning after 5 second of the footage...
 
Last edited:
Back
Top