It’s the Feature Countdown…

Like last year around NAB, this time Adobe announced the preview of the upcoming release of its Digital Video Applications (DVA) which include Premiere Pro, After Effects, SpeedGrade, Media Encoder, Prelude and Audition.

You can read the general overview of the new features in a few places (Creative Cow, fxguide, Studio Daily), various Adobe blogs give you a complete overview of the upcoming features, Scott Simmons at ProVideoCoalition gives a more indepth look into the new features of Premiere Pro itself, and for those visually oriented, Josh from reTooled.net prepared a video. Here as usual I will attempt to give you a bit more nuanced view with a possible long-term impact on the real world workflows. I also hope to showcase some of the most important ones in more detail pretty soon, and our favorite NLE will enjoy a separate detailed post. Right now let’s take a view from a few stories high.

The overall theme of this upcoming release is something that I would describe with a single word: “Finally…”. Finally we have a number of features that many have been asking for – sometimes for years. I know it may sound a bit ungrateful, and it’s no secret that we all would love to have these from the very beginning. But this release seems to really deliver – features galore, big and small, all to make your life as an editor easier. Therefore, when I use the word “finally”, it means that it is really there, without “buts” and “howevers”, and with full appreciation of the required time and resources, and a long road that all had to travel to arrive at this point.

One of the more interesting developments in this cycle is the new version of Prelude with its ability to trim clips in the rough cuts (finally), and tagging. The first feature makes it feasible to do the rough cuts in Prelude without the need to precisely mark the subclips, or to adjust the selections on the fly. We can finally do the quick assemblies, selects, what have you, and we can be as OCD about them, as we want.

Tagging, the second feature, has tremendous potential, similar to Keywords Collections in Final Cut Pro X. The ability to apply tags during playback using a fully customizable, state-of-the-art, JSON driven Tag Panel or to apply several tags to a single marker makes logging much easier and much faster. This is precisely what was missing in the metadata workflow between Adobe applications. Therefore we finally have a non-hierarchical way to quickly and consistently annotate the source footage. In the preview software versions that I had access to, tags are currently searchable only in Prelude, and only on the clip basis via the search box in the project panel. Hopefully, this is going to trickle down at least to Premiere, which can already see the tags, but can’t yet look for them or show them in any meaningful way, and that the searching capabilities will become more advanced.

On a technical note, tagging is implemented via an interesting extension of Flash Cue markers, and I will definitely elaborate on it soon. Right now, if you for some reason feel unhappy that the FLV format is being totally ditched from Adobe video applications in this upcoming release, you can comfort yourself with the knowledge, that not everything Flash-related is going to waste.

There are a few other new features that span throughout several CC applications. For one, Premiere and SpeedGrade now sport the Master Clip Effects (MCE). The idea is quite simple – when you apply an effect to a given clip, not to its instance in the timeline, it is applied as a separate “layer”, so to speak, below all timeline effects, and ripples through all instances of the master clips on all timelines in the project. It’s a great feature, especially useful with color correction, and the fact that SpeedGrade can also work in this mode, makes it even better. Here however I am not saying “finally”, because there seem to be a few quirks associated with it. I will elaborate on them in a separate Premiere Pro note, perhaps even wait for the release version of the software to see how these issues are resolved.

Regrettably, Master Clip Effects do not apply to sequences – yet? – which would make them totally awesome. This, and the possibility to render and replace such modified master clip or a sequence to the codec of one’s choosing. But even without it, it’s a killer.

The mechanism used for MCE allowed also Adobe to create the Live Text Templating for After Effects compositions in Premiere. Here we can see the roll-out of a 1.0 release of a feature, which covers only the most basic – though also the most frequently requested – ability to edit a selected text layers of Dynamically Linked AE comps straight in Premiere Pro. It’s a boon for all lower thirds, titles and similar graphics. It’s pretty simple to work with – you mark your composition as a Premiere template in the comp settings, and then any unlocked text layer in this composition or pre-comps (very clever!) is going to be accessible in Premiere in the same way MCEs are – by using match frame on the timeline clip or opening it in the Source Monitor, and then looking up the Effect Control Panel.

