Darren Manden

My feedback

  1. 26 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

    12 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Darren Manden commented  · 

    @Matt Stegner - No sweat!

    Yeah, the bezier curves are pretty much essential for customising to specific use-case scenarios. I pretty much stopped using the transition effects a long, long time ago for that specific reason.

    If the transition effects had modifiable curves, that would be nice, but truthfully, a more DAW approach would be faster overall. As far as I can tell at least.

    An error occurred while saving the comment
    Darren Manden commented  · 

    Unless I'm mistaken, none of the current fade effects in Premiere offer bell curves (or the customisation of the curves that we can only get from keyframes), which is why I always end up with at least one bezier keyframe at the start/end of my clips - please correct me if I'm wrong there, as that would be great.

    I can only speak for myself, but being able to click once, drag to the left/right to bring the fade in and then drag up/down to manipulate the curve, is just faster for me than the process of click for one keyframe, click for a second, hold down a manipulator key, and then create some bezier handles, and then adjust the curve.

    Spending a lot of time in DAWs, and then hopping into Premiere makes me miss that functionality.

    An error occurred while saving the comment
    Darren Manden commented  · 

    Agreed! I came here to pop in a feature request for this exact thing, and then saw your post. Vote added.

    Darren Manden supported this idea  · 
  2. 24 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

    14 comments  ·  Premiere Pro » Import  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Darren Manden commented  · 

    @Joe Hamilton
    There's something comforting in knowing that Premiere really doesn't discriminate who it goes and gets sloppy drunk with. It’ll show up at any front door, day or night, with a couple of warm wine coolers under the arm, low self-esteem glistening in its eyes.

    After that it’s pretty much just a rollercoaster ride of a cautionary tale as it drinks anything it can get its hands on, accidentally breaking anything that comes into its orbit, ending up stranded like a turtle on its back in the middle of the room, crying in a puddle of its own filth - constantly seeking reassurance that people still love it, but knowing deep down that nobody does.

    An error occurred while saving the comment
    Darren Manden commented  · 

    That's so bizarre! I don't know why they would heavily limit access to older versions. In CC, when I click the "looking for older versions link" I get sent to a page for 2017 versions of Illustrator, InDesign, and Photoshop...no Premiere, or any other video applications.

    Kind of hoping that this is just some weird oversight.

    Sorry man. If I come across any way of getting to the older versions of Premiere, I will let you know.

    An error occurred while saving the comment
    Darren Manden commented  · 

    Hey Jón Kristinsson,

    Sorry to hear that you're running into this as well. So far the only workaround that we've found is to drop back down to 13.1.3, and don't upgrade until whatever was broken with the updates gets fixed. Yeah, I know, that's hardly a workaround at all, but it might save a bit of misery for the time being.

    An error occurred while saving the comment
    Darren Manden commented  · 

    In the screenshot you can see an example from System B.

    This is the audio bin in Premiere, which shows the clip "DX_JAPAN_020.WAV". When the project started, we were using the file JAPAN_020.WAV, but I eventually ran that file through external software for noise reduction, and saved it as a new file, "DX_JAPAN_020.WAV". This was saved in a new folder, as part of my brute force testing to get around this bug. I then used "Replace Footage" to change out the original JAPAN_020.WAV in the project.

    This was all performed on System A.

    The project was then opened on System B, and this is where the screenshot comes from. I've brought up the Properties for the clip, and although it is showing as being correct in the bin itself, you can see that it is linking to the incorrect file. For what its worth, it's also linking to the incorrect folder as well.

    An error occurred while saving the comment
    Darren Manden commented  · 
    An error occurred while saving the comment
    Darren Manden commented  · 

    Adding some more detail:

    Update (19/10/10):

    One thing which I haven't previously mentioned is that this wasn't happening before the most recent update.

    We've tried testing with Shared Projects as we were advised that this could help, but we had no luck, and ran into the same issues.

    We also tried brute forcing our way around the issue, but unfortunately failed again. I'll explain, using the music example again.

    When replacing demo music, instead of putting the licensed file into the same folder as the demo track, create a new folder, and put the licensed track in there. Within Premiere, use the replace footage command to link to the licensed track in the new folder. This should make Premiere look for 1) a new filename, and 2) a new folder.


    No luck, unfortunately.

    As it stands, we can't use Replace Footage. Any help is greatly appreciated.

    An error occurred while saving the comment
    Darren Manden commented  · 

    I just remembered another bizarre bit of behaviour:

    When we replace the footage, save, and close, and then open on OS B, the timeline will show the updated filename, but will definitely be using the wrong file.

    If we reveal that clip in project, it shows the correct file in the bin, however if we reveal in Finder/Explorer, it takes us directly to the incorrect file.

    So, yeah. Weird. Premiere will be showing that it's using the correct file, but heading to the actual file shows that things are not right in Denver.

    An error occurred while saving the comment
    Darren Manden commented  · 

    Hi Kevin,

    Could you elaborate?

    I just realised that I didn't mention that we would be reconnecting to files with different names, or different extensions (eg: Replacing watermarked music tracks with final licensed versions) or sometimes both.

    I'm not really sure how the file path would come into play here, as shouldn't it be looking for a wholly different file at this point?

    So, instead of "watermarked_tunes.mp3", it would be "final_tunes.wav".

    Happy to fire through more information if you need it, but something is definitely weird here. Much like what Ryan mentioned back in 2017.

    Darren Manden shared this idea  · 
  3. 345 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

    33 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  4. 89 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

    45 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  5. 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 » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  6. 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

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

    We're seeing this with Amira anamorphic footage (3840x2160 in a 1920x1080 timeline). As soon as the footage is scaled to where it no longer fills the screen vertically, the footage is squeezed. The only workaround we have found is to use non-uniform scaling in the motion tab, but that's far less than ideal.

    As always, I am happy to share more information with anyone from Adobe on this.

    Darren Manden supported this idea  · 
  7. 47 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

    6 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  8. 112 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

    17 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Darren Manden commented  · 

    Can I also add to this: Regularly respond to UserVoice posts on bugs.

    More often than not, bugs are posted, and there is absolutely zero communication from Adobe. If we're lucky enough to have someone chime in, it's typically once with some non-committal response, and that's it. Gone for literally years.

    Good support is ludicrously important, which makes it genuinely baffling as to how the Premiere Pro support can be this terrible.

    Darren Manden supported this idea  · 
  9. 18 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Sounds scary; we’re not yet able to reproduce that behavior, here.

    Confirming: In Preferences —> General —> Most Recent, is yours set to show the Home screen (the default behavior), or have you changed the pref to “open most recent”?

    Darren Manden supported this idea  · 
    An error occurred while saving the comment
    Darren Manden commented  · 

    I had a similar issue that seemed to be linked to the multi-monitor bug "stuck panel" that was introduced in 14.5, but in 14.6 it seems to have disappeared. No word yet on whether Premiere will randomly delete my System32 folder in retaliation.

  10. 712 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

    214 comments  ·  Premiere Pro » Formats  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  11. 642 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

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

    @Scott Crozier - Absolutely agreed! It just seems like a great way for us to all feel like we're being useful by submitting bugs, but they might as well be going into a massive garbage bin.

    An error occurred while saving the comment
    Darren Manden commented  · 

    This would be great. If it could background render all currently open sequences would be excellent! It's one of the things I really miss from FCP.

    Darren Manden supported this idea  · 
  12. 1,574 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

    566 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
    Darren Manden commented  · 

    @James Alton - The BRAW plugin isn't an Adobe plugin, it's from Blackmagic themselves, which is why it doesn't get auto-updated when you update Prem. None of the third party plugins which you install update like that.

    Crossing fingers that Adobe get their own native support for BRAW going though, so then we don't have to worry about this.

    Darren Manden supported this idea  · 
  13. 1 vote

    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 » Formats  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden shared this idea  · 
  14. 26 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

    4 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  15. 53 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 » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  16. 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  17. 136 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

    20 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
  18. 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

    4 comments  ·  Premiere Pro » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Darren Manden commented  · 

    Hey there Melissa,

    Sorry to hear that you're running into this as well. I really do wish that I could say that I've figured out some work around, but nope, things are just as broken as they were before.

    Darren Manden shared this idea  · 
  19. 1 vote

    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 » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden shared this idea  · 
  20. 12 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 » Import  ·  Flag idea as inappropriate…  ·  Admin →
    Darren Manden supported this idea  · 
← Previous 1 3 4

Feedback and Knowledge Base