4K is kinda meh

df1716_4k-native_main

Lately I’ve done a lot of looking at 4K content. Not only was 4K all over the place at NAB in Las Vegas, but I’ve also had to provide some 4K deliverables on client projects. This has meant a much closer examination of the 4K image than in the past.

First, let’s define 4K. Typically the term 4K applies to either a “cinema” width of 4096 pixels or a broadcast width of 3840 pixels. The latter is also referred to as QuadHD, UltraHD or UHD and is a 2x multiple of the 1920-wide HD standard. For simplicity’s sake, in this article I’m going to be referring to 4K, but will generally mean the UHD version, i.e. 3840 x 2160 pixels, aka 2160p. While 4K (and greater) acquisition for an HD finish has been used for awhile in post, there are already demands for true 4K content. This vanguard is notably led by Netflix and Amazon, however, international distributors are also starting to request 4K masters, if they are available.

In my analysis of the images from various 4K (and higher) camera, it starts to become quite obvious that the 1:1 image in 4K really isn’t all that good. In fact, if you compared a blow-up from HD to 4K of that same image, it becomes very hard to distinguish the blow-up from the true 4K image. Why is that?

When you analyze a native 4K image, you become aware of the deficiencies in the image. These weren’t as obvious when that 4K original was down-sampled to an HD timeline and master. That’s because in the HD timeline you are seeing the benefit of oversampling, which results in a superb HD image. Here are some factors that become more obvious when you view the footage in its original size.

1. Most formats use a high-compression algorithm to squeeze the data into a smaller file size. In some cases compression artifacts start to become visible at the native size.

2. Many DPs like to shoot with vintage or otherwise “lower quality” lenses. This gives the image “character” and, in the words of one cinematographer that I worked with, “takes the curse off of the digital image.” That’s all fine, but again, viewed natively, you start to see the defects in the optics, like chromatic aberration in the corners, coloration of the image, and general softness.

3. Due to the nature of video viewfinders, run-and-gun production methods, and smaller crews, many operators do not nail the critical focus on a shot. That’s not too obvious when you down-convert the image; however, at 100% you notice that focus was on your talent’s ear and not their nose.

The interesting thing to me is that when you take a 4K (or greater) image, down-convert that to HD, and then up-convert it back to 4K, much of the image detail is retained. I’ve especially noticed this when high quality scalers are used for the conversion. For example, even the free version of DaVinci Resolve offers one of the best up-scalers on the market. Secondly, scaling for 1920 x 1080 to 3840 x 2160 is an even 2x multiple, so a) the amount you are zooming in isn’t all that much, and b) even numbered multiples give you better results than fractional values. In addition, Resolve also offers several scaling methods for sharper versus smoother results.

In general, I feel that the most quality is retained when you start with 4K footage rather than HD, but that’s not a given. I’ve blown up ARRI ALEXA clips – that only ever existed as HD – up to 4K and the result was excellent. That has a lot to do with what ARRI is doing in their sensor and the general detail of the ALEXA image. Clearly that’s been proven time and time again in the theaters, where files recorded using ALEXAs with the footage in 2K, HD or 2.8K ARRIRAW have been blown up via 4K projection onto the large screen and the image is excellent.

Don’t get me wrong. I’m not saying you shouldn’t post in 4K if you have an easy workflow (see my post next week) to get there. What I am saying is that staying in 4K versus a 4K-HD-4K workflow won’t result in a dramatic difference in image quality, when you compare the two side-by-side at 100% pixel-for-pixel resolution. The samples below come from a variety of sources, including the blogs of John Brawley, Philip Bloom and OffHollywood Productions. In some cases the source images originated from pre-production cameras, so there may be image anomalies not found in actual shipping models of these cameras. Grades applied are mine.

View some of the examples below. Click on any of these images for the slide show. From there you can access the full size version of any of these comparisons.

©2016 Oliver Peters

More LUTs from IWLTBAP

df1316_iwltbap_1

With more cameras shooting in some form of a log or flat color profile and more editing software being able to integrate color look-up tables (LUTs), numerous developers have designed their own LUT packages. Some, like Koji, strive to duplicate the colorimetry of certain film stocks, while others, such as SpeedLooks from LookLabs, create stylized “look” files that give you a range of creative color correction choices.

One new developer offering a package of easy to use LUTs is French filmmaker IWLTBAP. Through the website, you can pick up a comprehensive package of LUTs in the 32x32x32 .cube format, which are compatible with most modern editing and compositing software applications. If you edit in Adobe Premiere Pro CC, the Lumetri Color panel lets you browse and add any .cube LUTs you’ve saved on your hard drives. If you cut in Apple Final Cut Pro X, then the addition of a LUT plug-in, like Color Grading Central’s LUT Utility, enables you to add third-party LUTs to any clip on the timeline.df1316_iwltbap_4

