GH2 Running out of bandwidth/blocky image

Everyone has only the one standard answer I explicitely asked not for and a simple "No clue, can't help you." would have told the same as these 2 pages of posting.

Well, it's not only about you. This thread will whither away, but perhaps one day someone else will stumble across it, read it, and glean some helpful info/advice from it.

It's all potentially useful.
 
Because I don't want to buy cards that I can't use with the GH3 later and I don't want to spend money on UHS-1 cards that may later turn out to be a waste of money.
150eur per memory card with 3 cameras and at least 2 cards per camera is damn expensive.


Expensive? Looks to me like you're in the wrong business..... Imagine only 4 years ago what users were paying for P2 cards..... What about Red Users and their SSd hard drives? $165 is NOTHING for what the Gh2 is able to do with the hack, if you find that too expensive then restore the camera back to default or get a Canon dslr and never worry again....

You're crying for all the wrong reasons, people never appreciate anything.
 
I'm asking their technical support for Europe about the minimum write rates. Website and spec-pdf only mention a theoretical maximum of 35MB/s.
Let's see when there will be budget for this and if it solves the issue. My guess is that it will still be reduced/postponed but remain noticable.

I don't compete or compare with Red or Arri or Black Magic.
I want to get the most out of the camera I have and can affort and carry.
 
Last edited:
I'm asking their technical support for Europe about the minimum write rates. Website and spec-pdf only mention a theoretical maximum of 35MB/s

From first hand experience, the Patriot EP cards do work at 100 Mbps but they will sometimes "stall" when you first press the record button.

Variable bit-rate patches like LPowell's FlowMotion 2.02 may take care of this "stalling" issue completely.
 
Again, video stills comparing the quality vs the blocky image would be greatly helpful. I'm using Transcend cards and the Flowmotion hack and don't run into any issues while shooting in similar setups.

Which hacks have you tried and what cards are you using at the moment? I find it strange that you would wait to get new cards, but don't seem hesitant to drop money on a GH3 body, which may or may not better than the hacked GH2.
 
Which hacks have you tried and what cards are you using at the moment? I find it strange that you would wait to get new cards, but don't seem hesitant to drop money on a GH3 body, which may or may not better than the hacked GH2.

Who said I'm not? But I'm waiting for it to be released before I decide and given the difference between GH1 and GH2 I'm quite sure it will be enough of an improvement to replace a GH1 body with a GH3. Maybe before it gets hacked, maybe after.
 
When I read from Marcus that he seemed to get maybe 10 seconds of good footage, and then all hell broke loose, I thought of it maybe being that fallback mode issue that LPowell has talked about? I've had that happen to me using standard firmware and a couple of hacks (patches, diddly-dos. whatever the ****), where it looks good and crisp and detailed, and then like a mushy, SD, edge enhanced mess, but not with the previously recommended flow motion v 2.02, which I never had any issues with on Class 6 cards using the "L" mode (or most of the time "H" even"), and never any Motion Recording Stopped... messages on Class 10s in any mode.
I've also always been unclear if it's recommended to amend any patches (or WHATEVER, my apologies in advance, blah blah blah, yeesh), but maybe if it's just bitrate and not quantizer tables or what-not it's fine. Anyway Marcus seems like a smart dude, so I'm sure he's considered this too.
So I guess you can disregard all of this, because, no, I haven't had occasion to shoot strobes, and I haven't the foggiest clue what bit rate allocation means.
 
Back
Top