Pro: GH2 AVCHD encoder settings

EOSHD

Encoder 4 setting, set to 8, prevents crashing or hangs when 1080i set to 50p progressive mode in PTools. The corrupt AVCHD MTS file results but the camera functions normally and outputs to HDMI whilst recording, with perfect image at 50fps.

swen24

Encoder setting 1 enables B frames, 0010 off/0011 on.
Encoder setting 2 is same for 720p/1080p 0100 but 0110 for 1080i
Encoder setting 3 is 0100 for 720p/1080p and 1000 for 1080i

so we can try to set with 50/60p enabled 1080i setting1 to 3, setting2 to 3 and setting3 to 4.

daidalos

@sven24: 0001 0111 =39
..and
0000 0010 = 2
0000 0011 = 3
therefore first bit right is b-frame ? <-YES, it is - swen24 brilliant idea!<br />list continued:
0000 0100 =4
0000 0110 =6
0000 1000 =8
0000 1001 =9
0001 0001= 17

1080i has b-frames =encoder setting1 for 1080i/p =3, therefore suggest encoder setting 2-4 do NOT define b-frames

swen24

If You take a look at "PTool 3.60D: Encoder Setting 1 controls B-Frames" thread, i think it's the first bit. Don't know what the second does...

daidalos

YES, you´re right! i would not ask, i confirm

EOSHD

Tested:
1080i/p Encoder 1 = 3 (b-frames on)
1080i Encoder 2 = 3
1080i Encoder 3 = 4
1080i Encoder 4 = 8 (changed from default 17)
Progressive patch applied for 1080/50p, PAL

Results:
- 1080/50p FSH results in Card Speed Error when HDMI monitor is not connected, hangs (battery pull resets)
- With HDMI monitor connected, different result - recording starts and stops successfully, L/V and HDMI video feed is OK, but resulting AVCHD file is garbage both in VLC Player and when played back in-camera

daidalos

try encoder4 setting = 12 = b0000 1100 what happens, maybe we can isolate bit 3+4
=addition of 4 and 8
or:
if default=17, the alternate for non-crashing = bit 3 or bit 4 on -maybe
therefore 0001 0101 = 21 - bit 3 on , bit 4 off
or 0001 1001 = 25 - bit 3 off, bit 4 on

swen24

I think the problem is my bad english, set 2-4 have nothing to do with B-frames, of course.

daidalos

no probem,we have the same way

daidalos

..in meantime 720p60 - 56Mbit think stabled, but needs other tests and testers, poor B-frames are now better "higher-leveled" , buts its late for me to publication, comes next 24hs.
Footage looks good with high details and heavy panning, but not checked parameters enough for influence to 1080p, think little degration

EOSHD

Setting 4 = 12. Result - no change to output or behaviour of camera.

daidalos

OK, maybe chance with ES4 to 21 (bit 3 on) or ES4 to 25 (bit4 on)
third is bit3+bit4 on by outgoing point of 17 , then ES4 has to be 29 = b 0001 1101 , these means stability needs bit5, if success or thinking failure? but you reported 8 (= bit 4 on for preventing crashing), sorry, must end - too tired...

EOSHD

Must sleep now. Back tomorrow evening. Thanks for help guys. Someone else please test @daidalos settings :)

swen24

First thing i did after Vitalis Patch arrived, was to set 1080i bitrate to the same values as at 1080p24 including Buffer. The result was a higher bitrate in I (up to 28kbps) frames and B frames (700bps), but lower bitrate in P frames (9kbps). The result was much more better than "out of the Box" (Child playing in grass). I tried some higher values, but i get always artefacts starting at 28mbps, I frames are smaller then P Frames and something like that.
The average Bitrate is only slightly higher, but the Quality is much better (mud in grass).

swen24

@daidalos
29 doen`t work, same cardspeed error. trying to find some sleep

exhardy

There's one thing that I've noticed that if the 14-140 hd lens is attached to the GH2 which with 1080p50 patch enabled...
it will pop the card speed warning but once I use some manual lens it records normally but still a garbage avchd output.
so I think that the warning might also indicate In-camera lens correction is not fast enough.

Dazza

That makes sense, the in-camera lens correction will take processing cycles from the Venus Engine, so with a manual lens you would have more available CPU power.

daidalos

little news, tested with 720p60 56MBit : ES4 set to 29 (0001 1101): initializing with 1080i also OK (helps to do a init step less) , can review footage, seems stably, clear picture on footage -but others may see other things-
first 6-21 frame-rates are low, then stable high
a 1080i/p tester should also set E4 to 29 and look, whether the same appears
additional: 1080i footage is "pulsing" after a while at high details, but doesn´t crash, used card class10

daidalos

set ES4 for 1080i to 29: pulsing has gone, clear, heavy panning at high details ok, GOPSize 15, next test 30
for 720p60: clear with a little more 3D imagination (for me - good), crisp

hakimovruslan

@daidalos
can upload picture you full setting ?very interesting
thx

APXmusic

Do the MJPEG settings apply to 1080 24p? Has there been a successful high bitrate video made with that different codec?

cinegraphy

Hi there, someone on Vimeo asked me to upload my settings somewhere, so I suppose this is a good place :-)

It's a combination of several settings:
- 720p Mpeg high profile (developed by modulr)
- Avchd 720p50 short gop / B-frame settings, by mpgxsvcd (that is, the ones he posted about 2 days ago here)
- 30 min. limit removal
- Pal <-> NTSC

Aha - unfortunately uploading files never seems to work here (at leat in my case); is there any known incompatibility with Safari?

cinegraphy

Ok, finally works - looked in firewall settings etc., but it was some safari-problem, in my case...

daidalos

@hakivomruslan: wait a little, test series not yet finished, try to stabilize settings for all modes

daidalos

have settings now - stably i think on all modes - with 56Mbit on 720p modes - effective 32-46 MBit rates. MJPEG on 32MBit, 720p modes with a little 3D-touch as far as my eyes look right, work on testing impact to 24p and 1080i

Howdy, Stranger!

Categories

Tags in Topic

Top Posters