The drawback of Live Text Templates using MCE mechanism is that, if you want to duplicate this composition in the timeline, it will duplicate the clip in the Project Panel, similarly to how Titles currently work. This perhaps is not the most elegant solution – ideally we’d only have a single template, and only adjust the effects on the instances in the timeline – but it does work, and the link to the original AE composition remains, you can easily change anything in it in After Effects, and the changes will propagate to Premiere. Of course, it is not the final word in terms of templating. If you have comments or ideas, make sure to send them to Adobe, I know they are listening.

Next, both Premiere Pro and After Effects can now contain their effects using masks. Here I can definitely say “finally!”, at least when it comes to Premiere. Finally you can create a vignette or limit your color correction using a mask. Such masks can also be tracked, using the same technology that was already available in After Effects for past half a year. It works and it’s great. There is a minor limitation – currently there are only two types of masks present in Premiere – elliptical or polygonal. No bezier shapes or variable feathering, to access these you still need to go to After Effects. But these two types of masks will suffice for the usual 80% of cases, especially given the controls to expand or uniformly feather the mask.

Interestingly, the implementation in Premiere Pro seems much easier and much more elegant than its After Effects counterpart. While masks in Premiere are shown under each effect, AE requires you to navigate your timeline, make sure your effects masks do not interfere with masks that you apply to the layer, and so on. Quite a few inelegant steps on the way. The only positive side is that you can reuse these masks for multiple effects, which is not possible in Premiere. But the masks do carry over when you send a clip to AE via Dynamic Link, which is also a welcome addition.

Thanks to these features suddenly a lot of things became much easier to achieve in Premiere itself, without the use of Dynamic Link or After Effects round-tripping, especially in the Motion Graphics area. The only large things currently missing here are Pixel Motion algorithm for speed changes, and Motion Blur. About the impact of this release on the future of Creative Impatience plugins I’m going to elaborate in another note.

One of the best features in the upcoming Premiere Pro is the improved performance of the search field in the project panel. Yes, it seems tiny in comparison to all other loudly touted upgrades, and it’s more of a fix, than a marketable feature. But it means that finally we will be able to use the search box in larger projects, and that is no small change. On similar note, marker names will finally be visible in the marker panel, and can be searched for. For the list of all the features see Premiere’s blog, and an upcoming post on this website.

Astute readers and long time users of Premiere had most likely already noticed one feature that is sorely missing to complete the “finally” list. Unfortunately, Project Manager does not get an update in the upcoming release, and we will not be able to easily transcode or trim our projects either for archive or exchange. If I had to name a major disappointment, this would be the one. Here’s to hope that we’ll see some working solution soon – IBC perhaps?

But enough complaining. On another front, SpeedGrade seems to have finally received support for AMD GPUs in the Direct Link mode, including dual GPUs – owners of new Mac Pros rejoice – a new YUV vectroscope that works like every other vectroscope on the planet, and sports a decent graticule, a control to clamp the scopes instead of resizing them, and vertical sliders supplementing the offset/gamma/gain rings, easier to access and manipulate with a mouse. Some keyboard shortcuts became unified with the ones present in Premiere, and you can also enable or disable any track in the timeline in the Direct Link mode, which previously was impossible, making it easier to consider various grading options or simply hide distracting elements.

Media Encoder can finally be installed separately from other applications, which should make reinstalling and troubleshooting much easier, in case you ever need to do that, and apart from a number of bug fixes it also added support for industry standard AS-11 DPP, which you will never need unless you are delivering Broadcast material to UK, and – perhaps more importantly – encoding unencrypted DCP, which will be helpful if you’re going to submit your great movie to a film festival. Now, if only we had access to DCI P3 color space in Premiere…

Audition received a modest update as well – support for Dolby Digital, multichannel wav files, and some multitrack enhancements that should make your life easier if your sessions stretch vertically enough for you to consider turning your monitor short edge up.

