M3 Tests

[pljones]

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.

[gemada]

Jo,
Thanks for your reply...MULAB 3 is becoming better and better

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

Yes.

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...


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:

[Bonteburg]

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

[Nielzie]

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

Yes that was exactly what I was thinking. When replacing an instrument in a rack the midi focus should stay imho focused on the container where the replacement has been made, instead of the synth that has been replaced.

If that is possible of course (focusing on container instead of instrument).

[theorize]

I really like this M3..

Ladies and gentlemen I hereby declare that from now on I will use MU.LAB as my main DAW


Bye bye EnergyXT2 and Orion 7... just uninstalled

I'm with you man M3 has been a huge step in workflow improvement. Of course I had already given up on all the others a long time ago and the only VST host I've been using was tuna and only to make samples to feed Protrekkr. I can't give up protrekkr but it looks like now I can step back into using a modern host again, and I won't really have to use that many plugins with it I think.

Thanks for clarifying Jo I have the day off I'm going to do that and see how it works.

I haven't checked the latest beta but there was something I forgot to mention about the others; When it first starts up or a new project starts, I get an overload warning. Though it doesn't appear to really be overloaded since everything works fine and when I click on it it goes away. I'm going to try it on a different computer tonight when I test portability and see if it persists.

[theorize]

this is just pure sci-fi but all this talk about navigation gave me an idea... it would be pretty cool to use a joystick in conjunction with a mouse to move around.

[pquenin]

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

[pquenin]

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 ?

[Nielzie]

I'm with you man M3 has been a huge step in workflow improvement. Of course I had already given up on all the others a long time ago and the only VST host I've been using was tuna and only to make samples to feed Protrekkr. I can't give up protrekkr but it looks like now I can step back into using a modern host again, and I won't really have to use that many plugins with it I think.

You mean Tunafish from Bram Bos? I tried that one too. That one hasn't been actively developed for years Unfortunately it crashed all over the place when I migrated from XP to Vista.

And that's also what I like about MU.LAB, the development and support. Jo is very actively developing it (but don't forget to rest once in a while Jo ) and is listening very well to the input of the users.

Now with M3 I finally have the feeling it has been improved and finetuned enough for my personal workflow and needs so I can use it as my only vst host/sequencer.

And it's amazing to see how fast it evolves into such a wonderful little host, isn't it?

[Nielzie]

By the way, I really love Synthia's voice

Musynth sounds great too, but at this point it's too deep and modular for me to program myself

Jo, do you have any future plans/roadmap on improvement on the internal synths, samplers and effects or is will your main focus stay on the host and sequencing features?

No hurries, I'm just curious

[liquidsound]

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

[bpblog]

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

now, a little comment on how splitting parts using the split shortcut works. let's observe the following picture:


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.

[pquenin]

no, it's logic because when I want to split several parts at once, I only go to the correct position where there is no part : I don't have to select all the parts before : it's good like this. So the shortcut do the same, it's OK for me.

[bpblog]

well i know, it's very cool when you want to split several parts at once.

but splitting is a somewhat destructive operation, and i think that mulab should manage it with more sense of precaution. i mean, just clicking somewhere and splitting the whole screen feels like using a katana.

the way i see things, it should work like this:
- triggering the split shortcut would split a sequence hovered by the pointer, regardless of it being highlighted or not
- if several sequences are highlighted, all of them are split if one of them is hovered when the split shortcut triggers

this way, if you don't want to be bothered highlighting a group of sequences, you would still be able to quickly split them all by hovering them with the mouse button and triggering the shortcut a few times. like a fps game.

to me, this kind of setup seems more precise. but if you guys don't like it, oh well.

perhaps we can have a separate 'split' and 'katana split' shortcut?

[sorohanro]

Posted previously in the wrong thread:
"Ok, so I got the new Mu.Lab (mulab-3-0-10-win.)
Looks good, a bit too dark (I liked more the previous 2.7 skin and color palette).
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.
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

Also, why the demo song is so loud that clip ? it's not good for soundcards. Should be a limiter on the MASTER or made a bit quieter."

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

I totally love the way MultiSampla manage the samples, you don't have to browse/ find every single sample in a pack
Also, to my ears, sounds a bit "crispier"