Activity › Forums › Adobe Premiere Pro › New color and audio tools for Premiere
-
New color and audio tools for Premiere
Posted by Oliver Peters on April 3, 2018 at 4:41 pmOliver Peters replied 8 years, 1 month ago 3 Members · 5 Replies -
5 Replies
-
Greg Janza
April 3, 2018 at 5:32 pmThe two new features coming in the latest release are potentially very helpful.
Adding color match to the lumetri panel makes a lot of sense. It’s bad news for the RE-match plugin folks but it’s a logical progression for the color panel inside Premiere. And eliminating the creation of new audio files from a Premiere project timeline and instead just linking to the original files when working in Audition is also a major improvement in the Premiere to Audition workflow.
Now I just hope the bugs involved in these new features are minimal.
Windows 10 Pro
i7-5820k CPU
Nvidia GeForce GTX 970
Adobe CC 2018
Renders/cache: Samsung SSD 950 Pro x2 in Raid 0
Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280
Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync -
Oliver Peters
April 3, 2018 at 7:33 pmScott has done his usual great roundup of these features.
– Oliver
Oliver Peters – oliverpeters.com
-
Oliver Peters
April 4, 2018 at 1:16 pmFYI – These have been live since yesterday.
– Oliver
Oliver Peters – oliverpeters.com
-
Jim
April 4, 2018 at 8:08 pmHey Oliver,
Anybody brave enough to try the new updates yet. The last version was pretty buggy. One wonders if the new version fixed those bugs, exchanged the old bugs for new, or combined the bugs into a new and exciting package:-)
I’ve got two projects in cue. Once they’re out the door, I’ll give a look and report back.
Cheers,
Jim
-
Oliver Peters
April 4, 2018 at 9:11 pm[Jim Cunningham] “Anybody brave enough to try the new updates yet.”
I have multiple machines running on it today. So far so good. Not all that impressed with the new color and audio features, though. One of the other editors had his project start to crash when he used ducking (on an iMac Pro). Once he removed the keyframes he was fine again. I didn’t have the same problem on my machine (2013 Mac Pro), but I was only in a test project. Maybe his was a fluke. Maybe not. We’ve both been working on upgraded (not fresh) projects.
– Oliver
Oliver Peters – oliverpeters.com
Reply to this Discussion! Login or Sign Up