Sub tracks in Mulab 4?

[janamdo]

I think that the same subtrack concept like in Mulab 3 in Mulab 4 will be present ?

If so..than a more userfriendly approach for automation is maybe than possible in Mulab 4
The possibility to choose a automation track in the menu and not automation tracks..than at least you now where to focus on
Now it seems that Mulab getting more complex concerning automation is it time to organize this automations better
For a sound manipulation you can use the automation data again in a other song..perhaps it possible to setup different automations for the same sound to use in a composition
If you can store this automation data somewhere in Mulab and load again
Note:
By the way the word automation is not existing in the manual, so..?

[janamdo]

When it possible to choose a automation track ( as a subtrack ) than on the header of the track a JUMPMENU for choosing automation parameters adding.

So you can right away stay in the composerscreen and choose your automation target there in de menu entrance of the jumpmenu

Perhaps it is also possible to make a distinction between ...
Mulab instrument parameters
Vsti parameters
Midi parameters

for automation

[pljones]

Perhaps it is also possible to make a distinction between ...
Mulab instrument parameters
Vsti parameters
Midi parameters

I don't agree on the first two - conceptually I see these as the same: automation parameters. The last one is different: generating MIDI events. Whilst the editor should feel the same as automation of parameters, what's happening is not. (Automation generates a float, 0.0 to 1.0, however it's expressed; MIDI events are 0 to 127 -- and yes, it's important to be able to see the exact number in the MIDI case.)

[MuTools]

MuLab 4 will give you nice new options in this area.
Forgive me i keep the details for later.
It's tempting to start talking in detail about M4, but i really first want to finish R&D so that i can spend the necessary time communicating about it.
A first test version is really getting closer, october is realistic.

[Bonteburg]

Count me in for the Beta testing!

[janamdo]

Perhaps it is also possible to make a distinction between ...
Mulab instrument parameters
Vsti parameters
Midi parameters

I don't agree on the first two - conceptually I see these as the same: automation parameters

Yes, but i am looking to the practical use of it
I don't want to mix these parameter automations subtracks with eachother
Some organizing keeps things clear.
Ok when i use a Mulab synth track , than there is Midi automation and native Mylab synth automation possible
Although it is also possible to assign a VSti to a sequenze part ina track.

So there is group of 3 automations tracksdata possible for a track and the automation follows the flow of the music for a instrument
It seems for that it is necessary to recognize easy what automation data is involved

[janamdo]

MuLab 4 will give you nice new options in this area.
Forgive me i keep the details for later.
It's tempting to start talking in detail about M4, but i really first want to finish R&D so that i can spend the necessary time communicating about it.
A first test version is really getting closer, october is realistic.

Yes i am excited about this coming new release of Mulab:
Right out the box to use for the newbie ( the instruments are standing Ready..)with no first to understand a concept to get going ( although personally i doesn't bother me, but for a real music starter problematic)

At first sight easy to use..and than for the more advanced music lover enough tools to compose whatever you like

[MuTools]

Count me in for the Beta testing!

[Stephan326]

Count me in too!!!