M4 Test

[MuTools]

Fine tuning:

Sometimes, there's a short but noticable gap between the last click of the count-in and the start of a recording. This could be related to the number of times you have recorded in the same session before but I'm not sure.

Could it be that this happens when you're not positioned on a beat when starting recording?

[MuTools]

Fine tuning:

I recorded automation from the same parameter (Filter 3) of two instances of MuSynth (via GUI-knob tweaking).

The automation lanes both say "Filter 3" without telling you what MuSampler they belong to.

That's normal behaviour as MuLab will not include the full 'modular path' in the module name, that would really be overkill.

In case you have confusing auto track names, you can rename the tracks as you want via the tracks context menu.

General tip: If you assign the "R" key to the generic "Rename" function, the R key will work on any renamable object that has UI focus. That's one of the strong points of the shortcut system.

[MuTools]

Right Click on the Top Keyboard could be used to pop up the virtual keyboard...

Implemented in the next version, thanks!

[MuTools]

That's because all sessions are fully active in parrallel.
If you want you can mute a session via right-click on the play button -> "Switch OFF".

Ah, another "workflow" issue .

Would it be possible to automate this based on which session has focus..? Although I can see why you would not want this...

During R&D i experimented with this, but i felt it's better to have all sessions active in parrallel, and let the user decide whether some must be switched off.

"The main problem", I guess, is that "Open" creates a new session, rather than replacing the current session. Particularly with "Open Demo", this ends up with potentially many sessions open consuming CPU.

Ideally, there would be two menu options: "Open" and "Open in new session" (or the other way around, depending which should be default). Most of the time, I'm only working on one session: if I open another, it's because I've finished with the current one. Having to separately close it is an overhead I'd like to avoid. (Requiring "Switch OFF" is fine if I do choose to have multiple sessions open, in this case.)

When you open a session via the MULAB menu, it's a new session on top of the open ones.

When you open a session via the SESSION menu, it will replace the current session.

Does that work for you?

[MuTools]

A new MuLab 4 test version is available in http://www.mutools.com/mulab/cedar

Full package has changed as some graphic and library files have changed too.

What's changed:

* Splitting envelope parts now properly works.
* Changing the start of envelope parts now properly works.
* When inserting a new VST plugin using the "Browse..." option, there was a memory leak. Fixed.
* On first startup, when the demo sessions are listed, there is also an "Open..." option to open another session.
* Factory New.MuSession uses a nicer metronome click sound.
* Top panels have been re-ordered in such way that all controls are more close to eachother; keyboard fills the remaining space at the right.
* Fixed a possible crash bug wrt drawing sequences.
* Fixed a rare sonic bug in the synth engine.
* MuSampla device preset now has a more appropriate preset release time of 500 ms.
* MUX Play editor now uses consequent colors for the parameters.
* MuPad E3 now immediately reflects changes in the meta-parameter setup.
* Right-click on Focussed Module Panel => option to "Show Virtual Keyboard".

Looking forward to your feedback!

[MuTools]

I'm really interested in beta testing this on Mac. I've been moving from Logic to Reaper but I'm always open-minded and Mutools has a lot going for it.

Do I email the general Mulab email or is these an other address?

You can email me via

You can find the latest MuLab 4 test version here: http://www.mutools.com/mulab/cedar

Eventhough MuLab may not be a traditional DAW but rather a blend between a DAW and an instrument, i'm looking forward to your feedback, especially to your open and frank comparison between Logic, Reaper and MuLab. (Besides the fact that M4 is not yet multicore. That's planned for M5)

[liquidsound]

When I D&D a Synth from a Rack into a Track the color scheme is broken. It would be more coherent if the Slot in the Rack, where the Synth is, could obtain a form of visual clue together with the Track Header. Same as you do with the Rack/Track relationship. It would be more elegant and congruent with the new color system which I think it's brilliant!

You can also color the modules in rack slots. In fact any module can be colored!

That said, i'm a bit hesitating whether coloring the rack slots is a good thing, it might be overkill, but not coloring them breaks the coloring link.

Also going back to a previous post, is it possible to have a used parameter being checked or highlighted in the long list when it has being used?

In which list you mean?

The parameter list in the piano roll. For example if I use a filter knob in Zebra I then need to find it nested in the parameter list and their abbreviated names makes the whole process like hunting a ninja!
If the parameter used by that knob could be checked or highlighted would make it so easy and practical to find it. Sometimes you talking about more than 100 or more parameters to sort through. It is not just a matter of scrolling to it, but the problem is their names which very often it is not the one written on the synth UI
For example in Orion the parameter name is highlighted in pink. Well.... You can use a better color

[MuTools]

I'm open to improve things of course but please tell me: Why do you need to see the current parameter in that list? I mean: If you open that list, you won't open it to choose the same parameter, right? So you will be looking for another parameter. So why would you need highlighting the current one? Sorry if i'm missing something obvious.

[spaceman]

I'm really interested in beta testing this on Mac. I've been moving from Logic to Reaper but I'm always open-minded and Mutools has a lot going for it.

