I know it is fashionable to be mad at people online, and call bullshit and throw insults like little children on a playground, but several things:
This is a video limitation, not shutter speed for still pictures. When you go from a physical shutter to a rolling shutter, the transistors on the CMOS sensor have to be coupled to a specific clock, at which rate they can flush voltage to the video processor. That clock conditions everything, and this specific camera obviously has some clock lock step somewhere in the video processing chain that affect writes to disk because it’s specifications state very clearly a ton of limitations that cannot be explained away by legal bickering. (Not even to mention the other complexities like ISO amplification and a myriad of other factors also altering the rolling shutter refresh rate.)
So, from the manual:
My suspicion is that it has to do with using an ancient HDMI (and ancient codecs, because WTF is limiting MP4 to 4GB) and also the ties, at the time, of Blu-ray digital file formats compatibility with TVs. Back then, H.264 was still very NTSC/PAL oriented. That was the tail end of interlaced and progressive frame compression.
I’m completely confident that you are all super duper more intelligenter than Sony engineers. But again, just because it is digital, and just because it is Sony, and just because it was an expensive flagship, doesn’t mean it is magical. There’s a history and a cost in engineering R&D time for making these digital features we take for granted today, that did not exist 11 years ago.
As for: “TVs now don’t get sync from the mains.” That is true, but did you know that LEDs still refresh their voltage state at a regular interval that is fixed at manufacturing time? Which interval to use will depend on which market the TV is intended for. And, for convenience sake, factories still use NTSC or PAL as standard. This is why TVs are either 50hz or 60hz or 100hz or 120hz, even if they are LED or based on other solid state components. Your attitude is like somehow engineers nullified basic physics, no, they didn’t. They found workarounds so end users don’t have to think about it as much. But the technical constraints are still there. A 50hz TV will show an entirely different viewing experience of a 24fps movie, than a 60hz TV. Even if both are technically using the exact same LED technology, and both are internally DC electricity that is technically independent of the mains frequency.
I’m not mad at you, I’m just stating you are rambling on about things that makes no sense. Hense the LLM comment I made. I genuinely feel like I’m interacting with an LLM here.
I’m also not saying I’m smarter than the software engineers that worked on this product. You seem to assume that I think I am.
You also assume I have an attitude that physics don’t matter.
You keep talking about mains frequency and TVs which is not related to the topic of formatting a SD card to change from NTSC to PAL. The camera makes its own clock internally arbitrarily FACT. Otherwise, you’d be locked into a single multiple of 1/50 or 1/60 a second as I mentioned in another comment.
You keep adding side notes “did you know…?” that 1, don’t make any sense, and 2 aren’t even remotely about this original topic.
You are the one who gives me the impression “I don’t read the other posters comments” and can’t stop and think “hey, maybe I’m wrong here”, but rather you think you need to belittle me and say “I’m completely confident that you are all super duper more intelligenter than Sony engineers.”
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.
You are just making completely wild guesses here.
Seriously you sound like a LLM stuck in a hallucination.
I know it is fashionable to be mad at people online, and call bullshit and throw insults like little children on a playground, but several things:
This is a video limitation, not shutter speed for still pictures. When you go from a physical shutter to a rolling shutter, the transistors on the CMOS sensor have to be coupled to a specific clock, at which rate they can flush voltage to the video processor. That clock conditions everything, and this specific camera obviously has some clock lock step somewhere in the video processing chain that affect writes to disk because it’s specifications state very clearly a ton of limitations that cannot be explained away by legal bickering. (Not even to mention the other complexities like ISO amplification and a myriad of other factors also altering the rolling shutter refresh rate.)
So, from the manual:
My suspicion is that it has to do with using an ancient HDMI (and ancient codecs, because WTF is limiting MP4 to 4GB) and also the ties, at the time, of Blu-ray digital file formats compatibility with TVs. Back then, H.264 was still very NTSC/PAL oriented. That was the tail end of interlaced and progressive frame compression.
I’m completely confident that you are all super duper more intelligenter than Sony engineers. But again, just because it is digital, and just because it is Sony, and just because it was an expensive flagship, doesn’t mean it is magical. There’s a history and a cost in engineering R&D time for making these digital features we take for granted today, that did not exist 11 years ago.
As for: “TVs now don’t get sync from the mains.” That is true, but did you know that LEDs still refresh their voltage state at a regular interval that is fixed at manufacturing time? Which interval to use will depend on which market the TV is intended for. And, for convenience sake, factories still use NTSC or PAL as standard. This is why TVs are either 50hz or 60hz or 100hz or 120hz, even if they are LED or based on other solid state components. Your attitude is like somehow engineers nullified basic physics, no, they didn’t. They found workarounds so end users don’t have to think about it as much. But the technical constraints are still there. A 50hz TV will show an entirely different viewing experience of a 24fps movie, than a 60hz TV. Even if both are technically using the exact same LED technology, and both are internally DC electricity that is technically independent of the mains frequency.
I’m not mad at you, I’m just stating you are rambling on about things that makes no sense. Hense the LLM comment I made. I genuinely feel like I’m interacting with an LLM here.
I’m also not saying I’m smarter than the software engineers that worked on this product. You seem to assume that I think I am.
You also assume I have an attitude that physics don’t matter.
You keep talking about mains frequency and TVs which is not related to the topic of formatting a SD card to change from NTSC to PAL. The camera makes its own clock internally arbitrarily FACT. Otherwise, you’d be locked into a single multiple of 1/50 or 1/60 a second as I mentioned in another comment.
You keep adding side notes “did you know…?” that 1, don’t make any sense, and 2 aren’t even remotely about this original topic.
You are the one who gives me the impression “I don’t read the other posters comments” and can’t stop and think “hey, maybe I’m wrong here”, but rather you think you need to belittle me and say “I’m completely confident that you are all super duper more intelligenter than Sony engineers.”
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.