Since this patches are all a bit dated, I wanted to know if I they would work well on a 170MBps or faster Sand Disk card, like a SanDisk SDXC 64Gb 170MBps or faster.

Thanks in advance

Have a nice weekend

Hoping someone could help me narrow down my choices among the plethora of patches on here.

I mainly need a patch that would help me best with event capturing/running and gunning. (i.e. weddings, commercial events, concerts, etc.)

I'm looking for:

• Clean skin tone

• Low-light performance

• Reasonably sized files

• Fluid motion

• A decent 720p setting (for 60p slow-mo)

• Stability

The lens I'll be using most of the time will be the Voigtlander 25mm f/0.95.

Also, just to put it out there. I am also interested in a patch that would work great for footage with a lot of action for a music video project.

These are the patches I've tried out and tested so far:

@cbrandin 44M/32M(spanning) GOP12 AQ4

@bkmcwd 66M/50M GOP3 AQ3

@balazer Cake 2.0

I appreciate any help/advice from anyone. Thank you.

I have a GH2 with MD rokkor vintage lenses, im gonna shoot mainly music videos (with a lot of moving shots, slow motion, low lights and exterior) and some short films in the future. 30min of clips is enought for me I need quality but i really like the vintage look, im lost there is too much patch and informations, so i call your experience, what is the best possibility for me ?

Thank you for your help

I just did 2x on some basic settings, AQ4, and default GOP 15. The video bitrate was set up 32Mbps, and the result was 33Mbps.

Hopefully we can start polishing it.

The day I discovered the GH2 could do 2fps I got so excited, I loaded up a full battery, put the camera on the balcony and aimed it at the shopping mall door. I got over 3+1/2h of Cinema 24p footage (@2fps) and after speeding it up 15x (to 300fps) in VirtualDub I almost couldn't believe my luck. This is what I got and I have yet to grade it properly:

Since that event, I wondered about the best way to patch up the camera to capture them. MJPEG was the obvious candidate. It's a Full Intra codec and it can be setup to capture just 2fps. That means absolutely no wasted frames unlike AVCHD, so MJPEG must be great, but there was a caveat: even with stock settings there was a capture time limit that was well below AVCHD. How is that possible since it's only capturing 2fps, the bitrates have got to be frugal? Well, it happens that there is a 2GB filesize limit within MJPEG so even after taking Driftwoods Quantum 100-50's MJPEG settings and cutting the quality to take half the bitrate, you will end with less than one hour of footage. Compare that to AVCHD and you see what got me started.

Then there was the IQ issue. I stumped into this: http://sonnati.wordpress.com/2010/10/19/h-264-for-image-compression/ which made me start another full set of tests (http://www.personal-view.com/talks/discussion/2111/gh2-mjpeg-resolution-findings-and-myth-busting/p1) in which I found that unlike most crazy MJPEG resolutions that only seem to be 720p upscaled, the one used on Driftwoods patch was the best that ATM can be extracted from MJPEG and that even rivals with AVCHD. That test ended up on a tie, so in my book AVCHD wins for flexibility and recording time.

At the same time these tests were taking place, I fought a lot with the stock settings trying to make a patch that used GOP 13 and yes, that's the frequency at which you see major block changes when you set the shutter speed to 1/2s. This GOP13 would insure excellent quality as it makes the result Full Intra once you trash the needed frames. But the frames and limits and buffers and modes were giving me all kinds of speed messages Hell. By that time I also discovered that the null B frames that encoded no changes at 2fps were much larger than P-Frames which also appeared a lot more frequently than I wished they would. Null B-Frames were 2.5x bigger than P and when there was movement, the P-Frames would take as much space (and sometimes even more) than I frames, so I had to do something about it to make it more efficient. Meanwhile Nick @Driftwood and @LPowell were kind enough to share their knowledge and let me in on a few tricks. These allowed me to suppress B-Frames altogether and starve P-Frames to death.

So here I was armed with a bazooka and a missile and I couldn't even fire a pistol. Then a few days ago @Balazer came out with his Cake patch featuring a completely VBR approach through a Constant Quantizer as if he couldn't care less about bitrates, limits or buffers or all the stuff that was putting me down. I tried it a 2fps and I couldn't believe how well it worked. And since the frame rate I'm using is ridiculous when compared to normal video modes, there are no speed/buffer/spanning issues even if you have the slowest SD card in the business. In this case, this VBR aproach is a no brainer and the cherry on top is that you get Constant Quality at Quantizer 22 which is very very good IQ!

