Matt Stegner

My feedback

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

    We’ll send you updates on this idea

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

    10% is the default. You might have, long, long ago, set it to a number that is more to your liking and then forgot about it. Then installing the update set it back to the default. If you still have the old versions installed you might want to look and see what it was set to.
    Or just adjust it and see if you can get it to a setting that feels normal to you.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Could you check that the setting "Preferences>General>Zoom Factor (Time)..." percent is set as you would expect it? This could be that you had this set to a different percentage in a precious version and as you updated that percentage was not moved forward.
    I mentioned this because there hasn't been any code changes that I'm aware of in Audition that could cause any changes.

    I personally find a lower number to be a little easier to use, but the setting can be affected by the type of mouse that is used.

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

    We’ll send you updates on this idea

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

    This is a known issue (DVAAU-4202460) that is logged against audio only right now. Is it happening elsewhere also? Your report above doesn't specify.

  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  · 

    Two things:

    1. "Your Effects Control table-lookup is dropping the ball!"
    LOL!

    2. "AUGraphicEQ" is not a Premiere/Audition native effect. It is a 3rd party Audio Units effect built in to Mac OS. We don't have any control of how the AU effect reports parameters through the Audio Units API, Premiere/Audition just shows what the effect tells us.

    I tried this is Logic Pro X. The effect parameter names update correctly when switching the bands dropdown. But if you notice, the actual bands that are automated are incorrect if you change that parameter. Premiere are showing similar behavior, which points to an issue internal to the effect.

    I don't think there is much Premiere/Audition could do to address this.

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

    We’ll send you updates on this idea

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

    My comment below was referring to this: "creates a nasty glitching/grinding digital". That issue was fixed.
    I am able to head a pop when playing across an edit when this is applied as a clip effect. I will create a bug fro that right now. Is this what everyone is hearing?

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi All,
    Matt from the Premiere Pro Team. We have been fixing a ton of bugs related to this type of error. I don't have a specific bug against this effect, but most likely we have fixed this in 13.1 release this week. Can someone comment on whether this is fixed or if it is still happening?

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

    This is not a bug, it is literally how it is supposed to work.

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

    Can you verify that you have "Files and Folders" access for Audition in the "System Preferences>Security & Privacy>Files and Folders..." set up correctly? Maybe post a screen shot for us to investigate.

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

    Do you have any of the Premiere Cache Files locations pointing to the NAS? It sounds like Premiere is waiting to access a folder location on the NAS and is just sitting waiting until it is available.

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

    We’ll send you updates on this idea

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

    Hi,
    This dialog is thrown every time the Operating System tells us that the audio devices has changed. Since it could affect the inputs and outputs we choose to throw a dialog alerting the user, and added a "Do not show again" checkbox.
    What you're describing makes me think that you have an audio device or that it being repeatedly added or removed from the system. Even Bluetooth headphones or some other non-obvious thing could cause this. If you look at the System Preferences>Sound... do you see devices being added or removed repeatedly? If you do that will help us diagnose what is causing this.

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

    I am not 100% sure if I understand. In the video you posted it is really hard to see if there is a level change because the meters are jumping around. Are you saying that if you play over the area that has keyframes the volume changes, but the area with out keyframes does not change audio? The Auto-ducker will only add keyframes that the volume follows. If you do not see keyframes added to the music clip then there will simply be no volume change. In your video it appears there is no keyframes added.
    Or am I missing something here?

  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  · 

    These were know issues that, as far as I remember, were fixed in the 2020 release of Premiere.

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

    This is meant for the Premiere User Voice forum I think? Premiere has only for two ambisonic audio workflows right now. Correcting the 3d panning of an existing ambisonics recording. Basically repositioning the 3d sphere to match a video.
    Down mixing the 4 channel ambisonic audio to a binaural output for use with headphones.
    Premiere will also do head tracking that can move the sound field in conjunction with the video field. This has been the case since at least Premiere 2019, maybe earlier.
    Premiere will not do point source placement of audio in the sound filed. For that, we recommend using the Facebook SpacialWorkstation mentioned above. In Premiere 2020 we added even better support for audio channelization with adaptive audio which should make the Facebook plugins fully work.

  12. 3 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  · 

    What version of Premiere are you using? This was a bug on Windows when using HiDPI that has been fixed.

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

    Can you post a picture of your timeline? Mostly this is so we can see if you have track targeting turned on for audio or not.

  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  · 

    Hi,
    Can you post a screen shot of "Preferences>Audio Hardware..." so we can see how you have your audio configured?

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

    Continued...
    The "Generate Audio Waveform" command has some interesting uses. If you execute it on a clip that is highlighted in the Project panel, the entire master clip waveform will be generated (same applies to a selection of clips). If you have an In and Out point in the timeline, only the in and out point will be generated (same allies to all clips in a timeline). The command also can reprioritize the waveform generation queue. If you have 100 files that need waveforms, you can select the first 10 and start scanning them. Then you realize you actually need to see files 11-20 before 1-10, you can select them and execute the command. Premiere will reprioritize 11-20 and scan them first, then go back and scan 1-10. This also applies to sequences. You can reprioritize a certain sequence before another. You need al the waveforms for sequence “A”, select all and execute that command. Oh, you realize you actually need to see “B”, select the clips in there and Generate Waveforms and it will be next.
    Continuation...
    If you work on a Network Storage, I would recommend that you try disabling the automatic peak file generation and try generating them at will and see if that helps. The “Generate Audio Waveforms” command was designed with the idea that a user would turn off the automatic generation, then assign a keyboard shortcut to “Generate Audio Waveforms” and quickly generate them at will.
    Let me know if this helps or you have any more questions about this, I can try to help.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    We've tried to make this faster and it isn't easy to make this significantly faster. I won’t answer the question about parallization, but can try to explain below how peak feel germination works and how you might be able to optimize the peak file generation.

    Lemme explain some of the issue we face with generating peak files.
    Generally peak file generation is bound by the read from disk, so parallelizing it will only bog down the entire disk I/O. To get generate the peak file Premiere needs to read the entire video stream from the disk (or network storage). This means your 4k video file will stream to the local disk, then the video frames thrown away, just to generate the peak file. Running a bunch of those in parallel could saturate the network quickly. You'd start to slow down the entire network when generating peak files. And it might not be much faster (sometimes it would and sometimes it wouldn't).

    Lemme explain some of the way it does work. Not necessarily for you but for anyone coming across this post. I’m really trying to help here, please don’t misconstrue this as making excuses, but me trying to explain how a different workflow might help.
    The peak files are small pictures of the waveform, which makes it easier to edit visually. By default, Premiere will scan a file on import and generate the peak file. It will then cache that file so it can be used again and agin in multiple projects. That is part of the function of the Media Cache database. You don't need the peak files to edit, it just makes it easier to see what is in your audio clips. Generating these files is effectively a background process. If you play, Premiere will stop generating the peak files and give that disk I/O bandwidth back to the playback engine, so you don't drop frames. You don't need to sit and wait fro Premiere to finish generating the peak files unless you need to see something in the waveform. And, since it is paused during playback, you wont lose any performance either. Effectively, if you wanted too, you could ignore that little progress bar in the corner.
    Even in you do need to see something in the waveform, you can just scrub or play over that section of your clip and Premiere will automatically reprioritize the waveform generation of that section of the waveform, and draw it next. It pauses what ever file is being generated, and generates the current audio that is being touched. Basically, if you need to see a waveform right away but Premiere is busy generating a waveform for another clip, simple scrub or play over the section of the clip you need and the waveform will be generated on demand. Premiere has an optimization that it never need to generate the peak data twice, and by simply accessing a video stream (by playing or scrubbing) the waveform for that section will be drawn.
    I talked about how generating peak files over the network, you will need to read the entire video stream. So if you import 4 TB of footage from the network, Premiere will try to, by default, read all 4 TB of footage and generate waveforms for the footage. Not super efficient, and any other editors you have on your network will be sharing that same bandwidth. You can, in the Premiere Preferences, turn off the automatic generation of waveforms, so media will not be needlessly streamed to your local computer just to generate the peak files. Great, but you now wont have any waveforms to see what is going on. You can selectively generate waveforms in this case, minimizing the bandwidth issue, by using the command "Clip>Generate Audio Waveform...". This command creates a queue and starts generating waveform right away. Also, remember you could simple play or scrub over the section of the clip that you need to see the waveform and premiere will generate it first.
    Continued....

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

    We’ll send you updates on this idea

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

    Probably the closest existing thing this to this would to use sub-mix tracks. To use Tracks effects and Track keyframe automation on the sub-mix tracks. Visually it is very different. but conceptually it is similar.
    To accomplish this, you would want to route the track output to Sub-Mix track, not use the track sends section. This is (generally) how an audio person would accomplish this workflow.

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

    Can you record a Favorite to do this? Favorites can be executed during a Batch Processing run.

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

    Try "Preferences>Timeline>Default Audio Tracks>Stereo Media..." and set it to "Mono".

  19. 4 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 with 14.0.0. and should have been fixed in 14.0.1.

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

    This is a bug that is fixed internally and will be fixed in the next patch.

Feedback and Knowledge Base