I took these LUTs for a spin and like most LUT packages, they come in a groups. First you have Utility LUTs, which are designed to convert color spaces from log to Rec709 (the standard video color space) or in the opposite direction. These are organized by camera type, since not all manufacturers use the same logarithmic values. Then the color correction or “look” LUTs are grouped into Standard and Log versions.

The Standard LUTs are to be applied to images that are already in Rec709 color space, while the Log versions can be used as a one-step LUT to be applied to generic log images. For example, you could apply both a Log-to-Rec709 Utility LUT and a second LUT from the Standard group to achieve your result. Or simply apply the single Log version to that same clip and end up with similar results. The dual-LUT approach gives you more incremental control over the Log conversion based on camera models, whereas the single-step solution is designed for generic log images. However, both can yield the desired grade, depending on the clip. In addition to the paid LUT package, IWLTBAP offers two Bonus LUTs, which are available as a free download from the website.

df1316_iwltbap_2There are over 80 LUTs in each group and these are organized by color style and number. The numbers don’t really mean anything. In other words, they aren’t an attempt to mimic a film stock number. As you ascend in numbers, the next step is a more aggressive or somewhat different version of the previous. The key is the prefix and suffix for each. These LUT files carry a STD or LOG suffix so you know whether these are from the Log or Standard group. Then there’s a prefix: C for cold, H for hot, W for warm, F for film, and X for creative. Each style has several variations within that general look. For example, the LUT file labelled “F-9490-STD.cube” is a LUT with a filmic curve designed for a Rec709 image.

df1316_iwltbap_7When working with LUTs, it’s often hard to know what result you get until you try it. Then if you don’t like the look, you have to continue to slowly browse through your LUT files – applying each, one at a time – until you get the right look. Often that can lead to a lot of trial and error. The IWLTBAP package ships with lightweight Windows and Mac preview applications, however, the developer warns of some occasional instability on some machines. The easiest solution is to use their web-based LUT previewer. Simply upload a reference JPEG from your clip and then toggle through the LUTs to preview how those will affect the shot.

df1316_iwltbap_6I ran some tests on Blackmagic Design camera footage in both FCPX and Premiere Pro CC and got some really pleasing results. In the case of FCPX, if you use LUT Utility, you have to copy the .cube files into LUT Utility’s Motion Templates folder. This is found under Effects/CGC. Files stored there become visible in the LUT Utility pulldown menu. Note that only the first 50 or so files in that folder can be accessed, so be selective. If you apply two instances of the LUT Utility to a clip, then you can apply a Log-to-Rec709 conversion in the first and then the creative look LUT in the second. This plug-in has a mix slider, so you can adjust the intensity of the LUT to taste. As an effects plug-in, you can also place other effects, such as color correction in-between the two LUT Utility effects as part of that stack of effects. Doing this gives you nice control over color within FCPX with very little overhead on the application’s performance.

df1316_iwltbap_3If you are an FCPX user that has adopted Color Grading Central’s ColorFinale grading tool as your go-to color correction plug-in, then all of this LUT management within the application can be simply handled from the ColorFinale interface itself. Stack layers of LUTs and other color tools all inside the ColorFinale panel. LUT choices can be added or removed using the integrated LUT Manager and then relaunching FCPX to activate them as part of ColorFinale.

If you are a Premiere Pro CC editor, then the latest version was enhanced with the Lumetri Color panel. This control is organized as a stack of color modules, which include two entry points to add a LUT – in the Basic and the Creative tabs. In my testing of the new URSA footage, I applied a Log-to-Rec709 LUT for the URSA in Basic and then one the “look” LUTs, like the free Aspen standard version, in Creative. You still have all the other color control in the Lumetri panel to fine-tune these, including the intensity level of the LUT.

df1316_iwltbap_5LUTs are a creative tool that should be thought of as a stylistic choice. They aren’t an instant fix and shouldn’t be the only tool you use to color correct a clip. However, the LUTs from IWLTBAP provide a good selection of looks and moods that work well with a wide range of shots. Plus the package is very affordable and even more so if you get it after reading this blog! Readers who are interested can get 25% off of the retail price using the discount code DIGITALFILMS. Or by using this direct link.

Last but not least, check out the free, downloadable 4K film grain clip. It’s a ten second ProRes file that can be overlaid or blended to add grain to your shot.

©2016 Oliver Peters

Producing a Short Mini-Doc with the AJA CION

df0516_CION4
AJA surprised the industry in 2014 when it rolled out its CION digital cinema 4K camera. Although not known as a camera manufacturer, it had been working on this product for over four years. Last year the company offered its Try CION promotion (ended in October), which loaned camera systems to qualified filmmakers. Even though this promotion is over, potential customers with a serious interest can still get extended demos of the camera through their regional AJA sales personnel. It was in this vein that I arranged a two-week loan of a camera unit for this review.

