I was using 50mm 1.4 canon FD...I did the best I could to rest the camera on the back of a chair. I think I did a total of 30 tests with different settings all using the GOP of 15. I failed left and right except for certain variations of the settings I posted. I also moved the camera around/changed focus a bit since movement also caused some of the tests to fail. I posted so someone who is much more advanced then I am can examine my findings. I know the goal is to keep GOP numbers low but is it possible that higher GOP settings improve 24pn stability? The quality was still pretty good and will be able to post more test shots over the weekend.
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Possible breakthrough on Native 24p!
- Thread starter cbrandin
- Start date
I dont have time tonight but I will sometime soon. What is the advantage of locking off vs moving the camera? I would think movement would tax the camera more then just focusing onto a still frame. If its better to keep the camera still. Why did papa add the ability for the picture to spin?
I guess the theory is that movement can blur the image a bit. So a super-detailed still image is clearer and thus results in more detail. I guess the spinning part was for testing not only still images, since that was the big problem at the time (and still is for 24P) and what everyone was focusing on.
i tested this settings with papas chart, and when camera on hands it works nice, but when i start to shoot on tripod, camera shows "1 sec" and thats itTesting some more I was able to get stable settings using my sandisk extreme class 10 30MB/s WITH 24p checked:
Overall bitrate: 90xxx
FHD: 40xxx
GOP: 15
I was able to film papas chart here: http://vimeo.com/16509731
i tested this settings with papas chart, and when camera on hands it works nice, but when i start to shoot on tripod, camera shows "1 sec" and thats it
OK so the tripod does make a big difference...I was at a club/film premiere all weekend and was able to shoot 24p no problems handheld with the above settings. This issue seems to be completely backwards and illogical but I am probably just thinking about it the wrong way. If you take a computer graphics card for example. It will be taxed way more if images are moving vs standing still because the GFX has to create every single frame. Where as with a camera its more taxed not moving...I understand motion blurred images are easier to resolve due to less information to create the frame. But what I don't understand is why an image would throw the codec completely whack once it has been able to capture for a few seconds or longer.
It seems like the codec is continuing to try and resolve the image and with each resolve throw more bit rates at the image (like a never ending loop) causing an eventual write error. I do not understand or possess the technology to view AVCHD footage after the camera has crashed and deleted the footage. It would be very interesting to see how the bitrates/frames react while filming a complex non-moving image over time until crash. Maybe a safety buffer has to be coded in like a stop loss?
i tested this settings with papas chart, and when camera on hands it works nice, but when i start to shoot on tripod, camera shows "1 sec" and thats it
Actually, now that I think about it. You might need to cover the lens before filming an crazy scene like the chart. What happens is the camera throws a ton of bitrates at the image right away and it overloads the sensor. Try placing your hand in front of the camera when you hit record and then wait a second or two and slowly pull your hand away. I wish there was a way to tell the camera to not freak out like that and have it slowly increase bitrates when needed vs dumping them all at once. In the first second of filming I will get the highest bitrate and then it will level out. IMO this seems like a very weird way to have a camera handle its image processing.
Last edited:
Initial bitrate is exactly what "Preset Bitrate" and "Preset Bitrate 2" allow you to control. In my patches, I set both of these values to 180 to throttle back the data size of the first I-frame in the recording. That guards against almost all cases of recording failures immediately after pressing the movie button.What happens is the camera throws a ton of bitrates at the image right away and it overloads the sensor... I wish there was a way to tell the camera to not freak out like that and have it slowly increase bitrates when needed vs dumping them all at once. In the first second of filming I will get the highest bitrate and then it will level out.
What are the highest quality Native 24p settings that you would recommend?Initial bitrate is exactly what "Preset Bitrate" and "Preset Bitrate 2" allow you to control. In my patches, I set both of these values to 180 to throttle back the data size of the first I-frame in the recording. That guards against almost all cases of recording failures immediately after pressing the movie button.
Sorry, but I can't recommend any Native 24p settings. Nothing that I've tried has produced reliable results.What are the highest quality Native 24p settings that you would recommend?
EDIT: Until now! Check out my latest patch:
Blackout-Powell Native 24p Patch - GH1 FTW!!!
Last edited: