Airing now:

I'd love to hear your thoughts..

Unfortunately the slow motion of the video did not come out so prominently. I had the singer sing his song 2x as fast, while I recorded at 60fps. Slowed it down, and then synced the audio. But even at 2 times the speed, the singer had a hard time singing the song. I couldn't imagine making the slow motion effect any bigger.

Does anyone have any ideas on how to improve this effect? Any general comments or criticisms? Feedback is welcomed and encouraged.

Im a happy new owner of the GH2. Thus far i got the following lenses 14-140mm, 20mm, 7-14mm and two oldies: pentacon 29-2.8 and helios 58-2.0. I am looking for a lens with wide open aperture and a mechanical focus ring (for follow focus). I absolutely love the pancake 20mm, but its so small i doubt the focus ring would even fit, let alone the problems these lenses have when you want to focus manually. The pentacon 29-2.8 isnt bad, but i would like a bit wider aperture and wider angle of view.

The new 17.5mm voigtlander looks lovely, but a bit costly for now. Perhaps ill get lucky and find a killer deal on the 20mm :P

What else could you recommend?

I noticed the 64GB card shows up as "Untitled" on my Mac (after formatting it in my camera), while the 32GB one is called "NO NAME". When I change "Untitled) to NO NAME on my compter, it still doesn't work. (I am running the latest version of Lion). The card (64GB) does however work fine recording with any patch and I do have the other one for laoding patches.

But I still want to find out what the problem could be. Thanks in advance for any hint.

• Updated to GOP6 from GOP5, to fix stuttering.
• up to 60mbps
• 2x trick mode in some scenes (Death chart)
• QP16
• Borrowed I, P, B frame scaling from Flowmotion
• Improved Stability, so far have not been able to crash this in any test

Icarus 0.0.6 (indoor scene, f/2.8, 24mm, ISO3200, custom WB) (first couple seconds had rough motion, second half of bitrate distribution is what you normally see fairly static, where as movement scales up the B frames), typical B frames larger than Flowmotion's I frames.

Flowmotion 1.11 (same as above), much lower bitrate (imho it just cannot deliver with HBR modes), also crashes death charts with speed errors.

See what you think.

This is currently an Alpha Test. It needs more testing, but since I am pursuing the best HBR can offer, I've always found full daylight to be the bane of any attempt at raising HBR bitrate, I shall see how it performs in the morning in that regard.

Quantum v7. / 720 60p. / Lomo Anamorphic square front 35mm & 50mm / Converted in 5DtoRGB / Edited in Final Cut Pro / Graded with Davinci Resolve

Big thanks to Vitaliy and Driftwood!!

Enjoy. I'd be happy to hear comments or answer questions.

Results are great. I knew the gh2 is going to have blacks baked in, oversharp issues and lower latitude straight from the camera, but I am really impressed by what I got out - 5DtoRGB makes it pretty much comparable to C300- I think the image resolution wise is quite near to the c300 image and could be further tweaked to produce great results, that will go side by side with the best cameras out there.

Got to buy some extra fast cards though, as my allegedly 32gb class 10 Transcend card froze on me a couple of times.. Tell me what u think..

Thanks in advance and excuse my english, i am a french speaking person. Hello to Philip Bloom that spokes to me in french last year at NAB, what a great guy !

I do not know if anybody has reported the solution before, at least I could not find one here or the rest of the internet, but I faced this problem today and eventually found a fix.

The solution is that the SOURCE firmware, the one you load at the beginning, needs to be correctly named as well. When the problem happened to me, I had made a copy/paste duplicate of the very original Panasonic firmware that I had downloaded from the internet. This had resulted to a source filename "GH1__132 - Copy.bin"

One would imagine that it makes no difference, as PTool requests the user to give a name when saving and that is the only thing that has to pass the validity check. However, for some reason the original filename, probably "-" or " " character, echoes the saving procedure and the validity test is failed. For instance, when I finally tested renaming the source firmware first back to "GH1__132.bin and then saving it with the name"GH1__133.bin", it was suddenly again very acceptable name and finally got my hacked firmware saved.

.Patch: quantum 100

.iso 640 (down from 800)

.kelvin 6300

.24h

.standard -2,-2,0,-2

.shutter 40

.lens 14-140.

.AFS - continuous AF off

.OIS on (1)

.Tripod: Camera locked

late afternoon indirect natural light, indoors. grain and noise was constant and pleasing. Color was great and faithful...

But: In the middle of the shoot (two and a half mins in) after a pink shirt appeared on 1/5th of the frame, the image turned greenish, specially on the skin tones Mids.

this samples are two frames apart. direct screenshots from quicktime with avc plugin for playback of mts file.

I've also noticed this almost a year ago in a shoot, using original firmware. In a scene where yellow was background and blue and pink elements appeared in the foreground while panning. kind of like the pink shirt that comes in and out of the frame.

In this case it never goes back to normal up to the end of the clip, up to 5 minutes, the shirt keeps coming on and off frame every 10 seconds.

Anyone noticed this? It looks like although everything is locked the codec is performing some kind of auto white balance adjustment?!

I'm aware of the possible color shift in the first few seconds after you start recording, but this is different.

I've posted this on another thread but it was out of place.

I appreciate your input.

thanks

I'm using Balazer's Cake patch v.1.1 with Ptool 1.63. Thanks in advance for any help.

This is Driftwood's Quantum 'baby' 25/50. Everything shot at 24L so I would not run out of room. Slow motion shots @ 720 on SH. Neat Video used to clean scenes up a bit. Edit and Color in FCPX 10.0.3

Assorted SuperTakumar lenses from Pentax, Samyang 85mm, Panny 20mm, Olympus 9-18mm, H1 Zooms for audio. Steadicam Merlin. Kessler Pocket Dolly. Manfrotto Monopods '561'

Docustyle shooters - you can shoot with confidence with this patch!

Enjoy - and leave comment if you like. ; )

p.s. yes that ballantine's glass is empty but I'm not seeing things. Yet :)

I attached one setting which works great and very stable in 25p and 24p 1080 modes, spans until apertures f/3.5 always, if f/4.0 or darker- needs bit of luck, also with very fast SD cards. Firmware 1.0 and Ptool 3.63

I tried several times with different exposures and lenses, same result. So then I did a clean reinstall of firmware 1.0, same problem, likewise with firmware 1.11 and finally back to 3.64 with one check box marked against AVCHD for increase bit rate to 44. I went carefully through the entire process twice with all the firmwares, uninstalling and reinstalling so cannot figure out what happened.

I note that both 24H and 24L in cinema mode came out the same - 10-11 mbps. (Should be respectively 24 and 17 according to the manual.) On the last try after the second reinstall I got 15 mbps on cinema 24H and 12 mbps on HBR mode. The camera is a week old, working fine, the footage looks OK, so is there something I am missing with the camera settings or interpretation of the data?

I noted in another post somewhere here (cannot find it now) that someone else had a similar problem but managed to retrieve the bitrate after reverting to firmware 1.0. I am not sure if they did that working with V1.0 and 3.64 or just reverted to the factory settings of V1.0.

What should I do? Thanks in advance.