I’m a post guy and don’t typically write camera reviews; however, I’m no stranger to cameras either. I’ve spent a lot of time “shading” cameras (before that position was called a DIT) and have taken my turn as a studio and field camera operator. My interest in doing this review was to test the process. How easy was it to use the camera in actual production and how easy was the post workflow associated with it?

CION details

The AJA CION is a 4K digital camera that employs an APS-C CMOS sensor with a global shutter and both infrared-cut and optical low-pass filters. It can shoot in various frame sizes (from 1920×1080 up to 4096×2160) and frame rates (from 23.98 up 120fps). Sensor scaling rather than windowing/cropping is used, which means the lens size related to the image it produces is the same in 4K as in 2K or HD. In other words, a 50mm lens yields the same optical framing in all digital sizes.

df0516_CION_Chellee5The CION records in Apple ProRes (up to ProRes 4444) using a built-in Pak media recorder. Think of this as essentially an AJA KiPro built right into the camera. Since Pak media cards aren’t FAT32 formatted like CF or SD cards used by other cameras, you don’t run into a 4GB file-size limit that would cause clip-spanning.  You can also record AJA Raw externally (such as to an AJA KiPro Quad) over 3G-SDI or Thunderbolt. Video is linear without any log encoding schemes; but, there are a number of gamma profiles and color correction presets.

df0516_CION_prod_1It is designed as an open camera system, using standard connectors for HDMI, BNC, XLR, batteries, lens mounts, and accessories. CION uses a PL lens mount system, because that’s the most open and the best glass comes for that mounting system. When the AJA rep sent me the camera, it came ready to shoot and included a basic camera configuration, plus accessories, including some rods, an Ikan D5w monitor, a Zeiss Compact Prime 28mm lens, 512GB and 256GB solid-state Pak media cards, and a Pak media dock/reader. The only items not included – other than tripod, quick-release base plate, and head, of course – were camera batteries. The camera comes with a standard battery plate, as well as an AC power supply.

Learning the CION

The subject of this mini-doc was a friend of mine, Peter Taylor. He’s a talented luthier who builds and repairs electric and acoustic guitars and basses under his Chellee brand. He also designs and produces a custom line of electric guitar pedals. To pull this off, I partnered with the Valencia College Film Production Technology Program, with whom I’m edited a number of professional feature films and where I teach an annual editing workshop. I worked with Ray Bracero, a budding DP and former graduate of that program who helps there as an instructional assistant. This gave me the rest of the package I needed for the production, including more lenses, a B-camera for the interview, lighting, and sound gear.

Our production schedule was limited with only one day for the interview and B-roll shots in the shop. To augment this material, I added a second day of production with my son, Chris Peters, playing an original track that he composed as an underscore for the interview. Chris is an accomplished session musician and instructor who plays Chellee guitars.

df0516_CION_prod_2With the stage set, this provided about half a day for Ray and me to get familiar with the CION, plus two days of actual production, all within the same week. If AJA was correct in designing an easy-to-use cinematic camera, then this would be a pretty good test of that concept. Ray had never run a CION before, but was familiar with REDs, Canons, and other camera brands. Picking up the basic CION operation was simple. The menu is easier than other cameras. It uses the same structure as a KiPro, but there’s also an optional remote set-up, if you want a wireless connection to the CION from a laptop.

4K wasn’t warranted for this project, so everything was recorded in 2K (2048×1080) to be used in an HD 2.35:1 sequence (1920×817). This would give me some room to reframe in post. All sync sound shots would be 23.98fps and all B-roll would be in slow motion. The camera permits “overcranking”, meaning we shot at 59.94fps for playback at 23.98fps. The camera can go up to 120fps, but only when recording externally in AJA Raw. To keep it simple on this job, all recording was internal to the Pak media card – ProResHQ for the sync footage and ProRes 422 for the slow motion shots.

Production day(s)

The CION is largely a “what you see is what you get” camera. Don’t plan on extensive correction in post. What you see on the monitor is typically what you’ll get, so light and control your production set-up accordingly. It doesn’t have as wide of a dynamic range as an ARRI ALEXA for example. The bottom EI (exposure index) is 320 and that’s pretty much where you want to operate as a sweet spot. This is similar to the original RED One. This means that in bright exteriors, you’ll need filtering to knocking down the light. There’s also not much benefit in running with a high EI. The ALEXA, for instance, looks great at 800, but that setting didn’t seem to help the CION.

df0516_CION_Chellee13_smGamma profiles and color temperature settings didn’t really behave like I would have expected from other cameras. With our lighting, I would have expected a white balance of 3200 degrees Kelvin, however 4500 looked right to the eye and was, in fact, correct in post. The various gamma profiles didn’t help with clipping in the same way as Log-C does, so we ultimately stayed with Normal/Expanded. This shifts the midrange down to give you some protection for highlights. Unfortunately with CION, when highlights are clipped or blacks are crushed, that is actually how the signal is being recorded and these areas of the signal are not recoverable. The camera’s low end is very clean and there’s a meaty midrange. We discovered that you cannot monitor the video over SDI while recording 59.94-over-23.98 (slow motion). Fortunately HDMI does maintain a signal. All was good again, once we switched to the HDMI connection.

