@Angry_C

I think the time mode is not accounting for the full bit rate from the I,P, and B frames. The settings I am using appear to allocate much more bandwidth to the I and P frames than it does to the B frames which appears to be the only thing displayed in the time mode.

You can check the file sizes for the exact same scene recorded with 24p and 720p. The 720p files are much larger and have MUCH less compression artifacts despite their large GOP(30 vs. 12). Those bits have to be going somewhere.

@Angry_C

The max bit rate reported by stream parser is just a number. Look at the average bit rate value and the file size and you will see that the average bit rate far exceeds the value stated for max bit rate for Stream Parser. Stream Parser is just not giving the correct value for max bit rate. The average bit rate is accurate though.

@EOSHD Are you able to record the HDMI information from your camera? (HDMI intensity-Ninja? 6-Pack of beer given to video guy at local shop that has Ninja?) In an attempt to discover if the HDMI output has the same issues as previously noticed?)

@mpgxsvcd that is how I started the test. Same results.

@EOSHD

Don't change any of the other settings. Just check the 1080i to 1080p setting. Leave everything else unchecked.

HDMI mode was 1080/i, and image was fine on both LCD and SmallHD whilst recording.

It appears as if without HDMI monitor connected the GH2's LCD shows encoded footage (garbled) whilst with HDMI connected it is a different 1080/i feed that is shown on both screens, whilst AVCHD encoder gets the garbled information as normal.

To view settings I am using: http://www.eoshd.com/uploads/gh2hack/sete.ini

Until now I got the Memory Card error every time attempting 1080/50p, various settings tried, corruption in live view when record button activated - but then I plugged in a HDMI monitor (SmallHD DP6), hit record and the GH2 entered record mode fine, both the HDMI output and live view did not have the corruption of before, but unfortunately the AVCHD file recorded was corrupt with the half pixilation and half heavy macro blocking, weird corruption, etc. others have also reported.

Here is analysis of my corrupt 1080/50p MTS file. Bitrate seems far too low to support 60p, so need to change that.

Stream: Max Speed = 18,382,980 bps
Mode = 1080/50pN
PCR Timing Interval = 0.095 seconds
Clip Time = 0:00:11.54
Average Total Bitrate = 11,402,070
Average Video Bitrate = 10,759,986
Average Audio Bitrate = 235,896
Average Other Bitrate = 406,189
Max GOP Size = 1,165,248 Bytes (9,321,984 bits)
Video Frame Size (Min/Ave/Max)= 7,680 / 27,445 / 373,440

Notice size of first few frames in attached StreamParser GIF!

mpgxsvcd settings

Has anyone had a play around with the "1080 progressive" or "1080i59,97 --> 59,97p" patches yet?

First time you use them it freezes the camera, giving the "Memory card is too slow" message. But if you eject the battery and bootup again you can record just fine. Problem is that the video output is all garbled, top half of the frame is very pixelated and the bottom half has massive corruption with bright colours flashing all over the place and large horizontal bars of green and magenta scrolling upwards. Any ideas?

Absolutely fantastic. 28mb with b-frames completely kills the nasty motion artifact macro blocking of 720p mode.


Will post vimeo link after it gets done encoding so you can download. On youtube, watch in original quality for best viewing purposes
http://vimeo.com/download/video:57960995?v=2&e=1310089958&h=27003d303b6a523c37bdc3907387dce1&uh=55e53dc2505925abe86dea6433610fc1

I wonder if doing 24H first runs some kind of setup routine that is then re-used for any subsequent recordings..

@LPowell

Yes it can glitch. In fact if you look at deprecated topic you linked I started whole thing about problems.
But I think that talking about glitches in current context do not have any value.

Yes, StreamParser can glitch with unknown formats (in the time of development).