AVCHD high bitrate tests- MUD FREE footage
- Thread starter jobless
- Start date
kainekainekaine
Well-known member
http://panasonic.jp/support/global/cs/dsc/connect/g1.html
your 17mm lens does not support 1080, see footnote 7
Timmyjoe
Active member
I'm not seeing that. I have been shooting AVCHD at the "C" settings, and because I was having issues with the 24P, I went back to shooting in the 60i mode. I Log and Transfer into FCP as ProRess 422 (HQ) and then de-interlace with JES Deinterlacer. I just stepped through over 100 frames of some panning shots of foliage, and there wasn't any pulsing, skipping, hiccuping, freezing, or anything. Just very smooth motion with lots of detail in all the leaves and vines as they went past the frame.
Best,
-Tim
Please include a screenshot of StreamEye with your test reports like I did here http://www.dvxuser.com/V6/showpost.php?p=2020231&postcount=512
I found an error in my testing that warrants a discussion.
When testing higher bitrates I was able to get 5+ minutes at very high bitrates in detailed scenes on even class 6 cards. The error I found is that the scenes were moving slightly. When I revisited some of my settings with the camera pointed at a detailed scene that was completely static(no grass/trees moving in the wind, etc) I would quickly get card speed errors. As long as the scene had a little movement, the camera would NOT get the card speed error no matter how long I recorded.
I assume this is related to the I frame bitrate bug that was found.
Because of this, I think we should create some kind of testing protocol that designates what should be used as a target for the camera.
I used the brick siding on my house. There was plenty of detail to send this camera into fits and there was no movement like there is with grass/trees.
When testing higher bitrates I was able to get 5+ minutes at very high bitrates in detailed scenes on even class 6 cards. The error I found is that the scenes were moving slightly. When I revisited some of my settings with the camera pointed at a detailed scene that was completely static(no grass/trees moving in the wind, etc) I would quickly get card speed errors. As long as the scene had a little movement, the camera would NOT get the card speed error no matter how long I recorded.
I assume this is related to the I frame bitrate bug that was found.
Because of this, I think we should create some kind of testing protocol that designates what should be used as a target for the camera.
I used the brick siding on my house. There was plenty of detail to send this camera into fits and there was no movement like there is with grass/trees.
bumkicho
Well-known member
Below is my setting.
version change = ticked
version compare = ticked
3rd battery = ticked
24p = ticked
420 - 422 = ticked
MJPEG setting
-------------
356
24
220
24
200
24
184
24
AVCHD setting
--------------
42
44
50
All modes are stable including fast panning in high detailed scene with one exception, SH mode + extremely fast panning.
Question. What if I give more gap between average bitrate and max bitrate? I mean if I increase max bitrate from 50 to 60, will it allow GH1 to handle sudden spikes better?
version change = ticked
version compare = ticked
3rd battery = ticked
24p = ticked
420 - 422 = ticked
MJPEG setting
-------------
356
24
220
24
200
24
184
24
AVCHD setting
--------------
42
44
50
All modes are stable including fast panning in high detailed scene with one exception, SH mode + extremely fast panning.
Question. What if I give more gap between average bitrate and max bitrate? I mean if I increase max bitrate from 50 to 60, will it allow GH1 to handle sudden spikes better?
Timmyjoe
Active member
Svart,
Interesting. Just grabbed my camera, which is set with the "C" settings, but I am using 60i and not 24P (for reasons discussed previously) and I just pointed the camera at a wire mesh basket on my desk that I use to hold pencils. Very detailed object. Hit record and made sure nothing moved, and the shot ran for about sixty seconds with no issues, until I shut it off. As I mention on all my threads, I am using an adapter and manual focus lenses, so I am using none of the cameras electronics except for the sensor processing. And I am using a lowly class 4 card. So I'm not sure why you're getting that issue.
Best,
-Tim
I'm using a manual lens too. Make sure you have a lot of detail that's in the same focal plane. if things in the background are out of focus they generally have lower bitrates. Also, it seems that things that are darker don't utilize as much bitrate as things that are brighter.
I'll specifically test the "c" settings tonight and see if that works. I have everything written down in a spreadsheet and I'll be able to revisit more of my settings quickly now that Ptool can upgrade without version checking.
I'm also wondering if it doesn't have something to do with the encoder. I might be mistaken but it seems that files that have bitrates <30mbit don't seem to have the strange I frame size spikes while other files with bitrates above 30 mbits seem to have the spikes.
I have tested Ptool "C" Settings yesterday, which resulted in I frame size spike footage, avg. Bitrate around 35 Mbit. However, Adventsam has just uploaded a StreamEye screenshot for fairly file taken with fairly high settings, with resultant 31 Mbit avg bitrate and no spikes, so there might be other factors at play. Also, just a reminder to mention which C or B settings you test (Ptool, Jobless's (from beginning of this thread), or the new numbered settings in Car3o's thread).
Yes, of course. This was just observation so far. I wanted to get a sanity check to see if it was an anomaly on my camera or if others might have seen this as well before I go doing more tests. I was guessing around the 30mbit area since I have not tested every combination between 24-35mbit. Maybe we should collectively do that and see if there is indeed a place where the encoding breaks down. it could perhaps help the efforts to know where the tipping point is?
Thank you for following up. I set my camera with the 'C' setting again and am headed down to Orlando themes parks. So I'll report on the result (expecting heavy usage) when I return.
No worries, I do have a backup SLR and HV30 in case the GH1 starts acting up. Im looking forward to putting the GH1 under some laid with these patch.
Thanks again for helping me better understand the Olympus lens.
Timmyjoe
Active member
Svart,
Just so we're all on the same page, I am shooting at the 60i setting, not at 24P. So when using ptool, I am not checking the Native 24P/25P option. And since I am shooting 60i, I don't have the 1080p 24 GOP size option checked either. So I am shooting 60i, and I am using the what we used to refer to as the "C" settings:
Video Buffer - 40,000,000
Video Bitrate Adjust - 50,000,000
Overall Bitrate Adjust - 52,000,000
Limiting Bitrate Adjust - 60,000,000
And the basket I shot was silver, so that was pretty light colored.
Best,
-Tim
I'm still seeing problems when recording a static scene. As long as something in the frame is moving I don't get an error. Once all movement stops, I get the error.
bitrate simplified: 24,000,000
overall: 27,000,000
limiting: 30,000,000
Even at these settings I am getting card speed errors on a class 10 card.
I'm not sure what is going on here.
bitrate simplified: 24,000,000
overall: 27,000,000
limiting: 30,000,000
Even at these settings I am getting card speed errors on a class 10 card.
I'm not sure what is going on here.
John Caballero
Veteran
What's the 60i setting. My GH1 doesn't have that one. Unless is the 24p over a 60i stream of course.