Personal View site logo
Make sure to join PV on Telegram or Facebook! Perfect to keep up with community on your smartphone.
GF2 Stable Settings
  • 614 Replies sorted by
  • Thank's VK for Greate Help

  • 44mbit and GOP-1 seems to be working for me as well with a short test clip. I'm going to go out later today and shoot a bunch of footage to see how it comes out.

    For some reason it shows one P-frame stuck in there. Not sure why?

    I am using a Class 6 20mb/s Sandisk Ultra card.

    [Information] Comment=44-32-GOP1SD_Card=Any Camera=GF2 v1.12 [Settings] Version increment=1 Video Bitrate FSH/SH=44000000 Video Bitrate FH/H=32000000 720p60 GOP Size=1 1080i60 GOP Size=1

    44-1080-GOP1.png
    1290 x 686 - 166K
  • I got @stonebat settings to work, i was able to get 20mbps in a low detailed scene.

  • Good. Go out and press record button :)

    Another frame capture. I'm liking hacked GF2. Is it just me? I like the color and overall feel.

    00022_Feb 19, 2012 3.08.48 PM.png
    1920 x 1080 - 3M
  • Overall looks good, although I am seeing distortion (not sure if it's the right term) between the first two (on the top bar) wheels. With my test I am getting better bitrate with shutter priority than manual. Having said the bitrates have been in-consistent usually between 18 and 27.

    Capture11.PNG
    1827 x 926 - 3M
    Unt.png
    1920 x 1080 - 2M
  • Ha. Nice texture of salts and peppers on french fries. Yummy yummy.

    00030_Feb 19, 2012 3.47.06 PM.png
    1920 x 1080 - 3M
  • This is kinda footages that tickle my nose hair to do color grading.

    Hacked GF2 FTW!!!!

    00025_Feb 19, 2012 3.49.17 PM.png
    1920 x 1080 - 2M
  • @stonebat that's cruel guv, I am hungry now...

  • @stonebat which lens are you using to test btw?

  • x14-42. Power OIS works great at 1/60 shutter speed.

  • Prolly keeping AQ setting to 3 or 4 or equivalent custom quantizer number is a good idea.

    Finding a stable setting for low GOP & quantization & bitrate is like a crapshoot. We have in-house specialists like @cbrandin, @lpowell, @driftwood, etc.

    Simply I copied 1080i60 settings from @cbrandin's 44Mbps AQ4 patch. For those who need settings for 1080i50, look into the 44Mbps patch.

  • Stonebat, really nice tests. Could you show some videos? What is possible with the gf2? Any limitation against a gh2? Thank you!

  • Since 1080p30 is wrapped in 1080i60, it would need to be exported to 1080p30. Let's wait for the next PTool to remove the wrapper.

    GF2 limitation? Read the manual :)

  • Stonebat, i ordered the GF2, so i havent one to test; i mean is it possible to get gh1 quality with this little baby? Thanx

  • Frankly I don't know. I don't have GH13.

  • I went out today and used these settings Video bitrate FSH/SH: 40000000 Video bitrate FH/H:32000000 AQ for 1080:3 AQ for 720:3 I left the video buffer at 1800000 and didn't change anything else. With 1080i60 i averaged 40-42 mbps in most clips and with 72030p i averaged 33 mbps with each clip. It was steady for me with 72030p but the 1080i60 worked 85% of the time. Sometimes i would get the write speed error right away but other clips with same settings in the same area i could record and it would be fine. With this patch i mostly recommend using 72030p and the screen grab is 72030p. If you guys want me to try anything else specific with this patch let me know.

    Capture3.JPG
    638 x 361 - 67K
  • comment removed ^^

  • sorry for my mistake, i have edited my post.

  • My gut feeling is that.... lower AQ setting is worth for much higher bitrate. e.g. AQ3 for 66Mbps.

    Let's try to find the best stable setting for AQ4 and default-GOP. It will be a good benchmark for all future patches, and it will entice many GF2 users who have never tried firmware hack.

    I'm afraid that unstable lower GOP or higher bitrate might drive away hacked GF2 newbies.

  • Sorry, but I VERY new to this. I just uploaded @stonebat setting file onto my GF2. How can I start testing and see the newly added settings on my camera? Again, sorry for this beginners question. Thanks.

  • @vsynryco You gotta learn how to use @cbraindin's GH13 Stream Parser.

    Check out http://www.personal-view.com/talks/discussion/443/basic-and-beginner-questions for beginner questions.

    For advanced setting, Elecard Stream Analyser is prolly a-must learn tool. I don't know much about the tool. Only a few forum users have gone that far. I'm just waiting for the patch experts join in.

  • I tried Stonebat's http://www.personal-view.com/talks/uploads/FileUpload/31/a704042df61efe4abc3c1502f2cb79.ini from the first post with an adapted manualprime lens (no af). Stable at 720p from what I can tell, but doesn't last long @ 1080 with the test pattern before ""Motion recording was cancelled due to the write limitation of the writing speed of the card". Tried a few other settings and couldn't get 1080 and aq4 to be stable. When I go back to AQ0 I can't seem to dupe that error message regardless of bitrate. I suspect the limitation is not write speed on the card, but processing power required for that aq setting.

    Card PNY Class 10 "20MB/s"

  • Strange. I'm using Transcend 16GB Class 6. No error for me.

    Did you format the card? Also use the latest PTool.

    Changing from AQ4 to AQ0 will lower the image quality.

    Edit: I'm using SanDisk Extream 16GB Class10 30MB/s.

  • Yes, in fact since I started seeing the card read errors I just format the card as soon as the version up is completed every time. Ptool version is 200212.
    It's pretty quick to dupe the error if I pan or move the camera much while focused on http://www.personal-view.com/talks/uploads/FileUpload/f7/ca41bdbaa05bd518133efbee3e0d13.png

    edit: just tested with 1080p AQ4 set but all other settings unchecked, and could not get an error.. That's good to know that in my case AQ4 only became unstable at higher bitrate.

    edit: tested again with Video Bitrate FSH/SH=60000000, Auto Quantizer for 1080 modes=0 - All to motion and short test clip has 58026kbps bitrate, no errors.. To me it's further evidence that the previous errors not caused by card write speed despite the text in the error