Show Posts
1
General Development / Re: New Discussion about the merits of Video Hacks
« on: January 05, 2016, 05:42:16 PM »
Hi,
i know the topic is a bit old but i played with the video hack feature and try to understand a few things.
First of all i know about the risk using the Video hacks since they make persistent changes and can only be undone by ML firmware.
I think video hacks especially GOP would be a nice improvement for h264 without messing around with raw and the needed post workflow.
Now i have the following questions:
1. The video hack code disables audio recording. I set GOP to 1 and leave flush rate at 4, went back to the stock canon menu and turned audio recording on. I was able to record audio and video in 1280x720 @ 24p with CBR 1.2 so why does the video hack disable the sound recording ?
2. Is there an easy way to check if the GOP setting really has influence for the H264 compression ? I would like to check/verify if it really generates only I-Frames after setting GOP to 1.
i know the topic is a bit old but i played with the video hack feature and try to understand a few things.
First of all i know about the risk using the Video hacks since they make persistent changes and can only be undone by ML firmware.
I think video hacks especially GOP would be a nice improvement for h264 without messing around with raw and the needed post workflow.
Now i have the following questions:
1. The video hack code disables audio recording. I set GOP to 1 and leave flush rate at 4, went back to the stock canon menu and turned audio recording on. I was able to record audio and video in 1280x720 @ 24p with CBR 1.2 so why does the video hack disable the sound recording ?
2. Is there an easy way to check if the GOP setting really has influence for the H264 compression ? I would like to check/verify if it really generates only I-Frames after setting GOP to 1.