GF1 100mb/s footage acheived!!!

mpgxsvcd said:
Ok a few more clips using mike's settings. You can download the original files of these as well. The streaming version just doesn't do them justice. Keep in mind that the second file is 1.6 GB though!:Drogar-Shock(DBG):

http://vimeo.com/12878669

http://vimeo.com/12880009
Click to expand...


Uncheck 4:2:2- you'll get a better chance of less write errors- Also at this high of a bit rate
the color is already great with Mjpeg. Mjpeg is just jpeg photos in a motion wrapper in plain terms.
When was the last time we thought whether our DSLR taken photos in Jpeg mode were 4:2:2 or not. Anyhow,
give it a try, you might get better card writing results.

Looking forward to seeing if these settings will even work with GH1.

Pappas
 
If it's not asking too much it would be nice to see some skin tones in these testes. Also, close ups with a lot of dof are harder to evaluate than wider framed scenes with more information and diferent light conditions (this way we can evaluate dynamic range, detail, color reproduction, etc)
 
mpgxsvcd said:
Ok a few more clips using mike's settings. You can download the original files of these as well. The streaming version just doesn't do them justice. Keep in mind that the second file is 1.6 GB though!:Drogar-Shock(DBG):

http://vimeo.com/12878669

http://vimeo.com/12880009
Click to expand...

On the last scene on the last video from left to right you can see a house, the sky, a tree and bushes. This is a good frame to evaluate dynamic range. You can see that the highlights on the sky and the white house are completely burned. Now, since this was shot at 108mb/s it should give you a lot of head room for recovering those highlights. Could you try to do that to see how much CC can the footage take before falling apart?
 
PappasArts said:
and then shoot the star chart,
Pappas
Click to expand...

papas, do you have a link to the star chart, when i search for it, i get a whole bunch of dead leads.

i cant say for the others, but i'm really keen to get the 422 to work as i want to use the gf1 for broadcast, but i will shoot the chart with both 420 & 422.

thanks
 
rawfa said:
If it's not asking too much it would be nice to see some skin tones in these testes. Also, close ups with a lot of dof are harder to evaluate than wider framed scenes with more information and diferent light conditions (this way we can evaluate dynamic range, detail, color reproduction, etc)
Click to expand...

rawfa,

hopefully this footage will fullfill some of your request. I would like to have had a more varied sky for you to play with, but unfortunately we dont have any clouds here in barcelona :grin:

download the original files from vimeo

109mbits obtained with the 410 24 settings. 14-45 panasonic - a lens i don't try to use because it distorts everything for me :(

http://www.vimeo.com/12891887

 
sparedog said:
papas, do you have a link to the star chart, when i search for it, i get a whole bunch of dead leads.

i cant say for the others, but i'm really keen to get the 422 to work as i want to use the gf1 for broadcast, but i will shoot the chart with both 420 & 422.

thanks
Click to expand...


Sure, here you go.

Tip- when focusing on the star chart get the lines to a crispy jaggie dance. Also move the camera too in separate tests- to simulate change of scene doing circular motions as well swaying it, this will get the VBR going.
Shoot a Fstop at least f8- Gain the camera up and set the Detail to +2- This will force the codec to spike at it's peak more. This process is good for fine tuning the exact formula numbers towards the threshold before write error.

Here is a link to a file the 2k file- use this one
http://www.sendspace.com/file/scn6oz


I also uploaded a picture so you know what I'm talking about. Don't use this one, as it's just a sample- Use the one I uploaded

Pappas
 

Attachments

  • STAR CHART 2K EXTRACT SAMPLE DO NOT USE FOR TESTING .jpg
    STAR CHART 2K EXTRACT SAMPLE DO NOT USE FOR TESTING .jpg
    215.2 KB · Views: 0
Last edited:
papas,

filmed the chart many times trying to trip the error message. when it did finally, i just carried on and filmed some more. the error message has very little effect i can see on the 410 24 settings as the error was tripped at 106.06mbits and the next clipped filmed was 105.33 which continued till i stopped it at 30 second later

some mbits from the charts
105.65 - recorded successfully for about 30 seconds till i stopped it
106.01 - recorded successfully for about 30 seconds till i stopped it
106.06 - tripped error message, the only one i got in 20 clips of 30 seconds
105.33 - recorded successfully for about 30 seconds till i stopped it
104.06 - recorded successfully for about 30 seconds till i stopped it
103.96 - recorded successfully for about 30 seconds till i stopped it
103.36 - recorded successfully for about 30 seconds till i stopped it
104.45 - recorded successfully for about 30 seconds till i stopped it
101.92 - recorded successfully for about 30 seconds till i stopped it

gonna try q 400 with t22, as i really want to get the minimum bitrate up to above 80mbits whilst keeping max at 100mbits. i've hacked my camera 16 times just to do the table tests, i hope there's no limit lol

cheers, huw
 
no 400 20 is not stable :crybaby:

398 22 is not stable