CION features a number of color correction presets. For Day 1 in the luthier shop, I used the Skin Tones preset. This is a normal color balance, which slightly desaturates the red-orange range, thus yielding more natural flesh tones. On Day 2 for the guitar performance, I switched to the Normal color correction preset. The guitar being played has a red sunburst paint finish and the Skin Tones preset pulled too much of the vibrance out of the guitar. Normal more closely represented what it actually looked like.

df0516_CION_Chellee4During the actual production, Ray used three Zeiss Super Speed Primes (35mm, 50mm, and 85mm) on the CION, plus a zoom on the Canon 5D B-camera. Since the locations were tight, he used an ARRI 650w light with diffusion for a key and bounced a second ARRI 150w light as the back light. The CION permits two channels of high-quality audio input (selectable line, mic, or +48v). I opted to wire straight into the camera, instead of using an external sound recorder. Lav and shotgun mics were directly connected to each channel for the interview. For the guitar performance, the amp was live-mic’ed into an Apogee audio interface (part of Chris’ recording system) and the output of that was patched into the CION at line level.df0516_CION_Chellee8

The real-time interview and performance material was recorded with the CION mounted on a tripod, but all slow motion B-roll shots were handheld. Since the camera had been rigged with a baseplate and rods, Ray opted to use the camera in that configuration instead of taking advantage of the nice shoulder pad on the CION. This gave him an easy grasp of the camera for “Dutch angles” and close working proximity to the subject. Although a bit cumbersome, the light weight of the CION made such quick changes possible.

Post production

df0516_CION_FCPX_2As an editor, I want a camera to make life easy in post, which brought me to Apple Final Cut Pro X for the finished video. Native ProRes, easy syncing of two-camera interviews, and simple-yet-powerful color correction makes FCPX a no-brainer. We recorded a little over three hours of material – 146 minutes on the CION, 37 minutes on the 5D and 11 minutes on a C500 (for two pick-up shots). All of the CION footage only consumed about 50% of the single 512GB Pak media card. Using the Pak media dock, transfer times were fast. While Pak media isn’t cheap, the cards are very robust and unless you are chewing through tons of 4K, you actually get a decent amount of recording time on them.

I only applied a minor amount of color correction on the CION footage. This was primarily to bring up the midrange due to the Normal/Expanded gamma profile, which naturally makes the recorded shot darker. The footage is very malleable without introducing the type of grain-like sensor noise artifacts that I see with other cameras using a similar amount of correction. Blacks stay true black and clean. Although my intention was not to match the 5D to the CION – I had planned on some stylized correction instead – in the end I matched it anyway, since I only used two shots. Surprisingly, I was able to get a successful match.

Final thoughts

df0516_CION_Chellee6The CION achieved the design goals AJA set for it. It is easy to use, ergonomic, and gets you a good image with the least amount of fuss. As with any camera, there are a few items I’d change. For example, the front monitoring connectors are too close to the handle. Occasionally you have to press record twice to make sure you are really recording. There’s venting on the top, which would seem to be an issue if you suddenly got caught in the rain. Overall, I was very happy with the results, but I think AJA still needs to tweak the color science a bit more.

In conjunction with FCPX for post, this camera/NLE combo rivals ARRI’s ALEXA and AMIRA for post production ease and efficiency. No transcoding. No performance hits due to taxing, native, long-GOP media. Proper file names and timecode. A truly professional set-up. At a starting point of $4,995, the AJA CION is a dynamite camera for the serious producer or filmmaker. The image is good and the workflow outstanding.

Click this link to see the final video on Vimeo.

Originally written for Digital Video magazine / Creative Planet Network

©2016 Oliver Peters

Rampant Design Tools

df1215_rampant_1

Many editors are on the constant journey for just the right, cool set of plug-ins. By doing so, they often lock themselves into a single host application and often even a single machine to which the plug-ins have been licensed. If that sounds familiar and you are looking for an alternative, then moving to a package of drag-and-drop effects is the way to go. One of the best developers for such effects is Rampant Design Tools.

df1215_rampant_3_smRampant was founded by veteran visual effects artist Sean Mullen, so the effects have been created from the standpoint of what actually works. The beauty of these drag-and-drop effects is that you can use them with any nonlinear editing or compositing application, regardless of whether this is on Mac or Windows. As long as the system is running QuickTime and includes a playback component for Apple ProRes codecs, you are ready. Since the actual effects are media files, they can be archived with the project and moved between systems, without any need to license a plug-in on another machine.

