EDIT: Now that PTool 3.62d supports MJPEG frame widths greater than 1920 pixels wide, the GH2 can be patched to support 2x anamorphic adapters natively in 4:3 VGA video mode. For 1.33X anamorphic adapters, HD mode provides native support as well. Videos shot in the following anamorphic frame sizes with the appropriate anamorphic lenses will be played back at the correct aspect ratio, and will not require post-production stretching:

HD 720p mode:
1.33x aspect ratio: 1920x810

VGA 480p mode:
2.0x aspect ratio: 2160x810

Standard non-anamorphic modes:

HD 720p mode:
1.0x aspect ratio: 1920x1080

VGA 480p mode:
1.0x aspect ratio: 960x720

EDIT: see post above for recommended standard and anamorphic MJPEG frame sizes.

@Vitaliy

For this test can we vary Q and T or just T?

http://www.personal-view.com/talks/discussion/666/ptool-v3.62d-topic

Vitaliy_Kiselev
>Most users do not have any anamorphic lenses at all.
thank you
most users want no anamorphic lenses ;)

Thank you M-Team!

Using the settings below produced the highest completely stable bit rates for 1080p that I could get(bit rate was just over 90+ mb/sec). There is no in camera playback with these settings of course.

Q1-Q4 = 600,500,400,300
T1-T4 = 4,12,24,32

If anyone can get these settings to produce a write failure please let us know.

Cool Stuff LPowell. I didn't know about using E4 = 4. Was this testing done with the GH1 or the GH2?

so E4 table was good at 4. What about E1 table E2 table E3 tables? Should we use LPOWELL's tables with PMGXSVCD's Qualities?

@ishvar
This is strike team topic, not MJPEG questions topic.

Is anyone else messing around with mpgxsvcd's setting's with 3.62?

Q1-Q4 = 600,500,400,300
T1-T4 = 12,24,32,4

If not, please do try! Incredible.

@mpgxsvcd Thanks for reporting the results of your testing. Perceived resolution will always be a limited by the optical resolution of the lens filtered through the camera's optical low pass filter (OLPF) and then digitized and downsampled from the image sensor. While we don't have resolution measurements for the GH2, the BBC has tested the AF100 and concluded that its effective resolution is about 750 lines. If we assume the GH2 performs similarly, this 750-line optical resolution will set a limit on the perceivable resolution of higher digitized resolutions.

In most cases, it's preferable to resample an image to the desired resolution after all post-processing has been done to the image in its original resolution. However, in this case, the MJPEG encoder degrades the precision of the color data in the process of converting it from RAW 12-bit RGB data into 8-bit YCC in 4:2:0 color depth. For that reason, it is preferable to program the camera to scale the image to the desired resolution before it is degraded by the MJPEG encoder. While the difference in image quality may not be readily perceivable in most cases, as long as the encoder has adequate bitrate to encode the image at high quality, it will in no case be worse.

As you've determined, however, SD card write-speed issues impose a limit on the maximum bitrate that can be made available to the MJPEG encoder. With the GH1, I found that high vertical resolutions (up to 1080) were less stable than high horizontal resolutions (up to 1920). If this is also the case with the GH2, it may turn out that MJPEG resolutions higher than 1920x1080 are primarily useful for producing horizontally stretched aspect ratios for use with anamorphic adapters.

Here is a sample video that shows 720p slow motion along with 1 clip of 4mp 40 FPS. The 4:3 clip is obviously the still image clip. I rendered the video to 1080p and the stills clips really don't look that much better than the 720p clips. I bet that would change if I rendered to 4K instead. I don't have an editor that can do that though.