Just checked this camera manual (2015 Sony Alpha 7RII). It does H.264 (it calls it AVC, and it also uses specifically AVCHD, exclusive to Sony. So, old version) encoding of video. That encoding does have PAL and NTSC hard requirements when recording 24fps, 1080 24fps is only possible in progressive mode, which means it is tied to analog standards. The rolling shutter has to match the target frame rate. Encoding is done on the memory card, it is called real time compression. It is a format intended to create DVD and Blu-Ray directly compatible files. Which were still, back then, held back by PAL and NTSC standards as they were targeting a TV market that were still technically very analog limited¹.
The camera also has TV out (early microHDMI it seems), which is also limited by PAL/NTSC compatibility of the TV.
Like, this camera won’t do 24fps video in PAL mode, for example. It also won’t do MP4 for more than 20 minutes because it has a file size limit of 4GB. That is the age of technology we are dealing with. Things are not magical just because they are digital. There are hard technical limits and there’s a history behind the development of technology we have today. This camera cannot record certain fps settings when an HDMI monitor is connected at the same time, that tells me there’s hard wired video processing that lock steps a ton of what the camera can and cannot do.
¹: quick note, TVs are actually still limited by NTSC/PAL standards. Manufacturers have just implemented several tricks to circumvent technical limitations. Such as TVs nowadays can detect which type of grid they are connected to and pick and choose workarounds depending on what the user is trying to play (and also which analog signal tuner to use, if they still support that). This usually creates certain artifacts, like when a 50hz TV is trying to play a 24fps or 60fps digital video, for example. For the vast majority of content you wouldn’t notice unless you were looking for it. But on some movies it is extremely obvious, since it changes the pace of movement by dropping or repeating frames in a way that was not intended by the file format.
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.
The answer is 32 bits. Any time you see that 4 gigabyte wall it’s either related to a 32 bit FAT32 file size limitation, or a 32 bit byte counter somewhere running up against its limit. 2 ^ 32 = 4,294,967,296 which is 4 gigs on the nose if we’re talking that many bytes.
The online scuttlebutt I found indicates that this camera only officially supports the FAT32 filesystem and while it “can” read and write an ExFAT formatted card if said card is formatted externally, it’s not officially supported and Sony says there is “risk of data loss.” The camera itself will not format a card to anything other than FAT32, with all of the limitations that entails.
That would make sense. If the image processor is manhandling the storage driver while recording video, and also only supports or expects FAT32. Then forcing an SD card reformat every time the camera initializes is a heavy handed but effective way to ensure video is not lost.
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.
The camera can record 1080p60, 1080p50, 1080p24, 1080p30, 1080p25, 1080i50, and 1080i60 as well as some 720p and 4k resolutions it takes regular SD cards that do no processing and is able to run android apps (playmemories).
don’t think you know what you’re talking about.
Can you confirm that it is a 2015 Sony Alpha 7RII?
Just to make sure I’m checking the correct manual. If it is, it can indeed do all of those stuff, but the manual state some very specific limitations when recording 24fps and it also warns the user directly that changing between NTSC/PAL requires a reformat of the SD card and that some video options will not be available depending on the mode the camera is in. (I linked at some captures here.)
Also, the red flag is that those old HD versions come in progressive and interlaced flavors. That is the giveaway of the time that the camera is from. You did realize there’s no 24 fps interlaced? it is because of all the things I said above. It only does 24fps in progressive, which locks the camera to NTSC mode for both file formatting and capture. You’ll notice that cameras made after 2020 (or thereabouts) no longer use the little i or p after vertical resolutions. Because they switched to H.265 or HEVC, which doesn’t provide progressive or interlaced frames for video compression (technically it is all progressive now, but since there’s no longer a need for interlaced, it is just not mentioned). Today it is more common that they are referred simply as 1080 or just FHD. While 720 is now just HD and 4k stayed just 4k since there was never a need for interlacing 4k.
Here’s my suspicions after all the discussion on this thread:
The engineers had to change some internal workings for compatibility with PAL, most likely the CMOS sensor clock for the rolling shutter, and for some reason this also forced the camera to reinitialize completely, including the file storage. Thus, rather than implementing a fix, they just let the camera force a card reformat on the user. It seems sloppy because it is. It seems it was just easier to let the camera reformat the storage for every change. It is probably unnecessary for a change between NTSC/PAL modes but it was just easier to just let it be. Since most users will not need to change often, usually you just set the camera to your local mode once and live with it. They definitely didn’t intended for users to flip flop between modes.
This blob of text:
• Movies recorded in the [60p 28M(PS)]/[50p 28M(PS)]/[60i 24M(FX)]/[50i
24M(FX)]/[24p 24M(FX)]/[25p 24M(FX)] setting in [Record Setting] are converted by PlayMemories Home in order to create an AVCHD recording disc. This conversion can take a long time. Also, you cannot create a disc in the original
image quality. If you want to keep the original image quality, store your movies on a Blu-ray Disc. [p. 78]
Tells me that there’s some limitations with how files are handled for conversion. Since Blu-ray inherited several historical limitations from the DVD era for compatibility. Including support for NTSC/PAL analog TVs. A lot of this is holdover from a bygone era. The HDMI out port might’ve actually also forced this limitation, since HDMI was still tied to modes back then, for the same compatibility with old ways of processing video signals.
The MP4 limitation to 4GB files tells me there’s something funky or peculiar about how the camera formats the cards as well. Anyway, only the engineers know for certain why they decided to let things be that way. As I said, it is not rare for sensor and image processor to be lock stepped, it saves on resources and simplifies (usually accelerating) image signal processing. But it does brings about these sort of quirks.
It seems that if you must record 24fps you have to use NTSC mode. But if you want to synchronize with PAL to avoid flickering lights (only relevant with fluorescent and incandescent lights, or recording screens) you are forced to 25 or 50 fps.
Just checked this camera manual (2015 Sony Alpha 7RII). It does H.264 (it calls it AVC, and it also uses specifically AVCHD, exclusive to Sony. So, old version) encoding of video. That encoding does have PAL and NTSC hard requirements when recording 24fps, 1080 24fps is only possible in progressive mode, which means it is tied to analog standards. The rolling shutter has to match the target frame rate. Encoding is done on the memory card, it is called real time compression. It is a format intended to create DVD and Blu-Ray directly compatible files. Which were still, back then, held back by PAL and NTSC standards as they were targeting a TV market that were still technically very analog limited¹.
The camera also has TV out (early microHDMI it seems), which is also limited by PAL/NTSC compatibility of the TV.
Like, this camera won’t do 24fps video in PAL mode, for example. It also won’t do MP4 for more than 20 minutes because it has a file size limit of 4GB. That is the age of technology we are dealing with. Things are not magical just because they are digital. There are hard technical limits and there’s a history behind the development of technology we have today. This camera cannot record certain fps settings when an HDMI monitor is connected at the same time, that tells me there’s hard wired video processing that lock steps a ton of what the camera can and cannot do.
¹: quick note, TVs are actually still limited by NTSC/PAL standards. Manufacturers have just implemented several tricks to circumvent technical limitations. Such as TVs nowadays can detect which type of grid they are connected to and pick and choose workarounds depending on what the user is trying to play (and also which analog signal tuner to use, if they still support that). This usually creates certain artifacts, like when a 50hz TV is trying to play a 24fps or 60fps digital video, for example. For the vast majority of content you wouldn’t notice unless you were looking for it. But on some movies it is extremely obvious, since it changes the pace of movement by dropping or repeating frames in a way that was not intended by the file format.
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.
The answer is 32 bits. Any time you see that 4 gigabyte wall it’s either related to a 32 bit FAT32 file size limitation, or a 32 bit byte counter somewhere running up against its limit. 2 ^ 32 = 4,294,967,296 which is 4 gigs on the nose if we’re talking that many bytes.
The online scuttlebutt I found indicates that this camera only officially supports the FAT32 filesystem and while it “can” read and write an ExFAT formatted card if said card is formatted externally, it’s not officially supported and Sony says there is “risk of data loss.” The camera itself will not format a card to anything other than FAT32, with all of the limitations that entails.
One of which is 4 gig files.
That would make sense. If the image processor is manhandling the storage driver while recording video, and also only supports or expects FAT32. Then forcing an SD card reformat every time the camera initializes is a heavy handed but effective way to ensure video is not lost.
it uses exFAT though, not FAT32
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.
The camera can record 1080p60, 1080p50, 1080p24, 1080p30, 1080p25, 1080i50, and 1080i60 as well as some 720p and 4k resolutions it takes regular SD cards that do no processing and is able to run android apps (playmemories). don’t think you know what you’re talking about.
Can you confirm that it is a 2015 Sony Alpha 7RII?
Just to make sure I’m checking the correct manual. If it is, it can indeed do all of those stuff, but the manual state some very specific limitations when recording 24fps and it also warns the user directly that changing between NTSC/PAL requires a reformat of the SD card and that some video options will not be available depending on the mode the camera is in. (I linked at some captures here.)
Also, the red flag is that those old HD versions come in progressive and interlaced flavors. That is the giveaway of the time that the camera is from. You did realize there’s no 24 fps interlaced? it is because of all the things I said above. It only does 24fps in progressive, which locks the camera to NTSC mode for both file formatting and capture. You’ll notice that cameras made after 2020 (or thereabouts) no longer use the little i or p after vertical resolutions. Because they switched to H.265 or HEVC, which doesn’t provide progressive or interlaced frames for video compression (technically it is all progressive now, but since there’s no longer a need for interlaced, it is just not mentioned). Today it is more common that they are referred simply as 1080 or just FHD. While 720 is now just HD and 4k stayed just 4k since there was never a need for interlacing 4k.
It’s in pal mode currently, and these are the supported resolutions.
Here’s my suspicions after all the discussion on this thread:
The engineers had to change some internal workings for compatibility with PAL, most likely the CMOS sensor clock for the rolling shutter, and for some reason this also forced the camera to reinitialize completely, including the file storage. Thus, rather than implementing a fix, they just let the camera force a card reformat on the user. It seems sloppy because it is. It seems it was just easier to let the camera reformat the storage for every change. It is probably unnecessary for a change between NTSC/PAL modes but it was just easier to just let it be. Since most users will not need to change often, usually you just set the camera to your local mode once and live with it. They definitely didn’t intended for users to flip flop between modes.
This blob of text:
Tells me that there’s some limitations with how files are handled for conversion. Since Blu-ray inherited several historical limitations from the DVD era for compatibility. Including support for NTSC/PAL analog TVs. A lot of this is holdover from a bygone era. The HDMI out port might’ve actually also forced this limitation, since HDMI was still tied to modes back then, for the same compatibility with old ways of processing video signals.
The MP4 limitation to 4GB files tells me there’s something funky or peculiar about how the camera formats the cards as well. Anyway, only the engineers know for certain why they decided to let things be that way. As I said, it is not rare for sensor and image processor to be lock stepped, it saves on resources and simplifies (usually accelerating) image signal processing. But it does brings about these sort of quirks.
It seems that if you must record 24fps you have to use NTSC mode. But if you want to synchronize with PAL to avoid flickering lights (only relevant with fluorescent and incandescent lights, or recording screens) you are forced to 25 or 50 fps.