So, hands to work, bake the Cake, mix Driftwood's MPEG settings, apply the P/B-Frame tricks and it was working on the third try. :O

It could have been a lot faster as I tried to best the 60i mode and leave all other modes alone. It ended up being the wrong choice because the 60i GOP isn't sticking and probably the Interlacing is making too big P-Frames around the I-Frames. In the end I managed to use tweak 24p for timelapses and the frame usage when there is no movement is a beautiful set of I-Frame spikes with all else almost null. 60i is now GOP13 on I/P frames exclusively and the P sizes look generous, so the starved P-Frames on 24p don't seem to affect it. 720p modes seem also unaffected. In the end this patch tries to give you the best 2fps and still leave you with 2 very workable modes without repatching: 1080i60 and 720p.

USE IT AND ABUSE IT. DON'T forget to weed out the starved frames in post. AfterEffects instructions here: http://www.personal-view.com/talks/discussion/comment/49325#Comment_49325 and freeware workflow is here: http://www.personal-view.com/talks/discussion/comment/39079#Comment_39079

Thank you @balazer for baking Cake.

Thank you @drifwood for the MJPEG settings and no B-Frame trick.

Thank you @lpowell for telling me how to starve the P-Frames.

Thank you @cbrandin for StreamParser 2.4 which gave me wonderful new numbers.

.

VERSION HISTORY :

1 - TimeBuster 1 - First Release

• Based on Cake v1. It uses GOP13, a Constant Quantizer VBR approach without B-Frames, minimum P-Frame size and quality.

2 - TimeBuster 1.1 - with 2 significant changes:

• Now based on @balazer 's Cake 1.1, it has switched to use the Rate Control mechanism from @LPowell 's FlowMotion 100.

• 720p mode was broken due to use of a very low quantizer (12) which lead to skipped frames in 720p. It now uses QP=20 on both 720 & 1080 modes which will have an observable effect in both bitrate & quality even though it still gives you 24+ hours on 64GB.

3 - TimeBuster 1.2 - with 1 significant change for a fully featured 720p mode:

• Since @balazer 's Cake 1.1 is now heavily based on @LPowell 's FlowMotion 100, I decided to copy LPowells 720p settings since they will probably play better with the other modes. The only difference on 720p is a constant QP which had to be lowered yet from 20 to 21 because it still dropped frames on torture charts and/or sometimes present speed issues at very high ISO (>3200) on Class 10 SDs.

4 - TimeBuster 1.3 - with a lot of significant changes:

• Ported to PTTools 3.64d

• Savings on P-Frames is now accomplished by using a Scaling Table that is full of 0xFFFF for 1080p modes.

• Quantizer boundaries were removed since they are now much more dependent on the new Quantizer Tables.

• Redesigned for merging, these definitions try to be as independent as possible from their re-packaging definitions (in this case FlowMotion 1.1) and are published in two flavors: Timebuster 1.3 Base (for merging) and Timebuster 1.3 FloMo (merged with FlowMotion 1.1)

NOTE1: Timebuster Base 1.3 was merge tested with @LPowell 's FlowMotion 1.1, @Balazer 's Cake 1.2 and Nick @Driftwood 's Quantum X (v2) with minimal impact on all modes except for 1080p. I recommend FlowMotion or Cake for the simple reason that the 1080p24 Frame Limit is set to a much higher value in these settings. In fact, if you care for nothing other than the 24p timelapse IQ and don't mind impacting some of the other modes, you should set it to 10,000,000.

NOTE2: Merging Timebuster Base 1.3 with other settings is easiest done by loading Timebuster Base 1.3 first and then Alt+Clicking your choice of merger.

5 - Timebuster is now comprised of 2 main variants:

a) 24h Timebuster 2.0 - with the following changes (from TimeBuster 1.3):

• The GOP for 24p is now married to 2.5fps. The bitrate hit is a little above 20% but the recording length can be easily compensated by raising the QP. As a benefit it's still very close to 2fps and it's the closest to a 360º shutter we can get on 24p.

b) 24h TimeHBusteR 2.0 (NEW, uses HBR 30)

