Skip navigation
Currently Being Moderated

Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)

Mar 27, 2013 4:18 PM

Tags: #mac #update #pc #release #issues #problems #creative_cloud #fixes #markers #multicam #premiere_pro_cs6 #warp_stabilizer #cs7 #cs6.5

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 FCP7s 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.

 
Replies 1 2 3 ... 5 Previous Next
  • Currently Being Moderated
    Mar 27, 2013 5:55 PM   in reply to DMH79

    Great list!

    --Adobe Premiere Pro Engineering

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 5:57 PM   in reply to SteveHoeg

    Also, for #8 there are a few ways to locate where clips from the project panel are used in the timeline:

     

    1) In thumbnail view you can click on the orange filmstrip/waveform in the bottom right corner of the icon.

    2) In list view enable the audio/video usage columns then click the down arrow.

    3) In either view enable the preview area and see the down arrows next to usage indication.

     

    Any one of these will open a menu with all the timecodes the clip is used at, and clicking it will take you to that location.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 6:08 PM   in reply to DMH79

    I sort of had anticipation of "popping a bubble," when I saw the title, but that did not happen.

     

    I agree with most of what you took the time to write, and the rest was just not part of my normal workflow, so I have no comment. The bulk - great, and thank you for taking the time.

     

    Looks like some from "The Mother Ship," have seen the list.

     

    Good luck,

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 6:22 PM   in reply to Bill Hunt

    Very insightful thread so thanks for posting your thoughts, OP.  To add to your list, I'd like to see full GPU support as it seems the current implementation is more limited than other NLEs like Sony Vegas.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 11:21 PM   in reply to DMH79

    We love Bill and we would hold an intervention for his addiction if he wasn't so handy at answering tough questions. We realize that laying golden eggs is bad for the goose, but who can afford to cure him of such a minor flaw.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 1:34 AM   in reply to DMH79

    Nice list, however it does seem a little bit like you may be hoping that Adobe provides the Final Cut 8 package that Apple never delivered on. Having edited primarily with P-Pro for the last decade, I hope Adobe focuses more on getting the next release to run as smooth as CS5x does, strangling and crucifying all the codec and playback bugs that arose in CS6. To me, it appeared that too many of the changes in CS6 were semantic or cosmetic, meant to give a FCP user more familiarity. Why change the name of an edit function from "overlay" to "overwrite" after 15 years? Because it enhances the product, or because that is what Apple called the function in FCP? If Adobe renames the Program Monitor to the "Canvas" with the next release, I think that I might be sick. There were nice additions to the Creative Suite as a whole, but I hope the next Premiere release reverses some missteps made in CS6, and focuses more on stability and enhanced functionality. I also really hope that they have an open ear towards criticism; Apple did not and their users ended up with FCP-X

     

    It saddens me that the fixes I want most in a future release were purposeful changes between CS5x and CS6x.

     

    1) Provide the options for transport controls in the source and program monitors. All of the users at my office hate that the jog and shuttle were removed in CS6. JKL was an option prior to CS6 and if we liked it we would have used it. I keep reading the justification that this change was meant to save space and streamline the UI. I can't express cordially how much this bothers me to look at the empty wasted space in my CS6 UI where the transport controls should be. The experiment has gone on long enough.

     

    2) Restore the 3 Way Color Corrector to its previous functionality. The 3 way color corrector has been effectively neutered in CS6. Where in CS5x and earlier releases one could separately target the input/output levels of Highlights, Midtones, and Shadows, CS6 has only a master input/output level control. Why is less control better? Is it a 3-Way Color Corrector or a 1-Way Color Corrector?

     

    3) Restore Clip and Timeline markers to their previous functionality. I don't even.... I can't. A user shouldn't have to do work arounds to create a modicum of functionality. This again was an attribute that wasn't broken in earlier releases.

     

    4) Simplify the the task of pasting media into a targeted track. As it is now, pasted items will always go to the lowest activated track instead of the targeted track.

     

    Lastly I would like the Adobe Premiere teams to consider what an amazing accomplishment Premiere CS5x was. Upon CS5's release, a good portion of competitor's workflows became obsolete. CS5.5 refined, stabilized, and expanded functionality.

     

    CS6 changed the UI around, moving or deleting buttons, changed keyboard shortcuts, and renamed functions. Oh, and added hoverscrub, you know...like FCPX. In exchanged there was loss of functionality, stability issues and broken codecs.

     

    I really hope the next release is more like CS5x and less like FCPX

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 6:31 AM   in reply to Stephen_Spider

    Stephen_Spider wrote:

    I hope Adobe focuses more on getting the next release to run as smooth as CS5x does, strangling and crucifying all the codec and playback bugs that arose in CS6.

    I'll second that, and specifically call out the cache buffering issue between cs6 and nvidia cards, which I've posted on elsewhere, that has yet to be formally acknowledged by Adobe.  Once this fundamental flaw gets ironed out, PPro will be the most user-friendly platform I've edited on.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 2:39 PM   in reply to DMH79

    DMH79 wrote:

     

    16) Add the ability to "jog" and "shuttle" clips in the source and program monitors.

     

    My goal is to fix what's broken here in CS6 and to improve upon what other NLE's already do much better.

     

    Regarding what needs to be fixed and other NLEs do much better:

     

    • Do Avid Media Composer, FCPX, Edius, Smoke, Vegas, Media 100, Lightworks, or even Windows Movie Maker or iMovie have jog-shuttle controls? Answer: No. No modern NLE has them.
    • Do users complain about jog/shuttle missing in those products?: Never seen a complaint. Some users looking for that feature are looking for hardware alternatives, but are not really complaining.
    • Considering these things, it could be suggested that removing jog-shuttle controls are what modern NLEs are doing right and we followed suit.

     

    This does not discount the fact that you and some of your colleagues are missing having the feature, or might not be able to manipulate playback as you'd like to with JKL.

     

    Sorry to disappoint you, but ss I've mentioned in the past, I doubt that the controls are coming back. However, feel free to request it: http://www.adobe.com/go/wish

     

    One of the bigger problems I see is not listed: support for AVCHD spanned clips. That is definitely a top issue since it worked fine in previous versions.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 2:40 PM   in reply to DMH79

    DMH79 wrote:

     

    I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next)....

     

    Really appreciate this post, thanks so much! I added it to my top issues notes.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 5:16 PM   in reply to Stephen_Spider

    Stephen_Spider wrote:

     

    CS6 changed the UI around, moving or deleting buttons, changed keyboard shortcuts, and renamed functions. Oh, and added hoverscrub, you know...like FCPX. In exchanged there was loss of functionality, stability issues and broken codecs.

     

    I really hope the next release is more like CS5x and less like FCPX

     

    Sometimes, in the name of progress, things like this happen. Established users get annoyed at changes like you mentioned, and that's no small thing. For that, we apologize.

     

    I wouldn't say that Premiere Pro has much in common with FCPX, except the scrubbing, but even that's different. I would say, that I as a former FCP guy, LOVE the UI refresh. I was put off with so much clutter, taking away from the user experience. For me, anyway. I know some stuff got broken, but we do know about the issues, and are working hard to fix them.

     

    It's kind of interesting that all the things that annoy you are welcomed by folks like me. I came to Premiere Pro in CS5 and didn't like what I saw at first glance. Since CS6:

     

    • The UI is way cleaner. This is the one thing that turned me off prior to CS6.
    • I don't use buttons much, like most editors, I'm keyboard driven. I don't mind them being removed as long as a shortcut exists. The bonus is a cleaner UI.
    • Keyboard shortcuts are more standard in CS6, meaning they've migrated to shortcuts Avid and FCP might have had in common. Editors new to Premiere Pro like this. Established Premiere Pro editors probably do not.
    • Regarding renaming items to industry standards, it's a welcome change for most. For exemple, most editors moving to Premiere Pro are used to the term Overwrite and are confused by the term Overlay. Overwrite is used in all other NLEs except Premiere Pro prior to CS5.5, not just FCP.
    • Regarding Jog Shuttle, it was not only to save space. Feedback we got from users from the product improvement program showed us that people did not really use the controls much. See my response above or this blog post: http://blogs.adobe.com/kevinmonahan/2012/07/24/alternatives-to-the-jog -shuttle-controls-in-premiere-pro-cs6/
    • Regarding markers, they do need to improve, but the way they were implemented (numbered markers, etc.), is probably not going to return. For sure, make feature requests about how they should be improved. "Put it back the way it was," is not as helpful. Link: http://www.adobe.com/go/wish

     

    Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 7:36 AM   in reply to DMH79

    The next version just revealed should hopefully cross quite a few items off your list:

     

    • New audio clip mixer
    • Icon view sort options
    • Audio meters update during multicam
    • No more cut on multicam stop
    • Browse multiple Premiere Pro projects in the media browser
    • Option to control linear colour for GPU cross dissolves and opacity
    • Expanded GPU support
    • Through edit indicators
    • Sync by audio waveform
    • Simplified track targeting

     

    Plus lots more: 

    http://adobe.ly/14lWrrL

    http://adobe.ly/16qm3jV

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 7:38 AM   in reply to SteveHoeg

    Should we be thinking in terms of CS6.5 or in terms of CS7? Was there anything in there that deserved a new number to the left of the decimal point?

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 7:44 AM   in reply to Steven L. Gotz

    We've only announced a preview of the next version, but it is a big release.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 8:33 AM   in reply to SteveHoeg

    Great, but have you corrected the outstanding significant faults in CS6, e.g. the project bloating Warp Stabilizer, the AVCHD problem, the multi-cam difficulties, to list just a sample?  And how many of the new features will themselves introduce new problems?

     

    Sorry to be negative about this, but you will walk away from CS6 leaving those who purchased it, like myself , with a slew of unsolved problems.  Just as you do with every new release.

     

    You would do well to separate your major new releases by a greater time, and get the outstanding problems with the existing release patched, and hopefully the new release better beta tested.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 8:34 AM   in reply to SteveHoeg

    It's strange how they will not mention which version they are calling it.  I wonder when it will be available.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 8:40 AM   in reply to DMH79

    DMH79 wrote:

     

    Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that.

    Yes, it is. We made sure of that!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 8:45 AM   in reply to Kevin Monahan

    Have the choppy playback/cache buffering issues also been addressed?  This may not be as sexy as adding a whole bunch of new features, but it does impact a core functionality for many users.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 8:48 AM   in reply to Kevin Monahan

    Kevin Monahan wrote:

     

    One of the bigger problems I see is not listed: support for AVCHD spanned clips. That is definitely a top issue since it worked fine in previous versions.

    This is something I'll need to see fixed in CS6 before I pay any money for future versions, for what little it may be worth.  I paid a chunk of money for CS6 and I simple can not use it; I basically wasted my money.  My hope was that you guys would have figured it out reasonably quickly, but that didn't turn out to be the case.

     

    I can't realistically justify handing you any more cash until it's fixed.  It does look like the next version has some great and useful features, but...

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 8:54 AM   in reply to Jason Van Patten

    Jason Van Patten wrote:

     

    Kevin Monahan wrote:

     

    One of the bigger problems I see is not listed: support for AVCHD spanned clips. That is definitely a top issue since it worked fine in previous versions.

    This is something I'll need to see fixed in CS6 before I pay any money for future versions, for what little it may be worth.  I paid a chunk of money for CS6 and I simple can not use it; I basically wasted my money.  My hope was that you guys would have figured it out reasonably quickly, but that didn't turn out to be the case.

     

    I can't realistically justify handing you any more cash until it's fixed.  It does look like the next version has some great and useful features, but...

    Unfortunately I don't think that is going to happen.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 3:10 PM   in reply to Kevin Monahan

    Kevin Monahan wrote:

     

    DMH79 wrote:

     

    Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that.

    Yes, it is. We made sure of that!

    ALLELUIA!!!  The broken Multicam in CS6 was one of my biggest gripes, and also the reason I checked out FCPX (only to come running back to Premiere since everything considered, it's soooo much better!)

     

    Kevin, are you at liberty to shed any light on the 'Subclip scandal'?  Will be finally be able to create subclips with easily trimmable in/out points?

     

    'Join through edits', Dupe detection in the Timeline, integrated 'Plural Eyes', excellent news!!!  Thanks for sharing.  Feels like Christmas!

     

    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!!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 4:31 PM   in reply to PierreLouisBeranek

    PierreLouisBeranek wrote:

     

    Kevin Monahan wrote:

     

    DMH79 wrote:

     

    Honestly, my number one hope was the multicam fixes and it appears that's now fixed. I can't tell you how much I appreciate that.

    Yes, it is. We made sure of that!

    ALLELUIA!!!  The broken Multicam in CS6 was one of my biggest gripes, and also the reason I checked out FCPX (only to come running back to Premiere since everything considered, it's soooo much better!)

     

    It's really cool we were able to fix this little glitch, I hope it improves your workflow. No more Multicam Monitor, you work all in the Program Monitor. It's much more elegant.

     

    PierreLouisBeranek wrote:

     

    Kevin, are you at liberty to shed any light on the 'Subclip scandal'?  Will be finally be able to create subclips with easily trimmable in/out points?

     

    I don't know of a scandal, but yes, you can now create subclips without limits. Just uncheck the Restrict Trims To Subclip Boundaries box in the Make Subclip dialog box.

    Screen Shot 2013-04-04 at 4.24.54 PM.png

     

    PierreLouisBeranek wrote:

     

    'Join through edits', Dupe detection in the Timeline, integrated 'Plural Eyes', excellent news!!!  Thanks for sharing.  Feels like Christmas!

     

    We're really excited too. Glad you approve of our new features.

     

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 4:41 PM   in reply to Kevin Monahan

    Even better news Kevin!  Now that Premiere can create subclips without hard in/out points, it's a (big) step closer to being all it can be: the best NLE available!

     

    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! 

     

    BTW, I'm guessing you knew that this feature is coming up but never hinted at it in the thread I posted about subclips (as per NDA agreements).  Very well played. hehehe

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 5:55 PM   in reply to PierreLouisBeranek

    Hi Kevin,

     

    I have a few more questions if you don't mind.

     

    1. In the Adobe Premiere Pro Preview PDF, it states: "Source sequences can now be edited into other sequences without nesting, retaining all of their component tracks and clips."  It sounds like this just means the equivalent of a copy/paste of all contents when dragging a sequence from the Project window into another sequence that's open in the Timeline.  Is this correct or does it mean that nests can be unnested/renested the way they can in FCPX?
    2. Has the persistent trim tool selection problem been fixed? (i.e. if a user click-selects an edit point with the Selection Tool (red indicator), they can't toggle that selection to the Ripple Tool (yellow indicator) without first unselecting the selection.  This is a royal pain for many, myself included, so hopefully this has or still can be fixed.)
    3. Can subclips be created with imbedded effects? (i.e. the way FCP7 allows users to drag/drop clips from the Timeline to a bin, with all applied effects/keyframes preserved, for use later down the road).

     

    By the way, you were right when you wrote that you thought I'd be happy with this upgrade.  From what I've seen so far, it seems like a solid upgrade!  Just the fixes to multicam and subclips alone make it worthwhile for me.  My only concern is that I feel Adobe shouldn't use bug fixes to force users to upgrade.  For example, the well known multicam problem should have been fixed in a free update, IMO, rather than only included in the next version of PP (thereby forcing users who depend on proper multicam tools to upgrade).  I will be upgrading as soon as it's released, so it doesn't affect me, but I'm thinking about those who use multicam but won't/can't upgrade until later.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2013 6:26 PM   in reply to PierreLouisBeranek

    I forgot 1 big item:

     

    4. Has the Track Matte effect finally been fixed?  (So that you can scale/reposition the clip with the Track Matte effect without having to nest it first.  Currently if you use the effect directly on a resized/repositioned clip (instead of nesting the altered clip and applying the Track Matte effect the nest), it messes up the composite's positioning and scale.)

     

    Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 6, 2013 11:03 AM   in reply to DMH79

    DMG79 - Yes, this sounds exactly like the opacity behavior this new sequence setting gives you control over.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 6, 2013 1:42 PM   in reply to PierreLouisBeranek
    • Has the persistent trim tool selection problem been fixed? (i.e. if a user click-selects an edit point with the Selection Tool (red indicator), they can't toggle that selection to the Ripple Tool (yellow indicator) without first unselecting the selection.  This is a royal pain for many, myself included, so hopefully this has or still can be fixed.)

     

    Thats not true.  I have a Toggle set up to do exactly what you are saying.

     

    In my case  Shift-Z.  ( Custom KB Setting)

     

    This toggles thru any of the edit Modes

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 6, 2013 3:02 PM   in reply to shooternz

    You're right shooternz, you can toggle through every edit Mode with a shortcut.  So I should have been more specific.  What I want to know is if the new version allows users to immediately toggle back and forth between the left trim and the left ripple edit modes by hitting/releasing the Ctrl modifier, for example.  Not being able to do this is counter intuitive and very annoying IMO.  The current toggle isn't a good enough work around since it can require several keystrokes to reach the desired tool instead of just one, in which case it's often faster to simply deselect and reselect the edit point with the desired tool.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 6, 2013 7:25 PM   in reply to PierreLouisBeranek

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 7, 2013 6:13 AM   in reply to Kevin Monahan

    Speaking of multicam fixes, one thing I noticed while watching the Lynda.com series on the new Premiere features was that while the person presenting the course was cutting a multicam clip, the audio appeared to stay intact! 

     

    It's possible that the audio was a separate clip and I'm just fantasizing here, but this would be a much welcomed change in the behavior of multicam.  It's always baffled me why there wasn't at least an option to leave the audio alone.  And too many cuts to the audio always caused Premiere to have to "render required files", which also threw me for a loop.  Along with the way that instead of mixing the audio from the source sequence, it only played back what was on track one.  Truly quirky behavior.

     

    So I'm hoping what I saw in that Lynda series was an indication that this stuff got ironed out. 

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 7, 2013 9:21 AM   in reply to shooternz

    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?

     
    |
    Mark as:
1 2 3 ... 5 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points