M4 Test

[MuTools]

Does that work for you?

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.

Right, i see your point.

At the same time, when the user quits MuLab, he'll see that he has to close multiple sessions. And on windows each session has its slot on the taskbar so that's a visual indication too.

Anyway, we talked before about the possible confusion between MULAB -> New/Open and SESSION -> New/Open and i still have that point on the wishlist, will further think how to minimize confusion.

I do am convinced that the multi-session feature is a great thing to have because you can drag-drop parts, racks and modules from 1 session to another.
So if you have several ideas and want to merge some of them, that's possible using drag-drop. Or if you're cooperating on a track and each one has worked on a version, now it's much easier to merge the best edits into a master version

[MuTools]

@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!

No prob, i'm happy you found what you were looking for

[MuTools]

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

I will keep this on the wishlist as i think you make a point.
Maybe, when recording a MIDI controlled parameter, it should indeed be recorded as a parameter, not as a MIDI controller. On the wishlist for further evaluation/implementation.

[janamdo]

that's a visual indication too.

Anyway, we talked about before the possible confusion between MULAB -> New/Open and SESSION -> New/Open and i still have that point on the wishlist, will further think how to minimize confusion.

That i why i suggested earlier to chance the name New session --> in New Multi-session to get no confusion

[liquidsound]

that's a visual indication too.

Anyway, we talked about before the possible confusion between MULAB -> New/Open and SESSION -> New/Open and i still have that point on the wishlist, will further think how to minimize confusion.

That i why i suggested earlier to chance the name New session --> in New Multi-session to get no confusion

Why not having the new Session window Cascade and so on, in this way you are aware of an additional session and you have the option to just maximize the new one in an instant. The point is that by cascading a new session you get an immediate feedback of what's happening and still within the usual expected GUI behavior.

[MuTools]

That i why i suggested earlier to chance the name New session --> in New Multi-session to get no confusion

Janamdo, thanks for your suggestion, i've read that, but it's not the right terminology, imho.

If i don't reply on something it implictly means i don't see a benefit in replying on it. Sometimes i also wait with replying until more opinions are there and/or i found the time to reflect on it myself. There are many suggestions here on the forum, much thanks for that! I do read everything, but in order to optimize my time spending, i try to keep my replies as essential as possible. All with the goal to optimize MuLab development as much as possible. Hope you understand. Please keep on suggesting! I hope you already noticed i do listen to user feedback, and you saw the results of that in MuLab. Thanks again!

[janamdo]

I contribute with pleasure some ideas to Mulab.
Yes it is more difficult than only chancing a name.
Cascading the two mulab programs seems to be possible
The user noticed than that there with "new session" a new mulab program opens

A other idea is chance "new session" in "Open New Mulab Program"

[liquidsound]

Jo I'm looking at the color scheme and I see that when you drag a VST from a slot to the track, if the VST has a color then the Track gets the same color as well (works like the Rack to Track color). This is good indeed. But if the VST slot is white then the track of course default back to gray. Not so nice.
I did some visual test to see how it looks if the VST slot inherits the color from the Rack. It's not so bad looking and this prevents the Track from turning gray. (What others think about this?)

An issue appears in giving a color to a Rack. When you choose from the "Choose an Instrument" popup window (near the mini keyboard area) we have an option to set a color (test the sound = great!) for the Instrument Rack but when we choose directly from a New empty Rack via the popup menu we need TWO steps to set a color.
It's a little bit inconsistent with the flow.

Wouldn't be more consistent if we had the same popup window at the Rack level rather then a menu? In this way you can choose the color and additionally (if you want) we could have color choice for the VST slot itself too. One popup window that does everything and appears everywhere the same. No confusion and uniformity of functions/design.
It's more like having more control in setting up a new instrument or a rack: Choose the VST, Rack color, Slot color, test the sound, and whatever you will dream to put into the popup window making it very powerful due to those clever category buttons on top which can grow as you need. I think that window is a brilliant idea. Why not use it anywhere you can?

