Hi!
I am using Metafilter on 2 channels in a Live Set (Ableton 12.0.20) and even if the playback is paused can see the CPU usage of Metafilter is killing my Processor. It’s happening alternating. When channel a with Metafilter is calmed down, the other is rising and so on. That lead to the consequence i was forced to export every channel as an audio file so I am able to listen to it at 192khz for the final mixdown.
I deactivated the HQ button and tried to reload a new instance but nothing worked.
I’ve got an Intel i9 13900 (water-cooled), 64gb DDR5 Ram, 2tb Samsung Pro Evo whatsoever SSD on the Asus Pro art X670. (Graphics is a ProArt Nvidia RTX 4060 Ti 16GB GDDR6 ram). - I think it’s not a hardware error.
Is anybody able to give some advice?
Thanks and kind regards
Hi @derfritz,
Welcome to the Waves Forum.
The MetaFilter will consume his share fair of the CPU even at lower settings than 96 kHz.
If the issue persists on a supported sample rate, 96 kHz or lower, please consider Contacting Technical Support and allow them to investigate if you think there is a technical issue or abnormal CPU usage.
Actually you would think the HQ button should have worked, because that often translates to oversampling in Waves products.
Ins saying that, though, maybe it doesn’t oversample at all when used at 192k. I know some devs employ that approach, don’t know about Waves.
192khz is not supported with Metafilter. That may well be the problem.
If you look at the Waves Sample Rate Support page – Sample Rate Support - Waves Audio
You’ll notice Metafilter’s highest sample rate support is 96khz.
Is the problem only happening at 192khz? Does it go away if you drop to 96khz? If so, you found the issue.
PS. If you own a lot of Waves plugins it’s worth looking through there so you’re aware… Waves has one plugin (Flow Motion Synth) with a max sample rate of 48khz(!) Most max out at either 96khz or 192khz.
And for anyone else – beware if you’re using a wrapper or Reaper/Sonar to force oversampling, it’s not going to work correctly if your oversampled frequency exceeds the limits on that page!
PS #2. Don’t just assume everything is OK if the plugin appears to run at a higher sample rate. A lot of times it will appear to be normal but the math will be incorrect with various processes, knobs, etc.
1 Like
It’s also worthwhile remembering that oversampling adds latency. SO its not the kind of thing you really want if you’re tracking or performing live with a plugin.