M3 Tests

[liquidsound]

Now I found the "Templates" from where you can chose devices that you an use...
Should it be renamed ? Devices... Synths... Instruments ?

It seems (I am not sure because this is a Test Free version) that as soon you browse and choose a Plug-in, the context menu changes and the built in synths are listed by name and when collapsed they show the list of presets and the Template is no longer available in the first selection but nested inside a built in synth!.

Cool indeed but unpredictable at first.

and...a little strange

[liquidsound]

Jo, I think I found another alternative for the Plug Slot issue.

Arrow button:
as of now, LMB = Open Plug-in
how about, RMB = Close Plug-in (right now RMB is Null).
Or maybe a shortcut to close the Focused Plug-in...

What I am looking for is a way to get a Plug-in In and Out quickly for rapid adjustments of parameters via MIDI without going with the mouse up and down. On a laptop is even more important when the mouse is not available.

Actually a Shortcut to close the focused Plug-in would be even more effective in most cases. But both ways is even better.

As the Book says: Ask, and Ye Shall Receive.

Whenever possible...
<EDITED>
Never mind the shortcut!
I just saw the "Close" shortcut and i didn't realized it could be used for the Plug-in. Great!!

[theorize]

When it first starts up or a new project starts, I get an overload warning.

3.0.10 isn't doing this

[pquenin]

Edit Shorcuts :
I wanted to add shorcuts for "Loop on/off", "Record", because my midi keyboard has controls for them, and but no such thing in the list of shortcuts.
Maybe the tooltips in mulab, the menus entries names and the shortcuts functions names must be the aligned to simplify things.
And I don't understand what "generic" and "specific" is in the shortcuts system.
So, why don't we find all the mulab functions in the shorcuts, is it intentional, due to technical problems ?


Mulab 3.0.10 is very close to the perfection, congratulations Jo for your incredible work and reactivity !

[MuTools]

I think some care is needed on that... If you focus the rack, then fine, delete something in the rack should have no effect. But if you focus a particular target and delete it, surely that means you have to lose the focus? I can almost see myself expecting/wanting that to happen.

The only "intuitive" thing I can think that should happen is for focus to fall back to the container of the deleted target.

Sounds logical. Will try to finetune this.

[MuTools]

Do you mean you would rather want a doubleclick to popup the "Choose Target" list?

Yes.

What do others think of this?

[MuTools]

2-When you left click (once) the plugin in a collapsed rack it should expand the rack

It does!

Well, sometimes it does, sometimes not...it seems that if i don't click in the middle of the circle (in the collapsed rack) it just changes the white background to green...

Oops, you're right, there is an issue there. Will be fixed.

I've also made a small gui example of some (maybe) useful ad-ons like solo button, choose target and grid.
Here are some screenshots:
...

Thanks for the screen mockups.

My thoughts:

1) I think there is enough grid info in the mouse cursor display at the bottom-right of the editor. I try to keep the gui as simple as possible. The more texts, info, buttons, ... the more complex and the less transparant the gui.

2) Regarding the track headers: i had similar ideas, still evaluating this.

[MuTools]

The "save ok" dialogue makes a world of difference! Really good.

I'm not sure if I like the 180 you did on what key command makes real copies/ ghost copies, but then, we're animals of habit.

I managed to crash MU.LAB clicking around in a sequence while it was playing, though what exactly caused the crash is not in my power to tell:

crashlog

Thanks for the crash log. It seems to be in MU.LAB indeed. I'll try to repeat this. If others get similar crashes too please let me know what you last did, as it can be parts of the puzzle.

[MuTools]

Can the Mulab.txt file be commented, because we don't know what can be added, nor the possible values

http://www.mutools.com/mulab/docs/preferences.html

Updated docs coming when M3 is prereleased.

[MuTools]

Jo, do you have any future plans/roadmap...

Absolutely. And i whish i could R&D at double speed.

...on improvement on the internal synths, samplers and effects or is will your main focus stay on the host and sequencing features?

Both!

[MuTools]

Something I don't understand in the demo song : when you open this song, you see parts : some have a grid, some not, and those with a grid don't show the same grid...
Can someone explain me how this works ?

I think the grid inside some of the parts (KraftLine) is the length of the Part Loop, BUT, as you noticed the Key editor shows a grid of 4 Beat. By changing the Grid settings you can divide it but it seems that if I choose 2 beat or Bar the Visual 4 lines (4 beats = Composition measure) do not change. It should indeed, unless it's set to the original grid at the moment of creation.

Or maybe Jo wants to keep the major lines to reflect the Composition Beats per Bars

Indeed, the lines inside a sequence part indicate the sequence loop.

Sequence loops can be edited inside the sequence editor.

[Nielzie]

I don't know what others think of it, but personally I would prefer to have the loop points standard "on" (enabled). It's what I'm used to this from other daws I have used, and now I always have to put them on again.. I use this function a LOT.

Anyone else having the same preference or is it just me?

[MuTools]

first, a minor glitch report:
in the shortcut editor, under the undo/redo manager section, you can choose to make a 'rename' shortcut.

Thanks for reporting.

now, a little comment on how splitting parts using the split shortcut works. in the above situation, if we use a 'split' keyboard shortcut while sequence 'a' is highlighted, only that sequence will be split, no matter which one of the sequences the mouse pointer is hovering. this is good. if we use a 'split' keyboard shortcut while all three sequences are highlighted, all three sequences will be split. this is good. now, if we use a 'split' keyboard shortcut while none of the sequences are highlited, they will all be split again. this should be fixed imo. if none of the sequences are selected, either none of them should be split, or the hovered one should be split.

It works 100% as intended.

It's consistent with the behaviour in other editors.

E.g. when you have a T = Transpose shortcut, and you press T in the sequence editor, then only the selected notes are transposed, but if no notes are selected then all notes are transposed.

[MuTools]

Looks good, a bit too dark (I liked more the previous 2.7 skin and color palette).

Strange, nothing has changed in this aspect. It's the same skin.

The first bug was when I created a new rack while demo song was playing. While creating it I had a noisy click sound, the MASTER rack was showing clipping and also my souncard's mixer.

Lets keep an eye on this.

Another thing, I find confusing that you can't create instruments by choosing device (sampler, multisampler, synth...etc) but by browsing patches of instruments.
This way I spent minutes and couldn't figure out how to load a simple Multisampla and load my own patches

The reason why i switched from a "N synthss each give M patches" to a single "NxM" patch list is because it's my belief that in fact it' doesn't matter which synth engine makes a patch.

With the new system we have 1 contiguous patch library, which is a real advantage, imho.

And you can still easily choose an empty MultiSampla if you want: Synths -> MuSynth -> Templates -> MultiSampla.

[MuTools]

Now I found the "Templates" from where you can chose devices that you an use...
Should it be renamed ? Devices... Synths... Instruments ?

It seems (I am not sure because this is a Test Free version) that as soon you browse and choose a Plug-in, the context menu changes and the built in synths are listed by name and when collapsed they show the list of presets and the Template is no longer available in the first selection but nested inside a built in synth!.Cool indeed but unpredictable at first.
and...a little strange

I don't see what you mean. No such intended behaviour. The patch list should always be the same. No?