[MuTools]

Jo I'm looking at the color scheme and I see that when you drag a VST from a slot to the track, if the VST has a color then the Track gets the same color as well (works like the Rack to Track color). This is good indeed. But if the VST slot is white then the track of course default back to gray. Not so nice.

Yes i realized this too and am working on something.

An issue appears in giving a color to a Rack. When you choose from the "Choose an Instrument" popup window (near the mini keyboard area) we have an option to set a color (test the sound = great!) for the Instrument Rack but when we choose directly from a New empty Rack via the popup menu we need TWO steps to set a color.
It's a little bit inconsistent with the flow.

Wouldn't be more consistent if we had the same popup window at the Rack level rather then a menu? In this way you can choose the color and additionally (if you want) we could have color choice for the VST slot itself too. One popup window that does everything and appears everywhere the same. No confusion and uniformity of functions/design.
It's more like having more control in setting up a new instrument or a rack: Choose the VST, Rack color, Slot color, test the sound, and whatever you will dream to put into the popup window making it very powerful due to those clever category buttons on top which can grow as you need. I think that window is a brilliant idea. Why not use it anywhere you can?

Because the Add New Instrument dialog is specific for instruments.
And in rack slots you can also insert effects and sends, and that makes it not a simple step to use that dialog also for rack slots. Maybe this can evolve in a future version.

[MuTools]

Anyway, we talked before about the possible confusion between MULAB -> New/Open and SESSION -> New/Open and i still have that point on the wishlist, will further think how to minimize confusion.

Simple idea: When a new session is opened on top of already opened sessions, MuLab could give a little auto-hide alert stating the number of open sessions.

(FYI: an auto-hide alert is the same as when you do Session->Save i.e. it pops up and disappears automatically after a second.

[liquidsound]

Jo I'm looking at the color scheme and I see that when you drag a VST from a slot to the track, if the VST has a color then the Track gets the same color as well (works like the Rack to Track color). This is good indeed. But if the VST slot is white then the track of course default back to gray. Not so nice.

Yes i realized this too and am working on something.

One option would be that if the VST slot has no color then the Track stay the same as the Rack: No Changes
But if the VST Slot has a custom color then the Track should change to that color as well...

[> DiGiT <]

in 4.074 no matter what i do i cant seem to get a rack to display. mulab wont even display racks on the bottom of the screen like they do by default, unless this was changed. also, there is no hide option for the modular display. the small on screen keyboard is also only a few pixels tall now as well.



as you can see the little rectangle is all i get when i try to show a rack. there is also just a blank space where the mixing desk should be.

[pljones]

Simple idea: When a new session is opened on top of already opened sessions, MuLab could give a little auto-hide alert stating the number of open sessions.

Maybe there could be an entry at the top of the MULAB menu stating how many open sessions there currently are? (I don't like popups, even autohide ones, unless really necessary - so I'm just trying to think of an alternative.) This way, at least you'd see that by the third time you used MULAB->Open or MULAB->Open Demo you had two or more sessions already open. Another handy MULAB menu option might be "Close other sessions" (just above Quit).

I just noticed that when I quit, I get a series of "Are you sure to close MuLab Session?" questions. They give no indication of which session they're talking about, so it's impossible to make an informed choice. That could do with fixing.

[MuTools]

in 4.074 no matter what i do i cant seem to get a rack to display. mulab wont even display racks on the bottom of the screen like they do by default, unless this was changed. also, there is no hide option for the modular display. the small on screen keyboard is also only a few pixels tall now as well.

Looks like missing graphic files for some reason.
Best to do a re-install of the complete M4.0.74 zip package.

[Nielzie]

I still like the idea of "tabbed" session windows. First benefit is that you see on the amount of tabs (preferably somewhere up in the menu bar) how much sessions there are currently opened.

Second benefit is that one can change from session to session with one mouseclick on the particular tabs. Maybe the tabs could even be colored with the same coloring system that is used for coloring the racks.