Posted on

The Ever-Evolving F55 and F5

The F55 and F5 are really something.  Just when you think you know them, there’s another update!  For over a year now, the F55 and F5 have been steadily making their way on a pre-planned firmware path that continuously adds to what these cameras can do.  No other camera has gestated outside of the factory as long as these have.  Version 3.0 was going to finish the cameras but then 4.0 was announced and the cameras just keep giving!  The number of codecs (XAVC, MPEG50, SR, RAW and now ProRes and DNxHD!), frame rates (up to 180 internal and 240 on R5), and mount options (PL, F, B4, EF, etc.) make the F55 and F5 the most versatile cameras on the market.  It’s that flexibility, however, that can make them a little tricky to learn at first. Version 3.0 has been out for a little while so we’ve had some time to suss it out. We invite you to another F55/F5 demo in our Showroom on Wednesday, March 26th at 12PM to learn more. 3.0 Stand-Out Features: Apply, route, and record a variety of LUTs, e.g., shoot RAW and simultaneously record S-log with or without a LUT baked in on SxS.  You can even use Sony’s free software, Raw Viewer, to create your own 1D LUTs to load into the camera. 2K Center Scan mode is not to be overlooked.  Normally, you’re always using the full Super 35 4K CMOS sensor regardless of what resolution you want to shoot.  Windowing in on the sensor, though, allows the ability to use Super 16mm lenses which offers more choices for look, cost, and weight.  This is a great feature that got a lot of people’s attention. The new color space option, S-Gamut3/S-Log3 offers a more filmic curve that allows more detail in shadows and the application of standard LUTS, not necessarily made by Sony.  S-log 2 allows more information in the highlights, i.e., you can overexpose slightly with 2 and underexpose slightly with 3.

The side panel is now fully functional with quick access to the features you need and word is that 4.0 will even bring the full camera menu there.
-Jason Potz, Engineering,
Posted on

Live Keying with the Sony AWS-750 Anycast Touch

When the new Sony Anycast Touch live switcher showed up here at Rule, no one really knew what to make of it. The knee-jerk reaction to the dual touch screen, Star Trek looking switcher, was a wave of mild curiosity – followed closely by the inevitable “Where are all the buttons!?” See, in the world of live events, switchers usually have switches — physical buttons, knobs, and other touchy-feely things to give the user some satisfying real-world feedback when using the equipment. The new Anycast Touch, as one could assume from its namesake, looks more like an iPad than a switcher – and after you accept the new form factor, it’s awesome. In this post, I won’t be going into every nut and bolt on the Anycast Touch. Instead, I’ll be focusing on one advanced ability — live keying. If you’d like to know more about the overall basic operation, my tips and tricks, and a more in-depth outline of advanced workflows, RSVP to for my Learning Lab here at Rule on March 26th. We’ll be going over a handful of real-world switching situations to acclimate both seasoned vets and users who are new to live event production. In the past, doing live chroma key work has always been a daunting task. Lighting your green or blue screen evenly was absolutely essential to getting a good, passable key – and to a large extent, this is still true today. The Anycast Touch is very forgiving, though. It deals with hot spots and wrinkles fairly well, though spill is something one should always be mindful of. A good rule of thumb is to simply get your talent as far away from that colored backdrop as possible for your framing. The Sony Anycast Touch is unlike any other switcher when it comes to live keys (or anything else, really). The interface for keying will look familiar to any users who have used chroma keying features in any popular NLE. While it isn’t as populated with intricate refining features like Adobe’s UltraKey or Keylight, it’s surprisingly powerful. Sony gives us 3 main sections in the Chroma Key settings:  1) Chromakey, 2) Crop, and 3) Size/Position. I won’t spend too much time on the last 2, as they’re fairly self-explanatory. In the main panel, though, we have some interesting choices. The “Auto” mode is very robust, and often gets it pretty close. When in auto mode, we are given a small white box on our main display to move around (I prefer using a mouse and keyboard when using the Touch, as it makes dragging this box around much easier than using your finger). I find that selecting the darker spots of your green/blue screen produce the best results — though lighting your screen evenly is always recommended. Even so, I’ve gotten some remarkable results from wrinkled and uneven lighting — there is enough forgiveness here for users of all levels to give it a shot. Color Cancel is a great addition by Sony — it is your basic “spill suppression.” Instead of adding magenta to green, though, it simply finds any leftover areas of the sampled color and desaturates them.  This is fantastic for tough keys with fairer skin and lighter hair. I wish there were ways to adjust the amount of hue and luma for the key’s selection, but, even without it, it seems to work very intuitively. Sometimes, if your talent is wearing darker clothing, this can present itself as a fine grey outline. Fiddling with the manual gain and density adjustments is usually enough to get it passable. Disable Colors will help you select as to whether you want to composite your title graphics, or have them overlay as normal. Not much to worry about here – basic rule of thumb is to leave it be unless your titles are behaving strangely. My recommended workflow for keying is to use auto mode to get you in the ballpark – if you’ve lit your screen fairly well, you often won’t need to mess with anything else. If you’re finding issue, switching to manual will save the auto settings, then adjusting the Clip slider is usually enough to get you the rest of the way there. Here’s a photo of the test we set up: I tried to emulate a portable, lower budget situation for users who would be on location, streaming live to the web or to internal monitors. We used a collapsible Chroma Key flex-fill, clamped to a few C-Stands. For lighting, I threw up some Litepanels 1×1’s, with full diffusion and ¼ CTO to keep the greens looking green. For our single key light, I used the Litepanels Ringlite Mini. A small LED light would be a great addition to this set up for some fill light, but I tried to keep things simple. Our camera? Your standard Canon 5D mkIII with a 24-70mm, stopped down to f4. Here’s a still from this setup, with our own Jenn Jennings reading the weather! You can see that even with a very basic set up, you can get a pretty convincing chroma key up and running without too much fuss. Green screen live can be a great tool for corporate productions, broadcast situations, and webcasts. It can also be a great way to easily get a visually interesting interview background when space and budget is limited. In addition to the traditional chroma key situations, one can also use chromakey for using animated titles. The Anycast Touch, at the end of the day, is still a switcher, and switchers are always going to be limited in certain ways. With the Touch, we are unable to import animated graphics into the internal SSD for use in the titling section. Even when exported with an alpha channel, the Touch can’t process it. By using chromakey, however, we are able to circumvent this limitation. We can use the internal media player and chromakey effect to knock out the background, and use live animated graphics. In this way, your graphics are really limited only by your graphic designer’s talents! Here’s a video sample using a gaudy animated lower third I threw together in After Effects. Exported as a simple MP4, I used a highly saturated green as the background. The Touch removes it perfectly on the auto setting, and we’re able to use animations to really raise production value. The added text has been created and faded on using the Anycast Touch title interface. Perfect for sports when you need to throw back to instant replay, probably having two opposing team’s helmets smash into one another and explode. Or maybe a robot doing jumping jacks. You get the idea.  The one drawback to this workflow is that Sony only allows you to have a single media player for internal video at a time — so by using it up on the animation, we can no longer put an internal video behind it at the same time internally. Not the end of the world, or even a common situation, but definitely food for thought. So there you have it. Not so bad, right? With just a flex-fill green screen, a couple lights and a DSLR, you can add tons of production value to both small and large scale productions. I’ll be covering a whole lot more in my Learning Lab on March 26th, so be sure to RSVP: to get the nitty-gritty details on this cool new product. -Alex Enman, Engineer,