df1215_rampant_6_smThe Rampant Design Tools website offers a lot of options for how to purchase the effects, but their latest endeavor is Studio Essentials, Volume 1 and 2. These include paint effects, film grunge, distortion, flares, light transitions, fire, smoke, bokeh, snow, dust, and so much more. Nearly all of these elements originate from real and not synthetic footage, which Rampant has actually produced using RED cameras. The effects packages are available in 2K, 4K, and 5K resolutions. Even if you are only working in HD, you might still want a 4K package, because it permits you to reframe the effect to get a unique look, rather than by simply dropping in a stock effect “as is”. The elements are designed to be modular. For instance, you can build up layers of the distortion elements to create a different look. The files come as Apple ProRes 4444 media that works well when keyed or composited using blend modes. By combining, reframing, and adjusting blend modes, you avoid the rut of effects that can’t be modified or plug-in presets.

Rampant Drives

df1215_rampant_4_smThese collections are large enough, that delivering a 4K version of one of the Studio Essentials volumes would be unwieldy as DVD-ROMs or as a download. Instead, Rampant Design Tools sells these complete with their “Rampant Drives”. These are 4TB, USB 3.0 drives containing the complete volume. When you purchase the collection with this delivery option, you may select either Mac or PC formatting. Simply plug it in and start using the effects straight from the drive. Although there is no technical limitation to moving the files around on a SAN, simultaneous shared use is prohibited by the EULA. It states that the contents may only be used on one computer at any one time.

df1215_rampant_9_smAs there are a lot of effects in the contents of each volume, Rampant includes a PDF preview file for each set of effects. This is a quick starting point to decide which effects group to explore, without having to bring everything into your edit project at once. These PDFs can also be downloaded from the website, if you are trying to decide what to purchase. Effects may be purchased as part of a complete Studio Essentials volume or by individual categories in 2K, 4K or 5K sizes. That may still be a bit much for many users, so Rampant also offers a smaller set of HD effects for $29 each through its BudgetVFX companion site.

Pieces and Parts

df1215_rampant_2_smMost of the effects can be used as a single transition or overlay effect, but some in the Studio Essentials collections have been designed as toolkits. For example, there’s the Monster Toolkit, which is intended as a drag-and-drop creature kit. It contains over 1500 elements (stored as Photoshop files), made up of various body parts, such as eyes, ears, mouths, skin textures, and so on. The download size is a whopping 35.6 GB simply for that kit! One of the newest collections is a set of organic paint effects. This set includes 62 effects clips and features a wide range of real paint drip and splatter effects, which will easily blend with video using Overlay or Multiply modes.

df1215_rampant_8_smTo use the effects in an NLE, you would typically place the clip on a higher track above your main video. In FCP X this would be as a connected clip over the primary storyline. A transition effect would be positioned so that the meatiest part of the effect clip would be lined up over the cut to hide it. This is particularly true of lens flare and light blast transitions where the center of the clip often completely fills the screen. This technique has been used for years by After Effects compositors to add a transition between clips on separate layers.

Letting the effect control your video

df1215_rampant_7_smA particularly cool trick that Mullen has posted as one of his tutorials (youtube.com/user/RampantMedia) is how to have the effect actually modify the video beneath. This is an aspect of many plug-ins and something not often associated with stock effects clips. His example uses one of the glitch effect clips. Typically this would be an overlay above the video that would obscure the image, but not necessarily distort or bend it with the effect. If you composite in After Effects, however, you can use its tools to have one layer affect the other. This is accomplished by adding two effects to the base video layer: Stylize – Motion Tile and Distort – Displacement Map. Motion Tile is set to wrap the image as it is stretched and mirrored, so you don’t see black on the edges. Displacement Map is linked to the layer with the glitch effect clip. Displacement is based on channels, so that the lower video is displaced where the effect is visible and not displaced where the glitch clip is black. The last step is to set keyframes for the start and stop of the displacement, so that the video isn’t displaced when you want it to be normal. This trick also works for other effects, such as lens flares.

df1215_rampant_11_smThere are many stock effects vendors on the market. A quick internet search would pull up a page-full. However, most are still offering effects in older codecs or are limited to HD sizes at best. Many don’t offer a wide selection of effects. You might find some great lens flares from one company, but do they also offer fire effects? Quality, breadth of product offerings, and high-resolution is what sets Rampant Design Tools apart from these others. It’s a great way to add eye candy to any production with tools that give you total control in sculpting a unique look.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

The FCP X – RED – Resolve Dance II

df2415_roundtrip2_sm

Last October I wrote about the roundtrip workflow surrounding Final Cut Pro X and Resolve, particularly as it relates to working with RED camera files. This month I’ve been color grading a small, indie feature film shot with RED One cameras at 4K resolution. The timeline is 1080p. During the course of grading the film in DaVinci Resolve 11, I’ve encountered a number of issues in the roundtrip process. Here are some workflow steps that I’ve found to be successful.

