AVCHD high bitrate tests- MUD FREE footage

Look your self...
C Settings:
Csettings.jpg


D settings:
Dsettings.jpg
 
Oedipax said:
I didn't patch the GOP size on mine, just Video Buffer, Video Bitrate, Overall Bitrate & Limiting Bitrate. Aside from those I also did the MJPEG E1-E4 (Quality & Table) and native 24p, 3rd party battery & of course version change.
Click to expand...

Funny,

Doing this and using the b settings, and maxing out on the audio patch settings i get only 17261kbits/s.
Am I doing anything wrong?
 
However i Did retest D setting in hidetail scene with lot of zooms and pans and with shutter sped at 500 and strange thing is that I get spikes at low level...
My clip is 43.7 Mbps and Oedipax clip is 45.5 Mbps. So I suppose that camera limit for AVCHD is near by 45 Mbps...
And I didn't have any problems with recording.Maybe my scene is not so detailed.

download link:
http://www.nikolicnemanja.com/Dsettings-Hidetail .MTS


I will try to decrease velues for next test. ( but I can't find a scene with more details so Oedipax could repeat his test with slightly decreased values)
 
Last edited:
Shutter speed 1/500?, what does this tell us?

Shutter speed 1/500?, what does this tell us?

jobless said:
However i Did retest D setting in hidetail scene with lot of zooms and pans and with shutter sped at 500 and strange thing is that I get spikes at low level...
My clip is 43.7 Mbps and Oedipax clip is 45.5 Mbps. So I suppose that camera limit for AVCHD is near by 45 Mbps...
And I didn't have any problems with recording.Maybe my scene is not so detailed.

download link:
http://www.nikolicnemanja.com/Dsettings-Hidetail.MTS
Wait a minut... It's still uploading...

I will try to decrease velues for next test. ( but I can't find a scene with more details so Oedipax could repeat his test with slightly decreased values)
Click to expand...

I never go over 1/100, 1/125, why do we need to go so high? wont this cause issues? someone said your footage had high rolling shutter, is this why?
 
Adventsam said:
I never go over 1/100, 1/125, why do we need to go so high? wont this cause issues? someone said your footage had high rolling shutter, is this why?
Click to expand...

It's just for test purpose.... Higher shutter speed = more details...
As for rolling shutter, it has nothing with Avchd codec...
 
New test:

Video buffer 84000000
Video bitrate adjustment 70000000
Overall bitrate adjustment 72000000
Limiting bitrate adjustment 80000000

1080 - Overall bit rate : 11.0 Mbps
Maximum Overall bit rate : 73.3 Mbps

but interesting 720p - Overall bit rate : 43.0 Mbps
Maximum Overall bit rate : 73.3 Mbps
however camera stops recording after 5 sec when I do fast pans...
 
Last edited:
test 2 and 3:
Video buffer 84000000
Video bitrate adjustment 2)55000000 3)60000000
Overall bitrate adjustment 2)57000000 3)62000000
Limiting bitrate adjustment 2)63000000 3)70000000

2) 720 36,5 Mbps
1080 36,8 Mbps
No problems with recording

3) 720 44,1 Mbps (camara stops recording on fast pans after 3-4 sec)
1080 5478 Kbps
 
Did a quick test with the following settings:


video buffer 40,000,000
video bitrate adj 50,000,000
overall bitrate adj 52,000,000
limiting bitrate adj 60,000,000


All worked very well! Plays back nicely in camera and there is a definite improvement in mud reduction.

One question I have for any Mac user though - how do I extract the information showing bitrate etc? Jobless seems to have the elecard suite on windows for his analysis, but so far haven't come across anything on OS X that does the same thing with AVCHD files...
 
jobless said:
test 2 and 3:
Video buffer 84000000
Video bitrate adjustment 2)55000000 3)60000000
Overall bitrate adjustment 2)57000000 3)62000000
Limiting bitrate adjustment 2)63000000 3)70000000

2) 720 36,5 Mbps
1080 36,8 Mbps
No problems with recording

