AVCHD high bitrate tests- MUD FREE footage

Okay, one last tidbit for you folks -- the 24pN footage plays on a blu-ray player! It doesn't play back in camera, but it sure did when I put it in my blu-ray and played it on my 67" DLP TV. It will probably work from a PS3 as well.
Click to expand...

The PS3 certainly plays unmodified firmware AVCHD footage (1080 & 720) - even sent from my PC across a wireless network!

I'll try the PS3 with the "D" settings in the morning (if it works on my existing card) as well as trying the 'turntable' test.

Update (fwiw) - I've played the original 'Jobless' example and the ' garden-whipping' example on my PS3 with the files stored on my PC, across the network - the garden-whipping played a bit jerkily but that could be a network issue rather than a PS3 issue. Anyway, both looked great on the 42" Bravia connected to the PS3.
 
Ozpeter said:
Update (fwiw) - I've played the original 'Jobless' example and the ' garden-whipping' example on my PS3 with the files stored on my PC, across the network - the garden-whipping played a bit jerkily but that could be a network issue rather than a PS3 issue. Anyway, both looked great on the 42" Bravia connected to the PS3.
Click to expand...

Ditto when played on a WD media Player via HDMI.
 
Testing Ptool 3,36:

I can confirm playback of native 24p in camera.

I didn't check buffer for this test and I use C suggested setting from ptool...

1080 -- 41 Mbps ( camera on heavy pans recording without of problems)

1080p.jpg



720 --- 36 Mbps ( camera records normally on heavy pans but on really heavy pans ( like samurai with sword) stops recoding...




720p.jpg



I suppose that Video buffer option i Ptool don't work...
 
to jobless

1) Adjust Limiting bitrate to lower value to remove stops in recording.
2) Try and do systematic comparison between Video bitrate patch and Video bitrate simplified patch (check one or the other, both are useless).
3) I also think that buffer can be removed in later versions. But more testing is required.
 
ProjX v2.0 said:
Jobless, how are you reading Streameye to find the bitrate? When you mouseover the blue bars, is it the "size" that is the bitrate?
Click to expand...

Streameye have separate window for bitrate information (Alt-S).
In popup it only show info about frame.
MediaInfo can be not very accurate as it uses default fields, and not exact calculations.
 
tester13 said:
Streameye have separate window for bitrate information (Alt-S).
In popup it only show info about frame.
MediaInfo can be not very accurate as it uses default fields, and not exact calculations.
Click to expand...

ok, no more MediAInfo ...
 
Last edited:
Ah , thanks guys. ALT-S was the trick.
Is it the "bitrate declared" number that is the actual bitrate or is it the "bit allocation min/avg/max" numbers?
 
Last edited:
New test:

Same settings, just changed Limiting bitrate adj. to 5500000

1080 -.- 40 361 800 kbps ( no problem with Cam)

720 ... 38 941 620 kbps ( with samurai style paning camera stops rec.)
 
Native 24p in-cam works for me with the "D" settings!

However, when I patched MJPEG to 1920 and used the following settings:

  • MJPEG Size 1280M = Ticked
  • MJPEG Enco 1280M = Ticked
  • MJPEG E1 Quality = 400
  • MJPEG E1 Table = 103
  • MJPEG E2 Quality = 350
  • MJPEG E2 Table = 116
  • MJPEG E3 Quality = 250
  • MJPEG E3 Table = 120
  • MJPEG E4 Quality = 200
  • MJPEG E4 Table = 125
Click to expand...
I got write speed errors to the card after just a second or two of recording. Didn't seem scene dependent, either (I never successfully recorded a clip with MJPEG with those settings). Transcend 16gb card, class 6. Maybe I need a class 10, or maybe it's just too much for the camera's hardware.
 
Downloaded the "garden whipping" video right into the PS3 and it plays perfectly (c.43Mbps says the PS3 display). The big screen confirms that there's clearly still 'mud' in the fine foliage (eg base of big tree and the bush that appears above the top of the birdbath) but you have to step through frames to see it - in normal play nobody would be troubled by it. Actually perhaps the really fast pan isn't such a good test - it helps obscure possible problems as they flash past too quickly. A pan at the speed of a typical real pan might be better, one where you can still judge the quality of what you are seeing in normal playback.
 
Limiting bitrate adj. to 5000000

1080 --- Streameye want open the file, Mediainfo shows 37.4 Mbps.. I didn't have any problems during recording and player plays hte file normally...

720 --- 40 265 416 kbps ( camera stops recording after 5sec)





Limiting bitrate adj. to 4500000

Camera freezes when I hit record button ( However, LCd works normal but all other functions are not available... I needed to remove the battery....
It happens in 1080 and 720...
 
Fun thing is that as we now know weakest point of this camera is SD controller :-)
In case of CompactFlash, controller is inside card, and it uses UDMA. So, you can have really good speed, like 240Mbits/s. May be it's worth experimenting with 7D :-)
 
jobless said:
Limiting bitrate adj. to 4500000

Camera freezes when I hit record button
Click to expand...

Never ever make limiting bitrate lower than overall bitrate and, of course, video bitrate. It'll lead to freezing due to firmware bug (function do not process error code correctly). So, next time I hope they'll read something about unit testing.
 
Oedipax said:
Native 24p in-cam works for me with the "D" settings!

However, when I patched MJPEG to 1920 and used the following settings:
[/list]
I got write speed errors to the card after just a second or two of recording. Didn't seem scene dependent, either (I never successfully recorded a clip with MJPEG with those settings). Transcend 16gb card, class 6. Maybe I need a class 10, or maybe it's just too much for the camera's hardware.
Click to expand...

I'm using those MJPEG settings and haven't had any issue with recording up to 3 min on an Acumem 16GB class 6 card.
 
You must log in or register to reply here.
Back
Top