GH1 firmware research volunteers required

Ok i just tested the 60p mpeg patch with these settings , i have a class 4 16gb toshiba card ..

MJPEG - 60fps

Quality settings (E1 to E4) - 300, 225, 175, 150
Table settings (E1 to E4) - 24, 24, 24, 24

result- the gh1 records only for 4 seconds on the gh1 (but in reality its 8 seconds,meaning for each sec the gh1 shows it recorded,in real life time its 2 seconds)
-played the file back, it was 4 seconds speed it up, for normal results the file should be 8 seconds with normal speed play back
-sony vegas sees the file as 60p

here is the original clip (straight from gh1, 60p at 125ss )
http://www.sendspace.com/file/730b8a

here is the file i edited in vegas (to get 24p from 60p....instead of .4 play back, i had to use .2 because the original file was 8 sec not 4 sec)
http://www.sendspace.com/file/nmu2mw
 
I suggest to move all posts not related to testing according to tester notes to separate thread.
As I already said our target is systematic testing.
And most posts here have no use for me (but can have some use for guys who want to find some settings for their task).

We already miss some important things due to flood of messages.
Like AVCHD Compression testing in previous verion was not complete, 1920 testing was done correctly, but 1280 in all quality settings had been missed.
Next important thing is that you need to perform RESET operation from menu after each firmware update. Because some settings are stored in EEPROM (this includes some AVCHD settings).
 
tester13 said:
I suggest to move all posts not related to testing according to tester notes to separate thread.
As I already said our target is systematic testing.
And most posts here have no use for me (but can have some use for guys who want to find some settings for their task).

We already miss some important things due to flood of messages.
Like AVCHD Compression testing in previous verion was not complete, 1920 testing was done correctly, but 1280 in all quality settings had been missed.
Next important thing is that you need to perform RESET operation from menu after each firmware update. Because some settings are stored in EEPROM (this includes some AVCHD settings).
Click to expand...


I agree, I went to read up on your post that 1080p 30/new Ptool, and it was a flood in here.

This thread I set up is a perfect area for footage-analysis discussions that are not related to the actual R&D you and the testers are doing.

http://www.dvxuser.com/V6/showthread.php?p=2008984#post2008984

Pappas
 
I've cleaned up a bunch of posts. I will be deleting posts that are off topic here. The more people post random questions, the more results get buried, and the slower progress is made. So create new threads if you want to discuss results.

EDIT: Use Pappas thread for results and discussion/requests.

:dankk2:
 
1920p25 and 1920p24 sensor patches are upcoming.
Due to risky nature I won't be testing them myself.
But risk here is much smaller compared to our early third-party battery patches.
I'll change sensor mode setting from 30fps to 1920 25fps and 2397fps (no 2400fps setting is present).
 
Keep the 30P 1080 still there in the Ptool. There a lot of uses for 1080 @ 30FPS. IMHO it's the way the industry should go. 30 is excellent for television work.
 
tester13 said:
1920p25 and 1920p24 sensor patches are upcoming.
Due to risky nature I won't be testing them myself.
But risk here is much smaller compared to our early third-party battery patches.
I'll change sensor mode setting from 30fps to 1920 25fps and 2397fps (no 2400fps setting is present).
Click to expand...

why is so much risk you're not willing to try on a camera that was bought for testing purposes?
 
Car3o said:
why is so much risk you're not willing to try on a camera that was bought for testing purposes?
Click to expand...

Sorry, I don't get that you are trying to say or ask here.

Yes, camera was bought for testing purposes, but not for risky patches.
And this was clearly indicated from the start.
Because bricking or malfunction induce very big delay in our project.
 
tester13 said:
Sorry, I don't get that you are trying to say or ask here.

Yes, camera was bought for testing purposes, but not for risky patches.
And this was clearly indicated from the start.
Because bricking or malfunction induce very big delay in our project.
Click to expand...

Alright, I mean it's tougher to have people who use their camera's for business or leisure activities vs a camera that's used primarily for testing to install a patch that may brick a camera. I suppose there are some out there who have nothing to lose.
 
Car3o said:
Alright, I mean it's tougher to have people who use their camera's for business or leisure activities vs a camera that's used primarily for testing to install a patch that may brick a camera.
Click to expand...

