I was late to the GH2 game (as I really was fine with my GH1 other than the terrible green banding in low light that my camera produced. Honestly, it was one of the worst I've seen of any examples) and my job in the last couple years has been more projects and less time to dink around (I'm not complaining). So I've messed around with Flowmotion, and Sanity, not as much with Driftwood as I don't have 95 MB/s cards and don't have the time. But there are so many hacks, variations of Driftwood hacks especially, that I'd like to try out, but even being an "experienced" GH hacker, there are so many out there I have a hard time wrapping my head around what they do, or claim to do and what the new settings are.

Really, it's been this way for anyone coming into the GH hacking world from the beginning with the GH1. Tons of information spread across tons of forums and topics.

So, my question is: Is there anywhere that has a simple table with a lot of the major settings and some information on what their claims, bitrates and GOPs are? Something like the attachment below (this data is probably NOT AT ALL accurate, I'm doing it as an example). If there isn't one, doesn't anyone else think that this would be extremely helpful, especially for someone who isn't on the forums every couple of days keeping updated on the latest and greatest patch? I could have done this for the GH1, but I'm not qualified (as I stated above) to do this for the GH2.

Is there someone willing to put together a rough list? Maybe a wiki page somewhere so others can add details to each?

No color grading. Downsized in Avid to fit on Vimeo.

Hope you guys enjoy.

Thank you, Alexei

Without putting too much into grading/color correcting the videos the videos to match, would it be better to just go with a second GH2 and shoot everything twice, or just get two GH1s?

Also, if I went with the dual GH1 setup what hack would best match the GH2 Flowmotion 2.02 IQ?

I did a few searches and can see there are numerous topics scattered about, relating to Premiere Pro and Flow motion, but did not want to derail those ones as they are more focused on CS6 or Flowmotion Patch itself.

Been a while since I posted again.. Ive been experimenting with my GH2 a lot lately and have found that straight from the SD card into a Panasonic Plasma HD TV, the footage looks perfect. Then when I edit the footage together in Premiere Pro using import export settings recommended on EOSHD, I have trouble with distortion of image (graininess, low quality etc)

Can anyone suggest how to import the footage or how to set up my projects with which preset, and then suggest a custom export setting/preset that they work with using Premiere Pro CS5.5?

Basically, I use a standard GH2, hacked with Flowmotion V2.2, then a 95mbps SDXC card by Sandisk (64gb) Class 10.

In terms of my in camera settings I try to usually opt for Pal, in either HBR or Manual Movie Mode. Everything looks how I want it to when using my SD card into a friends TV as described before.

Thanks so much for any help I really appreciate all the advice I have received so far. I realise that when I have uploaded my footage to youtube and Vimeo it will be compressed somewhat but at the moment I just want to export the video at the highest possible quality so it ends up looking exactly how it did directly from SD card into TV.

Many Thanks again.

:)

I shot this last August. I got Flow Motion v2 hack and shot this 720p/50fps.

Thank´s all working around these amazing hacks :)!

For my next music video project I'll be shooting scenes in 60p which will be processed using twixtor to emulate approximate speeds between 500-1000fps.

I have invested in some SanDisk Extreme Pro 95 MB/s cards and I've searched around similar threads but most other posters are using slower cards.

So, I'm wondering if anyone has had experience shooting with these cards and if anyone can give recommendations for the best hack to use in this instance. I would like to push the cards to their upper limit without sacrificing stability.

Some of the shots I have in mind will contain large amounts of detail - splashing water, dust, etc so the higher the bit rate the better. They will all almost all be locked off frames.

Other posters have suggested the Flowmotion 2.02 is good for this purpose but the bitrate maxes out at 95 MB/s for this patch and if possible I'd like to make the most of the cards' capabilities and record at a higher bitrate. Will I be able to use one of Driftwood's 176MB/s patches? Does anyone have any experience shooting at 60p with these?

Are there other factors that I need to consider here to ensure the best workflow through twixtor?

Thanks JB

The short story: 31-OCT, the day the Portuguese Budget for 2013 was approved. People gathered in front of the Parliament to say we're being governed by thieves. Not very original I know, but it's a great place to shoot video and take pictures (well at last until it degenerates into mayhem which is rare around this parts but not unheard of until very recently). This is how I worked it.

1) The extremely simple setup:

GH2, screen folded back as a monitor, Transcend 32GB class 10, Samyang 7.5mm fisheye (my favorite video lens), set and forget to hyperfocal, ISO 400 I believe, SS=1/25s. Flowmotion 2 was used as I never know before hand how much video I'm going to capture or how many photos I'll be shooting, so I need something that is very good quality but doesn't make me have to change cards when something very important is happening. If the card is pre-formatted (the extended, not the quick format) it has never failed me to span.

2) The capture:

This is all about getting there up front and trying not to shake the camera. The police until very recently (and only after a 1h stone shower) has been instructed not to charge, so it's an easy job, you just dodge the TV reporters and other amateurs like me. So, here's my first mistake: the aperture is fine, this lens is sharp as an axe, but should have upped the ISO and set a faster SS because in these situations you are always bound to get bumped and it shows in wobbles after software stabilization.

