Matt Stegner

My feedback

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

  2. 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?

  3. 20 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?

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

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

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

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

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

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

  9. 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 version of Premiere are you using? What you are describing was a bug that was fixed months ago.

  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  ·  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/

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

    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?

  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  · 

    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.

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

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

    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.

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

  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 » 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".

  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 » 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?

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

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

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

← Previous 1 3 4 5 6

Feedback and Knowledge Base