August, 2013 Archives
Premiere Pro CC is built to be a rich, powerful video editing application that allows editors to meet the demands of modern post-production – quickly and intuitively, with minimal interruptions and maximum creativity. The Premiere Pro team focuses our priorities for each release by listening closely to problems and desires of editors. Of course, editors who cut with Premiere Pro are always excited when we release groundbreaking new features like the Mercury Playback Engine, Dynamic Link to After Effects, or the Lumetri Deep Color Engine; but it’s often the enhancements, the editorial polish that really make editors happy, make you say “Yes! This will make my workflow so much smoother!” It’s these refinements that we call JDI features – ‘Just do it’.
Between every engineering sprint (a several week period when the Premiere Pro team is developing features) we take short breaks to focus solely on JDIs. So how do we define a JDI? What elements make a feature request fall into the “this is gonna take a while” bucket or the “we should just do this” (JDI) bucket? The definition is very simple:
A JDI is a feature that can be fully implemented and fully tested in one day.
Some examples of recent JDIs would be –
• New keyboard shortcut or button for existing functionality – like the shortcut added in the July 2013 release to toggle between Source and Program monitors.
• Visual cues to ease the interpretation of your media – like through edit indicators added in the June 2013 release, or offline audio showing red that was added in the July 2013 release.
• Preferences to customize user experience – like the preference to not automatically jump to the beginning of the timeline or clip after playback has reached the end added in the July 2013 release.
The great thing about Creative Cloud is that now we can deliver JDIs faster and more frequently than ever before – we put time into engineering both the groundbreaking features as well as revisiting and continually refining the editing experience based on your feedback to help you work faster and more efficiently. So keep telling us what you think – we’re listening!
We asked. You answered. Many of the JDI feature requests submitted are already IN the October 2013 release of Premiere Pro, now you have the chance to help us decide one more feature that will be coded at the IBC Show and included as well. Vote via Twitter from Monday, Sept 9th at 6pm PST to Tuesday, Sept 10th at 6pm PST, including @AdobePremiere and #myJDI with the number/name of the feature YOU want in the next release:
- Render Multiple Sequences: Ability to highlight sequences in a bin, and choose to render them all – not encode, just render any effects on those timelines.
- Add Effect Preset: Double clicking an Effect Preset adds it to the selected clip instead of editing the preset. Making them the same behaviour as adding the base effect or plugin keeping workflow consistent.
- In/Out Ripple Delete: Ripple Delete works on in/out ranges not just selection
- Add Keyframe Shortcut: An Add Keyframe keyboard shortcut.
- Toggle All Target Shortcut: Ability to toggle target all tracks on and off at the same time.
If you have ideas for features you think are a little more involved than what would be considered a JDI you can always submit feature requests here.
The Premiere Pro CS6 (6.0.5) bug-fix update has been released, which addresses an issue with the Premiere Pro CS6 (6.0.4) update. This update is recommended for all users.
To install the update, choose Help > Updates in Premiere Pro CS6.
The update will show up in Adobe Application Manager (or Adobe Creative Cloud for members). Please restart the Application Manager or Creative Cloud application if you aren’t seeing the update.
A summary of the key issues resolved in the Premiere Pro CS6 (6.0.4) update is below.
- Spanned AVCHD clips could sometimes play back incorrectly.
- Smart rendering could sometimes cause segments to play back in the wrong order or incorrectly.
- Smart rendering progress could sometimes stall and become unresponsive.
- Premiere Pro could sometimes crash while the user was editing a growing QuickTime file.
- When importing a Final Cut Pro XML file, audio clips could sometimes incorrectly import with a level of -∞.
The Premiere Pro CS6 (6.0.5) update fixes a problem with the setting of In and Out points in the Source Monitor. Because updates are cumulative, installing the current Premiere Pro CS6 (6.0.5) update gives you the fixes in the Premiere Pro CS6 (6.0.4) update, too.