3) Defishing the Samyang:

Load the MTS into AE. Export as image sequence. Use a batch (http://www.personal-view.com/talks/discussion/comment/69869#Comment_69869) to defish the images and import the output again to AE now as image sequence. The defishing was done using the Panini projection. It's loads more natural on people than Rectilinear, it preserves a lot more corner resolution and still manages to keep a few lines straight. This was the first export and not reasonably quick because the synthesis part takes it's toll: ~2-3fps.

4) Stabilizing:

Throw AE's Warp Stabilizer on the footage. Set the "Smoothness" to 15-25% (it will require much less cropping later) set borders to "Stabilize, Synthesize Edges" (again a lot less cropping) but drop the "Synthesis Input Range" to 0,2s otherwise you'll bog AE. In this kind of footage there is usually little point in using a higher value. Skim the footage looking for black borders and try to resize and reframe it so that they don't become evident. Note: defishing after stabilizing should make more sense as you would have more image to work with (defishing crops it) but from a few rough tries, the AE stabilization isn't clearly as effective when working on fisheye footage. This was the second export and a very long one: below 1fps.

5) CC & Denoising:

Used some of ColorGHear's gears, notably GHrain killer to kill a bit of noise and blockiness, but the footage was already very clean from the start and little color correction was used, just a little bit of levels adjusment. This was the third export and I believe it was even longer than the third due to the noise reduction filters: below 0.5fps.

6) The "so long" part: video effects, tracking and subtitling:

Translations were pretty quick, the hard and long part (at least until I found out how to smooth it) was tracking. It was fastidious to track people's features, takes a long time and needs constant review and adjustment. In the end I found out a few tricks (like increasing the tracking area) and smoothing the tracking points. This eased the job a lot and gave much better results. In the end I had to do it sometimes up to 3x until I was satisfied with it. In the process I had to learn a lot about tracking, smoothing, 3D objects, texting, transitions and light sources. This was the forth, the quickest and last export, probably around 10fps.

7) Audio mixing.

This was the part I was more ignorant about, but turned out to be pretty simple. Even though it's pretty rough, the footage is little demanding with so much crowd noise. It was as simple as importing the last video export from AE into Premiere, importing the original sound, importing also "Le Tigre - Dike March 2001" cutting and pasting a few pieces of this track and adjusting the volume here and there to serve the original events while leaving the words of the protesters audible when needed and off I was to the final export.

The resulting video can be found here:

Here are a few pictures of the event.

Anything more you may want to know about any part of the process I'll be glad to detail it.

xB.

This stuff really stresses the AVCHD codec and the poor bugger that has to shoot it :-)

we had been been filming for 2 month in Vienna and this is what came out. I used Flowmotion 2.02 in HBR mode. So far I do not regret it, nevertheless 50p would have been better for slowmotion.

Critical feedback will be much appreciated.

I though it would be cool to show you what it looks like, since you made it possible with all the knowledge found here.

Anyway, this is THE FIRST TIME that I ever shoot with it so I can see lot of improvements that need to be done.

Used Flowmotion with nikkor 35mm f/2, all manual mode, very little grading and bit ruff edit since I shot and edit all of it in 1 and a half day.

Difficulties with the audio, but this wont last ;)

I've just started reviewing footage from a recent shoot and am a little perturbed by the amount of noise showing up in shadow details. The problem has occurred on a range of shots in different lighting conditions and even at very low ISOs.

I was using a GH2 for the shoot, with LPowell's Flowmotion 2.02 hack. This was the first time I had used a Gh2 (let alone a hacked one) so it was certainly a baptism of fire. For the majority of shooting I was using a lumix 7-14 ultra-wide lens.

I've uploaded a short clip with three different shots, each displaying the telltale noise. In the first, the noise is visible above the character's foot, on the side of the piano. This was shot at a ISO800 so it makes sense that there will be noise. Still, it seems like there is more than there should be. the second clip was shot at iso160 yet there is still a fair amount of noise showing up in the man's beanie. In the third clip, also shot at iso160, again there is a lot of noise in the man's sweatshirt.

http://www.mediafire.com/?1m7c10p98tvy883

I didn't fully test the patch and cam before the shoot so at the end of the day it's my problem, but I'm hoping someone can shed some light on the source of the issue so I can avoid this next time around.

Cheers

Shot in 720p50, smooth -2,-2,0-2 As second camera we used a 60D with a wide angle lens. Even on Vimeo you can see the difference between those two cameras

I know that Nostalgic film mode has best dynamic range (from what I've read), but I also read on EOSHD Guide to GH2 that Black and White Smooth Film mode on GH2 is supposed to have the best DR and smoothest gradation out of all film modes. Should I just shoot Black and White Smooth mode straight in the camera or do use another mode and then do B&W in post? How about the best patch?

Any input is appreciated enormously,

Thank you so much.

Visual Event Coverage ArtForm - Watch and become immersed in the beauty of the sea and the people who ride it's motion. All the action starts 2:00, nice slowmo sequence at 7:25