Melissa Tamporello

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

    0 comments  ·  Premiere Pro » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Melissa Tamporello shared this idea  · 
  2. 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 » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Melissa Tamporello shared this idea  · 
  3. 213 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

    149 comments  ·  Premiere Pro » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This is not a bug, it’s as designed. We specifically limit the visibility to one track at a time to avoid accidentally burning in multiple tracks. Also, when exporting to a format that only supports one captions stream like SRT or STL, we need to know which is the active track in order to export the correct track.

    But I understand why you might need two tracks visible at the same time.

    Multiple speakers:
    If we could automatically identify speakers and designate a style associated with them, would that help? For example speaker 1 is blue and on the left, speaker 2 is yellow and on the right?

    Multiple languages:
    Do you ever need to burn in both at the same time or is it just a matter of being able to see both to aid in translation and alignment?

    Thanks for the feedback, we really are listening :)

    An error occurred while saving the comment
    Melissa Tamporello commented  · 

    I have also been waiting for this to be fixed as I have the same issue @JP Avila. I was hoping they would release the fix for the 2022 version but have not. Huge bummer!

    Melissa Tamporello 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 » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Melissa Tamporello 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

    4 comments  ·  Premiere Pro » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Melissa Tamporello commented  · 

    I'm having the exact same issue, using Proxima Nova typekit

Feedback and Knowledge Base