@Botvinic did you check for artefacts on 720p ver2? can you also try 1080i50 too? I'll keep messing with settings. Damn trees... Why does everyone wanna slowmo trees all the time... TREEES... down on my knees with bloody trees.... thanks for testing.
@driftwood: Perfect! I won't be ordering after the weekend anyway. I need one that won't die. And in my case I need something that handles things like trees. A lot of work I do is second unit shooting, which often involves shots of nature...
Can't blame the GH2. Don't like the look of that card though :-( Before I go off improving tell me the artefacts - bad macroblocking? Update: Your card reviewed states Write 11~15MB = not good enough!
Yes, speed is low. But for some reason my settings to 50 Mbps and GOP24 work, but your settings (my modification of 32 Mbps and GOP12) give the artifacts? And why 24p to 100 Mbps GOP1 works without artifacts?
>>bad macroblocking? Well, I guess. The screenshot shows all
@driftwood cool. look forward to seeing the GOP 3 & GOP 6 versions. Someone else has asked too, but does anyone now the max bitrate of the GH2s SD card bus ? Cos I think in some cases with these 176M patches, when shooting something extremely detailed with high motion (shots where we actually hit close to the 176M limit), that it may be failing down to the bus speed rather than the card type.
@bkmcwd Running your patch at AQ1 it passed shooting those trees in strong window perfectly. I could shoot it all day, the results are really good too. Mind you its average bitrate was only around 133M. In a lower light, lower detailed shot it dropped to around 42M, which is pretty dramatic really.
@Botvinic '...for some reason my settings to 50 Mbps and GOP24 work, but your settings (my modification of 32 Mbps and GOP12) give the artifacts?' Botvinic, you can't simply adapt my settings by putting a different bitrate/GOP - theyre not set up that way. Each has to be tested. Of course my settings wont work at 32m! These patches of mine are refined for GOP1 176M or 132M GOP3 AQ2 respectively!
@Stray At 265M bitrate for GOP1 the buffer analysis reported summit like 187M death charts being employed so its well beyond! But stability was the issue. :-)
@driftwood Good to know, but its hard to say if stability could be related to the bus bandwidth I feel. But yep, if its going to fail elegantly with an 'unable to write' when it hits the speed limit of the bus, rather than being unstable, then we know that we can push it to 187M at least. So, given those assumptions, any write problems with a stream hitting under 187M are going to be card related.
Edit: I don't know if its that clear cut with card write errors though, I mean we've all seen them with cards running reasonably low bitrate interlaced 50i or 60i settings when far higher bitrate progressive footage works perfectly well.
I stupidly just used your 176 V2 on a job before testing it thoroughly (I have been using a transcend 32GB class 10 on all tried patches)
Footage looks great, but playback in camera was an issue. It was the same background/level of detail in all shots, just switching out the people. The clips were playing back in camera, but then I got read/write speed errors and after a hard reset (battery and card taken out) 'no valid picture to display'. However, I'm currently loading the footage to my desktop and I was able to watch the footage back in windows media player on a laptop via an internal card reader (didn't get a chance to see if audio was in sync, but hopefully it is because I will be referencing it when I sync up audio recorded to zoom)
Hopefully all will be good and yes I'm a berk for not testing/not using a better card.
Cheers for all your work, the best footage I've gotten of the gh2 has come from your patches. Also thanks to all the other contributors/testers
@PerryWilson The X264 can be used with any transcodable softwares like MpegStreamclip, or 5dtoRGB ect.. it just bypasses quicktime encode and uses it's own decode engine which is way better than quicktimes. I was digging a little bit more about it the only downside is that it does not integrate with Premiere Pro CS5. For better quality exports I'm thinking on switching my system to windows and getting a license for MainConcept Encoder 5.1 I've heard it's well worth it Perry..