If a self-created *.mux plugin has multiple outputs, why doesn't MuLab or a DAW recognize them?
What might I be doing wrong?
Or do these outputs only work if I insert the plugin into a *.mux modular environment?
- did'nt find anything about this in the manual or here in the forum -
multi-output mux
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
In MuLab Plugin, it are the inputs and outputs in the project's modular area that are connected to the host DAW.
For more details see https://www.mutools.com/info/M10/docs/m ... oject.html
For more details see https://www.mutools.com/info/M10/docs/m ... oject.html
-
- KVRist
- Topic Starter
- 121 posts since 7 Apr, 2008 from germany
Unfortunately, this answer doesn't help me, because both the DAW and MuLab itself only recognize signals from audio output 1.MuTools wrote: Sat Sep 13, 2025 12:17 pm In MuLab Plugin, it are the inputs and outputs in the project's modular area that are connected to the host DAW.
For more details see https://www.mutools.com/info/M10/docs/m ... oject.html
However, within the self-created modular section, there are
audio outputs 1 - 3.
The DAW allows me to create IP for four plug audio outputs (ALWAYS four??), but only audio output 1 carries audio.
- - - - -
is there a preset in the MuLab Library which use more then on e audio-Out, so I can look into it??
(found noone)
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Why do you not find it the best way?jd88 wrote: Sat Sep 13, 2025 1:27 pm ok, in Mulab itselfe I found the way (build Co-Channels and connect cables) not the best way,
but it's ok)
It does work.but not 3rd part daws
I just double-checked it.
I'll share an example project soon, but i made it with M10.1 Plugin.
I just shared M10.1 Plugin for Windows 64 bit but now i realize you're on Mac.
(M10.1 for Mac will follow later)
About the concept of multi IO in MuLab Plugin:
It are the Input and Output modules in the project's modular area = the top modular level that are connected to the host. So you have to connect your MUX to the IO in MuLab Plugin's project modular area.
-
- KVRist
- Topic Starter
- 121 posts since 7 Apr, 2008 from germany
thx, will be very helpfullwrote: I'll share an example project soon, but i made it with M10.1 Plugin.
I just shared M10.1 Plugin for Windows 64 bit but now i realize you're on Mac.
(M10.1 for Mac will follow later)
. I'll look into it.-
- KVRist
- 251 posts since 3 May, 2003
jd88 wrote: Sat Sep 13, 2025 12:07 pm If a self-created *.mux plugin has multiple outputs, why doesn't MuLab or a DAW recognize them?
What might I be doing wrong?
Or do these outputs only work if I insert the plugin into a *.mux modular environment?
- did'nt find anything about this in the manual or here in the forum -
Although this video was created for a more specific use case, perhaps watching 0:30 to 1:26 and 7:45 onwards will help you with your setup.
-
- KVRist
- Topic Starter
- 121 posts since 7 Apr, 2008 from germany
Thx.
no, its not helping, because in MuLab I found this way myselfe (near like in your vid) and it's working (I think about an optical better integration, but it works. So; fine );
---
---
In an 3rd DAW it's not working.
I need to load "ONLY" the VST-plug and it has to work without any complicated workarounds. Like the other VST's do.
checked with Tracktion, Reaper, Renoise and many more:
---
---
this way will not work too
---
no, its not helping, because in MuLab I found this way myselfe (near like in your vid) and it's working (I think about an optical better integration, but it works. So; fine
);---
---
In an 3rd DAW it's not working.
I need to load "ONLY" the VST-plug and it has to work without any complicated workarounds. Like the other VST's do.
checked with Tracktion, Reaper, Renoise and many more:
---
---
this way will not work too
---
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- Topic Starter
- 121 posts since 7 Apr, 2008 from germany
This will work (example Renoise)
WHY I cannot save this in anyway if I edit this in MuLab-VST directly in a DAW? Its not usable to edit it like that anytime I wanna use the plug in a 3rd-part DAW.
This is how it has to work under the hood.
I found this the fastest and 2. best way to solve the problem. But from this view I cannot go back to the plug-in-view???? I've to open it now allways in this modular view. WHY? it will be fine if I can go back, so if I open the plug, that I'll not see allways again this modular view.
(best way: only vst-plug and DAW can recognize the OP directly without those workarounds)
- - - - -
WHY I cannot save this in anyway if I edit this in MuLab-VST directly in a DAW? Its not usable to edit it like that anytime I wanna use the plug in a 3rd-part DAW.
This is how it has to work under the hood.
I found this the fastest and 2. best way to solve the problem. But from this view I cannot go back to the plug-in-view???? I've to open it now allways in this modular view. WHY? it will be fine if I can go back, so if I open the plug, that I'll not see allways again this modular view.
(best way: only vst-plug and DAW can recognize the OP directly without those workarounds)
- - - - -
You do not have the required permissions to view the files attached to this post.
Last edited by jd88 on Sun Sep 14, 2025 10:52 am, edited 5 times in total.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Save an empty Project MUX with as many outputs as you think you'll ever need as "New" in your user templates. MuLab will then use that for any new creation of yours. Of course, it will not update any old creations of yours or anyone else's.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Exactly.
Glad you found how it works.
You can!WHY I cannot save this in anyway if I edit this in MuLab-VST directly in a DAW?
But you have to save it as a project, not as a MUX preset.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Jd88 please do not ask extra questions by editing an earlier post. Chance is too high no one will see that you edited your post. I accidentally saw it now, but, please, if you have additional info or questions on a topic, put it in a new post so that it will be seen 
I cannot guarantee that i will see your edits in the future.
I do not get any notification about edits.
This is a question you added afterwards:
Especially the info about the Project Main Module.
I cannot guarantee that i will see your edits in the future.
I do not get any notification about edits.
This is a question you added afterwards:
Please read that doc page i linked to.jd88 wrote: Sun Sep 14, 2025 9:04 am But from this view I cannot go back to the plug-in-view? I've to open it now allways in this modular view. WHY?
Especially the info about the Project Main Module.
-
- KVRist
- Topic Starter
- 121 posts since 7 Apr, 2008 from germany
Yes sorry, you're right , I've not to edit a post like I did. So here in a separat post
EDIT
After a lot of trial and error, I've finally found the solution.
Setup as shown in the picture, multiple tests, saving with VIEW, loading as a project, etc., etc.
Honestly: This is really way too complicated!!!!!
The same applies if you save it as a template beforehand, etc., etc.
So you have to save multiple versions of a plug:
Once as a regular plug, then as a *.mux for the MuLab mixer view, and then another version for VST? And this all the time, if you edit somthing in the plug itselve ...
Sorry, if that's the case, this is completely unworkable and would be a real hassle for a normal user who is simply given a plug.
You then have to explain each time when and how to load it.
------
A better solution is absolutely necessary here:
"The user can easily load the plug-in as they wish (whether as a MUX or VST) and wherever they want (MuLab or 3rd-party DAW), and it works "completely" without any detours."
I've never spent so much time puzzling over what and how to solve this (and I think I can say that I know almost every DAW and almost all the essential plug-ins, and I have many of them here as well).
Even though I now have a solution, I'm very unhappy with the current situation. It's hard to explain this to a simple user (beginner, etc.). And these users are definitely the ones who are otherwise perfectly addressed by MuLab.
- - - - -
The rule should actually be that a DAW should be self-explanatory (:D
MuLab and MuLab plug-in). Now this was the first platform on which I had to dig through instructions and tutorials regarding certain issues.
(And unfortunately, I didn't find some things.)
- - - -
Please don't misunderstand this post.
The POSITIVE side, of course, remains:
MuLab is a really great DAW, especially a great synth plug-in. Nevertheless, I wanted to get this off my chest.
, I've not to edit a post like I did. So here in a separat post EDITAfter a lot of trial and error, I've finally found the solution.
Setup as shown in the picture, multiple tests, saving with VIEW, loading as a project, etc., etc.
Honestly: This is really way too complicated!!!!!
The same applies if you save it as a template beforehand, etc., etc.
So you have to save multiple versions of a plug:
Once as a regular plug, then as a *.mux for the MuLab mixer view, and then another version for VST? And this all the time, if you edit somthing in the plug itselve ...
Sorry, if that's the case, this is completely unworkable and would be a real hassle for a normal user who is simply given a plug.
You then have to explain each time when and how to load it.
------
A better solution is absolutely necessary here:
"The user can easily load the plug-in as they wish (whether as a MUX or VST) and wherever they want (MuLab or 3rd-party DAW), and it works "completely" without any detours."
I've never spent so much time puzzling over what and how to solve this (and I think I can say that I know almost every DAW and almost all the essential plug-ins, and I have many of them here as well).
Even though I now have a solution, I'm very unhappy with the current situation. It's hard to explain this to a simple user (beginner, etc.). And these users are definitely the ones who are otherwise perfectly addressed by MuLab.
- - - - -
The rule should actually be that a DAW should be self-explanatory (:D
MuLab and MuLab plug-in). Now this was the first platform on which I had to dig through instructions and tutorials regarding certain issues.(And unfortunately, I didn't find some things.)
- - - -
Please don't misunderstand this post.
The POSITIVE side, of course, remains:
MuLab is a really great DAW, especially a great synth plug-in. Nevertheless, I wanted to get this off my chest.