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
PierreLouisBeranek wrote:
One last thing: does "Option to control linear colour for GPU cross dissolves and opacity" mean that cross dissolves will finally be smooth (i.e. 0-100% fades instead of a choppy 5-95%)? If so, YES!!!! FINALLY!!
I assume so, but I should ask around before I can say that occurs.
Hi Kevin!
I too would love to know exactly what Steve meant when he said that as well. Interestingly I borrowed a co-worker's laptop that has an approved GPU and I noticed today that when GPU accleration is turned off in my project settings (so it says software only) those cross dissolve/opacity "5-95%" issues do NOT seem to appear in the project window ...BUT they do appear in the project window when GPU acceleration is turned on in the project settings. The opacity issue was also passed on to the exported video in most cases (depending on project and export settings). I know it's only been a short time so far since this little "reveal" but I'm curious if you've been able to ask around yet and find out what exactly Steve meant by his opacity quote above and if the issue I described above (#13 on my list) is resolved.
Like I said before, the new upcoming release looks outstanding. It appears that many of my top 15 are checked off and more. I'm still curious if some of the warp stabilizer issues (#3 and #5 on the list) as well as this opacity issue (#13) on my list above have been addressed but from what I've seen so far Adobe has done an amazing job of not only listening to their customers over the last year but also taking the lead in new and creative ways to expand and streamline the ways in which Premiere and other Adobe programs can be used individually and together. So be sure to thank the engineers for all their hard work. Can't wait!
Hi Dax!
Thanks for "bringing it all back home" again after this thread went in many directions. I've only limited PPro experience so far with a lot to like, but I had to stop and go back to CS6 due to the multicam bug mentioned below. See my responses underlined in bold below. Thanks!
Dax Roggio wrote:
I have been unabashedly pushing for Premiere Pro to become more like FCP7.
When I tried Premiere Pro CS5.5 a year and a half ago, it was somewhat Windows-y and had so many silly and seemingly easily correctable flaws that I almost gave up on it. (And those visual jog controls took up a crazy amount of space for controls that no one had touched since 2000 if they knew about J-K-L.)
But the overall editing paradigm was very similar to Final Cut Classic's. So I submitted my feature requests, posted a long blog article, and lo and behold, Adobe took some wonderful steps in the right direction with CS6. I guess I wasn't the only one clamoring for those things.
With CC, I think the Final Cut Pro 8 I've been not-so-patiently waiting for has pretty much arrived. Now that it has, I hope Adobe concentrates on stability, another hallmark of FCP7.
My list of 88 gripes has been reduced to 63: Premiere Pro CC: Wish List Scorecard
Back to DMH79's original post:
1, 2) That's great that the multicam flaws has apparently been corrected. Definitely nice not to have to deal with these two issues any more. Tested, and approved. HOWEVER, a new bug has infected and crippled the new CC multicam: http://forums.adobe.com/thread/1236698?start=0&tstart=0
3, 5) Warp Stabilizer has been very buggy from the start. It's super awesome when it's not causing crashes. I haven't had a chance to test it extensively in CC. How's it looking? I have only used it about 10-15 times on one project but I then stopped the project because of the multicam issue above and went back to CS6. But the ticktime error is gone I believe. It still has "Subspace Warp" as the default method in the settings which is unfortunate for the reasons I mentioned. I use multicam and stabilizer so much and really I have enjoyed the warp stabilizer experience outside of the few little gripes and I'm excited to try out VFX in AE soon.
4) The Project panel is still pretty slipshod when it comes to arranging and previewing clips. I second everything you said.
Additionally, when you double-click a bin, it never remembers the window size. Is this version 1.0?
Here's what I would really like to see also: get rid of the tiny little thumb in the Preview Area and make it so that a single click on a clip displays the clip in the Source Monitor panel. I tend to leave the Project viewer in list mode. I would love to use the arrow keys or click on clips — utilizing the sorting and info that comes with list view in tact — and immediately see the clip in the nice big Source Monitor panel. I actually think those are two great ideas! Single click display and arrow key navigation would be awesome. Make a feature request and maybe in 2015 we'll see them!
I kid of course...sort of.
6) The ability to open multiple projects simultaneously has been on just about everyone's list for a long time. Yes, please! The 15th post in this thread mentions that you can browse multiple PPro projects using the media browser. Haven't tried yet, but it's better than nothing. It's no FCPX in this regard, but again, better than nothing I guess.
7) Clip marking: It drives me absolutely crazy that you can't simply select a clip and mark a frame. Markers have been improved but again, I stopped messing around with CC when I hit the multicam wall, so I've yet to see if this is possible. Others in this forum probably know more about this.
8) As far as the ability to select a clip in the Project panel and find out where it’s used in the timeline, that would definitely be nice. The only thing is that I want them to rethink the whole manner in which clips in the Project panel are connected to clips in the Timeline. You actually can do this. I just didn't know at the time. See post #2 in this thread.
For instance, if you change the name of a clip in a bin, it doesn't change the name in the timeline. That's fine. Yet, I can't delete a clip from a bin if it's been used in any sequence in the entire project without removing it from that Sequence. Are they connected or not?
This brings me to another big gripe, which someone mentioned above, which is that you can't drop an effect or keep effects attached to clips in the bins. That seems pretty basic to me coming from FCP.
9) They added a “Join Through Edits” if you right click on a through edit. Just note that you have to turn on “Show Through Edits” in the Timeline settings to see them. Yes. Seems to look and work real nice in my limited time with CC. Great!
10) I can't help but notice that this is the exact wording of my gripe #51! Double clicking a clip in the timeline should definitely move the CTI in the Source panel to the same frame. It's super annoying. It IS the exact wording from your site because I wrote this post after reading through yours and I never knew how to describe this until I read your post so I copied
11) Better border controls for images/videos: Yeah, how about any border controls? It's great that I can jump right into Photoshop to add a border to a still, but that would be like having to Dynamic Link over to After Effects to add a vignette. Oh, wait… Not sure about this yet. Still have to check. I saw drop shadow in CC, but that might have been in CS6. But yeah, more border controls would be nice.
12) Better support for the GPUs of top-of-the-line iMacs has been literally #1 on my list since making the switch. I have given up hope on this one. The very latest iMacs have NVIDIA cards, but not the ones from just a year or two ago. They do now support all GPU's with more than 1GB of VRAM and so my 2011 iMac with the AMD 6970M w/ 1GB VRAM is now GPU accelerated. That's nice. I'm surprised this card (which was the highest end card of 2011-late 2012's iMac's didn't get officially "supported" but at least it works now.
13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves: I haven't come across this one, but it sounds irritating. I generally export to ProRes and then do my compression in Apple Compressor, because Media Encoder's H.264/QuickTime compression is visibly inferior at the same bit rates. I haven't tested this one either on the new CC. Post #15 did mention something about this being helped in CC, but it's a hard one to describe so I'll have to check myself if its solved. It's crazy that an export would look different than what you see on the timeline.
14) This makes sense. Have there been any improvements to activation/deactivation controls in Creative Cloud? No. Adobe was nice about my issue and gave me a free month which I didn't ask for, but honestly I'd rather pay for that month and have the ability/control so that I don't get "locked out" of my own projects ever again. This solution seems reasonable and efficient. I won't hold my breath, but you never know.
15) They added syncing by waveform for Merged Clips. I have not had any luck with this yet. It didn't work when I tried to use it, but maybe I'm doing something wrong. The one long timeline I sync'd by audio did work. So that's nice. I never double checked it was perfectly sync'd but it looked good to me. Again, I stopped working on CC, when I re-opened my multicam project and it was completely messed up due to the multicam bug in the link above (#1)...so I'm back on CS6 for now. Sigh.
My only new gripe in limited use so far (beyond the new awful multicam bug described above) is that if you change the "appearance" to a lighter background in Premiere Pro CC, you can't see the in and out markings/area in the source and project window. In CS6, changing appearance changed the color of that "work area" to light blue to work with the lighter background, but it seems as if Adobe didn't optimize the lighter background for actual use as the in/out area in PPro CC remains light in color and basically is invisible when you change appearances. Now, I agree that the dark background looks MUCH cooler and I really do like it, but it's hard on my eyes after 10hrs. a day - 6 days/week so I kind of need to change it to light background...but sadly, Premiere Pro CC's version of the light background is not so great. I submitted a feature request...but since it's not a bug report, I may be at the back of the line.
Mark Mapes wrote:
Since you say "still around," I gather you've tested this warp stabilizer issue in 7.2, but I wanted to confirm that. I thought it might have been fixed along with this bug: "Significant delays loading projects or exporting projects with Warp Stabilizer."
Hi Mark. Yes, it's still around from 7.0 thru 7.2
The other issue I don't think I mentioned in a forum thread. I actually pointed it out to Steve Hoeg in a PM and he was able to reproduce the issue and said that they'd fix it. Sound like they did which is great. It was a delay with sequences with multiple warp stabilizers where when you hit export in 7.1 (not present in 7.0.1) there would be a delay of SEVERAL MINUTES before the dialog box would open. The more warps, the longer it took. Really glad that's gone now. )
But yeah, the bug/issue with saving projects as mentioned in that thread above is still here in 7.2 ... 
AdChoices