Step 1 – For the edit, transcode the RED files into 1080p Apple ProRes Proxy QuickTime movies baking in camera color metadata and added burn-in data for clip name and timecode. Use either REDCINE-X Pro or DaVinci Resolve for the transcode.

Step 2 – Import the proxies and double-system audio (if used) into FCP X and sync within the application or use Sync-N-Link X. Ideally all cameras should record reference audio and timecode should match between the cameras and the sound recorder. Slates should also be used as a fall-back measure.

Step 3 – Edit in FCP X until you lock the cut. Prepare a duplicate sequence (Project) for grading. In that sequence, strip off (detach and remove) all audio. As an option, you can create a mix-down track for reference and attach it as a connected clip. Flatten the timeline down to the Primary Storyline where ever possible, so that Resolve only sees this as one track of video. Compound clips should be broken apart, effects should be removed, and titles removed. Audition clips should be finalized, but multicam clips are OK. Remove effects filters. Export an FCPXML (version 1.4 “previous”) list. You should also export a self-contained reference version of the sequence, which can be used to check the conform in Resolve.

Step 4 – Launch Resolve and make sure that the master project settings match that of your FCP X sequence. If it’s supposed to be 1920×1080 at 23.976 (23.98) fps, then make sure that’s set correctly. Resolve defaults to a frame rate of 24.0fps and that won’t work. Locate all of your camera original source media (RED camera files in this example) and add them to your media bin in the Media page. Import the FCPXML (1.4), but disable the setting to automatically load the media files in the import dialogue box. The FCPXML file will load and will relink to the RED files without issue if everything has gone correctly. The timeline may have a few clip conflicts, so look for the little indicator on the clip corner in the Edit window timeline. If there’s a clip conflict, you’ll be presented with several choices. Pick the correct one and that will correct the conflict.

Step 5 – At this point, you should verify that the files have conformed correctly by comparing against a self-contained reference file. Compound clips can still be altered in Resolve by using the Decompose function in the timeline. This will break apart the nested compound clips onto separate video tracks. In general, reframing done in the edit will translate, as will image rotation; however, flips and flops won’t. To flip and flop an image in FCP X requires a negative X or Y scale value (unless you used a filter), which Resolve cannot achieve. When you run across these in Resolve, reset the scale value in the Edit page inspector to normal from that clip. Then in the Color page use the horizontal or vertical flip functions that are part of the resizing controls. Once this is all straight, you can grade.

Step 6 option A – When grading is done, shift to the Deliver page. If your project is largely cuts-and-dissolves and you don’t anticipate further trimming or slipping of edit points in your NLE, then I would recommend exporting the timeline as a self-contained master file. You should do a complete quality check the exported media file to make sure there were no hiccups in the render. This file can then be brought back into any NLE and combined with the final mixed track to create the actual show master. In this case, there is no roundtrip procedure needed to get back into the NLE.

Step 6 option B – If you anticipate additional editing of the graded files – or you used transitions or other effects that are unique to your NLE – then you’ll need to use the roundtrip “return” solution. In the Deliver page, select the Final Cut Pro easy set-up roundtrip. This will render each clip as an individual file at the source or timeline resolution with a user-selected handle length added to the head and tail of each clip. Resolve will also write a corresponding FCPXML file (version 1.4). This file will retain the original transitions. For example, if you used FCP X’s light noise transition, it will show up as a dissolve in Resolve’s timeline. When you go back to FCP X, it will retain the proper transition information in the list, so you’ll get back the light noise transition effect.

Resolve generates this list with the assumption that the media files were rendered at source resolution and not timeline resolution. Therefore, even if your clips are now 1920×1080, the FCPXML represents these as 4K. When you import this new FCPXML back into FCP X, a spatial conform will be applied to “fit” the files into the 1920×1080 raster space of the timeline. Change this to “none” and the 1080 media files will be blown up to 4K. You can choose to simply live with this, leave it to “fit”, and render the files again on FCP X’s output – or follow the next step for a workaround.

Step 7 – Create a new Resolve project, making sure the frame rate and timeline format are correct, such as 1920×1080 at 23.976fps. Load the new media files that were exported from Resolve into the media pool. Now import the FCPXML that Resolve has generated (uncheck the selection to automatically import media files and uncheck sizing information). The media will now be conformed to the timeline. From the Edit page, export another FCPXML 1.4 for that timeline (no additional rendering is required). This FCPXML will be updated to match the media file info for the new files – namely size, track configuration, and frame rate.

At this stage, you will encounter a second serious flaw in the FCP X/Resolve/FCP X roundtrip process. Resolve 11 does not write a proper FCPXML file and leaves out certain critical asset information. You will encounter this if you move the media and lists between different machines, but not if all of the work is being done on a single workstation. The result will be a timeline that loads into FCP X with black clips (not the red “missing” icon). When you attempt to reconnect the media, FCP X will fail to relink and will issue an “incompatible files” error message. To fix the problem, either the colorist must have FCP X installed on the Resolve system or the editor must have Resolve 11 installed on the FCP X system. This last step is the one remaining workaround.

