You could argue with " I'll catch up on that in the end", but that makes life again only more difficult than it must be, because many decisions like the range of instrumental distribution, the usage of particular instruments at all, EQing and also adding plugins to single instruments depend largely on the avaiable space for each instrument in context to the composition. And you can't do proper gain staging if you start to work right away from the very beginning with a limiter on the master bus that pushes all instruments to their limits. Gain staging ensures that all of your instruments have room to breathe and that all of them together, the final signal on the master channel, don't cause any kind of distortion and clipping after exporting. So yes, it is about space - and how much it is about space! It is about using the avaiable space (volume) to distribute your instruments in the best possible balance. There can't be infinite instruments peaking at 0dB without your outcome becoming distorted and muddy. When you export in the end, you definitely have an audio budget. 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.This means, you'll have to do proper gain staging no matter if you temporarily make use of the benefits of floating-point processing and smash your volume bars into infinity without causing instant distortion. 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. 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. 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 Comments
Leave a Reply. |