Hi!
I've got a strange problem with Mux running the default patch "Pipe Organ 1" when it gets input from the Cthulhu Arp. First it worked, but after saving projects with it (one in Mulab and one more in Reaper), it suddenly started to only replay at a very low volume (the reverb send?) and the Mux plugin button becomes Orange and says "(num voices=48)".
I tried deleting the plugins, resetting the patch, reloading the projects with no success. It's very weird, because it worked with Cthulhu before. When I turn off Cthulhu, the Mux starts to work again - without the arp input, of course.
Does anybody have an idea what's happening? It seems to be Cthulhu's fault , but what's going on? What does an orange button mean?
Problem with Cthulhu (both in Mulab and other DAWs)
-
- KVRist
- 107 posts since 28 Aug, 2014
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
-
- KVRist
- Topic Starter
- 107 posts since 28 Aug, 2014
The event monitor only shows the notes from the arp, which seem to be alright, but there are many of them. I cannot select and copy & paste them here (doesn't work). The modular for "Pipe Organ 1" shows that the "Church Organ" module is overloaded, i.e., the "Church Organ" button is orange. Interestingly, when I switch off the "Amp Env" and "Amplifier" in the "Church Organ" patch, I get a crushing distortion noise. (No problem, there is an automatic protection.)
I can probably fix this by inserting another church organ vst, but out of curiosity: What is overloading? Does the patch get too many input signals within a given time from the Arp? Is there a way to prevent this?
DSP processing is not overloaded in general, this occurs on an i7920@3.8Ghz when no other synth is running.
Edit: What's kind of weird about it is that it worked before. I've played the project many times. Then, suddenly the problem occurred and it hasn't gone away since.
I can probably fix this by inserting another church organ vst, but out of curiosity: What is overloading? Does the patch get too many input signals within a given time from the Arp? Is there a way to prevent this?
DSP processing is not overloaded in general, this occurs on an i7920@3.8Ghz when no other synth is running.
Edit: What's kind of weird about it is that it worked before. I've played the project many times. Then, suddenly the problem occurred and it hasn't gone away since.
-
- KVRist
- Topic Starter
- 107 posts since 28 Aug, 2014
Okay, I've investigated this further and have found out that this is definitely caused by xferr record's Cthulhu, because totally weird things also happen with another vst instrument (first works, then the arp goes crazy). Sorry for the false alarm! Everything is fine with Mux. 
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe