@Vitaliy_Kiselev With PTool 3.61, Kae's 65Mbit settings did span right? I wonder what differences were made since @CBrandin's 44Mbit/66Mbit settings do not span. The bitrate is the same... does it have to do with Quantizer settings or where any other changes made to PTool that could influence this? Should there be a team to research this?
@gerondo, I only using a class 10 intergrale 23 megabytes a second. It seems to work fine no crashes just the span thing. I get conflicting infomation about whether SDXC cards will slove the span problem. I phoned Panasonic about compatibility of the SDXC cards and they said you should have no problems with the 4GB limit if you use a SDXC card. So lol......It maybe Ptools that needs a new feature or the type of card makes differnce.
Anyway we doing well to get this far so at least we got great settings to play with.
All my settings are proven stable video buffers maximising bandwidth. ANY crashes now are down to the camera settings (ISO/shutter speed). Even on a crash many of my settings still write a file - and the buffers (using Elecard buffer analysis) still look great - not dives into zero land. The crashes tend to happen on extreme limits. If you take my 220M AQ2 GOP1 example - the buffers are virtually constant. They resolve amazing IQ. For certain shots especially in darkness with a little light, its bloody amazing. But if you want extreme detail on say bushes/trees of death eventually the write to the sd card will stop. There are absolutely NO buffer underruns or overruns. period. The graphs look good - nice stable waves - no zero drops.
Its now down to taming the i frames at extreme detail. So in a way, I am working in a backwards principle to @cbrandin, Chris is working from bottom settings upwards with precision adjustments of Frame buffers and limits etc... to achieve top quality with stability, I am coming from the other end - to achieve maximised use of the available buffers and then to try and harnass the memory bandwidth given to i frames to achieve stability. So far we have reached peak bandwidth - we now need to adjust some of the other settings to pull it back down under high shutter/ISO etc.
I guess it wont be long before our settings meet in the middle somewhere... either way we need more testing of these found settings and to adjust (fine tune) them accordingly. Please experiment.
PS My 132M GOP3 AQ2 should NOT crash at all. Other settings I have posted below you can experiment changing AQ4 to AQ2 - and you should more stable success at higher detail objects/movement. I have stable buffers and excellent resolving IQ on GOP 3, 6 and 12 higher than 132M. These are brilliant for filmmakers but perhaps not so good for regular GH2 users who simply need to span files for documentary / long recordings etc.. ;-)
@driftwood - sounds good too me, the only setting it refuses to write to the card is 720p but thats because of the (all to detail setting), so my card is just not fast enough but orderd a faster one so fingers crossed.
chrimsbroome, The 4GB limit has nothing to do with the memory card. It is how the FAT (file allocation table) is defined for how the GH2 writes and reads from the memory card.
The GH2 uses FAT32 Like I mentioned in my earlier post. Do the math, FAT32 is capable of > 2^32 (power)=~ 4GB.
Since the hack involves additional processing increase, the GH2 with the increase demand from the hack on higher datarate may have a bottleneck due to either hardware, or how the code is written. Like Vitaliy mentioned above, he has not determined if this span issue is a hardware limited issue and "is very complicated and very slow to test".
On a stock GH2, on long video takes, when the file sizes gets larger than 4GB, it automaticaly creates another sequential file (up to 4GB) until your card is full. So if you were to record non-stop on a 16GB SDHC card you should have four 4GB files on the card before it's full.
On a long recording, If you're using settings with the hack great than 32Mb/s, just remember to stop your recording before it uses 4GB on the card, then restart it back up and continue recording.
@driftwood I have tested your "beautiful buffers" settings in 720/50p, so PAL, and with 56 and 55 in Video Bitrate FSH/SH the cards stop after 2 seconds and I have to pull the battery. I tested it with a Panasonic Class 10 16GB and a Sandic Extreme 16GB 30Mbit/s card, but both show the same behaviour.
I understand that you have not issued a PAL setting, but just to let you know.
Driftwood, Thanks again for your strive to find the highest stable possible from the GH2 using Vitaliy's current 3.62d.
Another approach, which I believe you're heading to now, is to crank the ISO to MAX (3200), increase the shutter speed to max, and shoot high detail such as Papas Death Chart (and other high detail footage).
Now, you could use the above settings as your reference, start at your highest bitrate settings and work down until it's stable. Then, maybe drop it down a bit more from there so we're not "hanging on the edge" of just working.
132Mb/s / 8 = 16.5MB/s ; therefore 16.5MB/s x 60 (seconds) = 990MB per minute. So, to play it safe you could keep your shots at 4 minutes or less.
But, even at 132Mb/s does not mean you will be averaging 132Mb/s all the time (of course). It depends on how hard you're working the datarate with higher detail (also higher ISO leads to more detail image: noise) and motion. So, you may be safe with 5 minute cuts with no issues. But, to play it real safe, keep it to 4 minute takes using 132Mb/s.
@driftwood, thanks- yes I understand about the Fat32 table. Do you think that GH2 can format a SDXC memory card to a exfat table spec or is it only restricted too fat32? spec. Because if Panasonic say a SDXC card will work in it (as it is stamped on the side of the camera). Then practically speaking the limit thing should be solved but I dont have a SDXC card to test the span issue.
@driftwood , Your settings 132Mbits 3GOP operate flawlessly for me. Recently I gelled on the lakes and I had no suspension of work with the camera settings on the card Transcend 32GB Class 10 and Class 10 Toshiba 16GB. Horny!
Extreme 6 GOP filmmakers setting: This is 100% stable buffer, ie it will only crash on extreme detail though ive had it thru pappas/trees of death for longer than 30 seconds static. AQ1 is better at longer recordings than AQ2. Both present wonderful IQ. This just shows what the GH2 can do. 1st Chart = Pappas + buffer analysis, 2nd chart = Shot inside house. PS They should playback in camera ;-)
220M 6 GOP AQ1 or AQ2 Extreme IQ - 152 065 024 bit buffer gives you nearly 108M on Pappas!.png
1676 x 690 - 58K
220M 6 GOP AQ1 or AQ2 Extreme IQ - 152 065 024 bit buffer gives you nearly 108M on Pappas - streamparser.png
1295 x 682 - 87K
Driftwood 220M GOP 6 Extreme setting - setc.zip
423B
220M 6 GOP AQ1 or AQ2 Extreme IQ - 152 065 024 bit buffer gives you nearly 108M SHOOTING IN ROOM - streamparser.png
I tested @driftwood today a lot filming cars and some landscape. God, what beautiful details I could get! The camera just "crashed" two times, using 720p with the shutter in 1/125. I used the Sandisk Extreme 35mb/s and, as I was with a t2i with magic lantern using the Pro 45mb/s card, I tried it too. Using the Pro, the same 720p settings did not crash even once, BUT, when I returned the 35mbs card to the camera, it did not crash too. So I could not reproduce the 2 crashes again. I don't know if it was because the the light changing of the day or something else I did. I'll install this last one right now in the camera and shoot tomorrow again. I'm with two cams, so I can get the GH2 just for testing! I can't thank you all enought for doing such a great job!
@paglez - well thats a let down Panasonic whats the point in haveing a SDXC compatible camera and it only use Fat32 spec. Well we a going to have to sort that one out.
@driftwood tested your extreme 6 gop filmmakers setting (posted today) in a low light setting with lot of blacks and some very fine details (white vitrage) and it looks unbelievably beautiful!! No noise or artifacts whatsoever. Did not see anything like this before. Wow! Thanks!
I think 132mbit is the max bitrate I will use. I transcode everything to ProRes 422... which has a avg. bitrate of 120mbit for 1920x1080 23.98fps. So that way, the harddisk space required stays about the same which gives me a very efficient workflow. SD cards are cheap enough to work with this. Keep up the good work @Driftwood
@driftwood GOP 6 is the sweet setting for me when it comes to fast motion but theres no way I'm trying your 220M setting, I may love it too much and then have to spend a load of cash on SD cards. I'll stick with bkmcwd's 66M GOP 6 for now. I am going to give that 220M GOP 1 a spin though, just to see it.
Edit The 220M GOP 6, does it always produce P-Frames the same size as I-Frames on static detail ? Or is that just a deathchart phenomena ? In fact its really odd that the ratio between I, B and P frames is like that on the deathchart to me, it looks wasteful.
@Stray Death chart phenomena. Look at the other chart - normal recording. 6 GOP looking good - I can't tell the difference between this and hdmi. Ive just been analysing my gig shots from tonight using this setting and checked image & lighting quality against stills on a Canon 7D and you could barely notice the difference at 320-3200 iso. Shadows and highlights seem much purer... love it :-)