Mel Matsuoka

My feedback

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

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

    OMG, I just accidentally discovered that Premiere 2020 (14.6, and perhaps even earlier) added keyboard shortcut mappings for both Difference and Normal Blend Modes!

    "Set Opacity Blend Mode Difference"
    "Set Opacity Blend Mode Normal"

    My long national nightmare is finally over!

    Mel Matsuoka shared this idea  · 
  2. 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

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

    Resolve also does not have this issue when playing out through a Decklink/Ultrastudio card. I've had one of my editors actually consider switching to Resolve for this one aspect alone!

    It's really surprising that this is still a problem in Premiere, because it makes the editorial process feel very sluggish.

    Mel Matsuoka supported this idea  · 
  3. 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

    1 comment  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mel Matsuoka commented  · 

    Premiere's timeline/bin searching is only useful for the simplest find operations. It's not useful for anything vaguely complex, and it really needs more love, because good media/clip management is a huge deal when working with projects containing mixed formats, frame rates, codecs etc etc.

    DaVinci Resolve's "Smart Bin" and "Edit Index" features really gets this right, and I wish Premiere would take a cue from that app in this regard.

    Mel Matsuoka supported this idea  · 
  4. 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka shared this idea  · 
  5. 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

    0 comments  ·  Premiere Pro » Projects  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka shared this idea  · 
  6. 33 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mel Matsuoka commented  · 

    This really needs to be implemented. I use a lot of Twixtor Pro in my sequences, and the filter often requires that you nest the source clip in a nested timeline and paste repeated instances of it to ensure that the plugin has enough media to work with. You then apply Twixtor to the nest itself. But you cannot utilize Render and Replace in these cases, which really frustrating, because this is a prime example of a situation when you'd want to be able to use such a feature.

    A nested timeline should be considered a "clip" in this context.

    Mel Matsuoka supported this idea  · 
  7. 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

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

    Following up with this issue:

    I reverted to an older version of Compressor (v4.4.6), and this issue does not occur with .MOV files encoded with that version.

    This would imply that the problem originates with Apple Compressor, and not Premiere/AE. However, what's puzzling is that Premiere/AE are the *only* apps which exhibit the issue with these files. The same .mov files which Adobe's apps barf on will load without any problems whatsoever in other apps like Resolve, Avid MC or Lightworks.

    Mel Matsuoka shared this idea  · 
  8. 121 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

    36 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mel Matsuoka commented  · 

    OMG yes! This is a very silly, and completely unnecessary dialog.

    Mel Matsuoka supported this idea  · 
  9. 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

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

    Thanks for that great workaround, Andrew.

    Just as an update, with Bridge 2020 & Premiere 2020, the Reel name of a previously imported clip will automatically update in Premiere if you update it in Bridge. You don't have to do the reimport/consolidate duplicates workaround.

  10. 99 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 » General  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka supported this idea  · 
  11. 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

    1 comment  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka supported this idea  · 
  12. 8 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 » Adobe Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka 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

    1 comment  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mel Matsuoka commented  · 

    This is theoretically a "great" idea, and one that I had originally suggested in years previous. However, I have since learned that there is nothing more annoying to someone for whom media management and data integrity is of important importance for an external process to write metadata into files behind their back. Doing so will invalidate file checksums and file modification times, which can wreak utter havoc with automated workflows.

    A possible workaround--at least on macOS--is to store this type of metadata in the file's extended attributes (xattrs), but this is a very platform--and filesystem/network filesystem--dependent solution which might end up being more problematic than is worth it.

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

    1 comment  ·  Premiere Pro » Preference & Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka shared this idea  · 
  15. 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

    0 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Mel Matsuoka shared this idea  · 

Feedback and Knowledge Base