I’m giving my impressions as I understand them. You are free to disagree, but come at me with technical reasons. Attack the argument, not the person. All I’ve read is “you don’t know what you are talking about, this is bullshit, you are an LLM”.
None of that disproves my points. Sorry if faced with nothing but ad-hominens I don’t take your comments seriously. You’d understand my frustration.
The camera makes its own clock internally arbitrarily FACT.
FALSE, the camera has a set clock, whichever the image processor runs at. It can’t make up new clocks arbitrarily. It has to use technical workarounds to provide a wider range of options for the user, and this creates technical limitations. The physical shutter CAN run at arbitrary shutter speeds, BECAUSE it is mechanical. The rolling shutter CANNOT run at arbitrary shutter speeds, because it is locked to the processor, and whatever the sensor can or cannot do.
The camera doesn’t set the file format arbitrarily because back then the encoding format couldn’t do it, FACT.
If you can’t seem to link why I’m talking about this things with OPs question and don’t seem to be able to come with a logical counter argument, have you considered that, hey, maybe you are wrong here?
Alright, I will admit after reading for a while about how the electronic curtain works on cameras, I was wrong about the clock of the sensor being variable. I assumed the line to line timing was variable, but I was wrong there.
BUT the main dispute I have here with our engagement is the weird justification you mentioned for requiring FORMATTING an SD card.
I can understand a reboot for this, but a format? That doesn’t make any sense. I don’t even think I need to reboot my cameras to switch from NTSC to PAL, nevermind a format.
I was speculating, we are all here together trying to answer OP’s question. As far as I remember, interlacing H.264 used to lead to weird really long processing times. Encoding took a long while as a tradeoff for way faster decoding. Which resulted on the speed of data writes being violently throttled when image processing took too long, not a problem when encoding disk to disk, like burning a video into Blu-Ray for example. But it was a problem when recording from a camera, which risked running out of working memory while frames were still coming in hot from the CMOS. So, engineers resorted to compressing on the storage rather than on RAM, as to free up processing resources, this was called real-time compressing (I know it is a counter intuitive name but software devs aren’t the best at naming things). They wrote pre-compression data directly to storage first, this freed up resources on the processor and RAM side so frames weren’t dropped. Then later, the video would be slowly compressed and the result written, again, in-situ on the final file format. In exchange, this process locked the video processing to the formatting of the physical storage media (stuff like format, block size, addresses and caches).
I have no basis to affirm whether this is the case on this specific camera. Maybe it is or maybe it isn’t. My best guess is that, either way, Sony engineers just said “fuck it, force the user to reformat, no one is ever gonna change that one setting other than the first time they use the camera”, and just moved on.
Certainly for more modern cameras—with faster processors, better compression algorithms like HEVC, variable rolling shutter speeds with anti-flicker (even global shutters which are all the rage now) and free from the archaic compatibility issues of NTSC/PAL video signal processors—this is no longer a problem.
I’m giving my impressions as I understand them. You are free to disagree, but come at me with technical reasons. Attack the argument, not the person. All I’ve read is “you don’t know what you are talking about, this is bullshit, you are an LLM”.
None of that disproves my points. Sorry if faced with nothing but ad-hominens I don’t take your comments seriously. You’d understand my frustration.
FALSE, the camera has a set clock, whichever the image processor runs at. It can’t make up new clocks arbitrarily. It has to use technical workarounds to provide a wider range of options for the user, and this creates technical limitations. The physical shutter CAN run at arbitrary shutter speeds, BECAUSE it is mechanical. The rolling shutter CANNOT run at arbitrary shutter speeds, because it is locked to the processor, and whatever the sensor can or cannot do.
The camera doesn’t set the file format arbitrarily because back then the encoding format couldn’t do it, FACT.
If you can’t seem to link why I’m talking about this things with OPs question and don’t seem to be able to come with a logical counter argument, have you considered that, hey, maybe you are wrong here?
Alright, I will admit after reading for a while about how the electronic curtain works on cameras, I was wrong about the clock of the sensor being variable. I assumed the line to line timing was variable, but I was wrong there.
BUT the main dispute I have here with our engagement is the weird justification you mentioned for requiring FORMATTING an SD card.
I can understand a reboot for this, but a format? That doesn’t make any sense. I don’t even think I need to reboot my cameras to switch from NTSC to PAL, nevermind a format.
I was speculating, we are all here together trying to answer OP’s question. As far as I remember, interlacing H.264 used to lead to weird really long processing times. Encoding took a long while as a tradeoff for way faster decoding. Which resulted on the speed of data writes being violently throttled when image processing took too long, not a problem when encoding disk to disk, like burning a video into Blu-Ray for example. But it was a problem when recording from a camera, which risked running out of working memory while frames were still coming in hot from the CMOS. So, engineers resorted to compressing on the storage rather than on RAM, as to free up processing resources, this was called real-time compressing (I know it is a counter intuitive name but software devs aren’t the best at naming things). They wrote pre-compression data directly to storage first, this freed up resources on the processor and RAM side so frames weren’t dropped. Then later, the video would be slowly compressed and the result written, again, in-situ on the final file format. In exchange, this process locked the video processing to the formatting of the physical storage media (stuff like format, block size, addresses and caches).
I have no basis to affirm whether this is the case on this specific camera. Maybe it is or maybe it isn’t. My best guess is that, either way, Sony engineers just said “fuck it, force the user to reformat, no one is ever gonna change that one setting other than the first time they use the camera”, and just moved on.
Certainly for more modern cameras—with faster processors, better compression algorithms like HEVC, variable rolling shutter speeds with anti-flicker (even global shutters which are all the rage now) and free from the archaic compatibility issues of NTSC/PAL video signal processors—this is no longer a problem.