Matt Stegner

My feedback

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

    We’ll send you updates on this idea

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

    @LB, We addressed this situation recently. The NDI driver was being set as the default and the audio is routed to it, but with no endpoint the audio goes nowhere and is swallowed by their software.

    With completely new preferences this should have been corrected, but I'm guessing there was an issue when you updated from 14.3.2 to 14.4. If NDI was turned on in the Playback prefs, but the Playback pref itself was turned off then the update might have set the playback prefs back to on.

    Either way, you can turn reinstall the NDI tools if you need, you just need to make sure that in the "Preferences>Playback>Audio Device..." is set to Adobe Desktop Audio and not to the NDI driver and you should hear audio from your speakers.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    @Nick Kusters, Can you try my suggestion below?

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Do you have any Transmit device or the NDI driver installed? My hunch is that the Playback Prefs are routing your audio somewhere you do not expect.

    You can verify this by going to "Preferences>Playback..." and under "Audio Device" make sure it says "Adobe Desktop Audio", if that doesn't fix the issue can you report back to me here?

  2. 1 vote
    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  · 

    Glad to hear it helped.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    The Auto-Match feature, and the Normalize feature will end up canceling each other out if I am following what you are describing above. Both features analyze the audio content of the clips on the timeline and adjust the Gain.
    The analysis portion of the two features work very differently though. The Peak just looks at the instantaneous volume level and adjusts according to that. That isn't how our ears work though, we hear in an averaged fashion. The Auto-Level feature scan the audio and calculates the perceived volume for each clip. This is more akin to how we, as human beings, hear audio.

    "My ultimate goal is to have my voice have roughly the same volume across the entire video"
    Normalization is not what you want to be using then. I see a lot of misinformation about normalization as it is used a lot in tutorials when it probably shouldn't. The auto-match feature is designed to set all of the audio clips to the same volume level, which is what I think you want.

    If I can make a workflow suggestion based on your statement "My ultimate goal is to have my voice have roughly the same volume across the entire video".
    1. Select the voice clips you want to have set to the the same level. Tag them as Dialog in the Essential Sound panel.
    2. Turn on Loudness>Auto-match. This will scan through each file and adjust it to a LUFS level of -23dB. Each clip will be adjusted by a different amount, but the total perceived volume between all the clips should be the roughly the same.
    3. "get my voice volume anywhere close to 0dB or even 3dB" What needs to happen next is to add an equal amount of make up gain to raise all the clips by the same amount. So, with all the clips still selected, turn up the "Clip Volume>Level..." section of the Essential Sound panel. Play the audio and watch the meter. Adjust the Level slider until you reach the desired output.

  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 » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    Do you have any 3rd party software for controlling the mouse installed, particularly the Logitec extension for Premiere? I ask cause I cannot reproduce this as written above.

    This also might be related to a specific project, if you can send a .prproj that this happens on we can investigate.

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

    We’ll send you updates on this idea

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

    This should be fixed in the next Public Beta build that goes out. Please let me know if it is not fixed.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    It is the effects causing the buzzing. There is no workaround that I'm aware of.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    I was able to reproduce using the project you have supplied. It is written as DVAAU-4203215. You can use that number when referencing the issue. Thank you again for providing the project, it made it possible to reproduce this in a timely manner.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi Trevor,
    Thank you so much for the project. I'm investigating now.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    I downloaded the project "Audio Glitch test.prproj" from the dropbox share below and was unable to reproduce this in either the current development build or the current public beta build. Can you verify with that project? Or provide an updated project? If you would rather email me directly send me an email at audbugs@adobe.com attention Matt.

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

    We’ll send you updates on this idea

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

    You need to include the punctuation.

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

    We’ll send you updates on this idea

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

    Hi Michelle,
    Thanks so much for the project, it helped me understand that this is related to the relinking dialog. I have been able to replicate and think I understand what is happening. I have filed a bug, under our internal reference number that you can refer to when talking to us in the future about it: DVAPR-4225878

    A workaround that might help you now would be to turn on the feature: “Preferences>Media>Write XMP ID to files on import…”
    What this does it add metadata to your files on import that gives it a unique number that Premiere uses to relink. If that is off then Premiere relies on only file names and paths. When you have file names that match, but in separate folders, the relinking dialog can get confused and automatically link to a file based on just the filename and extension. This feature will alter your files metadata and timestamp, so if you use some sort of source control system they will be altered.

    A second workaround is to not use the same file names for unique clips. I understand that some cameras make that difficult. The Premiere ingest workflow via the media browser can give clips unique names. If you are working with a specific camera that writes generic file names, you might want to look into this.

    Explanation of the bug:
    The bug seems to happen when you move a project or project media, and the application needs to relink. When you point to a single file in the relink dialog, Premiere attempt to figure out of it can use that file path to automatically relink the other files. This is a convince added to Premiere so you don’t have to manually relink every single clip. When you have a file “/Folder1/Foo.mp3” and “/Folder2/Foo.mp3”, Premieres auto relinking system seems to be looking for just “Foo.mp3”, finds it in folder 1, and relinks to it, even though it really needs to be linked to the “Foo.mp3” file in folder 2.
    This seems to only happen when relinking after moving project media.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi Michele,
    I don't think the project was attached, I don't see it. The project will be helpful so I can see the exact properties of the clips and if there are additional details like speed changes or effects.

    Can you attach the file again or send it to audbugs@adobe.com attention Matt.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Could you provide a Project file so I could try to replicate this? I've tried some tests on my end but it works fine for me.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    What format is the footage that is having the issue?

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

    We’ll send you updates on this idea

    6 comments  ·  Audition » Multitrack Editor  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    @Christoph Spiegl The initial bug was fixed, and in the newest beta that was released yesterday, another bug appeared and should already be fixed, again. Whack a mole.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Yup, I can confirm this bug. Thanks for reporting it.

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

    We’ll send you updates on this idea

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

    @Jonathan, I've been able to reproduce and have created an internal bug for this: DVAAU-4203170

    If you are on Mac, the Audio Units version of the same effect is not affected.

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

    We’ll send you updates on this idea

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

    Catalina has caused lots of issue due to the removal of 32 bit binary support. Most audio effects will need new builds for Catalina compatibility.

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

    The Audio Clip Mixer can be used for this. Drag the clip directly into the Source monitor then view the clip mixer. Please not that this will affect the volume of the clip as it is added to and sequence, so please take that into consideration.

  11. 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 » Export  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    If it possible to update? There was a bug that fixed an issue that you are describing.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Can you list the exact version you are using of Premiere?

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

    We’ll send you updates on this idea

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

    Nothing was changed here as far as I know. Could you post a video so I fully understand what you are referring to?

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Are you referring to the snapping toggle switch in the Timeline panel? That toggle is defaulted to on, so if you create a new project, it is on. The state of the toggle is also stored in the project, so if you save a project with the snapping turned off, then reopen the project, the snapping will remain off. If you need it on for a specific project, turn it on and save the project.

  13. 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  · 

    Would you be able to provide a .prproj to me so 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 » Preference & Settings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    The console is only for internal development use. No support is given for the console.

  15. 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  · 

    From what you describe, Premiere already has a dedicated button to do what you are asking.

    Open your original multichannel project, and then open "Window>Audio Track Mixer...". In the Audio track mixer scroll over until you see the track labeled Master. In the Master Track, right above the track fader, there is a button with what looks like two little speakers facing opposite directions. When you hover over it it will say "Monitor All Channels".

    Turn that on, and when you play, all your master track audio outputs will be played out of your speakers (if you have Audio Hardware outputs sections set correctly). Please note that this is just for monitoring the audio, and will not affect the export. The button is also global so will affect all sequences.

  16. 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    Are you looking for the Rolling Edit tool? Press the N key.

  17. 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  · 

    This sounds like you are describing zooming on the timeline? Timeline zooming has been part of Premiere for ever. The keyboard shortcuts are "-" and "=".

    If you mean somthing other than zooming, please elaborate so we can better understand.

  18. 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  · 

    Can you send an affected project file (.prproj) to audbugs@adobe.com, attention Matt so I can investigate?

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

    We’ll send you updates on this idea

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

    Another question: Are you using some sort of project manager or project converter application at all?

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Maybe there are some crossed wires. Deleting the Cache is a workaround, not a fix, I mention it though because represents a clean state. It is the only way currently to try and figure out if this is cruft from badly formed peak files for already fixed bugs, or that this is repeatedly happening on new peak files after the bug fixes were put into the executable. The cleanest way to delete the Media Cache is to close Premiere, delete, and restart. If you are not restarting then I think there might still be some things left over. I'm not 100% sure what steps you have taken. I can speculate but that is ultimately all it is, speculation.

    If I reading the below correctly, you are reporting that the peak file is repeatedly being generated wrong, that is the thing I cannot reproduce on my end. That is what I am trying to solve. I need to eliminate variables, and have been trying to do that. There are lots and lots of variables to eliminate though since I'm not able to sit and watch your workflow.

    I've watched your video quite a few times. And all I see in that video is the Premiere window. All I can do is speculate that there is some background process running on you computer, or some permissions issue, that I don't have running so cannot reproduce. I don't have enough information to reproduce. I also cannot open the project you provided below. It is corrupted for some reason, this hinders my investigation also.
    I understand that you are angry, that is partially why I offered the audbugs@adobe.com email below, so you can contact me directly via that email. I will even have a phone conversation or screen share session if you wish, since I want this solved.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    "WTF? If you want to tell us that the issue was fixed, then name the exact version"
    According to some research that Mitch helped me with, this could be one of 4 bugs, fixed over 14.1 and 14.2 releases. We cannot reproduce internally as I stated below, but we can speculate that it has been fixed but cannot accurately name the exact build number as we don't know which bug your are hitting. So we can only assume that this is fixed.

    The Peak file system is retained between versions. So, if a bug is hit in version X.1, and a malformed peak is created, installing version X.2 might not fix the issue. Deleting the Media Cache will reset the peak system, and new peaks will be created minus any previous bugs.

    We think that the best course of action is for you to delete the Media Cache files. We suspect that your issue will go away when not using stale peak files. If it still happens after a complete deletion of the Media Cache, then we will investigate further. Please delete the Media Cache, if you still have issue contact me via the email I gave below.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    A couple things:

    1. The project you sent is corrupted. Can you send it to audbugs@adobe.com attention Matt. We can also take this offline if you'd prefer, just reach out to me via that email.
    Are you using any sort of project converter or any other software that is manipulating the data inside the project?

    2. Please restart the application after deleting the Media Cache, this guarantees that the peak files are not being cached in memory and will result is less problems. If you want to guarantee that the Media Cache has been cleaned, Close Premiere, and delete the content of the Media Cache folder.

    I understand it is frustrating. This isn't a general problem and something is messing with Premiere's media cache system on your computer. If you can think of some utility or something else that might be changing timestamps or manipulating files that would be a huge help. Any deamons running on your computer that I would not have running on my computer.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    @Vasiliy Zukanov
    This is EXTREMELY helpful. This level of information, including the video, eliminates hundred, if not thousands of variables for my tracking this down, decreasing the time it take to investigate.
    Bugs, with out a solid way to reproduce, will not be filed. We generally do not file speculative bugs as there is no actionable information. I ask for more info so I can have a better understanding of how to approach an issue.

    Would you be able to send me the Project file (without media) so I can investigate? And, if possible, post the media file that was showing the bug from the video?

    Right now, my hypothesis is that there is something with the OBS MP4 file that is causing this. Getting the file will help immensely.

    At 4:15 in your video, you reimport the file, and state that the waveform doesn't show up. If you watch your video, you will notice that when you re-import, Premiere starts to generate the waveform again (you can see it in the lower right corner) and that is why initially, there is no waveform. The waveform generation competes at 4:35 and the waveform appears. This is expected.
    Premiere must scan through the entire file to get the amplitude information for the peak file, which is what you see displayed in the timeline. This take a finite amount of time, and happens as a background process that we show progress for.
    What is more worrying is that, when you drag that file in, a new peak file is generated. This should not happen. The peak file system in Premiere (Media Cache Database) should know that the file already has a peak file, and use the exiting one. Is the file set to read-only or have some other permissions issue?

    Edit:
    I spent some time generating files from OBS, in mono as you seem to be doing in the video. I cannot get anything to happen that is similar to either the issue you reported of the waveform disappearing or sync breaking, or the issue of the waveform being calculated a second time.
    I suggest that you close premiere, and delete the entire contents of the Common folder where your media Cache files are and let them rebuild.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi All. We are unable to replicate this internally, and there isn't much for us to go on in the below comments. If we were able to recreate this internally we would file a bug and have it fixed.

    This might be related to specific files, and how the peak files are related to those files after you upgrade from one version of Premiere to another.

    Premiere should reuse the peak files from version to version, but that might be failing in unpredictable ways. So, some info that would help up enormously (again, since we cannot replicate in our testing):

    1. Were the files originally imported in an earlier version of Premiere?

    2. Do you have the peak files set up to be stored in the Media Cache folder, or next to the original media? You can find this setting in "Preferences>Media Cache>Media Cache Files>Save .cfa and .pek media cache files next to original media when possible..."

    3. Is you media on a network or other type of NAS?

    4. What formats are showing this issue?

    5. Does deleting the Media Cache files ("Preferences>Media Cache>Media Cache Files>Remove Media cache files..." button) have any affect on this issue?

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

    We’ll send you updates on this idea

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

    Paul is correct.
    The waveform is calculated by reading through the entire contents of a clip, and a .pek is generated, and written to the Media Cache database system. If you want to have the nest show the waveform you will need to perform some sort of render and then recalculate the waveform again for the nest. This is work that just has never been done in Premiere.

    A new User Voice can be created, and then upvoted, or this thread can be upvoted. The more votes the higher the priority is relayed to the Premiere team.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    This might not be a bug.
    If a nested sequence (multicams are a form of nested sequence under the hood) has to mix down audio, the waveforms are not displayed. Premiere has always worked like this. The only way to see waveforms in a nest is to have a direct 1:1 pass through. Even simple things like cuts or trims will cause the nested waveform to be not drawn.

Feedback and Knowledge Base