I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next). As a former FCP7 user myself, Premiere CS6 was a quick and necessary switch (especially after changing the main keyboard shortcuts back to what I was used to). I’ve since gone back to FCP7 on occasion for certain things and I can tell you that I’m so glad I’ve switched. For all the headaches and serious errors that I still get daily/weekly with Premiere Pro CS6, it’s still definitely a big step up. I'm encouraged by staff members like Mitch W. that have expressed confidence that many of these issues will be resolved in the next release. Here is my personal list of “Top 15 issues/fixes” needed in the current Premiere Pro CS6…
(Adobe STAFF...feel free to print this out and hand it to the engineers responsible for making changes 
)
1) The infamous multicam FLAW. Needing no introduction…when you are editing your video in the multicam window and you hit pause or stop Premiere has decided that’s a great time to make a cut on your timeline and also switch angles back to the original angle whether you like it or not. You cannot stop ever while editing multicam without Premiere making these unwanted cuts and angle changes. Awful. Multicam in PPro is otherwise pretty nice, but this issue is terribly counter-productive especially when you are editing longer complex multicam sequences. Imagine if every time you hit pause or stop in the regular timeline it made a cut there and switched clips. Ugh. You get my point.
2) The audio meters/levels do not work while in the multicam window. A staff member in the forums (I think it was you) said this was a bug. Hope it will get fixed. The audio levels work in every other window and its essential to be able to keep an eye on the levels while editing multicam.
3) Ticktime.cpp-207 error. Ugh. What a nightmare. I have confidence that it will be fixed soon. Mitch W. from the forums is my new hero for taking on this error. How to replicate it?…simply have 6 (or 7) or more clips with the warp stabilizer effect added on the same timeline as a nested multicam clip and you get this error upon reopening your project. The more warp stabilizers you use, the more times you’ll have to hit “continue” to get through the error before you can open your project or export it to AME. I deal with this every single day because all my projects use these two elements. Most of my projects I have to hit “continue” on the error message upwards of 350-450 times to open my projects. Gets old fast.
4) Icon View order control. When you display all your clips in icon view instead of a list view (In the project window), there is no metadata to allow you to put the clips in order somehow (or at least maintain the order that you have in the list). There are roundabout workarounds, but c’mon.
5) Warp Stabilizer fixes…it is an AMAZING tool (far, far, far better than smoothcam in FCP7) BUT…it has it’s issues. Since I use hundreds of times/week (no exaggeration) I know it’s functions/flaws really well. The issues with Warp Stabilizer:
a) #3 above
b) Toggle OFF the effect after it’s applied and then hit Analyze again and PPro crashes. (easy to avoid but annoying bug)
c) If a clip is in the middle of stabilizing (not just analyzing…but the final step labeled “analyzing”) when Auto-save comes up…most of the time PPro freezes and crashes.
d) The DEFAULT “method” (in the settings for Warp Stabilizer) should NOT be “Subspace Warp”…it should be “Position, Scale, Rotation”. Why? It’s FAAAAARRRR better and more efficient. 95 out of 100 times it causes MUCH less “wobble” in the final stabilized clips AND most importantly 95 out of 100 times it scales the video less. Way better method.
6) The ability to open multiple projects simultaneously. As simple as FCP7 had it…or even better…as cool and efficient as FCPX does it would be nice.
7) The ability to mark a clip and not just a point on a timeline (because if you move the clip, the marker doesn’t go with it). I know you can use “Clip Marker” but it's very limiting, can't be moved, can't add notes, can't advance to the next marker (as far as I know). Also a marker list like FCPX has would be nice so you can see your markers all in a list at a glance and adjust them as needed.
8) Ability to select a clip in the Project window and find out where it’s used in the timeline. I LOVE how you can do the reverse and take a clip in the timeline and “Reveal in Project Window” but it would really help to go the other way around. Dealing with several hundred clips for every project I’ve missed this feature from time to time (FCPX handles this really well).
9) Add a through-edit indicator in timeline and “re-join clips” option. If you cut a clip but keep both clips together it’s just one continuous clip. But I really hope Premiere adds the not only an indicator of some sort (like FCP7′s way of having two small red triangles facing each other on that cut) so you know it’s one continuous clip BUT ALSO the ability to right-click and “re-join” the two clips into one.
10) When clip is double-clicked in timeline, CTI position in source viewer should match location in timeline. This one is pretty annoying and a fix would be incredibly helpful. The way it is now is very counter-productive. Definitely hope this gets fixed ASAP.
11) Better border controls for images/videos. Can’t do much with images right now in PPro. At least allow to customize the color and size/strength of it’s borders and shadows.
12) Better support for Mac/Apple's top end computers/GPU's. I'm still surprised that 2011 top of the line iMac cards (AMD 6970M) that have 2gb of ram are not supported. I’m sure/I hope 2012 iMac’s will be supported with their new Nvidia GPU’s…but I’ll hold out hope that the top iMac (up until 3 months ago) is supported at least at it’s full power. All around better Mac support would be great considering the wave of new users coming over from FCP.
13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves, etc. For some odd reason videos exported from Premiere CS6 have issues with cross dissolves or minor transparency. I’ll try to explain…in the program window of PPro CS6 cross dissolves look fine. Also, if you take a clip and stack it on top of another clip and put the top clip at say 99% opacity instead of 100 it looks like it should in PPro. But, if you export the clips you’ll quickly see that there are issues. It’s almost like the exported videos dissolve from 5 to 95. They skip the subtle beginning (0-5%) and subtle end (95-100%) of any fade. A clip in PPro as described above that is on top of another but set at 99% will look more like 90-95% in the exported file ESPECIALLY if the two clips are contrasting (eg. top layer dark, bottom layer with bright elements). It’s like the opposit of ease-in/ease-out. I have to ease-in/ease-out of every dissolve to avoid this issue…and even then, it’s not THAT much of an “ease” as one would hope. Another user in a forum once posted a video that shows how abruptly exported videos end their transparency changes…see: THIS SAMPLE VIDEO Perhaps this is a GPU/processing issue with AME vs. Premiere Pro but whatever it is, it should be fixed so videos you export look like the videos you edited!
14) Better control in Creative Cloud over which devices are “activated/deactivated” We have 3 computers and it would be nice if one could log in to their Creative Cloud account and see a list of which devices they have and just toggle on/off which one’s are activated/deactivated. This is especially helpful when you are mobile and forget to deactivate one of your two home/office devices so you’re stuck now until you get back to the home/office to deactivate it. This is not a Premiere thing, but just a general wish.
15) Ability to sync multicam clips automatically using the audio. Plural eyes apparently does this well. Would be nice to have it built into Premiere like FCPX does. Select all the shots you want to sync, One button click, wait a few seconds, done.
That’s my top 15. Everything else is awesome in my opinion for what I do 10 hours a day 6-7 days a week. I’ve included bug reports/feature requests for all of these at one point but if you are someone else reading this go to the following link and ask for these issues to be fixed: FEATURE REQUEST/BUG REPORT
I wish Adobe did smaller updates more often. Because even if they were smaller updates, we’d at least know you are working on fixing some of these issues that have plagued this NLE for years. Holding off fixes for one or two big “updates” every year is tough to deal with in a world of the ever updating apps we live and play with daily on our phones. I realize Premiere is a much larger scale and far more professional than a phone app, but hopefully you get my point. Here’s to hoping the next release (NAB 2013?) resolves all my top 15 issues. Here’s to hoping that these issues will be resolved sooner than later so I can stop raising hell in various forums. I’m honestly ready to start praising and defending Premiere Pro instead of griping about it’s bugs and flaws. It’s a fantastic program “on the way” to being the best. I hope.
167
Replies
I u nderstand your point entirely ...because the Default...would not be my choice as default ....but I customised it to Shift -Z so its ergo efficient and convenient for the purpose.
Actually I can zip thru the modes faster than I can even remember which one ...in which direction ...that I want or need at the time. A minor delay lets mybrain catch up with my fingers.
Dont think my head would cope having a separate shortcut for all the modes.
Editing does not have to be about speed...its craft. 
shooternz wrote:
Editing does not have to be about speed...its craft.
But anything that gets in the way of an editor's creative flow does hinder the craft. Of course we can get around this, but it's undeniable that the more an NLE gets out of the way by offering fast, intuitive tools, the better it is at supporting our craft of editing.
PPCS6's stubborn edit point selections, that can't be toggled between trim and ripple with a simple press of the Ctrl key, is a clear instance of the NLE getting in the way of the editor's workflow. This current behavior is illogical and frustrating. Using a keyboard shortcut as you do to toggle between all of the trim edit modes is not intuitive and efficient, since it requires learning yet another shortcut, and it isn't nearly as fast as pushing/releasing the Ctrl key, which can be accessed 'blindly' (i.e. without diverting one's attention from the screen) due to its favorable position in the bottom left corner of the keyboard. IMO, one of the best things about PP is that you can instantly toggle between the trim and ripple tools on the fly with the Ctrl key. This was workflow genius on Adobe's part! But to not allow the same brilliant toggle once an edit point is selected? Sorry to say, but that's just down right stupid.
There shouldn't even be a debate about 'if' Adobe should fix this. It's a workflow haste that needs to be fixed for the sake of efficiency and allowing us to do our craft without getting in our way with unnecessary restriction.
Then again, maybe it has already been fixed in PP Next. Can anyone confirm this?
Anything is possible with software code...so make a feature request. Unfortunately, with software development, you can't just snap your fingers and change everything at once. We're humans and are subject to schedules and budgets. You want many, many, things and I know it's hard to be patient, but give it some time. Keep in mind we do a lot of things much better than FCP 7, and some things in FCP 7 never got fixed.
Yes, I definitely agree that Adobe does A LOT of things better than Apple does! I'm just concerned with how long things take to get fixed sometimes. For example, the Premiere team broke the subclip feature by adding hard in/out points in version CS2, years ago, and only now in version CS Next has that mistake finally been fixed. IMHO, the ability to create a subclip by drag&dropping it from the Timeline to the Project window is such a basic 101-editing type thing that I don't understand why it wasn't programed that way to begin with in the first version of Premiere Pro. Currently, Premiere Pro offers zero ways for editors to save clips with effects, keyframes and/or markers in the Project window for future use. This is a serious workflow problem that needs attention ASAP. I understand that Premiere users might not be clamoring suffienciently for this shortcoming to get imediate attention, but that's because Premiere users who have never used FCP likely don't even know what they're missing (and likewise can't request what they don't even know exists as an option). As I've said many times, IMO, this is PP's biggest shortcoming vs FCP (and also FCP7's last remaining big advantage vs PP).
Looks like your campaign for clip slipping is already under way. Hope you get your feature request in the next version of Premiere Pro.
With Adobe's new Cloud model that allows features to be legally released before their yearly upgrades, waiting until the next version of PP is too long a wait IMO. I, for one, would switch to Adobe's Cloud in a hearbeat if they added this simple feature before next year! And I'm sure many many other users would too if Adobe released regular updates the way Apple does with FCPX.
That's one area where I have to commend Apple. They keep release free updates with new feature for FCPX... in an attempt to hold on to the users they've been losing to Adobe and others, but it's a commendable effort nonetheless.
I know about Nesting and it's a great feature
Well, that means all your statements here about using a stock film burn transition are just false arguments.
Advantages of storing clips with effects/markers/keyframes in the Project window:
- Searchable
- Viewable in Icon view in addition to list view
- Sortable
- Easy organization through Bin/Sub-Bin hierarchies
- Access to metadata columns such as 'Video Use', 'Audio Use', etc.
- Can delete the original instance from the Timeline, thereby setting the 'Video/Audio Use' metadata column values back to zero, making it easy to keep track of which subclips have or haven't been used yet.
- Can delete the original sequence without losing any of the created subclips
And in which way sequences are not searchable, sortable, have difficulties in organising through bin hierarchy ??? And how deleting a nested sequence instance in the timeline or even deleting original sequence, which contained the nested sequence affect the nested sequence asset in the Project panel ??? 
Regard to icon view and access to metadata for the project asset called 'Sequence', maybe it's a different story?
srukweza,
I guess you have your answer now. Only Cloud for new features from here on.
PierreLouisBeranek wrote:
Hopefully that checkbox remembers the last state used, so you don't have to uncheck it everytime you create a subclip. Do you know the answer to that? Outstanding news!
Yes, I just tested it. It does remember the last state used.
AdChoices