FS7: Almost cannot believe it but... FM 3.0 is here.

Can somebody please remind me what do I do to not loose all files?
+1 I'd love to have a recap on that.


I'm going to wait until friday for the update, have a shoot with another FS7 Owner/Op and big talent on thursday and don't want to run into any snags that aren't the snags I've been dealing with for the past 8 months, lol.

Bummed to hear that a clean display still shows no record light. I find myself constantly peering over the VF and checking that red light. Oh well, I'll deal.



A little unsure if I understood correctly that there are two different center crop modes now? Sounded like there's two options, one of which has less aliasing and a slightly more narrow FOV. Am I off base?
 
Can somebody please remind me what do I do to not loose all files?
Just copy them from your SD card to hard drive and then reload. Like someone said before: I would be cautios about using All Files from 2.0/2.1 on 3.0 firmware.

A little unsure if I understood correctly that there are two different center crop modes now? Sounded like there's two options, one of which has less aliasing and a slightly more narrow FOV. Am I off base?
Yes, you are ;) First is full scan, where full hd is calculated from the full frame (only option from the very beginning) second is center scan - recorded from the center of the sensor, pixel to pixel (this is new, crop mode).

Wow, I still cannot believe how fast it is now to switch between custom, CineEI and different resolutions. :O

Side question:
In CineEI viewfinder lut on/off is greyed out and ganged together with SDI1/Internal. Does anyone remember what are correct settings to have Lut on viwefinder but not recorder? I've tried everything, my memory have blanks now :/
Edit: Lens> distortion comp>off (not on auto)
Firmware update will reset that, so keep in mind!
 
Last edited:
Can somebody please remind me what do I do to not loose all files?

Before you start the FW update process as described in the Sony .PDF, just pop your SD card into your computer, and copy the whole file structure. Next, re-format the SD card, and start the update process as usual. Once it's upgraded, then you can re-format the card again, before copying the file structure back from you computer onto the SD card.

You can also keep hold of the file structure as a backup incase you have to re-format the SD in future.

-jason
 
In most of the cases all files lost their purpose for me now. When you change all files (even when two varies only slighty) camera will reboot every time. For example changing resolution and frame rate (from 4k to 180p hd) will take a lot quicker manually if you'll set your user menu right, with options close to each other. Same with centerscan (like said above).
 
You need to remake them. Unless, you want your camera to be a door stop. ALL FILES need to be made with the current firmware.


Hey, I agree that what you're saying sounds like a sensible precaution, but are you speaking from direct experience, or more from general first principles? I only ask because I have successfully loaded a 2.1 all file with 3.0, and didn't experience any issues. Just wondering.

Also, does the cam no longer need to reboot between resolution/base setting/framerate changes, cos if so I can dump my all files anyway!

Cheers, j
 
Hey, I agree that what you're saying sounds like a sensible precaution, but are you speaking from direct experience, or more from general first principles? I only ask because I have successfully loaded a 2.1 all file with 3.0, and didn't experience any issues. Just wondering.

Also, does the cam no longer need to reboot between resolution/base setting/framerate changes, cos if so I can dump my all files anyway!

Cheers, j

It's standard operating procedure. I'm surprised Sony don't flag this up - maybe they do, I didn't read the manual...

Lots of FS7 users have had issues using ALL FILES with the wrong FW. It's a well-known issue with many cameras, not just the FS7.

Indeed, FW V3 changes quite a few things, adds features that weren't in earlier versions and moves others around the menu. You're definitely asking for trouble using older ALL FILES.

Certainly, with boot time and menu navigation significantly faster plus the shutter-bug being sorted, there is less need for ALL FILES, though I still remade all of mine since I use different recording set-ups with the Odyssey.
 
So, regarding this "ALL FILES" from prior firmware. Imagine that as a software engineer, you have to store preferences. You store the user's current settings as index values relative to the position in the menu they had selected. Now the firmware changes, new options added, some old ones removed. The user attempts to reload their old preferences file. The file references index numbers. But the index numbers have changed now. They point to different things (becuase new options in the menu shifted everything else), and they also potentially point to indexes that are now invalid. The behavior is undefined.

The above may or may not describe the Sony "ALL FILES" situation well, but it certainly is a very real computer engineering situation - and I just ran into it with software I'm developing.
If folks like Ned are warning to not use old firmware ALL FILES, definitely don't do it.
 
To switch gears a bit - Ned - maybe you can shed some light on this - when / or will - the new fw release get posted on Sony's US site for download? I'm more curious than anything - but for those of us in the US... fw 2.1 was never posted, was it? Wondering if same will be true of 3.0?
 
So, regarding this "ALL FILES" from prior firmware. Imagine that as a software engineer, you have to store preferences. You store the user's current settings as index values relative to the position in the menu they had selected. Now the firmware changes, new options added, some old ones removed. The user attempts to reload their old preferences file. The file references index numbers. But the index numbers have changed now. They point to different things (becuase new options in the menu shifted everything else), and they also potentially point to indexes that are now invalid. The behavior is undefined.

The above may or may not describe the Sony "ALL FILES" situation well, but it certainly is a very real computer engineering situation - and I just ran into it with software I'm developing.
If folks like Ned are warning to not use old firmware ALL FILES, definitely don't do it.

If there isn't idiot proofing in the firmware then Sony should make a point of officially telling people to ditch their All Files after FW update.

I think people should ditch their All Files because a firmware update could alter the menu order options and an All File that you think has the camera set up in one way might not be as expected. But bricking a camera? I think that would be extremely poor programming on Sony's behalf not to parse the All File safely or not check against the date/Version the All File was saved with and disallow loading.
 
Can anyone explain the thinking behind 2K Full? 2K Centre I understand as an option for HFR and as a digital zoom.

What possible use is there for 2K Full? Why would anyone want the nasty aliasing as a choice over Normal?
 
What possible use is there for 2K Full? Why would anyone want the nasty aliasing as a choice over Normal?

Why would 2K have nasty aliasing? HD on the FS7 doesn't and isn't that the full sensor also? The line skipping or whatever voodoo that was causing aliasing was only for the HFR options not on HD. I don't know enough about 2K full it to have a knowledgable opinion. I'm hoping to update my FW this afternoon at some point.
 
Back
Top