Step 8 option A – If FCP X is installed on the Resolve machine, import the FCPXML into FCP X and reconnect the media generated by Resolve. Then re-export a new FCPXML from FCP X. This new list and media can be moved to any other system. You can move the FCP X Library successfully, as well.

Step 8 option B – If Resolve is installed on the FCP X machine, then follow Step 7. The new FCPXML that you create there will load into FCP X, since you are on the same system.

That’s the state of things right now. Maybe some of these flaws will be fixed with Resolve 12, but I don’t know at this point. The FCPXML list format involves a bit of voodoo at times and this is one of those cases. The good news is that Resolve is very solid when it comes to relinking, which will save you. Good luck!

©2015 Oliver Peters

Avid Media Composer Goes 4K

df0915_avidmc83_5_sm

Avid Technology entered 2015 with a bang. The company closed out 2014 with the release of its Media Composer version 8.3 software, the first to enable higher resolution editing, including 2K, UHD and 4K projects. On January 16th of this year, Avid celebrated its relisting on the NASDAQ exchange by ringing the opening bell. Finally – as in most years – the Academy Awards nominee field is dominated by films that used either Media Composer and/or Pro Tools during the post-production process.

In a software landscape quickly shifting to rental (subscription) business models, Avid now offers the most flexible price model. Media Composer | Software may be purchased, rented, or managed through a floating licensing. If you purchase a perpetual license (you own the software), then an annually-renewed support contract gives you phone support and continued software updates. Opt out of the contract and you’ll still own the software you bought – you just lose any updates to newer software.

You can purchase other optional add-ons, like Symphony for advanced color correction. Unfortunately there’s still no resolution to the impasse between Avid and Nexidia. If you purchased ScriptSync or PhraseFind in the past, which rely on IP from Nexidia, then you can’t upgrade to version 8 or higher software and use those options. On the other hand, if you own an older version, such as Media Composer 7, and need to edit a project that requires a higher version, you can simply pick up a software subscription for the few months. This would let you run the latest software version for the time that it will take to complete that project.

df0915_avidmc83_1_smThe jump from Media Composer | Software 8.2 to 8.3 might seem minor, but in fact this was a huge update for Avid editors. It ushered in new, high-resolution project settings and capabilities, but also added a resolution-independent Avid codec – DNxHR. Not merely just the ability to edit in 4K, Media Composer now addresses most of the different 4K options that cover the TV and cinema variations, as well as new color spaces and frame rates. Need to edit 4K DCI Flat (3996×2160) at 48fps in DCI-P3 color space? Version 8.3 makes it possible. Although Avid introduced high-resolution editing in its flagship software much later than its competitors, it comes to the table with a well-designed upgrade that attempts to address the nuances of modern post.

df0915_avidmc83_2_smAnother new feature is LUT support. Media Composer has allowed users to add LUTs to source media for awhile now, but 8.3 adds a new LUT filter. Apply this to a top video track on your timeline and you can then add a user-supplied, film emulation (or any other type) look to all of your footage. There’s a new Proxy setting designed for work with high-resolution media. For example, switch your project settings to 1/4 or 1/16 resolution for better performance while editing with large files. Switch Proxy off and you are ready to render and output at full quality. As Media Composer becomes more capable of functioning as a finishing system, it has gained DPX image sequence file export via the Avid Image Sequencer, as well as export to Apple ProRes 4444 (Mac only).

df0915_avidmc83_4_smThis new high resolution architecture requires that the software increasingly shed itself of any remaining 32-bit parts in order to be compatible with modern versions of the Mac and Windows operating systems. Avid’s Title Tool still exists for legacy SD and HD projects, but higher resolutions will use NewBlue Titler Pro, which is included with Media Composer. It can, of course, also be used for all other titling.

There are plenty of new, but smaller features for the editor, such as a “quick filter” in the bin. Use it to quickly filter items to match the bin view to correspond with your filter text entry. The Avid “helper” applications of EDL Manager and FilmScribe have now been integrated inside Media Composer as the List Tool. This may be used to generate EDLs, Cut Lists and Change Lists.

df0915_avidmc83_3_smAvid is also a maker of video i/o hardware – Mojo DX and Nitris DX. While these will work to monitor higher resolution projects as downscaled HD, they won’t be updated to display native 4K output, for instance. Avid has qualifying AJA and Blackmagic Design hardware for use as 4K i/o. It is currently also qualifying BlueFish 444. If you work with a 4K computer display connected to your workstation, then the Full Screen mode enables 4K preview monitoring.

