M4 Test

[MuTools]

Updated version M4064 in the same webfolder, which includes a change log file.

[MuTools]

Ok,

it only works here, if I choose "Browse" to locate directory and "New file"...

It doesn't work here, if I leave the default entries on the "save as" dialog...
It doesn't work here, if I click directly in the text boxes "Folder" and "Name" to change to desired folder and filename...

I'm sorry for my previous message on this, i guess i retried after it was fixed.
It should be ok in M4064

[Trancit]

And Jo,

please can you check the multisample in MuSynth...

1. Open the multisample editor, draw a new zone, rightclick and "delete zone" causes a crash here everytime

2. I draw in a zone and load a sample for it...if I now expand the zone to more than one half tone (lets say before zone was from C3 to F3 and after loading the sample I expand the range to G3 instead of F3) the pitch changes...
Expanding the zone only one half tone doesn't change the pitch...

Btw, why there is no root key setting??? Could be very handy...

How does the pitch detection for the root key in the multisample works??? From file name or embedded root note data or both???
What does MuLab, if there is no data at all available???

[Trancit]

Ok,

it only works here, if I choose "Browse" to locate directory and "New file"...

It doesn't work here, if I leave the default entries on the "save as" dialog...
It doesn't work here, if I click directly in the text boxes "Folder" and "Name" to change to desired folder and filename...

I'm sorry for my previous message on this, i guess i retried after it was fixed.
It should be ok in M4064

Confirmed... Save as bug is gone

Cool close dialog...so what's next...made me smile

[janamdo]

I use also karmafx in MUlab and the structure of audiopath and modulations is also easy visible as blocks and cables
There is a visual logic there in the soundconstruction, because the basic module elements do have the same position in the deep editor there all the time when i browse thrue the sounds of a soundbank.

I like to see this also in MUlab on polysynth level( if possible)
There are 2 levels of modules in the deep editor and the first level is the complete synth sound with additions.
This works 100 % when i go thrue the sounds for level 1 in the deepeditor.
But on level 2 in the deepeditor ( when i open deepeditor level 1 and 2 both screens at the same visible for me )it is not possible to scroll thrue the sounds, because Mulab is crashing than.

The event input with all those blue lines can this not be simplified?
Is it possible to remove the event input ?

[Nielzie]

The closing bug has gone

Nice idea to have an extra "so what's next" dialog windows when closing Session. And also very nice to have [Devices] on top of the Instruments and Effects lists

The MULAB and SESSION menu's right next to each other seems to work fine. One thing I personally would prefer is that the "Play"/"Record" buttons and display where in the middle of the screen, like in M3. But I may be in the minority with that

Maybe in 4.x or M5 it would be interesting to be able to drag the 3 visual menu buttons/display/items on the top to left and right positions ourselfs if possible. That and tabs for the Session Windows would make it ideal imho

[MuTools]

1. Open the multisample editor, draw a new zone, rightclick and "delete zone" causes a crash here everytime

Confirmed. Will fix. Thanks!

2. I draw in a zone and load a sample for it...if I now expand the zone to more than one half tone (lets say before zone was from C3 to F3 and after loading the sample I expand the range to G3 instead of F3) the pitch changes...
Expanding the zone only one half tone doesn't change the pitch...

Btw, why there is no root key setting??? Could be very handy...

How does the pitch detection for the root key in the multisample works??? From file name or embedded root note data or both???
What does MuLab, if there is no data at all available???

All that is related:

If MuLab finds a key-name in the sample name like "Trumpet-D4" it will set the root key to C4 and so the multisample zone will use that root key.

If there is no explicit root key set, the multisampler uses an implicit rootkey which is in the middle of the zone.

You can edit the rootky of a sample via the sample's popup menu.

[MuTools]

This works 100 % when i go thrue the sounds for level 1 in the deepeditor.But on level 2 in the deepeditor ( when i open deepeditor level 1 and 2 both screens at the same visible for me )it is not possible to scroll thrue the sounds, because Mulab is crashing than.

I assume what you call 'level 1' is the MUX, your 'level 2' is a PolySynth within that MUX. I think it's easier to call things by the actual name.

Anyway, i tried to crash M4 while switching patches with all deep editors open, but could not repeat it. Can you give me a step by step, using M4064, how i can repeat this crash? Thanks.

The event input with all those blue lines can this not be simplified?
Is it possible to remove the event input ?