• Similar philosophy to 24h Timebuster 2.0 Base but as the name suggests, uses HBR mode instead of 24p. There is another difference, P-Frame quality is fully preserved as this kind of frames is used for one of the interlaced slices on Key Frames.

• GOP married to 1/2.5 on HBR 30p (NTSC) and to 1/5s on HBR 25p (PAL). The big benefit is that both are using a 360º shutter. Uncheck "1080i50 and 1080p24 GOP Size=5" before merging if you don't plan to use Shutter Speed (SS) =1/5s and want to better preserve the 24p mode and HBR 25.

Both variants are now:

• Using B-Frames. There is a 6% penalty in bitrate usage but this was necessary to make sure the QP was respected. I believe the gain from setting the QP at will is just too great to ignore, since not everyone wants to record for 24h straight. QPs as low as QP=16 were tested and theoretically it could go as low as QP=12 @ISO160 when merged with FlowMotion 1.11 on regular tripod mounted footage.

• GOP married to 2.5fps. The bitrate hit is a little above 20% but the recording length can be easily compensated by raising the QP. The reason behind this was getting as close as possible to 360º.

• User definable GOP - GOP can be set at will according to intended SS, use the attached "GOP-SS-table.png" to look up the right value. Defaults settings are SS=2.5fps and GOP 1080i=10 for 24h Timebuster 2.0 and SS=2.5/5fps and GOP 1080i50/i60=12/5 for 24h TimeHBusteR 2.0.

• User definable QP - QP can be set at will according to desired IQ/recording length. I've gathered quite an amount of information so that in the future I can make an Excel tool to estimate the best QP from Card Size/Footage Snapshot/Desired ISO/Recording Length. Default settings are Q24/23 for 24h Timebuster/TimeHBusteR.

As before, there is the Base Release to be merged at wish with popular settings (load Base first in PTTools and then "ALT+Click" your choice of merger) and there is also the FlowMotion Release (already merged with FlowMotion 1.11). I've merge tested against @lpowell 's FlowMotion 1.11, @balazer 's Cake 95, and @bkmcwd 's GOP3ZILLA and no undesirable effects were observed. The key is using a VBR settings definition with a very high "1080p24 Frame Limit", especially if you are going for a low QP (<22).

(edit) If you want to merge with Nick @driftwood 's settings, I recommend going for Cluster v1 as shines in being both a long GOP set and also having the biggest "1080p24 Frame Limit" of all the sets I know.

6 - Updated Release of Timebuster/timeHBusteR 2.02 FlowMotion - WARNING HBR version IS BROKEN at 24p

• (EDIT) This turned out to be a rushed release. Several users have reported problems with timeHBusteR (the HBR variant) It looks like FlowMotion 2.0(+) is highly dependent on GOP length (trough heavy use of GOP Tables, GOP Opt Tables and GOPx2 parameters). I'm investigating other possibilities right now so watch this space for further news. In the meantime I recommend you stick to timeHBusteR /Timebuster v2.0.

Since FlowMotion 2.02 looks very stable now, I'm releasing my pre-merged versions of Timebuster/timeHBusteR. There is nothing new regarding timelapsing except for FlowMotion's 2.02 changes.

• 24h Timebuster 2.02 FlowMotion which is 24h Timebuster 2.0 Base merged with FlowMotion 2.02

• 24h timeHBusteR 2.02 FlowMotion which is 24h timeHBusteR 2.0 Base merged with FlowMotion 2.02

7 - Updated Release of Timebuster/timeHBusteR 2.02 FlowMotion variants - 24p is now fixed on timeHBusteR. There was a note telling you should remove the "1080i50 and 1080p24 GOP Size=5" for better preserving 24p but no one seemed to read it and it was causing more trouble (to most of those who wanted 24p preserved) than it was worth (for those who wanted more timelapsing versatility.

NOTE: The mergeable timeHBusteR wasn't updated! Just the the FlowMotion variant. I ASSUME that if you are using this base for merging that YOU KNOW WHAT YOU ARE DOING, and read the DOC.

The day is not over. :)

This is the best thing I loaded to my GH2. Stable, reliable and excelent image quality in all modes, works for cards with 24/30/36/45MBps constant write speed or above depending on the version loaded. Best option is to use 45MBps cards and above, which I used for the tests.

setg is the recomended version, safe and great quality. seth and seti are for lower speed cards, but does not have same quality of setg. setj has more aggressive settings for even better quality.

