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 . Not sure if this made it into CC. 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.
... View more