Matt Stegner

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

    Under Review  ·  13 comments  ·  Audition » Workflow & Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Matt Stegner commented  · 

    I've created a bug to investigate this. There seems to only happen when starting with a new 16 bit file, and does not happen with a 32 bit float file (if anyone needs a workaround).

    An error occurred while saving the comment
    Matt Stegner commented  · 

    No progress, I'm still not exactly sure how to reproduce the bug.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi,
    I not sure what you are asking for here? Can you please give a step by step way to reproduce the error, and what is expected at the end of the steps.

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

    7 comments  ·  Audition » Effects  ·  Flag idea as inappropriate…  ·  Admin →

    We’re unable to see any difference in behavior in the CCE effect, or from your screenshots. The pop up about CPU and latency is a warning, not an error, and can be disabled by checking the box on the dialog if your system is capable of rendering it during real-time playback.

    Most of the presets default to use “Center” as the Extract mode, which disables most of the parameters which are used to customize the position of the affected audio in the stereo field. You can change this option to Custom to unlock all the parameters and adjust them as desired.

    There are certainly some exciting new advanced in AI and machine learning technologies around isolating different components in a recording. CCE is based on DSP that was developed for isolating elements in a mix based on the content in a specific region of the stereo field. Many of the…

    An error occurred while saving the comment
    Matt Stegner commented  · 

    "CCE workflow did not function through the Effects Rack anymore." I am looking at it, it is working for me. You should to provide video showing it not working, a screen recording.

    I also reviewed the video, it also is correct still. The video is not showing the Center Channel Extractor being used outside of the Effects Rack (again, at 50 second in the video you cleary see Jason launch the effect via "Effects>Stereo Imagery>Center Channel Extractor..." and NOT via Effects Rack. So stating repeatedly that the tutorial is launching the via the Effect Rack, and there for wrong, is puzzling. The tutorial is fine from what I can tell. Please, if I am mistaken, point to exactly in the video where it is incorrect.

    In the last screen shot you posted, you have the effect open via the Effects Rack, and the Effect Rack set to the Process; Entire File. In this mode the effect will be active on all of the audio, regardless of selection. The default behavior is "Selection Only" which is more similar to launching the effect outside of the Effects Rack, similar to Jasons tutorial.

    Also, the Center Channel Extractor is pretty unique in that it works only on specific types of audio. Music is what is was designed to work on, if you run it on a mono clip nothing will happen. Again, a video from you will showing how it isn't working will help clear up any confusion here.

    When launching any effect via the Effects Rack, the UI is different than launching it outside of the Effects Rack. When launched from the Effects Rack, there is no transport control UI in the effect window.

    Please, instead of us going back and forth ad nauseam, post a video showing what is not working so I can see exactly what istt' working for you.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    "With all due respect, I followed the work flow exactly as in the Adobe Tutorial where the individual accessed the Central Channel Extractor through the Effects Rack --> Stereo Imagery --> Central Channel Extractor and it led directly to him being able to have the floating effects panel offer the preview option and the Apply button directly in the pop-up menu. If that is no longer the case and that is not working in the software any more, that tutorial video should be removed and updated."

    At 50 seconds into the video that is exactly what he does. I don't see that the video is incorrect at all.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    I am part of the team that makes Audition, the Center Channel Extractor has not been removed or altered for quite some time. The person on the phone was simply mistaken.

    By looking at your screen shot it appears that you are trying to use the Center Channel Extractor effect via the Effects Rack, that is why there are missing the "Apply" button. When launching the effects via the Effects Rack, the Apply button is in the bottom portions of the Effects Rack panel, not in the floating effects panel UI.

    To see the play, loop, and Apply button (like shown in a large portion of Jasons tutorial) you will need to launch the effect from the menu: "Effects>Stereo Imagery>Center Channel Extractor...", not via the Effects Rack.

    "Central Channel Extractor would run but show an error about CPU and latency loading issues". This warning is just to tell you that the effect will use more CPU or have a higher latency than other effects in Audition. This is perfectly normal and you will only see this described if the effect is launched via the Effects Rack. If the effect is launched via the menu item as I described above, there is no warning.

    If the warning is causing issue, you can simply put a check next to the option "Don't show this alert again". This will suppress that warning dialog in the future.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    "Bring Back Central Channel Extractor"
    The center channel extractor has not been altered and is still fully functional. Your screen shot implies are accessing it via the Effects Rack, which functions differently than via the effects menu.
    Jason's video (which you linked above) covers this at 38 second mark.

    "an error about CPU and latency loading issues"
    The dialog is warning that the effect will use high amounts of the CPU and may not playback in realtime. It mentions nothing about a loading error.

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

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

    This has not been changed as far as I am aware. What previous version of Audition showed this behavior?

  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

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

    Hi Aaron,
    I'm unable to replicate this using a standard file. Can you give some details on how you are hitting this? Is it in the Editor or in the Multitrack, What is the sample rate of your source (either source file or the Multitrack sample rate). Are you working in the Effects Rack or on a stand alone effect? Are you using a preset with the effect?

    Thanks.

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

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

    "consider Snap to Zero as an outdated feature. Fade/crossfade is inherently destructive and might not be desirable in every circumstance."

    That is why we left ported the feature from the old code base to the new. For advanced user it is highly useful, but with great power comes great responsibility, and it can make selections harder to make if you are a novice and don't understand that a zero crossing is.
    Welcome to the world of building software, where everything is compromise and you literally cannot please everyone.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    @ GS
    Responding to each:
    1. If I fully understand what you are asking for, it is a feature request, as I previously stated. Audition has many ways to make selections, "Easy" is subjective though.
    2. When snapping is on, you can drag the selection edges and they will snap. This works.
    3. Snapping works on the mouse actions only. To extend a selection and have it snap to a marker, hold shift and click on the marker. Any existing selection will be extended to the snapped location of the mouse click (the marker in this case).

    An error occurred while saving the comment
    Matt Stegner commented  · 

    @Jim Coursey
    In the video you posted, it looks you have the global button for snapping turned off.
    In the upper right corner of the Editor view, click on the magnet icon next to the ruler. When it is blue, snapping is active.

    Also, Snap to Zero Crossing was added for legacy reasons from Audition 3.0 (the original code base). Current versions of Audition have a feature that automatically adds a tiny fade/cross-fade on edits in the Editor view. As long as you have it turned on (it is the top two check boxes under "Preferences>Data>Data..." you will not need to worry about zero crossings, and you can place edits at any location in the editor.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi All, Matt from Adobe team here.

    I've been looking at Audition 14.4 and snapping, as it is designed, is working here for me. The original video posted by GS does not show the snapping button. I've attached a video showing how it working and how to turn snapping on and off. Please let me know if there is something I am missing so I can investigate and file a bug.

    @Cindy Loyd The playhead does not snap to markers, it never has as far as I remember.

    @Jim Coursey "I want to be able to zoom in to set a marker for an edit point, zoom out, zoom in on a second edit point, zoom out, and then select the precise region from one to the next so that I can copy / delete / trim / loop. But this is impossible at present."

    This is possible, in the Multitrack, you will want to have snapping turned on, and use the Time selection tool. Please post a video clarifying what is failing for you.

    @David Gurney That functionality would be a feature request, Audition has never done that. I think it is good functionality though.

    I'm here to help, and posting a quick video of the issue showing the issue can save lots of back and forth and frustration.

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

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

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

    Just a quick note to say that this should be reverted, and the old behavior returned in the current Public Beta version of Audition.

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

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

    Thanks, I've verified and created a bug for this.

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

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

    Could you send a copy of your .sesx to audbugs@adobe.com so I can inspect it? Send it attn: Matt.

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

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

    You cannot redirect these files to a new folder, but you can simply turn them off and Audition will generate them on the fly when needed. The setting to turn them off is "Preferences>Media & Disk Cache>Save Peak Files..."

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

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

    Is this a request for Audition of Premiere?
    Audition has had clip groups and multiselect for years now. In premiere you cannot adjust fades as a group but you can apply them to groups of clips.

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

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

    There is no default keyboard shortcut for Silence, but Audition has an extensive keyboard shortcut editor where you can easily add one. Look under "Edit>Keyboard Shortcuts..." then search for Silence, and assign what ever keyboard shortcut you want.

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

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

    There are default commands to zoom in and out in Audition editor and the multitrack. "-" and "=" zoom in and on horizontally on the Playhead, and "option and -" and "option and =' zoom vertically in the editor and the multitrack.
    All of these commands can be customized via the Keyboard Shortcuts dialog.

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

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

    @Danny Kahler Could you be a little more descriptive on when it fails (or even better, get a video of the failure happening and post it here). I'm unable to replicated a failure like this on my end.

    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.

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

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

    I am not seeing this issue, I just tested this on an ARM based Mac with Premiere Beta build 15.2.0x22 and used a Presonus FaderPort 2 in Mackie mode via USB.
    It is working fine for me. Can you provide more information? What device are you using? Have you set the device up for Premiere 15? Are you on Mac or Windows?

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

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

    Ok, thanks for the follow up.

    An error occurred while saving the comment
    Matt Stegner commented  · 

    Hi, I just tried this and was unable to replicate. Can you provide some more info? Can you post a screen shot of the Audio Plug-in Manager for me?

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

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

    Can you post a picture of your timeline?

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

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

    Are you using the "Fill Left with Right" or the "Fill Right with Left" effect? If you are, then this is a known issue and will be fixed in the next release.

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

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

    "Media Encoder DOES NOT RENDER 3rd party vst plugins". This was a bug and should be fixed in the next version of Premiere Pro.

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

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

    @Matt Crum: Could you send me a project file that shows this bug? Send it to audbugs@adobe.com Attention Matt.

    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?

← Previous 1 3 4 5 10 11

Feedback and Knowledge Base