You can remove it, but then that MUX/PolySynth won't be able to receive events.
For PolySynth that's absurd as a synth needs notes to play.
For MUX it may be ok to have no event input, eg for an audio effect without meta-parameters. Note however that automation from the composer also works with events, so a MUX with meta-parms best has a event input so the meta-parms can be automated. But it's your choice & freedom as a patch designer.

[Trancit]

All that is related:

If MuLab finds a key-name in the sample name like "Trumpet-D4" it will set the root key to C4 and so the multisample zone will use that root key.

If there is no explicit root key set, the multisampler uses an implicit rootkey which is in the middle of the zone.

You can edit the rootky of a sample via the sample's popup menu.

Wow, this is really hidden...but documented after 4 times reading...

Case closed, users fault...

[Trancit]

One thing I am still interested in:

How far can you reach with further optimizations???
I noticed, that MuLabs internal modules take about double or more CPU cycles than VSTi equivalents, especially multisample playback is quite high on CPU...can you achieve this??? Will there be enough room to lower CPU consume by half???

Because there will be still no multi core support in M4, this is a quite important thing to me...

[MuTools]

Optimization is what i'm currently working on.
Still researching though, up to now i did not yet found the very bottleneck(s).
Continuing the search...

[MuTools]

I noticed, that MuLabs internal modules take about double or more CPU cycles than VSTi equivalents, especially multisample playback is quite high on CPU.

'Double or more', that's really a lot, that's not what i see here.
Can you please mail me the exact comparison setup and numbers. Thanks.

[janamdo]

This works 100 % when i go thrue the sounds for level 1 in the deepeditor.But on level 2 in the deepeditor ( when i open deepeditor level 1 and 2 both screens at the same visible for me )it is not possible to scroll thrue the sounds, because Mulab is crashing than.

Ok, it seems that it is working now 100 % when i scroll thrue the sounds in the play editor and on MUX level and sound construction level too.
Perhaps more userfriendly to try to get a division in the deep editor( the name is also not so clear , better is is to chance this to "sound construction editor")

I assume what you call 'level 1' is the MUX, your 'level 2' is a PolySynth within that MUX. I think it's easier to call things by the actual name.

Yes definitely, but there is no clue in the gui what kind of screen this is.
In fact it is the MUX editor..
The MUX seems to be difficult to find and is now become a basic effect?

So the "sound construction editor"( replaces the name for the deep editor) and exist of the MUX editor and the sound editor

Perhaps is it possible to add a button on this MUX screen to go to the actual sound itself?
MUlab detects than the second screen and add a button for it
It seems that soundconstruction start with a basic synth(=MUX) and the module MUX is disappeared?
The event input with all those blue lines can this not be simplified?
Is it possible to remove the event input ?

You can remove it, but then that MUX/PolySynth won't be able to receive events.

Not remove completely, but make a event connection on the module itself(on/of) ..so the blue lines are not necessary anymore

For PolySynth that's absurd as a synth needs notes to play.
For MUX it may be ok to have no event input, eg for an audio effect without meta-parameters. Note however that automation from the composer also works with events, so a MUX with meta-parms best has a event input so the meta-parms can be automated. But it's your choice & freedom as a patch designer.

Is it possible to open the 2 screens of the deep editor at he same time and then go scrolling for sounds so that the 2 screens stays open?

Further for "Add Module" in the deep editor i like to see the name "Others" for adding modules in the deep editor chance in a other name : sound construction

[Reincke]

Hi M4ists,

have just opened the Demo "Distant Moon #3" (previously upgraded to 3.2.14) in M4 (4.0.63). There are more than 4 Tracks now. This behaviour is different to M3. Why that? Bug or feature? Haven't found a hint in release note or this forum.

Auf Wiedersehen.
JR

[Nielzie]

I think I may have found a bug or at least it's something that behaves differently from M3, where it probably shouldn't.

When I have Sonic Charge MicroTonic open and I set it to play from its internal sequencer (so I'm NOT playing midi from M4 sequencer) it starts to play like supposed to, but when I add an effect in the rack below it while it's still playing, then it stops playing imediately.

This does not happen in M3 (or any other hosts I've used before). When I add an effect there while uTonic is playing it just keeps playing.

So something is different there. Quite annoying personally, because this is my go-to drum synth/sequencer..

Anybody else using MicroTonic or perhaps another plugin with built in sequencer that can be played while host seq is idle, who can confirm this?