3) 720 44,1 Mbps (camara stops recording on fast pans after 3-4 sec)
1080 5478 Kbps
Click to expand...


Are you adjusting ABCDEF? Where are you putting these numbers in?
 
GMC said:
Yeah, funny. I was actually referring to early Car3o footage when he was for the first time showing the native 24p patch. He had cars going back and forth at night. This footage dropped to a 23.976 1080p Edius Neo 2 timeline was "real" 24p. The latest footage of jobless (first post on first page of this thread) clearly is not correct 24p, or at least Edius doesn't interpret it correctly (whatever it is).

Just relying on players (and scrubbing back and forth) to judge if it is 24p or not doesn't work (you run into all these issues with "tolerant" players and less tolerant players, plus the fact that computer screens typically run on 60Hz, thereby possibly hiding some of the issues). You have to go to a timeline in an editing software and check frame by frame in a 23.976p environment. Then you see it.

Anyway, thanks to all the efforts. We are damn close!!


UPDATE: I used the vimeo example on page 3 just now, "C" settings and Field of Flowers from IanB (downloaded the MTS file) and also this was supposed to be native 24p. It is not. Out of curiosity I applied the pulldown I usually have to do with original GH1 footage and now I get "real" 24p. Hence, I think that the native 24p patch doesn't work correctly or somehow is obsolete if high AVCHD bitrates are chosen from ptool.
Click to expand...

Did some further research. When the MTS (24p native) is directly dropped into an Edius 23.976 1080p timeline, it looks like the original 24p -in-a 60i wrapper. When I convert it first to Canopus HQ and then drop it into the same timeline it is "real" 24p. Hence there must be some room for misinterpretation in the file header (Edius gets it wrong, the Canopus HQ conversion utility gets it right). I thought that I should mention that.
 
Paul Shields said:
Did a quick test with the following settings:


video buffer 40,000,000
video bitrate adj 50,000,000
overall bitrate adj 52,000,000
limiting bitrate adj 60,000,000


All worked very well! Plays back nicely in camera and there is a definite improvement in mud reduction.

One question I have for any Mac user though - how do I extract the information showing bitrate etc? Jobless seems to have the elecard suite on windows for his analysis, but so far haven't come across anything on OS X that does the same thing with AVCHD files...
Click to expand...

Wait

so you CAN PLAY THIS BACK IN CAMERA NOW???? Thought it froze the whole thing.

So this is all ready to go then?
 
Yes in-camera viewable but

Yes in-camera viewable but

not with native 24/25p patch ticked? so if your happy with pal 50i wrapper or 60i wrapper and can pull-down, you are good to go, we are just looking for optimum settings and maximum-minimum iq that removes mud best.
 
Psynema said:
Wait

so you CAN PLAY THIS BACK IN CAMERA NOW???? Thought it froze the whole thing.

So this is all ready to go then?
Click to expand...
I don't think there were ever problems playing back footage with modified bitrates. The only problem that was (and still is) playback of 1080 native progressive footage.
 
Psynema said:
Wait

so you CAN PLAY THIS BACK IN CAMERA NOW???? Thought it froze the whole thing.

So this is all ready to go then?
Click to expand...

I'm wondering about this too.
I used the B settings, and I get "This motion picture cannot be played".

Should I be able to play this back in camera? I have a PAL camera if it matters(no native 25p patch).

EDIT: I also added the battery, 30 min removal and audio encoding bitrate patch. Maybe it's the bitrate patch that causes the problems?

Thanks!

Anders
 
Last edited:
AndersM said:
I'm wondering about this too.
I used the B settings, and I get "This motion picture cannot be played".

Should I be able to play this back in camera? I have a PAL camera if it matters(no native 25p patch).

EDIT: I also added the battery, 30 min removal and audio encoding bitrate patch. Maybe it's the bitrate patch that causes the problems?

Thanks!

Anders
Click to expand...

it's because you changed the audio bit rate
 
to headintheclouds46:

In 1080 your bitrate with this settings is only 11 Mbps...

Did you try to shoot 720? And what bitrate you getting?
 
You must log in or register to reply here.
Back
Top