Andrew

My feedback

  1. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » GPUs  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew shared this idea  · 
  2. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew supported this idea  · 
  3. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew shared this idea  · 
  4. 225 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Premiere Pro » Adobe Interoperability  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Florian,

    while this is a rather critical and large change to the way the application works and will take some time to be implemented, we’ll definitely put this under consideration.

    There’s more than one solution to this problem, though.

    A good short term opportunity is to use the parallel install feature in the creative cloud application. It should help to at least take away some of the issues working with people on a different version of the application.

    Another thing worth keeping in mind is that you can install CC on two different machines (if you’re on an individual subscription). That gives you additional opportunity to keep different versions around for compatibility reasons.

    I’ll update the status of this request as we move along.

    If you have further thoughts on this matter, please keep them coming.

    Thanks
    Patrick

    An error occurred while saving the comment
    Andrew commented  · 

    Honestly, the most simple solution to this is to just have Premiere be able to convert newer project files to be compatible with older versions of Premiere. If I open a newer project in an older version, instead of just telling me "You can't open this."... give me an option to convert it so that it's openable, even if that means getting rid of some features in the project or whatever it would entail. Just offer some kind of automatic solution so that your customers who need some kind of solution don't have to go searching for workarounds. It really shouldn't be so complicated.

    An error occurred while saving the comment
    Andrew commented  · 

    Backwards compatibility is always a good thing. Far too rare, unfortunately.

    Andrew supported this idea  · 
  5. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew shared this idea  · 
  6. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew shared this idea  · 
  7. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    Well, I certainly agree that they need to figure out all the bugs and streamline everything as well, but like I said, I figure that cutting out the doubling of efforts in creating a different set of filters for Premiere would help increase efficiency at Adobe anyway. Streamlining is exactly what I'm asking for, and part of that would be making sure that everything works smoothly. It would be MUCH smoother to only have to have one program open instead of having to open Premiere AND Media Encoder AND After Effects AND Audition... that's tougher on a computer than just having one big program open.

    I know this would be a long way off if they committed to actually doing this. But it's what I think Adobe needs to move towards going forward if they don't want to end up being irrelevant in a few years. Davinci Resolve already offers pretty much what I'm asking for here, and if it weren't for me being so ingrained in the Adobe eco-system right now, I'd probably have already made the switch. If Adobe keeps disappointing me for much longer, I'll have to take the leap and make the switch sometime soon.

    An error occurred while saving the comment
    Andrew commented  · 

    Forgot to mention Media Encoder. Why is it a separate program? Just have it be a panel within Premiere that operates as a background process.

    Andrew shared this idea  · 
  8. 35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    I agree it'd be a useful option, but like Anonymous and Johan Meimsten suggest, it would be best if it were an option that's activated with a modifier button, NOT just the default.

  9. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    Thank-you! I was wondering what was up with this for a couple weeks now.

    Please don't just turn things like this on by default without telling us, Adobe!

  10. 1,558 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    563 comments  ·  Premiere Pro » Formats  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:

    - The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
    - It does work with AME, so if you want to use it for batch processing, that’s very doable
    - If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.

    Patrick

    An error occurred while saving the comment
    Andrew commented  · 

    Might be time to address this, Adobe. Anybody gonna let us know whether you’re working on implementing it or not?

    Andrew supported this idea  · 
  11. 83 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Andrew,

    your comments are as thoughtful as they are timely.
    While I usually would have to close this item as it isn’t specific enough, I’m gonna leave it open so others can see this and add comments:

    Please come back and vote for exactly the items that you feel need a V2, some polish, or just remove friction in areas that have grown over time. Add a new request if what you’d like to see revised isn’t discussed yet.

    We’re already seeing good patterns on User Voice as to which items and areas would be good candidates for upcoming releases. You can see some of the top runners already marked as “Under Review”. And while that won’t tell you with which release exactly we’ll have things ready for you, it’s an indicator of an investment we’re making to improve features and workflows where most users express their needs.

    Cheers,…

    An error occurred while saving the comment
    Andrew commented  · 

    Just wanted to respond to Warren Heaton: "I did not vote for this topic because the very last thing that Premiere Pro needs is "its 'Final Cut X' style leap forward". If anything, Premiere Pro should strive to be what Final Cut Pro 8 would have been."

    To clarify, as I said in the original post, it shouldn't necessarily be in terms of visual design or layout. That aspect of Premiere is fine (although I imagine there are some improvements that can be made, it shouldn't be the priority). Final Cut X changing everything completely the way it did from FCP7 was actually one of the reasons I balked on FCPX and switched to Premiere. Too much change too fast is offputting to those who are familiar with the program and value that familiarity.

    But what FCPX did bring that was valuable was a massive upgrade in terms of features, usability and preparedness for the future. There was a greatly improved stabilizer. Everything was more-or-less improved over FCP7 in terms of smoothness, speed, etc. It introduced background rendering. It introduced new format compatibility that hadn't been there before. It introduced a multi-format timeline that hadn't been possible in FCP7... so many things that hadn't been there just one version earlier were suddenly there!
    On that front, it gave FCP so much that it had been needing in one fell swoop, and THAT'S essentially what I'm asking for here.

    EVERYTHING that Premiere needs in order to be where it ought to be in 2018 should come asap, in one upgraded version that delivers a massive amount of improvement. New stabilizer, background rendering, noticeably improved speed and smoothness, and hopefully a bunch of goodies that I can't even think of because it's Adobe's job to think of them, not mine.

    So I'm not saying that Premiere should change everything and revamp the entire layout and look and feel of the program. I'm actually with you in feeling that they SHOULDN'T do that. But the technical aspects of the program need to be streamlined and improved to such a major degree, that functionality-wise, it should be like an FCPX leap forward. That's what I meant.

    An error occurred while saving the comment
    Andrew commented  · 

    Yes, even on a good system, I find it a bit laggy and playback can often be choppy. There's gotta be a way to make things smoother.

    Andrew shared this idea  · 
  12. 510 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    29 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Under Review  ·  Reg Santo Tomas responded

    As Jim Simon noted, there is already a request for this so certainly upvote that request.

    This is an area we are looking into for future versions to make auto-save more reliable and out of the way.

    An error occurred while saving the comment
    Andrew commented  · 

    By and large, Adobe needs to embrace background processes way more. Autosave, rendering, creating proxy jobs, etc... all stop you from working and can take way more time than they should. Speed things up and let me work while they're doing it.

    Andrew supported this idea  · 
  13. 276 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  61 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew supported this idea  · 
  14. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew shared this idea  · 
  15. 46 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    Yes, this is probably the most time-wasting and project-cluttering flaw with warp stabilizer. 95% of the clip I want to stabilize also require speed changes or resolution changes, and I'm CONSTANTLY having to nest clips just to use the stabilizer. PLEASE HURRY UP AND FIX THIS, ADOBE!

    Andrew supported this idea  · 
  16. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew supported this idea  · 
  17. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    Yeah, but when it does already know where it is, it should just automatically connect.

    Andrew shared this idea  · 
  18. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew shared this idea  · 
  19. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew supported this idea  · 
  20. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    "Nest timeremapping then add effects."

    Would be nice if this wasn't necessary. Seems that they left a LOT of stuff to be solved by nesting with this program... why can't they just solve these problems so we don't have to worry about it? I'm sick of having to nest so much stuff for it to work. If a filter or action needs nesting in order to work, program that filter or action so that it nests within itself automatically. Then we don't have to think about it or waste time and make our timelines more complicated than they need to be.

Feedback and Knowledge Base