four versions: (use setg if you have proper card, it is safe and avoids all mosquito noise and texture mud in the high bitrate modes)

setg: for cards with constant write speed 36MBps and above, I frames compression = 3

seth: for cards with constant write speed 24MBps and above, I frames compression = 4

seti: for cards with constant write speed 30MBps and above, I frames compression = 3.5

setj: for cards with constant write speed 45MBps and above, I frames compression = 2.5

The base is FlowMotion 2.02 from LPowell because he did a great careful job to tweak the quantization, matrices and tables and get perfect image quality in all modes with quiet camera or camera movements.

The modifications are in datarate and gop to make it completely stable and reliable without stop recording in all modes. For best image quality use the 24H, SH, FSH and HBR. The 24L, H, FH does not have the same quality and are for save memory space and for you to try in lower speed cards if needed.

The bitrate is very well distributed among the I, B and P frames giving a fluid random texture and noise in all modes and isos, The gops and datarate are well balanced to each other with the benefits from the quantization, matrices and tables from FM202.

In the setg 24H, SH, FSH and HBR, the texture is beautiful, noise is homogene, no macroblocking, no mosquito noise, no texture mud. Great use of the 8 bit codec in dark areas, excelent high iso performance which cleans ok with neatvideo and with a small amount of film grain you cannot tell it was shoot in high iso. Optimal results for blu-ray output and big screen projection.

720p 60p upscaled to 1080p works great for slow motion, just use your skill to denoise, sharp and upscale it. Apply film grain to your taste. If you like the feel of the original noise, just keep it, or just remove a little bit of chroma noise keeping the luma noise, and no need film grain.

No stop recording in all tests with setg. tested with green grass under sun and shadow and also tested in all modes with the four Stray's colour death charts. Tests done with 6400 iso which is very difficult to the hack to handle and it worked ok. Tests also done in the end of card space (3 minutes left) and no stop recording also. Sandisk 32GB SDHC 45MBps was used.

The audio has Pasadena settings, from FM202.

Spanning was not tested with this patch. Also it needs transcoding with 5DtoRGB free software before editing to avoid the diagonal pattern (rain). It is clean after converted to Apple ProRes. I Converted to the LT version with great results and smaller fle sizes.

If somebody wants to test spanning I recomend to use the lower bitrate modes and tweak the TOP and BOTTOM datarate limits in the advanced settings for testers in PTool.

Enjoy!

Setup - In order to achieve the higher bitrates I had to use M from the dial atop the GH2. The camera icon with the M would not allow this. The tradeoff was Auto ISO with M, and adjustable ISO with the camera icon with the M. I use mostly Canon FD lenses.

1a) Bitrates - I have tried a few hacks with varying success. The best I have got is about 100MB with Flow Motion v2.02, however, most of the shots I got with this hack seem to be from 70MB-90MB. I tried Flow Motion, Driftwood's Moon T7, and two Driftwood hacks (176MB & 220MB) from a pack made by the user Sohus on this forum.

Is it common to be well below the stated bitrate amounts?

1b) AVCHD vs MJPEG - I never seemed to get very high bitrates when using 1080i, despite the hacks stating to be much higher. They would range from 15MB-40MB. To achieve higher bitrates with Flow Motion, I used MJPEG which boosted them much higher.

Shouldn't I be achieving high bitrates with AVCHD?

2) Auto ISO - Whenever I use M (from PASM) the ISO would always be set to Auto ISO. I could adjust the ISO when using the camera icon mode (with the M), but then the bitrates would suffer. I tried changing the ISO before shooting, but Auto ISO would kick in no matter what.

How do I change the ISO while in M mode?

3) EV - I know that EV depends upon shutter, aperture, and ISO, but I can see the EV when I push the Display button so I was hoping there was still a way to change it.

Am I correct to assume that because I am using Canon FD lenses I cannot use EV? Even if using a Panasonic lens, how do I change the EV (I tried, but failed).

4) Modes - I have only been able to use the hacked bitrates - and only to a certain degree - by using M with MJPEG.

What modes should I be using to use the hacked patches? The camera icon with M? High Bitrate? 24P? 1080i?

Sorry for all the questions. I am not unhappy with the camera, but I really want to know why the bitrates are not working? And moreso, why the Auto ISO can't be changed (as I don't like the amount of noise it can introduce)? Thank you!

I can't seem to use it on the newer MBPr.

