Why use a MuSynth core

[liquidsound]

Is there a reason to use a MuSynth core in a MuSynth when I am just building something using only one MuSynth Core???

[janamdo]

Is there a reason to use a MuSynth core in a MuSynth when I am just building something using only one MuSynth Core???

woow man that is deep
What do you want to do with the musynthcore

[MuTools]

If you only want to use a MuSynthCore then only use a MuSynthCore.
It's as simple as that

[liquidsound]

If you only want to use a MuSynthCore then only use a MuSynthCore.
It's as simple as that

Sorry! I meant this: Why do I see MuSynth patches with the following:
Event Input > MuSynth Core > Audio Output

Now:

Whatever it is done in the MuSynth Core can be done right there at the first level of the Deep Editor right? Or I am missing something
If it is cosmetic then I may agree at the underling intention.
Or maybe is for easy future addition to the first layer of the Deep Editor leaving some space for future development.

The question remain: What's the intention of design?

woow man that is deep

I know!

[janamdo]

Now:

Whatever it is done in the MuSynth Core can be done right there at the first level of the Deep Editor right? Or I am missing something
If it is cosmetic then I may agree at the underling intention.
Or maybe is for easy future addition to the first layer of the Deep Editor leaving some space for future development.

The question remain: What's the intention of design?

For me is MusyntCore a high level module and a sound ... so it is easy to use this sound somewhere else (copy)for your own soundmaking.. acting as a template
Easy to work with only a rectangle!

The deep editor level 2 in Mysynth has no rubber band (in windows e.g)to select all this rectangles in one take ( you can only copy ..one for one )

Suppose you have a special sound in mind than use the musyntcore in deepeditor level 1 (copy a soundexample) and alter in level 2 the individual elements to get the desired result (sound)

You can divide sounds in the way they are constructed seems to me
All sounds in the Mysynth core are made via subtractive sound synthesis i think
There is no use of additive soundsynthesis (summing up oscillators to get Fourier series soundwave)?

[liquidsound]

For sure that is one of the Good reasons but I was thinking in terms of Techs.

Is this a more efficient way to handle modularity since the first level seems to be preferred for effects rather than sounds?

Should I (must I) use the MuSynth Core in order to do it correctly for MuLab engine?

I am still busy with other things but I am really planning to reWrite lots of sounds eventually.
I like to think waaayyy ahead if possible.

Thanks for your input on design intention.

[MuTools]

MuSynthCore is the core synth engine that handles polyphony.

And so it does not include any effects.

You can perfectly use a MuSynthCore on its own, no problem.

The MuSynth is there to add effects to it. And it also functions as an implicit indication that it is about a synth patch.

Recently i've been thinking/researching more about this and i am in the process of thinking that the 'MuSynth' level may be dropped because in fact there is only little difference between a MuSynth and a MUX. So as well synths as effects would all be done in the MUX. The MUX would be the one and only powerhorse. The advantage would be that the system is simplified. Synth patches would then be 'tagged' by simply putting them in the proper library subfolder e.g. Library/Mux/Synths/...

Anyway i need to research this more.

[pljones]

Can one supply an XML skin for a MUX(/MuSynth) patch? (Or is that a FR? )

[MuTools]

Theoretically yes, but it's not yet foreseen that it can be done by the user. I should research this more how to neatly make it available to the user, and then it should be documented. And i can't do that right now. So the practical answer for now is: not yet.

[janamdo]

Recently i've been thinking/researching more about this and i am in the process of thinking that the 'MuSynth' level may be dropped because in fact there is only little difference between a MuSynth and a MUX. So as well synths as effects would all be done in the MUX. The MUX would be the one and only powerhorse. The advantage would be that the system is simplified. Synth patches would then be 'tagged' by simply putting them in the proper library subfolder e.g. Library/Mux/Synths/...

Anyway i need to research this more.

What will be than the gui "workflow" in Mulab when the 'MuSynth' level may be dropped ?

[MuTools]

I first need to research this more.

[janamdo]

I first need to research this more.

Not neccessary anymore..
I do the work for you : see my solution http://www.kvraudio.com/forum/viewtopic.php?t=285681

[liquidsound]

Recently i've been thinking/researching more about this and i am in the process of thinking that the 'MuSynth' level may be dropped because in fact there is only little difference between a MuSynth and a MUX. So as well synths as effects would all be done in the MUX. The MUX would be the one and only powerhorse. The advantage would be that the system is simplified. Synth patches would then be 'tagged' by simply putting them in the proper library subfolder e.g. Library/Mux/Synths/...

YES!!! This is what was bother me. I was using MUX for everything and I could not really understand the MuSynth addition.

Thank you for your explanation. I will keep using the Monster MUX...


OK that was deep!