@kevin the only issue there is that I'd have to have a section of clean room tone to use in the first place to capture the noise print from. Right now, I get audio from various sources and room tone isn't provided. I have to go in and manually delete chunks of audio that are too loud to be room tone. I can whittle an hour long audio clip down into room tone in about 15 minutes, but I'm slowly manually doing what an algorithm could do in seconds. The best workaround right now is to use other software, which is what we're doing. But I truly think this feature would be beneficial to a number of Audition users. ... View more

@kevin This is exactly what I was looking for! It would be amazing to have this feature out in the open instead of buried in a menu so we could adjust it more frequently ... View more

This would be a neat addition, but in the meantime, you can rename Caribbean and Cerulean (and all the color labels) to whatever you want. ... View more

I used to have this issue in the mid 2010s. Started capturing some tapes yesyerday. Sure enough, 8 tapes later and now I'm getting the blank (not black, grey, like theres no video even attempting to play) issue discussed here. Everything else is working, I'm just flying blind.   Disabling my integrated Intel UHD Graphics 630 and relying on my dedicated NVIDIA GeForce card seems to temporarily fix the issue as a workaround. For now at least.   If you have two graphics cards, perhaps try disabling one 🤷‍:male_sign: ... View more

I'm having the same problem in Windows 10 using the newest version of Premiere Pro (15.0.0, Build 41)   Proxies are toggled off, but the Export Frame option is exporting the proxy for no apparent reason. I want it to export what I'm seeing in the Program window.   Please fix this bug ... View more

Re-installed both. Tried installing Au before Pr. Cleared preferences too. Same error. Errors twice for every clip I try to import ... View more

Glad I'm not the only one in the world with this bug. Can you come vote to have this bug fixed? https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/34053712-bug-lumetri-color-creates-garbage-glit… ... View more

Vote for these ideas to get fixed! Fix Alt+Scroll Zooming on Windows Machines with Display Scaling Enabled – Adobe video & audio apps Zoom to mouse on timeline (Alt + Scroll) Broken – Adobe video & audio apps ... View more

Yeah, same here. It was definitely faster in the previous version. I really wonder what they changed to cause this to happen. I've heard they're more likely to fix issues if multiple people report bugs, so if you want to file an official bug report, it might help. I'd hate for this to be one of those issues that persists through years of new versions. ... View more

My colleagues and I are having the same issue on Windows 10. Previous version would save in a reasonable amount of time. Now that we're using version 15.0.1 (Build 73), my colleagues and I all have excessively long save times. What does your project look like? The one I have open right now that is saving slowly has: ~20 mp4 HEVC files (3840x2160) ~16 comps ~8 Black Video (they came in from Premiere Pro, so they're all the same) at least one Photoshop file Two of the comps have a 3rd-party plugin on them. All of my project files are very similar to this one. I reported this as a bug to Adobe last week, but unless others have similar issues, I'm not sure they'll take it seriously. ... View more

I, like davidpayne1981, have also used the bug report form with no luck on a number of occasions. This is one of them (the Alt+Scroll to Zoom bug specifically). There's a much less egregious bug that really doesn't harm much that's been around for years that I reported officially and on the forums. If you hold down the alt key and put your cursor over the timeline, right around where the colored lines are (red, yellow, green... the line that shows you how choppy playback is likely to be), you'll get a hand cursor, and you can actually click and drag the Work Area around... even when the Work Area bar is completely disabled. I get why a bug like this might not get patched out, because is it really worth the time to fix? Is anyone besides me (and the people I point it out to) going to notice, or care? Officially reported bugs like these ones not getting worked on don't make as much sense to me. Also, just ignore Jim_Simon in this thread. Whenever I've seen him come across a bug that has a workaround, or is a bug that doesn't affect him directly, he's very dismissive (even if he is technically correct). Kevin pointed out as an official that the best workaround is to not scale our screens... we already know that, and have known about that for 2.5 years. Some of us have laptops with 4K (or even 2K) screens. Whether we chose to buy them ourselves or were gifted them. Sometimes we may want to edit on the go. Most of us wouldn't want to lug around a monitor as it wouldn't be practical. There are situations where Jim/Kevin's workarounds aren't that helpful, because we're stuck with small, high resolution screens. Hopefully the developers will take this more seriously now than they did years ago, now that it is becoming much more prevalent every day as people upgrade to 4K monitors. Serious question for Kevin-Monahan​ though. Is it beneficial to submit multiple bug reports for the same bug? There's been a number of updates since I first reported the bug... how long should I wait before submitting the same bug report for lingering bugs? Once a new version gets pushed out, are bugs from older versions of Premiere just assumed to be fixed, and that's how they could get lost? Or would it be better to submit the bug report just once and hope it doesn't get lost in the shuffle? But what happens if/when some bug does get lost in the shuffle and years have passed? ... View more

This is still an issue in the 2017.1.2 update! ... View more

Using a very brief crossfade does help, but I use longer crossfade durations intentionally, and can be anywhere from .3 to 1s. Sometimes the room tone outside has changed due to traffic and I want to blend the two audio clips together (louder traffic, and the less-loud traffic from my reference room tone). Sometimes the sounds recorded are in a room with lots of reverberations and I want to use a longer crossfade duration to keep the reverberation tails of sounds. There are plenty of situations I've come across where the room tone is just different enough for a ~5ms crossfade to be much too short to blend two similar (yet slightly different) audio clips. ... View more

I figured there was a logical, mathematical reason this was happening. But it does seem like it would be unwanted by users, no? Are there any instances where an artifact like this would actually be a useful result? Using "bug" in the title was probably misguided, but it does seem like something that could be improved, no? ... View more

The other company's software can generate room tone from a clip where there isn't any notable room tone. You can run it over dialogue and it will come back with something. The more clean room tone there is, the better it is at coming back with a decent result, but it works either way. My colleague has been trying it out and is very impressed with how well it works. It might be enough for us to switch software, or use both (which is obviously less than ideal). ... View more

In a perfect world, you're right. But sometimes we have to shoot near a highway or outside on a windy day, and we aren't able to mic every speaker individually. Or shooting an interview inside a running factory. Field recording is messy. The image I showed was 2 to 3x louder than most normal situations would be. The result shown is still sadly very perceptible to the human ear. I'm sure I can't be the only one in the world who has to repair source audio recorded from a single mic that's was recorded in less than favorable conditions... can I? ... View more

I have this issue all the time in real life with various room tones. Outdoors with lots of traffic and rumbling, indoors with A/C, indoors with no A/C. Any time I have any sort of background noise, this same thing occurs. Brown noise was for easy visualization. The same thing happens with any crossfade durations I've tried. It's much less noticeable if you have a longer crossfade duration (close to 1s or higher), but that's because the dip becomes so much more gradual that it's much less noticeable. ... View more

Good question! I kept the defaults; 2 and 5 ms respectively as shown in your screenshot ... View more