Would it be possible to write to an entirely different codec at 50 mbps?Not that any of these details really bother me anyway. Is the mpeg data from the avchd(mts) the same as the data contained in the mxf container and would that container be a better solution for the gh2 at 50mbps and up?

>tests with as many cameras as possible until the hack becomes 'stable' could take a few months, no?

You are citing words of @svart here, not mine. And add here speculation of your own.

>I do not know where you got it, and that you assume under "approved hack tests" :-)

i just tried to gather any information from all the discussions (that is, here), and it looks to me that doing all
the tests with as many cameras as possible until the hack becomes 'stable' could take a few months, no?
correct me if i'm wrong :)

i hope for all of you guys that you are not holding back any production plans while waiting for the hack...
it could work, it might not, it might be great, and might be of a just little advantage.. (with respect to Vitaliy ;) )
from what i read here it could take a few good months, or even 1/2 a year (until finished & approved hack tests)..
so unless you find GH2 completely useless at the moment (not my case - i will use it for a feature),
there is no use waiting.

>Did the guys from ML had to code feature like Zebra Stripes from scratch, or is it easier to do that on Canon firmware

ML uses foundation made by CHDK. I think thaty some code came from here.
Also other part is that OS is known for years and plenty of debug information is present.

Ok, in an effort to help answer some questions and hopefully keep the "what features...etc" questions down to a minimum, I'll state some generalities.

"hacks" are different than writing code. Hacks generally just change values of numbers or jump functions/features. Don't hold out too much hope of getting features/improvements that are not already part of the code.

This GH1/2 work are hacks because the code is not going to be re-written to add special functions that were not there to begin with. Adding things like that would be nigh impossible in assembler and especially so without guidance from some higher level code or documents.

That being said, I believe that since a lot of research has already been done on the GH1, that any improvements on the GH2 will start with similar improvements such as bitrates, language selection, region changes, etc.

Anything else after that would be up to VK to decided what changes are the lowest risk/highest reward or simply, what is easiest to do.

It then moves to testing. People will be asked to test the changes on as many cameras as possible. Just like the GH1, there might be problems at first so don't expect perfection on the first try.

Lets be patient though.

V, what feature will you first add when you complete the hack? What are your priorities?

>whether there is any further information about what features will be possible to add to gh2

At least at initial stages you must expect something similar to GH1.

>Vitaliy - any thoughts about the ability to add interval recording?

I do not have such plans.
It requires bunch of code, including interface.
Better just buy very cheap remote.

maybe I'm too enthusiastic, but whether there is any further information about what features will be possible to add to gh2

The interlaced HDMI out is due to the firmware or to the software ? There is any chance to have a clean 24p hdmi out ?

ok sounds good. How is the hack coming along Vitaliy. I took the GH2 out last night and also noticed that the LCD viewfinder changes colour after pressing record. Do you think this will be a possible fix in the hack?

how would I flatten the image on Final Cut or Premiere Pro instead of using Sony Vegas?