400 24 is not stable either

it seems as with mike797's setting and with 410 24, these become stable once the first error message has become tripped.

therefore i am setting my camera to 410 24 for now. 100mbit 422 is the same specs as DVCPRO HD which is used as the main camera format on many discovery, nat geo channel, history shows :D

in fact, does anyone know of any reason (moire, resolution, etc) the GF1 100mbit 422 footage would not pass broadcast standards as main camera footage, if for example i wanted to make an underwater documentary using gf1s in housings?
 
Last edited:
in fact, does anyone know of any reason (moire, resolution, etc) the GF1 100mbit 422 footage would not pass broadcast standards as main camera footage, if for example i wanted to make an underwater documentary using gf1s in housings?
Click to expand...

Thanks so much for posting the vid. I'm watching this one VERY CLOSELY....I have a GF1 (as well as a GH1). I'm excited to see this....

Quick request: Could you please post a screen capture? It is really hard to see anything on the Vimeo video. I'm not saying that it's not impressive...I am saying that it's hard to tell if it's in focus....and/or what is Vimeo compression issues, etc...

Thanks again for posting!
 
sure here a grab - i'm not sure if the focus is spot on in the clip lol

and below it is the highest bitrate i've recorded successfully, but the codec would fail too often to be useable.

109mbits.jpg

149MBIT.jpg
 
sparedog said:
papas,

filmed the chart many times trying to trip the error message. when it did finally, i just carried on and filmed some more. the error message has very little effect i can see on the 410 24 settings as the error was tripped at 106.06mbits and the next clipped filmed was 105.33 which continued till i stopped it at 30 second later

some mbits from the charts
105.65 - recorded successfully for about 30 seconds till i stopped it
106.01 - recorded successfully for about 30 seconds till i stopped it
106.06 - tripped error message, the only one i got in 20 clips of 30 seconds
105.33 - recorded successfully for about 30 seconds till i stopped it
104.06 - recorded successfully for about 30 seconds till i stopped it
103.96 - recorded successfully for about 30 seconds till i stopped it
103.36 - recorded successfully for about 30 seconds till i stopped it
104.45 - recorded successfully for about 30 seconds till i stopped it
101.92 - recorded successfully for about 30 seconds till i stopped it

gonna try q 400 with t22, as i really want to get the minimum bitrate up to above 80mbits whilst keeping max at 100mbits. i've hacked my camera 16 times just to do the table tests, i hope there's no limit lol

cheers, huw
Click to expand...

Excellent testing- The Star chart is really good for this.

The right numbers are important- it appears that the right combination is the key. The more people doing it, the more we learn...

Has anyone done these settings with the GH1 yet- filming the start chart?

Pappas
 
sparedog said:
it seems as with mike797's setting and with 410 24, these become stable once the first error message has become tripped.
Click to expand...

I have noticed this even with my settings. A first error- and after that no more. Maybe a buffer needs to purge out or?

Pappas
 
mike797 said:
Ok i just changed all Q settings to 545 and everything failed!

It gave me 2 sec clips at 120mb/s when i filmed my computer screen.

Going to try lower them.
Click to expand...

mike,

my calculations say for 545, you are writing about 140mbits/sec so you need a table setting of above 32, but then again, i was never very good at maths at school lol

today, i will try all t settings set to 35 with 545 and let you know

huw
 
ok tested 540 with 40.

the write error was tripped alot, even without switching off the camera. however, on the simpler test subjects and when the star chart was not full screen, i got up to a reading of 108mbit.

interestingly when the error message tripped on a clip, that clip showed no bitrate information in quicktime.

therefore, for me, 540 40 is no bitrate improvement, just more errors

108mbit.jpg

57mbit.jpg
 
sparedog said:
mike,

my calculations say for 545, you are writing about 140mbits/sec so you need a table setting of above 32, but then again, i was never very good at maths at school lol

today, i will try all t settings set to 35 with 545 and let you know

huw
Click to expand...

What is the equation to calculate Q settings vs. actual recorded bit rate?
 
i am working from my own equation, nothing definate yet. i'll explain

my table tests said the following

all quality set to 100 - max bitrate recorded 22.33
all quality set to 200 - max bitrate recorded 49.68
all quality set to 400 - max bitrate recorded 106.60

so far, in my tests, table settings have had no effect on top bitrate, just the difference between top bitrate and bottom bitrate, with lower table settings giving smaller differences.

hope this helps
 
sparedog said:
i am working from my own equation, nothing definate yet. i'll explain

my table tests said the following

all quality set to 100 - max bitrate recorded 22.33
all quality set to 200 - max bitrate recorded 49.68
all quality set to 400 - max bitrate recorded 106.60

so far, in my tests, table settings have had no effect on top bitrate, just the difference between top bitrate and bottom bitrate, with lower table settings giving smaller differences.

hope this helps
Click to expand...

Your numbers are precisely what I have experienced so far as well.
 
You must log in or register to reply here.
Back
Top