Do I email the general Mulab email or is these an other address?

You can email me via

You can find the latest MuLab 4 test version here: http://www.mutools.com/mulab/cedar

Eventhough MuLab may not be a traditional DAW but rather a blend between a DAW and an instrument, i'm looking forward to your feedback, especially to your open and frank comparison between Logic, Reaper and MuLab. (Besides the fact that M4 is not yet multicore. That's planned for M5)

Cheers Jo. That's how I always describe a host like Renoise as well (and Reason)
I think it's a great concept and these host tend to be very direct, which I love.

[liquidsound]

I'm open to improve things of course but please tell me: Why do you need to see the current parameter in that list? I mean: If you open that list, you won't open it to choose the same parameter, right? So you will be looking for another parameter. So why would you need highlighting the current one? Sorry if i'm missing something obvious.

Because the one I just recorded, is not displayed by default. Only velocity are there as usual.
I record a part by playing or write directly with the pencil tool.
Then I record some filter variations or other obscure stuff in zebra ro whatever synth.
Hit stop, choose Merge, open the piano roll and the new recorded parameter is not there of course. Only velocity still showing. From there I then need to go into the Parameters list and choose the one I just recorded BUT, as you know, those list can be quite long and the names are abbreviated and different from the synth UI, even showing double names according to the synth pages etc. It's a real pain to find what you want. And if you got lost in playing and move several of those parameters on the fly.... well good luck in find them all. You need to go one by one.

[AndreasD]

@liquidsound
The parameter list in the piano roll shows on top any parameters or controllers which are in the sequence. That could help finding existing things quickly.

I am just playing with U-He's Diva in an ACE based session with a lot of automation. Urs has badly recognizable parameters. Some with the same name. And I was changing parameters from ACE to Diva (best done in the list editor/select all/ double click parameter) and the curve disapears after changing a param, but is in the top Content list of the piano roll param list.

If you are manually creating automation, use envelope parts and use the "Drag last tweaked parameter" in the Option menu of the synth. Tweak a synth knob, select the option and drag it on an automation track and the problem with parameter names is gone.

Andreas

[pljones]

Does that work for you?

It would if I'd tried it, I'm sure . That makes perfect sense.

Although there's no Open Demo there. And the problem was triggered by having a stack of demos open -- and that's what's going to cause problems, if anything. People demoing MULAB may end up thinking "Oh, CPU usage isn't good" or "lots of crackles" without realising they've eight demos open all eating CPU.

[liquidsound]

@liquidsound
The parameter list in the piano roll shows on top any parameters or controllers which are in the sequence. That could help finding existing things quickly.

I am just playing with U-He's Diva in an ACE based session with a lot of automation. Urs has badly recognizable parameters. Some with the same name. And I was changing parameters from ACE to Diva (best done in the list editor/select all/ double click parameter) and the curve disapears after changing a param, but is in the top Content list of the piano roll param list.

If you are manually creating automation, use envelope parts and use the "Drag last tweaked parameter" in the Option menu of the synth. Tweak a synth knob, select the option and drag it on an automation track and the problem with parameter names is gone.

Andreas

ANDREASD!!! I can't believe it! I missed those on TOP!!! I was playing with DIVA as well here in the office. I need to go and check my Blind Spot. Maybe it has moved
Sorry Jo!

[Bonteburg]

...while the parameter automated is the correct one, it says "Pan" on the automation lane, potentially causing confusion.

This is the same behaviour as in MuLab 3.

I'd say let's forget about it then - if anything this goes to show how little I use my keyboard knobs in non-test situations. And I don't recall anyone ever complaining about it.

...short but noticable gap between the last click of the count-in and the start of a recording.

Could it be that this happens when you're not positioned on a beat when starting recording?

Hmmm... will check!

The automation lanes both say "Filter 3" without telling you what MuSampler they belong to.

That's normal behaviour as MuLab will not include the full 'modular path' in the module name, that would really be overkill.

+1.

General tip: If you assign the "R" key to the generic "Rename" function, the R key will work on any renamable object that has UI focus. That's one of the strong points of the shortcut system.

Nice!!

Cheers

[janamdo]

I'm open to improve things of course but please tell me: Why do you need to see the current parameter in that list? I mean: If you open that list, you won't open it to choose the same parameter, right? So you will be looking for another parameter. So why would you need highlighting the current one? Sorry if i'm missing something obvious.

But if i read this from @liquidsound than has he a good point for finding easy the right parameter in a list..by coloring it!
Does Mutools understand this from @liquidsound considering his reaction here above?
Or do i miss something and was @liquidsound wrong?

For example if I use a filter knob in Zebra I then need to find it nested in the parameter list and their abbreviated names makes the whole process like hunting a ninja!
If the parameter used by that knob could be checked or highlighted would make it so easy and practical to find it. Sometimes you talking about more than 100 or more parameters to sort through. It is not just a matter of scrolling to it, but the problem is their names which very often it is not the one written on the synth UI