Posted on

“Those who cannot remember the past, are condemned to repeat it.”

Let me ask a silly but timely question:  Pretend you were a race car driver in NASCAR. You were in the middle of a race, flying around the track at 190 MPH, and a message popped up on your dashboard that told you that new firmware for your fuel system was available and ready to install, would you click OK?

Historically, meaning as little as a few years ago, editing and post production suites were built and deployed as a completely designed system not unlike a race car.  Under it’s branded and packaged “system” exterior, it was made up of components that, when described individually, were familiar to us.  It had one or many CPUs, operating system, memory, storage and I/O and several specific software applications, waveform/vector scopes and video source/record decks.  In addition, you would certainly have accurate monitoring of audio and video signals, ideally, in an acoustically-treated suite with appropriate lighting and wall color that would not confuse or deceive your visual cortex.

This turnkey package was very tight, in large part because the bits and pieces worked only in a small but specific “compatibility matrix”.  As a result, it was always understood and firmly communicated that you NEVER update software in the middle of a production, you disable Auto-Update (to satisfy the previous requirement) and that you work with and depend upon capable experts before and during planned upgrades. Upgrades, in truth, need to be considered full re-designs in the sense that there is a delicate inter-dependency between all components and interrupting this “matrix” will have a series of consequences, and unless your name is Neo, you may not even realize that the matrix exists! (Sorry, had to throw that in there.) Consequences come in many sizes and shapes.  Some, you may never even notice or feel and some may only effect you if a second or third seemingly unrelated event interacts with the dormant first consequence.  If the majority of customers work only on a stand-alone computer with the most common of add-on devices, then the lowest common denominator challenges or conflicts get addressed and corrected early, often during beta test cycles. Companies like Apple and others have also done a great job intentionally or unintentionally inducing Pavlovian Conditioning with frequent and ever-improving app updates that have taught us that Updates = Good.  Many of us treat these update requests like a new message from a friend, a gift or a present that randomly appears and, best of all, is free!  Why wouldn’t you do it?  Often it corrects and patches flaws and security risks that we didn’t even know existed (until the update told us).  After all, who doesn’t want to keep up with the latest and greatest? But beware, the editing and graphics ecosystem that you have built, however streamlined it appears, is more fragile and requires more planning than a typical computer or smart phone.  Major operating system updates – like Apple Mavericks 10.9 – change a multitude of things, for reasons that have nothing to do with you or your business. Here is an example advisory for some high speed, external media readers that came out upon the release of Apple Mavericks: WARNING Qio E3 is not currently compatible with OS X 10.8.5 and 10.9 (Mavericks). Sonnet is working on a fix for this issue. Qio E3 is compatible with OS X 10.8.0 through 10.8.4 when using Qio E3 software v1.2.1c and later. Until a new driver is ready (1.2.2), do not upgrade your computer’s OS to 10.8.5 or 10.9.” Personally, I do not blame 3rd party board and hardware manufacturers for this.  A computer is a complex beast, designed for many markets and many uses.  In our high performance, time sensitive, video production world, we depend on our computers to connect with dozens of speciality devices.  Somehow, we have collectively come to expect that all parties involved have been handed a rule book that defines accurately and immediately, all use cases and all code corrections.  In truth, companies like Apple are famous for not providing detailed information about code or methodology changes that may break or change the way pieces or components behave.  There is limited access for developers to beta OS releases and it is next to impossible for a hardware company to run structured quality control tests on all possible configurations. So, in summary, I offer a few polite words of caution: • DO NOT be tempted to hit that Upgrade, Update or Download button without first KNOWING why you need it and what it might affect. • PLAN for upgrades with production and business calendars in mind.

• SCHEDULE downtime and testing as part of the upgrade.

• BACKUP the current system before an upgrade.

• TEST all of the devices and software after the upgrade.

Thanks for listening.  I hope it helps. Tom Talbot,