Best regards,

D

I, living in Norway, can only record for 29min 59sec. (This limit is an EU law has this restriction as it is a still picture camera and not a motion picture camera. Different taxes).

But I can not do it in Panasonic GH2 or any other DSLR camera, the white point must be higher then 20000K and improve the white point in dark blue. If you have some idea, or any patch for this problem...

Lenses used: Jupiter 3 50mm f1.5, and Jupiter 9 85mm f2.0 M39 mount adapted to M4/3 A few clips were colored with FilmConvert. Edited in Sony Vegas. Enjoy!

All tested with GH2 + Sandisk SDHC 32GB 45MBps card

I did not test spanning because I do not need it.

seta = modified FlowMotion 2.02 with high datarate for both 1080p 24p and 720p 60p, gop3 for 1080p 24p and default Panasonic gops for other modes, long gop for 720p is more stable than short gops. avoids the diagonal pattern (rain) noise in 1080p 24p, the other modes needs transcoding with 5DtoRGB free software before editing to avoid the diagonal pattern (rain) noise in dark low light. (best choice, workhorse)

setb = modified FlowMotion 2.02 with high datarate for 1080p 24p and mid datarate for 720p 60p, gop3 for 1080p 24p and default Panasonic gops for other modes, long gop for 720p is more stable than short gops. avoids the diagonal pattern (rain) noise in 1080p 24p, the other modes needs transcoding with 5DtoRGB free software before editing to avoid the diagonal pattern (rain) noise in dark low light. (for low speed cards)

setc = modified FlowMotion 2.02 with mid datarate for both 1080p 24p and 720p 60p, gop3 for 1080p 24p and default Panasonic gops for other modes, long gop for 720p is more stable than short gops. avoids the diagonal pattern (rain) noise in 1080p 24p, the other modes needs transcoding with 5DtoRGB free software before editing to avoid the diagonal pattern (rain) noise in dark low light. (for low speed cards)

setd = modified FlowMotion 2.02 with high datarate for both 1080p 24p and 720p 60p, gop3 for 1080p 24p and gop9 for other modes, avoids the diagonal pattern (rain) noise in 1080p 24p, the other modes needs transcoding with 5DtoRGB free software before editing to avoid the diagonal pattern (rain) noise, more noticeable than in the previous patches in this list. (highest quality for 720p)

sete = conservative settings with just datarate and gop changing, high datarate for 1080p 24p and mid datarate for 720p 60p, gop3 for 1080p 24p and default Panasonic gops for other modes, avoids the diagonal pattern (rain) noise in all modes.

setf = conservative settings with just datarate and gop changing, mid datarate for both 1080p 24p and 720p 60p, gop3 for 1080p 24p and default Panasonic gops for other modes, avoids the diagonal pattern (rain) noise in all modes. (for low speed cards)

I did some research in the forum about PTools settings but I did not find the answers I need...

What happens is:

Only GOP which works good for 720p 60p are GOP 30 and GOP 3, all other GOP gives diagonal pattern (rain) in computer monitor. But the GOP 3 in 720p always stops recording and it seems the card is not the problem, I am using Sandisk 45mbps and other people says the Sandisk 95mbps also stops recording in 720p hacks... The GOP 6, 12 and 15 works for some shoots, but they are unstable (sometimes stops recording) and gives diagonal pattern (rain) in computer monitor. GOP 3 stops recording all the time, no matter the bitrate (I tested GOP 3 from 40 to 200mbps). So GOP 30 is the only option.

Problem is: when using the GOP 30 the camera encoder always keeps the bitrate very low when the camera is quiet, when there is no motion in the image, and this gives lots of macroblocking and texture lost in low light. Even when I set the bitrate to 48mbps or 64mbps in PTools the camera does not record 48mbps or 64mbps, StreamParser shows only around 23mbps... (for static low light shoots)

The auto quantizer all to motion or all to details did not make any difference. So I did some try to change settings in TESTER options of PTools. I fount the TOP and BOTTOM bitrate limits and I enabled it with 48000 and 42000 for top and bottom 720p, but this makes no effects in encoding, bitrate is still very low for static shots no matter the bitrate I type in PTools...

Only thing I found to make the bitrate encoding keep high is the GOP 3, but camera stops recording in all 720p shoots, the GOP 3 just works for 1080p.

So I am wondering if there is a way to keep the bitrate high using GOP 30 in 720p...

