Adobe Creative Cloud Jumps Ahead to 2017

Adobe CC 2017 with a focus on VRCredit: Adobe
The newest full revision of Adobe Creative Cloud brings VR and HDR into Premiere and gives a glimpse into the future of social video creation.

Some people wish they could have skipped 2016 altogether, so Adobe did, going straight from CC 2015 to CC 2017 with the newest revision of Creative Cloud, out this week. Many of the features were first discussed back at IBC in September, but they are now live for the public, and their release comes with the beta release of a Social Publishing Panel that should solve some social media headaches.

This revision focuses heavily on making VR integration and creation as easy as possible in Premiere, and adds a new set of 3D modeling tools to After Effects. There are also refinements in the user interface, with revised icons and an easier tool for editing shortcuts, which should make it easier than ever before to customize the interface. For enterprise Creative Cloud clients, there is the new Team Projects feature. This shares media on the cloud for a variety of editors to work on simultaneously, which could potentially move in on Avid's dominance of multi-editor projects.

Adobe Team ProjectCredit: Adobe

Premiere has integrated a new set of controls for dealing with HDR video that should be interesting for those moving into the format. As more monitors are capable of displaying high dynamic range imagery, it's rapidly becoming a delivery spec that filmmakers should have a handle on, and it is good to see the capabilities being built straight into Premiere.

Premiere HDR controlCredit: Adobe

This release also comes with a new beta set of social tools that are currently invite-only, with plans to go wide. For now, paid Creative Cloud members can apply for an invitation here. This toolset offers the ability to manage thumbnails, metadata, keywords, and tracking directly from the Social Publishing Panel, making it easy for filmmakers to maintain consistency and quality as they post across a variety of social networks.

The  Strategic Recommendations for Peak Performance analyzes how your work performs on social networks and uses that history to make recommendations for future timing.

One interesting feature of the social tools is Strategic Recommendations for Peak Performance, which will analyze how your work performs on social networks and use that history to make recommendations for future timing and metadata decisions that might help your future posts perform better. While this will be somewhat useful, especially in helping you identify what time of day or day of the week is the best for your particular audience (and schedule your posts to go live at these times in advance), the social landscape is constantly evolving and it can be hard to separate the signal from the noise when analyzing why a previous video had good engagement. Maybe it was the time of day or your keyword choice, or maybe it was just a great video with compelling, dramatic content.

The recommendations should be taken with a grain of salt, but having a single panel that allows for pretty sophisticated control across platforms is pretty cool, and a great indicator of the future of where video post is going. Even if you aren't a social media celebrity, social is increasingly part of the audience engagement element for every filmmaker, and making it easier to release deleted scenes, BTS videos, or other promotional materials while you are working will be useful to a lot of people.

As always, Adobe projects don't travel backwards in time very well. If you are collaborating with a team, and are not an enterprise client using Team Projects but just a normal filmmaker sharing a hard drive and project files, make sure everyone upgrades at once. Otherwise, handing projects back and forth to team members won't work. You'll be asked to update the project file to a new version when opening it in CC 2017, and it won't open in CC 2015. While the upgrade is free as part of the subscription, your collaborator might have a good reason (like system compatibility) to be waiting to upgrade. If you're a solo auteurs, however, there should be no reason to hold off on your upgrade.     

You Might Also Like

Your Comment


Might want to add that it's best to hold off updating if you're in the middle of a project.

November 4, 2016 at 12:50PM

Gareth Ng

This has always been and always is the case. Never update in the middle of an important project!

November 4, 2016 at 1:05PM

Wisse Stolk

I don't know how long this has been a feature, but I just learned about it. If you click update, then click on advanced, there is an option to keep the old version of the app as well as the new one. This way you can test the new features while not worrying that it'll break in the middle of a project. From Adobe's Site: "By default, when you install a new Creative Cloud 2017 app, it will remove the previous versions of the app on your computer. If you want to keep your previous versions installed, click Advanced Options and deselect the Remove old versions checkbox in the update confirmation dialog box."

November 4, 2016 at 1:53PM, Edited November 4, 2:01PM

Michael Trest
Multimedia Developer

Or altogether. This release is terrible. On the first day of use, I've found that overlays on the source & program viewers don't work most of the time, and glaring rendering defects with the title generator aren't fixed.

As usual, Adobe wastes time adding stupid gimmicks instead of fixing bugs that prevent GETTING WORK DONE.

Not to mention: If you can't design a file format that can handle incremental changes and new features while degrading gracefully on older versions, you're an incompetent software developer. The reality for Adobe is probably a combination of two things: incompetence and an urge to screw customers over by intentionally "breaking" project-file compatibility.

But hey, while we're NOT getting work done, we can "track the performance" of our old crap on "social networks." Because THAT belongs in an editing suite.

November 12, 2016 at 6:38PM, Edited November 12, 6:39PM

David Gurney

I'm going to wait to update Premiere. Their last release finally became stable for me after 2-3 years of nothing but nonstop bugs, freezes, unresponsive keys (like the entire spacebar/play button) and constant crashing. I do not need VR/HDR right now and don't feel like risking my system at this point just to gain those features. I wish Adobe would dedicate every other year to stabilizing Premiere instead of constantly adding new features that introduce bugs and quirks. This yearly release model pushes their developers to the wall and I think the software suffers because of it.

November 4, 2016 at 1:10PM

Director, Cinematographer

This latest release is a perfect example. Talk about dog shit.

November 12, 2016 at 6:40PM

David Gurney

Sorry, but I'm not into the subscription Adobe for me....

November 4, 2016 at 5:19PM

Ed Wright
Director, DP, Writer

I'll wait for the first update after most bugs are indentified :-p
I always waited for the .1 updates since CS2

Better VR tools: yeah!

November 4, 2016 at 6:56PM

Director, DOP, Writer, Editor, Producer

I took the plunge and updated. So far I can't report any bugs or drop in performance so that's good. CUDA still doesn't work properly with my MacBook Pro though. Loads of graphical glitches and weirdness. I've always had to use OpenCL

November 5, 2016 at 2:42AM

Liam Martin
DP, editor, part time director

Hey what MacBook Pro do you own? 2012, 2013 or 2015. What's your spec? I have gfx glitches mostly when in the color workspace.

November 6, 2016 at 1:00AM

Olufemi Bamigbetan
Director of Photography, Web Enthusiast and Animation buff

I did the update for Premiere Pro, and it's not very nice. It seems to have some glitches indeed and I don't posses the right vocabulary to pinpoint the problem which is very annoying for me and for the people trying to help me out. So, just wait for the update for this one. Really.

November 14, 2016 at 10:42AM, Edited November 14, 10:42AM

Gaétan Verdikt
film student

The same project render 64% slower on CC 2017 vs. CC 2014 (the last version to support multiprocessing.
Has anyone else seen this difference?? (see article below)

November 17, 2016 at 6:18PM, Edited November 17, 6:19PM