Avid Media Composer | Software version 8.3 is just the beginning of Avid’s entry into the high-resolution post-production niche. Throughout 2015, updates will further refine and enhance these new capabilities and expand high-resolution to other Avid products and solutions. Initial user feedback is that 8.3 is reasonably stable and performs well, which is good news for the high-end film and television world that continues to rely on Avid for post-production tools and solutions.

(Full disclosure: I have participated in the Avid Customer Association and chaired the Video Subcommittee of the Products and Solutions Council. This council provides user feedback to Avid product management to aid in future product development.)

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters

Sorenson Squeeze 10

df0415_sqz10_4_sm

Video formats don’t hold still for long and neither do video codecs used for file encoding. As the industry looks at 4K delivery over the web and internet-based television streaming services, we now get more codecs to consider, too. Target delivery had seemed to settle on H.264 and MPEG-2 for awhile, but now there’s growing interest in HEVC/H.265 and VP9, thanks to their improved encoding efficiency. Greater efficiency means that you can maintain image quality in 4K files without creating inordinately large file sizes. Sorenson Media’s Squeeze application has been an industrial strength encoding utility that many pros rely on. With the release of Sorenson Squeeze 10, pros have a new tool designed to accommodate the new, beyond-HD resolutions that are in our future.

df0415_sqz10_5_smSorenson Squeeze comes in server and desktop versions. Squeeze Desktop 10 includes three variations: Lite, Standard and Pro. Squeeze Lite covers a wide range of input formats, but video output is limited to FLV, M4V, MP4 and WebM formats. Essentially, Lite is designed for users who primarily need to encode files for use on the web. Desktop Standard adds VP9 and Multi-Rate Bundle Encoding. The latter creates a package with multiple files of different bitrates, which is a configuration used by many web streaming services. Standard also includes 4K presets (H.264 only) and a wide range of output codecs. The Pro version adds support for HEVC, professional decoding and encoding of Avid DNxHD and Apple ProRes (Mac only), and closed caption insertion.df0415_sqz10_1_sm

All three models have added what Sorenson calls Simple Format Conversion. This is a preset available in some of the format folders. The source size, frame rate, and quality are maintained, but the file is converted into the target media format. It’s available for MP4/WebM with Lite, and MP4/MOV/MKV with Standard and Pro. Squeeze is supposed to take advantage of CUDA acceleration when you have certain NVIDIA cards installed, which accelerates MainConcept H.264/AVC encoding. I have a Quadro 4000 with the latest CUDA drivers installed in my Mac Pro running Yosemite (10.10.1). Unfortunately Squeeze Pro 10 doesn’t recognize the driver as a valid CUDA driver. When I asked Sorenson about this, they explained that MainConcept has dropped CUDA support for the MainConcept H.264 codec. “It will not support the latest cards and drivers. If you do use the CUDA feature you will likely see little-to-no speedup, maybe even a speed decrease, and your output video will have decreased quality compared to H.264 encoded with the CPU.”

df0415_sqz10_2_smAs a test, I took a short (:06) 4096×2160 clip that was shot on a Canon EOS 1DC camera. It was recorded using the QuickTime Photo-JPEG codec and is 402MB large. I’m running a 2009 8-core Mac Pro (2.26GHz), 28 GB RAM and the Quadro 4000 card. To encode, I picked the default Squeeze HEVC 4K preset. It encodes using a 1-pass variable bitrate at a target rate of 18,000Kbps. It also resizes to a UHD size of 3840×2160; however, it is set to maintain the same aspect ratio, so the resulting file was actually 3840×2024. Of course, the preset’s values can be edited to suit your requirements.

It took 3:32 (min/sec) to encode the file with the HEVC/H.265 codec and the resulting size was 13MB. I compared this to an encode using the H.264 preset, which uses the same values. It encoded in 1:43 and resulted in a 14.2MB file. Both files are wrapped as .MP4 files, but I honestly couldn’t tell much difference in quality between the two codecs. They both looked good. Unfortunately there aren’t many players that will decode and play the HEVC codec yet – at least not on the Mac. To play the HEVC file, I used an updated version of VLC, which includes an HEVC component. Of course, most machines aren’t yet optimized for this new codec.

df0415_sqz10_3_smOther features of Squeeze aren’t new, but are still worth mentioning. For example, the presets are grouped in two ways – by format and workflow. Favorites can be assigned for quick access to the few presets that you might use most often. Squeeze enables direct capture from a camera input or batch encoding of files in a monitored watch folder. In addition to video, various audio formats can also be exported.

Encoding presets can include a number of built-in filters, as well as any VST audio plug-in installed on your computer. Finally, you can add publishing destinations, including YouTube, Akamai, Limelight and Amazon S3 locations. Another publishing location is Squeeze Stream, the free account included with a purchase of Squeeze (Standard or Pro versions only). Thanks to all of these capabilities, Sorenson Media’s Squeeze Desktop 10 will continue to be the tool many editors choose for professional encoding.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2015 Oliver Peters