Premiere CC 2017 Adaptive Noise Reduction Delay Issue

[JesseMS42]

Hi Everyone,

I edit a lot of interviews and often the footage that is supplied to me has background hissing noise. When I apply the Adaptive Noise Reduction or the DeNoiser effect to a clip there is about a two second delay after I export before the effect works.

I've tried extending and lowering the volume, I've tried putting all the clips that need it on it's own track and using the track mixer to apply the effect, nothing seems to work.

I know I can do this in Audition but when it works in Premiere after the delay its easier, and I think it sounds better.

Does anyone have any suggestions? Am I exporting it on the wrong settings? Is there something I am missing?

I know this has been a problem that has plagued lots of people for years, I don't know why Adobe has not fixed it yet.

Thank you!

[JesseMS42]

IT WORKED! Thank you so much! This is a great solution.

[jasontcox]

Awesome! Glad to hear it. Especially since I just re-read my response and realized step 3 had a huge typo in it when I said "out point" and meant "in point"! lol

[elaineb70415244]

This is ridiculous and I am trying to edit a voicer over and the few seconds are throwing out the sequence.  Is there not another solution?

[jfredrickson01]

I'm struggling so hard with this right now. I'm editing an interview that had some background noise and adaptive noise reduction works great until I have to make some cuts. Now I've got the background noise jumping up high at the beginning of every cut. It's really jarring. The workarounds sound great for single clips, but what are you supposed to do when you are making many cuts in one clip?

[tsu_fum10291677]

There isn't much that can be done but more work with a few seconds ahead of the video clip.  Unless CC 2018 solved the problem, that is the only solution. Even Audition doesn't have a solution. Now, the best solution I have found since having posted my last post about it being a workflow killer was to edit it all to the final product then rendered/exported all the audio and took all the audio to Pro Tools where I was able to get exactly what I wanted. Softwares designed for music is the solution. Even as I thought Audition was designed for that, it isn't. It still lacks some pro qualities that softwares like Pro Tools are built for. There are free music softwares out there that you may find more helpful for voice over or voices in clips.

[Oren Agami]

I found a partial solution, it helps to avoid the two seconds bug if you want to apply noise reduction to multiple clips, in cases such as interviews etc: Unlink the audio from the video and nest it, then apply the effect on the nested sequence. Using this method will contain the bug to only the beginning of your main sequence.

[julianm44443758]

I have the same problem with the delay with Adaptive Noise removal, I'm running Windows 10 and I was told by someone in Adobe that the delay is because I don't have a soundcard in my relatively new computer.  I doubt that somewhat. I was told I don't need a soundcard by the computer sales person when i bought this computer,  Do people in this thread who have the problem with Adaptive noise removal delay as well, have soundcards or not ?

[tsu_fum10291677]

Hi there Julian,

You do need a sound card and a great one or top of the line so you can run everything properly just like you need a great CPU, GPU, and fast and/or plenty of rams. The computer sales guy either wasn't sure what you were talking about and didn't inform you properly or didn't know what they were talking about. It is night and day when you have a great sound card VS a stock sound card.

My laptop was specifically designed for gaming with a great sound card, high end CPU/GPU and 64 gigs of ram total. And as most gaming towers or laptops will have a descent to high end sound card to give customers a full package experience and even with my laptop, that problem is still present in my editing.

The problem is the ANR itself as it needs a few seconds to sync in with the sound before it can be applied as truth is it shouldn't and be applied immediately no matter where you choose to cut the video. All the solutions we have written down work but it consumes your workflow especially if you are on a time base work.

Unfortunately, choose one of the solutions written and don't get too frustrated.

[OsakaWebbie]

I don't have any sort of special computer, and I run Premiere Pro just fine. Sure, a better CPU, GPU, and soundcard will render faster, look smoother, and sound better while you're working on your project, but I don't think the computed end result will be any different.

[tsu_fum10291677]

Hi there,

You are right indeed if you have no deadlines and are completely okay with the speed of your workflow.  However, over the years for me I have found that the need for a fast computer is important because it is all about workflow for me as my clients have deadlines for me to meet and I also have my own deadlines for my own projects to meet.  I do video editing, photo work, 3D work, CGI, and VFX and have began to do it all in 4K.  I can say this with great certainty for me is that my workflow has greatly increased from my A computer to my B computer.  And already I cannot wait to purchase my A tower with the latest tech to take my workflow to the next level and leave both my laptops as back up computers when my A tower is doing something super taxing.  For me, I need a fast computer but for you, your needs may be completely different from mine, hence, why you are okay with what you have. 

But in regards to the problem we are all complaining about, it is definitely an Adobe issue because I still have that problem and so do many of us.  My hope is that it will be fixed with an update.

[OsakaWebbie]

As you acknowledged in your second paragraph, my point was simply that the issue discussed in this thread is not related to the type of hardware one is using, in spite of what julianm44443758 was told by someone.

