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.
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.