GH1 firmware research volunteers required

That 24P in MJPEG is looking promising! If you want to send me a link to an original MJPEG file I can throw it up on vimeo so people can download native quality. Keep it up. :beer:
 
And new test:

VA 720p GOP Size: 26 -> 11 ( All right - Bits/(Pixel*Frame) : 0.333, Video Bit rate : 15.3 Mbps )
VA 1080p GOP Size: 13 -> 11 ( All right -Bits/(Pixel*Frame) : 0.333, Video Bit rate : 17.3 Mbps )

It's incredible news!!!! video bit rate up more 16.6 Mbps!!!


General
ID : 0
Complete name : E:\PRIVATE\AVCHD\BDMV\STREAM\00020.MTS
Format : BDAV
Format/Info : Blu-ray Video
File size : 135 MiB
Duration : 1mn 1s
Overall bit rate : 18.3 Mbps
Maximum Overall bit rate : 21.0 Mbps

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.0
Format settings, CABAC : No
Format settings, ReFrames : 2 frames
Duration : 1mn 0s
Bit rate mode : Variable
Bit rate : 17.3 Mbps
Maximum bit rate : 16.6 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 fps
Standard : NTSC
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Interlaced
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.333
Stream size : 125 MiB (93%)
 
I think the MJPEG is still jerky. If you scrub through frame by frame it looks like every fourth frame is jumping. Anyone else seeing that?
 
And new test:

VA 720p GOP Size: 26 -> 11 ( All right - Bits/(Pixel*Frame) : 0.333, Video Bit rate : 15.3 Mbps )
VA 1080p GOP Size: 13 -> 11 ( All right -Bits/(Pixel*Frame) : 0.333, Video Bit rate : 17.3 Mbps )

It's incredible news!!!! video bit rate up more 16.6 Mbps!!!

Have you done a quick pan test to see if the mud is improved?
 
I think the MJPEG is still jerky. If you scrub through frame by frame it looks like every fourth frame is jumping. Anyone else seeing that?

I believe that I know how to fix that (but may be I am wrong here).
But first we can get reports from NURBS about private version testing.
 
NURBS file is reading as 24p in Cinema Tools analysis pane, not 23.97p. Which one do we want?
 
If you can, please download and look this MJPEG on Cinema Tools, my NLE on this time on the modding process :-)

Media info said that:

Video
ID : 1
Format : M-JPEG
Codec ID : jpeg
Duration : 1mn 0s
Bit rate mode : Variable
Bit rate : 12.9 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 fps
Bits/(Pixel*Frame) : 0.583
Stream size : 93.0 MiB (96%)
Language : English
Encoded date : UTC 2010-04-27 19:11:35
Tagged date : UTC 2010-04-27 19:11:35
 
NURBS file is reading as 24p in Cinema Tools analysis pane, not 23.97p. Which one do we want?


It is my opinion that 23.97 is used only in AVCHD encoder.
Native sensor FPS is 24,50,60.
MJPEG can't be set to 23,97 also, only 24p
One of the mud reasons can be some kind of frame conversion during encoding, so it is worth to try making 60.00 instead of 59,94.
 
24 converted to 23.97 is an easy fix. Can do that easily in cinematools. Just getting the 24P cadence right plus defeating AGC would be huge.
 
Tested and confirmed, the file still skip one frame AFTER 4 frames.
With v 3.07, Mjpeg Patch.

Confirming that the bitrate change with the audio if that wasn't confirmed.
 
Tested and confirmed, the file still skip one frame AFTER 4 frames.
With v 3.07, Mjpeg Patch.
Confirming that the bitrate change with the audio if that wasn't confirmed.


OK, understood.
We need time to understand this mode clearly.
Do you want to say wht it actually shoots at 30fps and drops one frame after each 4 frames making it 24fps?
 
PTool 3.08 released

MJPEG patch completely rewritten, as we moved to much higher level this time.

To conclude current day:

Few working patches added - especially GOP adjustment is useful. Mud must be less with large GOP values. But top barrier on P frame size can also cause mud.
Audio encoding bitrate is also useful.
Most time was spend on MJPEG and few AVCHD encoders details reversing. We are still only at the beginning stages.
Hope that new MJPEG patch will be better.
 
Last edited:
I thought GOP length didn't have anything to do with filesize or overall quality and that only the structure of I/P/B files that constitute the quality? Do we see any way to control which frames are used in the firmware?

Do we know the exact GOP structure used in the AVCHD files and MJPEG files from the GH1?
 
Back
Top