First, we have third-party battery patch that went through few iterations.
And this patch was 10x times more risky (as it changes system startup code).
MJPEG Sensor patch can be risky, yes.
But bricking probability is very low generally.
I played with some sensor settings (changing 1920 mode) and nothing happend.
I believe that you sometimes forget about our projects status.
This is not work project, this is free will and community project.
 
I get the impression that tester13's geographical location may not enable any kind of quick repair to the 'project GH1' if bricked. Others may be more favourably placed. But of course, if testers are depending on daily use of a GH1 to earn a living, that's another problem.
 
tester13 said:
Sorry, I don't get that you are trying to say or ask here.

Yes, camera was bought for testing purposes, but not for risky patches.
And this was clearly indicated from the start.
Because bricking or malfunction induce very big delay in our project.
Click to expand...

No sense in damaging your camera. This GH1 is vital for your research. 30FPS will work wonderfully, until a safe passage to 24FPS mode can be established.

That said 30FPS format is one of my favorite and is very important; as I worked with Iwerks, and 60FPS showscan. 30 always felt right. So no matter what, this is a win win situation.

Tester, could you please send me info so I could read up on how the Mpeg Quality settings (E1 to E4) Table settings (E1 to E4) work. I would like to stop the VBR on low end. so, no matter if the cap was on the lens it wouldn't dip below 45Mbits. A range of 45 to 80mbits top is very good. The lower would lend to very good compressed shadows and dark areas not having it fall below 40.


Pappas
 
Last edited:
That said 30FPS format is one of my favorite and is very important; as I worked with Iwerks, and 60FPS showscan. 30 always felt right. So no matter what, this is a win win situation.
Click to expand...

Please, stop mentioning 30fps mode as it is dying.
Use new patch and look it help hint.
It is still in place and will remain so.

Tester, could you please send me info so I could read up on how the Mpeg Quality settings (E1 to E4) Table settings (E1 to E4) work.
Click to expand...

Sorry, I can't you send this info, as I don't have it in the form you request.
 
Testing news.

After some more analysys I tested sensor patch.
1920 settings,
MJPEG 24fps
Plus sensor mode changed to 7.
For me it looks like FullHD MJPEG at 24fps is working, but I not analyzed it carefully, as main target was to test risk.

You can test it yourself at any time.
With zero risk (status updated to "Tested").
 
Last edited:
Time to get a GH-1 AGAIN.

Amazing work, guys. I feel like a bottom feeder, but stellar.

Already beastly camera made even more beastly. SD out is going to really be nuts.

Exciting.
 
I tried mpeg 720p50 at 83 mbits on a moving fan, its works only for 6s, but the framerate can be increased without damage, though it can't be used for serious purpose.

P1050781.MOV 06-Jun-2010 08:59

right click + save as
 
Lexcalcin said:
I tried mpeg 720p50 at 83 mbits, its works only for 6s, but the framerate can be increased without damage, though it can't be used for serious purpose.
Click to expand...

Please, read other posts before posting.
Your 6s limit is due to too high bitrate. It is known.
And about framerate also.

Plus all posts not related to sensor patch testing will be moved to other thread.
 
I have a question, Tester:

What is the highest class card that would handle the bitrate? And, is it beneficial at all to spend the money just to run a high bitrate 1080/24P?

Thanks for all of your hard work?

What's next on the list? Working on AVCHD? Video out?
 
Kholi said:
What is the highest class card that would handle the bitrate? And, is it beneficial at all to spend the money just to run a high bitrate 1080/24P?
Click to expand...

Camera itself have limit at around 80Mbit (and this is not average bitrate!).
If you look at GH1 from MJPEG side, you'll see that Panasonic need only to improve data throughput of SD controller (I say about 4x times), MJPEG encoder (2x times) and increase buffer size (3x). All is easy and cheap to do.
And they'll have dream of many guys (200-250Mbit MJPEG is quite good :) ).

What's next on the list? Working on AVCHD? Video out?
Click to expand...

I provided plan some time ago.
Today we need information and tools.
I wrote about it before, please search posts by user name.
Otherwise we'll hit the wall.
 
You must log in or register to reply here.
Back
Top