Finally, After Effects enjoys integrated Mercury Transmit for live preview, support for HTML5 third-party panels (can be pretty significant in the long run), some updates to Curves effect (still not compatible with Premiere’s RGB Curves though), and an interesting technology for improving the mattes that you get from Keylight or other keying effects. Both will definitely come in handy, especially since I’m right now involved heavily with Hero Punk project which was shot totally on green screen.

There are also updates to Story and Anywhere, but I can’t meaningfully comment on either.

All in all, it looks like it’s going to be a pretty solid release, centered on Premiere Pro. Dare I say – finally? 😉

The Day I Dreamt About Has Come

dream-fi

My current daily job requires producing about 50-60 minutes of content per month of something that roughly falls into mostly unscripted reality show. Within 30 days we have to prepare the final edit, sound mix, including voice over and music, motion graphics, any potential VFX shots, mostly cleanups, and finally some rudimentary grade and DVD authoring. The time is precious, and short. And sometimes changes have to be introduced a day before, or even on the mastering day.

see more

Adobe Media Encoder Grows Up

ame-fi

Adobe revealed today, that Adobe Media Encoder will receive a few very worthwhile updates, including long awaited GPU acceleration, direct implementation of Premiere Pro engine, and a number of new features. There are two, which are of special interest to me: the so-called mini-pipe – adding new effects such as image overlay, timecode burn-in, or a given SpeedGrade look – and the ability to import FCP XML sequences without the need to pass them through Adobe Premiere. Both have potentially important workflow considerations in the long run.
see more

Exploring Temperature and Tint

temperature-feature

When dealing with footage which was shot at improper white balance, and trying to correct it, I sometimes wished that Premiere had the temperature slider present in Camera Raw or in SpeedGrade. When a friend expressed similar concern, I decided to take my shot at it. After all, it should be relatively simple, right? It’s only moving the pixels towards blue or orange, and in the case of tint, towards magenta or green.

I even found a sample approximate algorithm to calculate the white point at a given temperature, and almost ended up using it. However, after reading on how the proper mixing requires conversion to HSL colorspace due to change in luma value of each pixel, I decided to explore the issue in more detail. It turns out, like with many other issues, that there are differences on what “temperature” exactly means in various software packages. Consider the following images:

original

Original image.

camera-raw-temperature

Camera Raw/Lightroom temperature adjustment set to -100. The image is brighter, and the tint is much stronger, washing out the shadows.

speedgrade-temperature

SpeedGrade’s temperature adjustment at -1.0 (equivalent of -100). The shadows are not washed out, although the image is darker due to clipped blue channel.

Clearly, Camera Raw is brightening the image, and almost looks like it is trying to mix the blue or orange solids with the picture. Perhaps similarly to what Tanner Helland described in the comments to his algorithm, but without the attempt to retain luminance. I find this adjustment not so great, especially for images with rich shadows that get washed out in the process.

On the other hand, the blacks in SpeedGrade are untouched, and it seems that the temperature/tint sliders operate only as gain adjustments, multiplying red and blue (temperature) or all three (tint) channels at the same time by roughly the same amount, and leaving the luma mostly intact except for the places, where the blue channel is clipped.

I even explored playing with gamma on the a and b channels in Photoshop L*ab color space, which directly code the interesting information (a is the tint scale, b is the temperature scale), but these were also not as satisfying as SpeedGrade’s. In the end, I decided to stick with the color correction software.

I experimented for a moment with the formulas and values, but in the end, I turned to Nuke to find how it resolves the issue, because it does provide an immediate numerical output. Finding out the exact adjustments was quite easy. Using grade and expression nodes I was able to mimic what Nuke was doing during temperature or tint adjustments, and came up with very simple formulas.

nuke

A very simple setup in Nuke allows to find the proper formula for handling temperature and tint adjustments to mimic SpeedGrade’s controls.

Implementing them as a plug-in for Premiere was relatively uncomplicated, and took me less time than writing the documentation for it. In fact, I was also able to successfully tackle OpenCL acceleration as well, but this will be incoming in the paid version some time in August.

A Storm Or A Spoon

luma-curve

Update: The 7.1 version due out in October is going to fix the issue altogether. Great job, Adobe!