Any suggestion welcome, thanks.

I would like to know what which latest Ptool setting is recommended for broadcast ready/approved documentaries.

thanks in advance. H Kitano

For the former, I want the camera to be able to shoot for long periods of time (spanning), and it's nice to get good quality, so I usually use the Cake 2.3 patch in these circumstances. Higher bitrates, reliable spanning.

For the high-quality stuff, I'll be using a high-bitrate hack (Intravenus 2 seems to be my best bet), and while spanning is desirable, it's not strictly necessary.

Is it possible to create a patch where these are combined? When I shoot at 30fps, it uses Cake 2.3 settings, and when I shoot at 24fps, it works like Intravenus 2?

Here is my question... Which combination of SD card and patch work reliably together?

Here is my shooting scenario...

It will be mostly indoors (bar, bedroom), low light. I am using a Rokkor 1.4 50mm lense. We will use Adobe everything, on a Mac, for post.

The other big factor is that it will be screened in a theater. So quality is very important.

Thanks again as this camera is new thing for me and any advice is very welcome.

I make short comedy sketches for youtube and have experimented with a few hacks. I'm looking for one that doesn't take an absurd amount of data, is flexible, but also increases the quality decently well.

I'll mostly be shooting in my basement with some lighting, but will shoot outside a bit as well.

Thanks!

All this tested on GF2, i think it's same for GH2.

1. Video Bitrate FSH/SH : you can set it for example to 200 000 000, final bitrate will depends on what quantizier you will set.

2. GOP Size : 1

3. Encoder settings 1 180i/p : 1 Without this video will very jerky.

4. Quantizier : depends on your card speed. Fast card needed. Take 32 for start number.

5. Quantizier table : all to be 1.

6. 1080 Scaling I : all to be 0x0. First 16 part is for Y, second for Cb, third for Cr.

7. Table flag1 I : all to be 0x0. (Not shure affect this seting or not )

8. Table High I : all to be 0x0. (Not shure affect this seting or not)

And that's it. You should to set all picture adjustments to -2 except sharpness. This settings will give you image that very close to that what you see in live view.

I need your suggestion about what patch to use for low altitude aerial footage, filmed with panny 7-14, subjects are most of the times under very contrasted sunny light, most of the times buildings or detailed nature..

I need low contrast and high latitude to color grade in post and most of all I need the lowest amount of sharpness possible, or not at all would be perfect.

What patch and settings do you suggest me ? (24p or 25p is good)

Thanks

Thank you.

Attention, noob questions ahead !

I would like to know a few things : - Which is the smoothest hack on the GH2 ? (All the detail, no macro-blocking) - What does "Intra" or "AVC-Intraa" mean ? - What is Auto Quantitizer ? I'm not sure if a higher number means a better image (lower compression) or it's the inverse. What is better, AQ0 (all to motion), or AQ4 (all to details) ? - What does GOP stand for, and there is "Low-GOP", but then does that mean there's "high GOP" ? What are 12/15 GOP, 3 GOP and 6 GOP ? - What are P-frames, B-frames... ? - What is "Matrix" and "444 Matrix" ? - On some settings there's written "14-16 QP", or "QP16". What does QP mean ?

I've not seen much smooth looking GH2 videos on Youtube (unlike the canon videos), lots of them have a lot of macroblocking or whatever and causes the video not to be smooth, and sometimes there are some sort artifacts (I think it's because of the compression or something...). I'm a bit of a pixel-peeper :P Could someone explain me the causes of the un-smoothness, and why are some videos really clean compared to others ?

Example of smooth videos I've found :

PS : Can someone give me the link to download the 244mb/s hack ?

And here on EOSHD there's an article about Intra :

http://www.eoshd.com/content/4452/gh2-gets-avchd-intra-at-176mbit

But I still don't understand the difference between the 176mbit so-called "Intra" hack and any other one ! I'm confused...

Please answer !

Thank You.

Muppets and the BBC love the Sedna - titles shot entirely on Sedna and GH2 + Rokkor 35-70 old beast for the upcoming primetime BBC Saturday night show:) Love the "I don't give a fuck if you think my camera is small" of me chum, who filmed it the day after a 10 camera Epic shoot in LA with the crew from IronMan 3.

http://osgfilms.com/gh2-quickstart/

So is there any difference ?

Thank you.

Any suggestions?