MVocoder CPU usage
-
- KVRian
- 1256 posts since 15 Mar, 2007 from Yorkshire, England
This is a great plugin but I am finding it very heavy on CPU. On a current project performance meter in Cubase reads 100% and struggles with mvocoder on. When I disable MVocoder the meter shoots down to about 40% which is a huge difference. Strangely if I leave MVocoder on but turn off the two modulators at the bottom CPU usage again drops from 100 to about 40% so those modulators are the things causing the issue.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
That's quite possible. You have to understand that with plugin of such depth some settings may be very cpu consuming indeed. Especially when modulating filter parameters. Try settings/settings and change the modulator protection.
-
- KVRian
- 1059 posts since 28 Jun, 2006 from Germany
Sorry for bumping this thread after a year, but I did not want to open a similar thread.
I also noticed that MVocoder seems quite huge on the CPU load. If I compare MVocoder to Vocodex (the vocoder inside FL Studio) it is very high on CPU, while Vocodex stays quite low, even with the vocodex HQ option enabled (disable "draft"). Is there any way to improve the performance, when using MVocoder? Or does anybody have any ideas what I might do wrong? Maybe there are some hidden quality settings I accidentially cranked up?
Btw: Vocodex can have even 1/4 of the CPU load, while using 2x bands
Info:
I used MVocoder inside MXXX, but also tested MVocoder only. They have the same amount of CPU load. I set up the bands the same way in all plugins. I used FL 12 64 bit and 32 bit. Win 7 64 bit.
I also noticed that MVocoder seems quite huge on the CPU load. If I compare MVocoder to Vocodex (the vocoder inside FL Studio) it is very high on CPU, while Vocodex stays quite low, even with the vocodex HQ option enabled (disable "draft"). Is there any way to improve the performance, when using MVocoder? Or does anybody have any ideas what I might do wrong? Maybe there are some hidden quality settings I accidentially cranked up?
Btw: Vocodex can have even 1/4 of the CPU load, while using 2x bands
Info:
I used MVocoder inside MXXX, but also tested MVocoder only. They have the same amount of CPU load. I set up the bands the same way in all plugins. I used FL 12 64 bit and 32 bit. Win 7 64 bit.
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, these vocoders are just different, hard to say how, I know the interior of MVocoder only 
. But I'm afraid I checked this several times. With the filters the plugin is using it just takes that much. There's a possibility of multitasking (who knows if Vocodex does that), but I'd like to get to multitasking with some more overall solution later.
. But I'm afraid I checked this several times. With the filters the plugin is using it just takes that much. There's a possibility of multitasking (who knows if Vocodex does that), but I'd like to get to multitasking with some more overall solution later.-
- KVRian
- 1059 posts since 28 Jun, 2006 from Germany
Ah okay. Already nice to hear. Thanks for your reply - we'll see what will come up in the future then. 
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
-
- KVRer
- 3 posts since 25 Sep, 2020
Hehe, now few years later i still find myself with the same problem didnt you find a solution for that so far?
didnt you find a solution for that so far?-
- KVRian
- 1094 posts since 23 Sep, 2006
I only find it heavy when bands and resonance are high. Which I guess you'd expect as that's a lot going on.