When activated together (or one with any other combination of Plug-Ins that need more than 1/4 of the green bar), this results in clipping sound. Each of them uses about 3/4 of the CPU resources (i.e. by targeting the plug-in workload to a core that is blocked from any other workload?) - just my hope!Īdditionally, I think it is fair to comment that it is strange to see that WaveLab itself comes with two of such resource-intense Plug-Ins in the “Restoration” tab, RestoreRig and DeReverb. However, it might be possible for you and your colleagues to further investigate possibilities to better use limited resources of Apple Silicon processors (e.g. This is, of course, linked to other undesired implications (such as that you can only play back with one plug-in at a time). However, there are other DAWs which take a different approach/use other techniques and thus don’t have that clipping issue. Last night, I have played around with other DAWs (which was never my intention since WaveLab’s functionality is pretty much perfect for my needs) and found all sorts of interesting things: There was one DAW which behaves even worse than WaveLab in terms of “making use of M1 CPU resources”, thus clipping even more than WaveLab. Maybe I was indeed exception too much from Apple Silicon-native Applications. ![]() I cannot see what else would hamper the performance? I store all files and applications on the internal SSDs, and there is still plenty of space left on this SSD. Or, is there another factor that limits the audio processing? And, as I have said, the performance cores in my machine are only used approximately 25%. So, there might be something wrong/different in the two software setups, since all M1 processors are the same, just some of them have more performance cores. The comment you have posted from the fellow user, cannot be confirmed by my experience. And the task that both applications perform is essentially the same: offline rendering of one file using the very same plug-ins. This is is contrast to the way, iZotope‘s Audio Editor Application performers: There, all cores are maxed out from start to finish. However, this is not the case.Īdditionally, when rendering a file, the same performance limitation apply as well. I would understand your comment if Wavelab would just utilize one performance core to the maximum. Other cores have up to 80% unused resources left. During the audio clipping (when audio processor bar is at full extend) there is still approximately 20% unused resource left on the one core of M1 which is most used. However, Wavelab appears to spread the workload „somewhat“ amongst the 4 performance cores that my M1 has, even today. I understand that audio processing is a sequential task in general. ![]() So, please be aware that as of now, WaveLab Pro 11.1 appears to be only capable of handling “light” Plug-In Workload! In essence, this is a worthless approach. This leads to Audio Drop outs if I just use one (1) of iZotopes Plug-Ins, not to speak about a chain of Plug-Ins. So, there is roughly just one fourth of the power of the machine used. In comparison, an optimized app (lets take a photo editor like DxO PhotoLab or the iZotope Audio Editor) utilize this machine with up to 750%. Even a background render just utilizes 138% of the CPU. However, when I try to use this combo to perform some tasks, my issues start to become obvious: The maximum amount of CPU usage that I will get is 140-180%. Additionally, I use some Plug-Ins from Waves (Restoration Bundle) and iZotope (RX9), all latest and greatest version, all as VST3. Just installed the latest version of WaveLab Pro 11.1 which “supports” Apple Silicon. I have a Mac mini M1 with 16 GB of RAM running the latest MacOS12.4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |