@Iolo, +100, but I would want it for timelapses. That would give us 4k shots + lots of aspect options, without burning out the mechanical shutter (apparently the GH2's are only specced for 50,000 to 70,000 activations). And audio isn't needed for 'lapses anyway.

I think removing the 1 second limit for high fps shooting won't work - the issue (especially with 4K) is how fast the frames can be written to the internal buffer & the memory card. But it would work perfectly for timelapses.

@veloci, true but maybe the shutter speeds can be hacked too. After all you can use much slower speeds in MF for video modes.

@lolo, the 40fps mode doesn't support RAWs (the buffer would fill up too fast as they are much larger than JPGs).

The Personal View video mode!

btw, according to the manual (page 76)
"the burst mode speed may become slower depending on the following settings.
sensitivity- page90
picture size-page119
quality-p120
focus priority-page130
focus mode"

so this means that there has to be a sweet spot on the buffer in order for us to squeeze the maximum of it,

but of course all of this proposal depends if this is actually a software limitation and not a hardware one

@johnnym i have only a sd card slower than yours, the kingston 100x, are you saying that the 1 second limitation was caused by my slower card, are you sure you have 20 seconds at 40fps?

well i have just counted the seconds,
with manual focus it takes 8 seconds,
with autofocus on it takes 16 seconds
both with focus priority off

quality doesnt seems to make any difference in writing time

still, we have to see if lowering the fps from 40 to 24, has any big consecuence in the 1 second limitation

because, this means that it is writing in the card as the buffer in the camera records the picture, so perhaps, if we are lucky, if we lower the fps the internal buffer will record at the same time that it writes in the sd

but i don´t know, it is possible that panasonic aint squezzing all the buffer that this mode can take, i´m mean from the other options hacked we know that much at least, so

still think is worth hacking

@lolo very interesting. Speaking as a programmer, I'm surprised that higher ISO values are slower. I'm trying to figure out why that should be... [penny drops] actually it's probably due to the NR processing (higher ISO needs stronger NR).

Since the iso unlock has been revealed in movie mode, it could be nice to hack the "iso limit" setting too. :-)

@beavis

We have topic about this :-) This is in plans, but not easy.

I am working on v1.1 firmware, looking at encoder changes and preparing stuff for porting.
It seems that changes are present, but not drastic, just small ones.

If this is where we suggest features for the Stalin hack, here's one. It's an interesting feature on the Magic Lantern hack for Canons, a method for doing high-dynamic range video. It relies a lot on post-processing, but it requires that the camera capture alternate frames at a different ISO setting.

A video illustrating the process can be found at

@Vitaly_Kiselev

Can you actually write entirely new code/functions in the firmware? Or do you need to keep that consistent size?

@B3Guy

In fact, for quite long PTool not onyl change simple parameters.
Some patches look simple but have bunch of code and related changed inside.
And yes, we have parts of code written from scratch. They are small, but anyway.

@vitaliy
By the way, any date for new ptool release?