3 modulair area's editors with sub-levels ... ?

[liquidsound]

Question:
What would you tell me if I say I prefer (as an option) to have a Plugin popping up instead of the MPA? (read>>PREFER)
You need to answer in order to get to the next page.

Suppose it is working like i have in mind ( what maybe could wrong.. why not )

The MPA is not popping up, only if you choose it in the menu and if you choose a slot in a rack than the content i spoppping up

So if the Slot has a Zebra then the Zebra pops-Up, if I have a Synthia then the Synthia popsUp?, if I have a Sampla or a MultiSampla?
And why then you force the use the MPA just because you need to work on a MUX which, with your way, I need to get First to the MPA before I can get right to the Deep editor of the MUX? I must love your mouse buttons!

If you stop at the Auto placement of the slot content in the MPA then that's a welcome alternative, but you are forcing an alternative into a One Way choice, thinking, as usually normal mortals do (unlike leaders), that your way is waaaay better.
See, you are not saying: let add this for the benefits of giving more flexibility to users by giving an alternative choice.
You are saying: Never mind what Jo has come up with and it's working great. My way will make EVERYBODY happy and never mind who's not going to like it.

Well perhaps there is no need to have so much freedom in Mulab.. that is my idea

That's say everything...

[janamdo]

Well perhaps there is no need to have so much freedom in Mulab.. that is my idea

That's say everything...

Why you are so upset from this ?.. i try only to find a logical workflow
Perhaps i repeated too much my idea that you think it must be mine way
The next time i try to be more to the point.
No .. i am a Mulab user and not a developer so i am satisfied with the program
The purpose from my post is to try to improve MUlab

It was Jo who says that mysynthcore and Mux are overlapping in functionality
To reduce this overlap i thought my idea was a possible solution
I do not need have 3 modulair editors ..separated
In the mux deep editor can be used also for the mysynthcore and i stand alone mysyntcore deep editor can be removed
If i am can working from the MPA alone ( that's my idea ) than it is also good i think

[liquidsound]

Well perhaps there is no need to have so much freedom in Mulab.. that is my idea

That's say everything...

Why you are so upset from this ?.. i try only to find a logical workflow
Perhaps i repeated too much my idea that you think it must be mine way
The next time i try to be more to the point.
No .. i am a Mulab user and not a developer so i am satisfied with the program
The purpose from my post is to try to improve MUlab

It was Jo who says that mysynthcore and Mux are overlapping in functionality
To reduce this overlap i thought my idea was a possible solution
I do not need have 3 modulair editors ..separated
In the mux deep editor can be used also for the mysynthcore and i stand alone mysyntcore deep editor can be removed
If i am can working from the MPA alone ( that's my idea ) than it is also good i think

But, as I wrote previously, I like the Idea of having an Auto set up in the MPA for the Slot's content. What I was pointing out was just the Push toward the elimination of the existing method which made many of us comfortable and happy with (and made what MuLab is) and which ultimately, of course, is up to Jo to revoke or not.

I like your innovative spirit, don't get me wrong, but I found very little room in your posts for other users preferences.

Anyway, don't stop coming up with ideas (the Auto set up is a good one), this is a forum for all of this: discussions.

I hope I was not to hard on you suggestions. But again this is the way it is on forums (and life).

[sorohanro]

I was reading this thread and all I could understand is this:

But i do want to see this be done automaticallythis top-level modules by MUlab and forget the Mysynthcore and MUX modulair editors

That tells me actually:

But I want everybody to be automatically forced to work like I want and forget their workflow

sorry if I understood wrong

[liquidsound]

Deleted....

[MuTools]

Replying to a couple of different posts at the same time:

Jo from Mutools said that he want look at the mysynthcore and Mux because there functionalityis overlapping

I did not say this. I was talking about MUX and MuSynth.
But i also said that i need to research it more.

When you work on a effect(MUX) or sound than you are already in the session modulair window

Incorrect. The MSA - MUX/MuSynth - MuSynthCore modular editors are all 3 different in nature. As messaged before.

The only possible simplification may be to merge the MUX and MuSynth.
But again i need to research it more. I can't give more comments about this now.

All what you add to a rackslot is automatically showing up in the musession modulair window as i suggested

That's not how the system works. And it will not work like that in the future.

pljones explained it perfectly in this post: http://www.kvraudio.com/forum/viewtopic ... 15#4078715

You can have as many modular levels as you want.
If you (that is: janamdo) only want 2 levels, then feel free to only use 2 levels. That's your freedom.
But please also respect that there are other users that want to work in another way.

What could be an option is to be able to embed a module editor within the modular editor so that, for example, you could see the rack slots directly in the MSA as you would see a rack editor in the MSA.
Technically it's not what janamdo proposes, but practically it may look a bit like that.
In an earlier version of MU.LAB this already was a feature. But for technical reasons i had to drop it. (it was also not really used at that time)
But since the evolved rack system in M3, i could re-research this. Added a note on the wishlist about it.

[janamdo]

I was reading this thread and all I could understand is this:

But i do want to see this be done automaticallythis top-level modules by MUlab and forget the Mysynthcore and MUX modulair editors

That tells me actually:

But I want everybody to be automatically forced to work like I want and forget their workflow

sorry if I understood wrong

Misunderstanding .. don't worry ..at rack level MUlabs adds automatically in the MPA( or MSA =mulab session area..via menu) those rackslots (my idea)
Futher it works the same like it does now.
The same freedom of working with the deep editors (Musynth and MUX), but perhaps more logical

[janamdo]

When you work on a effect(MUX) or sound than you are already in the session modulair window

Not at the moment, you are not. When you open a MUX/MuSynth, you are in a different environment than in the session area.!

Misunderstanding..
Suppose Mulabs adds automatically the rackslots content in the MPA(or MSA..via menu)
If you click on a than on MUX or musynth(in the MPA window) you go to the deep editors
Now you must first go to the rack and from there and open the the deep editors

By adding the auto placement of rackcontent in the MPA tthere is a another way of working with the deep editors

[janamdo]

What could be an option is to be able to embed a module editor within the modular editor so that, for example, you could see the rack slots directly in the MSA as you would see a rack editor in the MSA.
Technically it's not what janamdo proposes, but practically it may look a bit like that.
In an earlier version of MU.LAB this already was a feature. But for technical reasons i had to drop it. (it was also not really used at that time)
But since the evolved rack system in M3, i could re-research this. Added a note on the wishlist about it.

Sounds interesting .. i do see it as a again another way of working with mUlab
It is enhancing the modularity..but perhaps i maybe wrong

[pljones]

Suppose Mulabs adds automatically the rackslots content in the MPA(or MSA..via menu)

Oh.... I thought there was a right-click option on the slot content to export it to the MPA already. Was that an older version or is my memory inventing stuff?

[MuTools]

You can 'Cut' a module out of a rack and 'Paste' it into a modular editor. (if that modular editor supports that kind of module, e.g. you can't paste a muverb in musynthcore)