Sustainer - very high cpu usage

BETA TESTING
1

the sustainer works fine with midi data for me, but when sustaining the analog guitar signal i get very high cpu usage.

with a preset containing only the sustainer and string retuning modules the cpu meter turns red as soon as i hit a note.

1 Like
2

I saw your note here and did the most rudimentary test last night on my M3 iPad, to see if I could reproduce. I was running MG3 as a plugin in AUM, with a simple patch: two audio-only Chains each with just a Transposer (my 12-string sound). CPU baseline was maybe 5%. I added a Sustainer to the un-shifted Chain, and while I didn’t ping red by any means, it was a very noticeable bump in the MG3 CPU meter (new baseline was about 15%).

FWIW.

(not strictly relevant, but I thought the sound was pretty cool; I kinda dig how the piano sustain gives a bit of “harp-style” sound even with notes on the same string. :nerd_face: )

3

thanks for looking into this. are you running mg3 or mg3hex?

i agree on the sound shaping potential, i look forward to experimenting further.

4

I am “merely” MG3 standard. Getting myself into Hex is something I’d love, but even a GK or Submarine Sub Six is beyond my budget for now. (Oh, the design ideas I have for even a meager actual budget… :nerd_face: )

5

@jamo if the hex sustain is maintaining six separate instances that could explain the difference in cpu usage between standard and hex.

if so, would it be possible to have two sustain modes, one with the separate instances, and one with all six combined?

i can achieve this by running mg3 standard alongside mg3 hex, but it would be nice to have another option.

6

Yes, actually there is only a polyphonic sustainer. So, hex will mixdown and sustain the polyphonic signal. This isn’t ideal. I need to reimplement the audio side of the sustainer.

2 Likes