I don't know why it does it, but it does and it's been doing it since day 1 many years ago for me. I've had it happen on songs that I just started with one or two tracks and I've had it happen on songs I'm almost finished with that had 50 or more VST's including a Limiter, in all stages of buffer setting from low for tracking to high for mixing. It happens when adjusting VST's and there's no repeatable pattern to cause it. So having a Limiter in place won't stop it from happening. I thought it was a fail safe of some kind that shut the audio engine down when the internal level got to a certain point and it was displaying that max level but I was completely wrong. I assumed it was a dB level because when you hover over it it says "Clip / Peak Levels" but it is actually the amount of times clipping occurred not how loud the clip was. Mwright pointed out in my original thread that I was wrong about it being a dB level and I'm glad he did because it makes a big difference in this case. I wonder if it's because I use a -1 or -2dB limiter 98% of the time on the master. I'll consider myself lucky as this has never happened to me.
ICE9 AUTOMUTE DRIVER
If it IS the interface / driver that's causing the blasts, then it's dubious that something like Ice9 will prevent the issue, since the plugin will likely be "upstream" of the noise blast.Scottyo7 wrote Wow. Noise blast issues seem to be more widely reported by users with USB audio interfaces like Focusrite Safire etc., so perhaps it's a USB thing? I've been using MOTU interfaces the whole time - first the PCI based 2408 systems, and now the AVB+Thunderbolt 112d+1248 boxes - and their reliability and predictable performance is part of the reason why I stick with them.
ICE9 AUTOMUTE MAC
I definitely use just about every VI and library you can think of, and never had this issue, from the Mac G4 era through G5's and cheese graters all the way to the cylinder Mac Pro. In 20+ years of using Logic's native audio I have NEVER had a noise blast, so unless someone can narrow it down to a particular VI or library causing it in a repeatable manner, I'm inclined to suggest it's due to the audio interface's driver taking a crap. When the noise blast happened, did it show up on Logic's meters? Like, did the peak-hold indicator show some ridiculous level like +700db? If so, then it WAS coming from inside Logic, but if not, then it was coming from the audio interface driver and was therefore "downstream" of Logic's audio engine. So yes, it would be helpful for anyone to file a bug report with Apple (I did). Something is weirs, but at least I was able to isolate and reproduce it. In a worst scenario, these piano clusters would result in a little bit of clipping, even though my levels are not even high enough for that. I wonder what is actually triggering Logic to create such noise. Once I tamed the piano cluster chords it was fine. Thanks to the Ice9 plugin I was able to see it happen repeatedly without anything getting hurt.
ICE9 AUTOMUTE PRO
Last night I moved my production to my new Mac Pro (2019, 16 core, 224RAM) for the first time and low and behold, the same issue persisted there too (Catalina 10.15.6 vs Mojave on the Trashcan 10.4.6) Some stacked clusters with sustain pedal enabled caused triggered Logic to go into a frenzy. It was an instance of NI's grand piano The Grandeur. I found out where the noise burst came from.
Shouldn't a DAW have such a safety mechanism built in? Not sure how it actually happened but that is rather irrelevant to the question of how can we protect ourselves from such things in general?ĭoes anyone know if there is an application out there that can monitor the computer's audio out ports for potentially harming noise and suppress it on detection? It did not happen like this before and I could not reproduce it afterwards. Recently Logic gifted me with a truly deafening and absolutely dangerous burst of noise.
0 kommentar(er)
