Matt Stegner

My feedback

  1. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    This is a known issue that we are actively working on. The problem is placing clip effects versions of the DeNoise, as more instances of the effect are added, it takes time to calculate the latency for each instance.
    Until we can correct this, the recommended workaround is to remove the effects from the clips, and apply the effect as a track effect. The downside to this is that it will require more organization as track effects will process all clips on the affected track.

  2. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    I'd like to add a few problem solving steps to this, since Premiere doesn't generate an error if no keyframes are added.
    1. Always double check that there is something to duck against that is properly tagged. Autoduck works by analyzing the audio levels of the source (usually dialog) and calculating the keyframes from that. So, a simple workflow is to select your dialog, tag it as dialog in the Essential Sound panel, then tag your music, turn on auto-ducking and then press the generate button. Always double check that the "duck against" buttons are lit up correctly (they turn blue when active). That is how the algorithm decides what to use for ducking. You can turn off all of the duck against buttons and the generate keyframes will still work. No keyframes will be generated in that case. Basically, always look for a blue icon under duck against.

    2. The ducking algorithm will add fades to the duck. If the fades are larger than the ducking amount, no keyframes will be added. When determining the timing, set the fades relatively short, then increase them for the final product.

    3. After any changes the keyframes will need to be regenerated. if you move a clip, or change a slider, press the generate keyframes button again. In Audition the keyframes will auto-generate, in Premiere they will not.

    4. Start with very aggressive settings, then back them off. This allows you to determine the timing of the ducking then dial it back so that it sounds good. When starting a new ducking sections, set the Sensitivity and Amount to the maximum (all the way to the right) and the fades to the minimum (all the way to the left) and generate. Then inspect the result, and set the sensitivity down and regenerate until it seems that the sensitivity is correct. Then repeat with the amount. Finally do the same with the fades. Remember to play the autoduck and listen with your ears. You cannot set audio parameters by just looking at your timeline. And if it sounds right it most likely is right. "That looks good" is bad. "That sounds good" is good.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    "Bear in mind my dialogue is at -6DB from max so it is more than loud enough to trigger at 6."

    It doesn't work that way, though I can understand why you would make that assumption based on the UI. The meters are reading the audio as a peak measurement, the Auto-ducking is measuring the audio using an averaged RMS measurement. The numbers in Auto-duck sensitivity are just for reference, and are not measuring any sort of decibel level. That is why they are unlabeled. Just think of it as more sensitive or less sensitive.

  3. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    What you are describing is the automation system, specifically that it appears to be in Touch mode.

    For Clip effect: Look in the Audio Clip Mixer, and the keyframe button to the right of the Mute and Solo buttons. If it is highlighted blue, any parameter changes made during playback will be written as keyframes.

    For Track Effects: In the Audio track Mixer, look for the dropdown underneath the pan knob, and make sure it is set to Read or Off, and not to Touch, Latch, or Write. If it is set to "Touch, Latch, or Write" new audio track keyframes will be written during playback.

  4. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    What version of Premiere are you using? What you are describing was a bug that was fixed months ago.

  5. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Audition  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    This is possible, but only with a single device with multiple inputs and it will not work across multiple USB devices. Basically, Audition is designed to use just a single device for In and Out dues to thinks like clocking and routing. It was not designed to use multiple USB devices together. It is possible to create virtual devices that can get around this limitation if needed though.

    If you are on Mac OS you can create an aggregate device that can active this:

    https://support.apple.com/en-us/HT202000#:~:text=Set%20up%20an%20Aggregate%20Device&text=From%20the%20Finder%2C%20choose%20Go,left%20side%20of%20the%20window.

    And, on Windows, you should be able to create a single device that uses both USB inputs using a pice of software called ASIO4All.
    http://www.asio4all.org/

  6. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    I'm not sure I understand. "Changing from ASIO from the decklink to MME". Changing from what ASIO device? The Decklink ASIO driver to Windows MME?

    When using a Transmit device, to guarantee sync, the recommended set up it to have the Transmit driver handle all of the audio output (as well as the video output). This is achieved by turning on Transmit in the Playback Preferences, and by setting "Preferences>Playback>Audio Device..." dropdown to the Decklink device. When the "Audio Device" is set to something other than "Adobe Desktop Audio", all the I/O settings in "Preferences>Audio Hardware..." are ignored. My question was to determine the general configuration of Premiere.

    You are not providing enough information to start to trouble shoot, and I asked how you have the system configured so we can move on from there. Can you please post screen shots of both the preferences pages for Playback and for Audio Hardware to establish a baseline for us to work from.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Can you check that "Preferences>Playback>Audio Device..." dropdown is set to Adobe Desktop Audio? And if it is not, set it to Adobe Desktop Audio and see if the bug reproduces?

  7. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    How many clips are you adding the audio effect to?
    There is a known issue that is being worked on right now where Premiere will take a long time to start playback if there are hundreds or thousands of audio effects on clips in the timeline.
    What you will see is when pressing the play button or pressing the space bar, the Transport will change from a triangle to a square, but the transport will not move. If you wait long enough, it will start moving. The length of time spend waiting is directly proportional to the number of audio effects you have.

    As a workaround for now: If you are using the same effect with the same preset across all of those clips, you can add the effect as Track based effect, and remove the clip based effects. This will apply the effect to all clips on the affected track, so you must be more diligent about the placement of audio clips. The advantage is that instead of having hundreds or thousands of instances of the Multiband Compressor running in system memory, you will have just one for each track.

  8. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Do you have the NDI Driver installed? Please check that "Preferences>Playback>Audio Output..." dropdown is set to Adobe Desktop Audio.

  9. 25 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    This is fixed, and is in the current Beta. It should be in the next release of Premiere.
    We JUST barely squeaked it in this decade.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi all,
    I've been able to reproduce a bug when executing Render Audio command on a nested sequence. It is logged with the internal bug number DVAAU-4202616 for reference. Thank you for the bug report.

  10. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Audition » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    I answered this in the Premiere thread.

  11. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    Have you recently installed the Newtek software or NDI driver?
    If you have please check that "Preference>Playback>Audio Device..." dropdown is set to "Adobe Desktop Audio" and not to "NDI Output".

  12. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    Would it be possible for you to get a video showing this to us?

  13. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  7 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi Erez, thank you for sending me the project. I never would have figured this out with out it.

    I'm going to respond here so anyone else can search for this and see if it helps them find the answer.

    I've created a bug for this: DVAAU-4202878

    It appears that you were trying to create what is called a reverb tail. There is an issue when rendering the audio, that doesn't appear when simply playing. The nested source, on track A1 of your project, is disabled, I'm assuming to add length to the clip when you nest it into the main sequence. This is fine on playback, but on render, Premiere only take into account the shorter clip on track A2 of the source nest. That is the bug.

    As a workaround. In the source nest, readable the clip on track A1, and turn the volume do the clip down to negative infinity. This will properly render, and sound the same.

    Again, thanks for the project as I never would have been able to understand this without it, considering the scant explanation of the problem in the original post.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Can you post a non-client project that shows the error? Or even a screen shot of the effect window running in the problem project? Or send me the project at audbugs@adobe.com attention, Matt.

    The Obsolete Reverb effect is completely different code and should be working. It is irrelevant to any failure in the Convolution Reverb.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    I just tried the Convolution Reverb and it is working for me on a Stereo clip and Track, and a surround Clip and Track.
    When you say "Won't Export" do you mean that Premiere fails to write a rendered file to disk, or that the effects is missing when the export happens?
    Are you Exporting directly from Premiere or from AME?
    Are you on Mac or Windows?

    Convolution Reverb is special, in that it uses a .WAV file on disk as the seed for the convolution. If Premiere cannot find that seed file, the effect will output silence. There also isn't an error message currently if the seed is missing. You can also use your own .WAV seed files, and they are referenced from their original location. So if you move a project to a new machine and the seed file is not in a location that Premiere expects, the effect will not work.
    If you post your .prproj, I can investigate.

  14. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    This initially sounds like you have the sample rate of your audio device set too low. In "Preferences>Audio Hardware>Sample Rate..." set it to either 441000 Hz or 48000 Hz.

    Please let me know if this helps or not as we can troubleshoot further if the problem persists.

  15. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    What version of Mac OS are you seeing this in? I tried both 10.14 and 10.15 and was unable to reproduce the issue.

  16. 8 votes
    Sign in Sign in with Adobe ID
    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
    Matt Stegner commented  · 

    This was added to Premiere recently, but for Mac only. For now on Windows you will still need to manually switch.

  17. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This is a know issue and should be fixed in the next patch. You can see the fix in the current public beta build.

  18. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Google search "Track Targeting in Premiere Pro" and follow a tutorial about how it works.

    To answer your question, in your video you see the blue squares on the left hand side of the track. On the the 3rd video track V3 with the text V1 that isn't blue. Click on it and try again.

  19. 70 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    "you can apply audio plug-ins to entire tracks".
    You can do this in Premiere and have been able to for years. Open the Audio Track Mixer panel, in the upper left there is a twirldown, open it. That exposes the Track inserts and sends area. In the inserts section click on the dropdown and select the effect you want to apply to the entire track.

    Does this help or are you talking about something different?

  20. 1 vote
    Sign in Sign in with Adobe ID
    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
    Matt Stegner commented  · 

    If you right click on the FX badge on the clip, you will see a fly out menu with options to add keyframes to the clip directly. Is this what you are looking for?

Feedback and Knowledge Base