In the case of a clip that is used in its entirety (there is no content prior to what is in the timeline), I can understand that ANR has no way to get a running start, but when there is something there but not in the timeline, it would seem at first glance that the ANR code should be able to look at the unused content to develop its beginning noise print. On the other hand, a tricky thing is the potential of other effects on the clip above (applied before) ANR - some of them could affect the noise print also, so as a developer of ANR, do you extrapolate backward those effects at the settings of their first keyframe, or what? In software this complex, nothing is simple. (I'm a programmer myself, so I can sympathize with the challenge.)

[tsu_fum10291677]

Challenges is what makes a company great if willing to take it on and make the program even better than before making us the customers happy who pay for it and will continue to pay for it.  I hope they welcome this challenge and show us why they are indeed top dogs in the field among many others.

Premier and Audition has always ran well for me but even with obsolete, I had the same problem at the beginning of every clips I cut.  From there, I took all of my clips to Pro Tools and resulted exactly in what I wanted my clip to sound like with less background noise that gets recorded no matter how quiet an environment is.  I would suggest to them to speak with developers who do nothing but with sound software design and bring that tech to their software.

This is their forte and the answers I leave to them to find so my $60 a month is worth my paying for software I need to work day in day out.  Do I feel sorry?  If I did, if we all did, Adobe wouldn't have come this far.  Because we didn't, they have come a long way by creating software we need and are willing to pay for.  I put my faith in the programmers to figure it out just as my clients don't feel sorry for the amount of work I put into their videos because they paid for result and don't care about the amount of hours I put into it.  All they want is the end result.  And I enjoy this way of thinking because no matter what, I hold myself accountable with no excuses especially when I mess up shots.  

Perhaps you can help them since you are a programmer. I'd like to hear more of what you believe is wrong with the software and what you believe can make it work. 

[OsakaWebbie]

I have no interest in dropping what I'm doing and applying for a job at Adobe - I'm content to be a consumer of their software. Plus, the sort of programming I do these days is quite different - online databases are a far cry from heavy-duty signal processing. I merely meant that I can easily imagine how hard it is. Sure, we should hold software of this caliber and expense to a high standard, but I think that overall they do a good job of providing powerful, low-bug-rate software. So, like you, I find the functionality worth the subscription (I juggle projects in print design, web development, and video - these days I spend more time in InDesign and Photoshop than Premiere). Sorry, I don't have a list of bugs and suggested fixes. I just came to this thread to find a solution/workaround for this one.

Fortunately, my regularly occurring video projects are single-audio-track, so I can get away with the Sequence In/Out workaround. If I have a more complex project before Adobe fixes this, I'll try Oren Agami's nested sequence trick.

[tsu_fum10291677]

No worries no worries.

As you said, the software they have provided are great and have gotten better every 2 to 3 years to ensure the demand of all artists who use their complete master collection. I surely enjoy their products as I mostly use After Effects, Premier, Fuse, and Photoshop. In time I'll learn to use all other programs.

I know it is a great tasking to be a developer but that is the route they have chosen and so I simply say: "Fix it and keep us happy because noise reduction is a huge part of videography and filming."

All of our solutions are sound and until Adobe takes care of it as you said, we just pick what works best for us in hopes our workflow doesn't get hit too hard.

[psion99]

I just learned that you can apply the "adaptive noise reduction" effect to the whole track in the Audio Track Mixer window.  That gives you a hiss on the first two seconds of the very first video clip, but does not have an issue with any of the subsequent clips.   So just put your dialogue track on A1, make sure there are no gaps between the files, and hopefully it should work.  I'm testing it now, and so far, it seems to help

[cameronc27155319]

Shame on you Adobe

So if the audio track mixer with denoiser isnt working for you, give this a try.

>Apply denoiser to entire track with noise using audio track mixer.

(this should now reduce noise on all clips apart from the first which still has a 2 second delay)

>Add a few seconds of noisy sound before your first clip.

>Apply a volume effect from the volume pannel to this noisy sound clip. (not the normal volume controls)

>Reduce the db until silent

[stephenseagull]

I didn't know you could apply effects with the mixer...

I did it clip by clip and extended a few seconds ahead of every clip, then did a volume effect to mute the handle after the adaptive noise reduction filter.

[Novel_MP]

I ran into this yesterday on a video. I ended up rendering out just the VO as a wav file and then pulled it into Logic to process the HVAC noise. Rendered out of that and back into Premiere. The Adaptive Noise Reducer is a decent tool once it gets going, but that 1-2 seconds to start up is a dealbreaker. I appreciate all the creativity into the workarounds, but we shouldn't have to do that. Render and replace is NOT a solution either. Adobe needs to fix this, either with an "Apply" or "Process" button that applies the effect non-destructively. That's also one of the problems I have with the "Audition" workflow. Hitting that "edit clip in Audition" is dangerous. It's very clunky to "go back" if you make a mistake or aren't getting the results you want.

[stephenseagull]

Agreed we shouldn't have to do this but the method that jasontcox invented / explained works very well and non-destructively all within Premiere. I used longer handles than 1 - 1.5 seconds but that's the only variation.

[jblo]

I understand it needs to analyze the sound to determine the noise before it can reduce it.

But why not make it like the stabilize effect? You apply it and it looks at the entire clip in the background, then applies it.

Maybe it takes a little time, but it's certainly quicker and more effective than adding 3 seconds to hundreds of soundbites.

My 2 cents.

[OsakaWebbie]

Agreed, jblo. It doesn't even need to look at the whole clip - just looking at the first few seconds would suffice. And if it did that, it would work even on clips that don't have any extra on the front even in the original source.

By the way, I just got a notification of Albright Productions responding with their workaround, but "View the full discussion" link goes to a different thread ID (https://forums.adobe.com/message/10384457) which doesn't exist, and the response is not here either, even though their profile says they responded on this thread (see https://forums.adobe.com/people/Albright%20Productions/content?filterID=participated). Weird. Anyway, their method sounds even more complex than other workarounds proposed - two round-trips of exporting, importing, and replacing audio.