Being the one to spoil the party is no fun, especially if you like the host, or enjoy the meals. But when your favourite dish was rotten and received only a little ketchup treatment, well… sometimes you have to be vocal about it.

Let me at first say that I love the party. To have an update within a month of the release, that fixes a major multicam bug (which for some reason I have not fallen prey to) and adds plethora of new features that will make life and editing easier is awesome. This is the power of Creative Cloud that a lot of people were talking about. There’s no denying, that the party is well deserved.

If you want to learn of all the new features and improvements to Premiere Pro which come with version 7.0.1 update, take a look at the official Premiere Pro blog or reTooled.net tutorial. They will show you the goodies, and these are plenty.

But unfortunately for me, one issue is not completely resolved. And it’s not for the lack of trying.

I wrote before about a nasty curves issue, and for some reason my post was not received with enthusiasm at the home of Premiere Pro. I really, really hoped it would be resolved in this update, and that I will be able to join the happy fest. Well… it is, and it isn’t.

The good news is that the curves no longer clip superwhites and superblacks on input. Depending on how you use the curves it might or it might not be the solution. If you never move the starting and ending points of the curves from their places, you’re good to go. Also, if you only move them up or down, to reduce the dynamic range, you should rejoice, because it works as it used to as well.

But if you ever move these points to the inside, namely the point on the left to the right, or the point on the right to the left, to add contrast, and you hoped to later recover the clipping, your troubles did not go away. Sometimes they might even be compounded.

Unfortunately the curves still not work as they used to. This example of course is exaggerated to the extreme to make a point.

Unfortunately the curves still do not work as they used to. This example of course is exaggerated to the extreme to make the point.

Because the curves will flatten everything what is beyond the leftmost or the rightmost curve points up until the left or right border. Then they will resume their 45 degree slope. To many it might be a non-issue. To me it is. To me it means that most of my old projects will still have to be rendered out in CS6, and I will have to be careful with the new ones, especially when using Jarle’s grading presets.

I am not happy. Depending on where you sit, this is either a storm in a teacup or a spoonful of tar that spoils the barrel of honey. Unfortunately, I belong to the second group, and it’s no fun at all.

Warning about using RGB and Luma Curves in Premiere Pro CC

curves_feat

Update: The 7.1 version due out in October is going to fix the issue altogether. Great job, Adobe!

Update: The 7.0.1 patch for Premiere Pro CC fixes some of the below mentioned issues, although unfortunately not all of them.

To my great chagrin Premiere Pro CC changed the way curves operate. Right now the curves, both RGB, and Luma, clip the superwhites and superblacks, and there is no interpolation going on after the curves hit 0 or the white level (255 or 1.0). In CS6, the curves followed the general slope, and it was possible to recover some of the “overshot” material. Right now, if you stick to curves, all clipped data is lost.

cs6

Curve's interpolation in Premiere Pro CS6 allowed to recover superwhites or superblacks, and correct the contrast in the same instance.

cc

Premiere Pro CC clamps all superwhites and superblacks, and recovering the detail is not possible with the use of RGB or Luma Curves.

This is completely new, unexpected, and if you ever used curves, it changes your workflow dramatically, even if you don’t know it yet.

It means that you must remove the superwhites and superblacks from the clip before you use RGB curves. It means that if you were like me, using curves to apply the basic correction and contrast in one go, you cannot do it now. You have to first make the signal “legal” – reduce the superwhites and raise the superblacks with for example Fast Color Corrector, so that they fit between the range that curves operate on – RGB scale that is not overshot in either direction, even if you are working in the floating point (max bit depth).

fcc

In Premiere Pro CC you need to use Fast Color Corrector or Three-Way Color Corrector to bring the superwhites back into the RGB scale. Only then you can apply curves, and be sure that you are not loosing data.

It also means that there is no real backwards compatibility within the projects that used curves. Your colors will not be the same, if you had any superwhites in the project. I highly advise you to finish your current projects in CS6, and only then create the new ones in CC, being mindful about the necessity to use Fast Color Corrector before applying curves.

Adobe is aware of this issue, and hopefully some fix will come soon, but while using CC 7.0.0 version of Premiere you need to remember about this very real problem.