Sony F55 quirks

After working 6 weeks with a Sony F55 on a feature shoot, here are a few notes focusing on some idiosyncrasies of this quite nice camera.

Basically, the camera feels like a mini-version of the Alexa. I don't know how much cheaper it is, but it is definitely a lot lighter. With a Fujinon 19-90 zoom, this is a very nice solution for shoots where an Alexa with an Allura zoom would be much too cumbersome (or too expensive?).

We used it to shoot XAVC S-Log with normal gamut, and were very satisfied with the grading tests we did during preparation.

However, the camera has many little quirks which may be worth knowing about. It does excellent pictures, but don't expect the reliability and solidity of an Alexa. The firmware we used is version 1.21 from August 2013.

Hole in camera body

The biggest problem was a hole in the camera body, which produces flares on the sensor when the sun hits the hole under the right angle. Not all models seem to have this hole. Most cameras turned up by this Google image search don't have it. But this video does show the same hole that we found on our camera body, between the viewfinder connector and the focal plane mark.


I suppose that is where a viewfinder connector cap would be attached. If the cap is removed, it opens a path for light to the sensor. Our camera had an Arri "VFA-1 Viewfinder Adapter". I guess that cover was removed when the Arri adapter was installed.

The problem was easy to fix with some black tape, but it had already ruined 1 shot when we found out.


The camera's manual says it accepts many different signals on it's Genlock input. We used an Ambient timecode generator, and set it to send a 1080p25 signal. The camera didn't accept that, nor did it accept a 1080p50 signal. However, 1080i50 seemed to be accepted, even though we were really shooting 25p.


We made the effort to find the correct Genlock which the camera would take, in the hope to have reliable frame-accurate timecode sync with the external audio recorder. But even with a Genlock feed from the Ambient to the camera, the external audio is still often 1 frame in advance of the picture (and the camera's audio), sometimes even close to 2 frames. Apparently, timecode-synced external audio is never late in relation to the camera audio and picture. It is either correct, or 1 or 2 frames early. (On a 7 week shoot with the Alexa last year, timecode sync was frame accurate on every shot).

Another problem related to TC is the "EXT-LK" indicator on the display. It is supposed to show when the camera receives external timecode. The problem is that if you remove the external timecode, and even reboot the camera, the display continues to show "EXT-LK", even though it is obviously wrong. So don't rely on it.

And of course, you do need a permanent external generator. The internal one will drift much too quickly, like with (almost) any other camera.

Camera randomly stops after starting

A few times per week, the camera would appear to start, and then stop after about 2 seconds. When it happened, it tended to happen a few times in a row, and then not at all for several days. We were always starting the camera with the "Assign 4" button which was mapped to "Rec". I don't believe it had anything to do with the way the button is pressed. Weird.

Spurious "backup battery" error

Twice during the 6-week shoot, the camera said the backup battery was bad and needed to be replaced. Rebooting the camera seemed to clear this "error", which looks more like a sensor or software error, than a real problem with the backup battery. After the reboot, the date and time were still correct, but the timecode had reverted back to "rec run" instead of our "free run" setting. The other settings had been preserved.

WiFi remote: fun but unusable

We wanted a remote switch, and the only option we had available was the WiFi dongle. It was fun to try it out, but after playing with it for a while, I wanted to actually use it three times, and these were exactly the times when it failed. It is much too unreliable to be of any real use.

The problem seems to be that the wireless connection gets lost very easily, even when the smartphone I used was less than 1m. away from the camera. This was a Samsung/Android phone, with which I otherwise never have wireless problems.

The worst case was when we started the camera from the phone, and then couldn't stop it. Neither with the phone, nor with the switches on the camera. Nor could we shutdown the camera with the power switch. The only solution was to remove the battery. Of course, if you want to use a remote switch, it's usually because there are some difficulties with the shot, so it's definitely the time when you don't want to have weird bugs show up. That is when we stopped trying to use the wifi.

Can't we just have a 2-wire cable with a mechanical switch for starting and stopping the camera remotely? It may not be trendy and fun, but definitely tends to "just work".


The camera has no notion of daylight savings time. So when shooting during the summer, you have to set it to your neighbor timezone to get correct times in the metadata and (some of) the file timestamps (some time stamps will still be completely off for some other reason).

File times

While the "CreationDate" recorded in the XML matches the camera's time, some (not all) of the .MXF files on the card have weird modification times. That means you cannot rely on the times displayed by your file manager. I still don't know what triggers this weird behavior. Battery change? Viewing clips? Something else?

Aspect marker

We were shooting scope, and used the apsect marker mask. It would be nice if the aspect mask could remain even when using the "display" button to turn off all other information in the display. And it would be nice if the mask could also be sent out on the second SDI output, to avoid the need to mask the monitors with tape or whatever.

Labels: , , ,


Post a Comment

Links to this post:

Create a Link

<< Home