GF1 100mb/s footage acheived!!!

Any more luck with stable settings?
I have reverted back to my original settings of Q545,500,455,410 T24

stability sure is prooving to be tricky lol

one thing you could try with Q545,500,455,410 is setting the table settings back to the factory ones

i'm starting to think that to get 100 percent stable settings the following has to be true:
if the top bitrate is as much as 106mbits, then the table settings have to be very high meaning the bottom bitrate is very low, even as low as 18mbits.

so far i have had some luck with very high table rates with all set to 400, but i dont think these are really that useful, because of the massive bitrate lattitude. has anyone found any thing different?

at the moment, i am really testing the hell out of 400 24, to see if it really is stable once the 'switch on-error once' has occurred. if this is the only problem with it, then that is extremely livable with!!! :2vrolijk_08:
 
in fact, does anyone know of any reason (moire, resolution, etc) the GF1 100mbit 422 footage would not pass broadcast standards as main camera footage, if for example i wanted to make an underwater documentary using gf1s in housings?

Unfortunately, I believe there are couple of situations when I personally wouldn't accept it.

For example:

I shot this with 81Mbit and chroma just fell apart where I had lot's of low-contrast dark-green details. All the bits went into encoding hi-frequency flower chaos and there was just no data left to encode leaves.
Granted, this is probably worst-case scenario (lot's of chroma-intensive random detail, hi contrast) . AVCHD fared better (despite 1080p and roughly half bitrate). Using 4:2:2 would probably make things even worse and push the bitrate above upper limit.

I still believe that MJPEG should be used as special purposes one-trick pony only (low-light, chroma-keying, soft-focus etc.) AVCHD is just plain better as soon as there is lot's of details in the image. 30p is quite unusable in PAL-countries as well and 25p just frame-skips.

Settings:
MJPEG E1 Q: 280
MJPEG E1 T: 14
MJPEG E2 Q: 226
MJPEG E2 T: 14
MJPEG E3 Q: 200
MJPEG E3 T: 14
MJPEG E4 Q: 170
MJPEG E4 T: 14

4:2:2 unchecked.

Average bitrate: 81Mbps

81Mbit_MJPEG_frame.jpg
 
Last edited:
I shot this with 81Mbit and chroma just fell apart where I had lot's of low-contrast dark-green details. All the bits went into encoding hi-frequency flower chaos and there was just no data left to encode leaves.
It's really worst-case scenario (lot's of chroma-intensive random detail, hi contrast) . AVCHD fared better (despite 1080p and roughly half bitrate). Using 4:2:2 would probably make things even and push the bitrate above upper limit.

I still believe that MJPEG should be used for special purposes only (low-light, chroma-keying, soft-focus etc.) AVCHD is just plain better as soon as there is lot's of details in the image. 30p is quite unusable in PAL-countries as well and 25p just frame-skips.

Settings:
MJPEG E1 Q: 280
MJPEG E1 T: 14
MJPEG E2 Q: 226
MJPEG E2 T: 14
MJPEG E3 Q: 200
MJPEG E3 T: 14
MJPEG E4 Q: 170
MJPEG E4 T: 14

4:2:2 unchecked.

Average bitrate: 81Mbps

Do you have a sample picture from the AVC-HD file? Even your MJPEG sample looks better than just about any other camera video I have seen though.
 
Do you have a sample picture from the AVC-HD file? Even your MJPEG sample looks better than just about any other camera video I have seen though.


Left: AVCHD @ 35Mbit sec, 1080p25 scaled down to 1280x720 (we have to compare apples to apples)
Right: MJPEG @ 81Mbit sec, 1280x720 native.

avchdvsmjpeg.jpg
 
Left: AVCHD @ 35Mbit sec, 1080p25 scaled down to 1280x720 (we have to compare apples to apples)
Right: MJPEG @ 81Mbit sec, 1280x720 native.

avchdvsmjpeg.jpg

Excellent comparison. I just hope that they get the 1080p @ 24 fps working for the GF1 soon.
 
I shot this with 81Mbit and chroma just fell apart where I had lot's of low-contrast dark-green details. All the bits went into encoding hi-frequency flower chaos and there was just no data left to encode leaves.
Granted, this is probably worst-case scenario (lot's of chroma-intensive random detail, hi contrast) . AVCHD fared better (despite 1080p and roughly half bitrate). Using 4:2:2 would probably make things even worse and push the bitrate above upper limit.


4:2:2 unchecked.

Average bitrate: 81Mbps

it is difficult to compare the two codecs, without and with 4:2:2 as without 4:2:2, the color will fall apart massively, hence why we are keen to use 4:2:2 :)
 
Last edited:
it is difficult to compare the two codecs, without and with 4:2:2 as without 4:2:2, the color will fall apart massively, hence why we are keen to use 4:2:2 :)

It this kind of situations, 4:2:2 would just make thing worse. There would be even less bits available to encode luma details.
 
Grunf. How did you manage to get 1080p25 on AVCHD in your GF1 ? Mine only does 720p25
What settings do you use ?
 
Grunf. How did you manage to get 1080p25 on AVCHD in your GF1 ? Mine only does 720p25
What settings do you use ?

Are you sure you have enabled "FHD" and "AVCHD" in camera and Native "24p/25p" in Firmware patch? What's preventing you to get 1080p? Do you get card write errors?
 
Are you sure you have enabled "FHD" and "AVCHD" in camera and Native "24p/25p" in Firmware patch? What's preventing you to get 1080p? Do you get card write errors?

There is no 1080p AVCHD on GF1...GH1 Yes...GF1 no...not yet anyways :-)
 
I have a GF1 in the mail on it's way... If I just want the best 720p output (not interested in 1080 as my 5Dmk2 does that just fine), what settings should I be doing on the GF1? I often color grade in magic bullet looks. Thanks!
 
canuck88, it seems that you can use anyone of the higher bitrate settings (adammada's, mike797, papasarts, etc), as they all will record fine once your have tripped the write error, so long as you have a class 10 card

my current settings are '400 10'
follow the settings on my vimeo link below but set all q to 400 and all t to 10
http://www.vimeo.com/12918955
 
Last edited:
Back
Top