M4 Test

[janamdo]

The coloring for the whole racks is too much for me, sufficient is only to get the trackheader colored the rest of the rack stays grey (uncolored)

So a focussed track is only visible as a colored rackheader and the other racks are not colored if there is no sequenze for that track.
So the condition for a rackheader coloring is that there is focus on a track
There is than only one colered rackheader visible than
Only a focussed track has a color.
It is a reminder that the is user working on this focussed track

It is very simple with me..only a focussed track has a colored rackheader and a colored trackpanel and a colored sequenze
All other tracks/racks/panels tracks are grey(= not colored)

[Nielzie]

The coloring for the whole racks is too much for me, sufficient is only to get the trackheader colored the rest of the rack stays grey (uncolored)

So a focussed track is only visible as a colored rackheader and the other racks are not colored if there is no sequenze for that track.
So the condition for a rackheader coloring is that there is focus on a track
There is than only one colered rackheader visible than
Only a focussed track has a color.
It is a reminder that the is user working on this focussed track

I agree about coloring the whole rack being too much atm. However I would like to keep the track headers colored also when they are not focused. I would prefer to have only the small colored line at the border of the rack that's focused to make it stand out from the rest

[MuTools]

Note that that small green box around UI components has nothing to do with the MIDI focus. That small green box indicates the UI focus i.e. it indicates where the keyboard keys are sent to.

The MIDI focus, which is always indicated in the focussed module panel at the top, is about which module is on your MIDI keyboard.

I made a quick mockup of doing the focussed rack in another way, also using a border: http://www.mutools.com/pics/temp/p20111212.png

How does that feel?

[janamdo]

By default opening it seems too big the keyboard?

What monitor resolution are you working on?

yes it is a widescreen : 1920 x 1080 that explains all ..

[Nielzie]

I made a quick mockup of doing the focussed rack in another way, also using a border: http://www.mutools.com/pics/temp/p20111212.png

How does that feel?

Yess, that's exactly what I mean, looks good

[janamdo]

Note that that small green box around UI components has nothing to do with the MIDI focus. That small green box indicates the UI focus i.e. it indicates where the keyboard keys are sent to.

The MIDI focus, which is always indicated in the focussed module panel at the top, is about which module is on your MIDI keyboard.

I made a quick mockup of doing the focussed rack in another way, also using a border: http://www.mutools.com/pics/temp/p20111212.png

How does that feel?

Feels nice this coloring too for the Midi focus..it concerns the whole rack and it is on the background
Perhaps also for midi focus of the trackpanels a colored header and also for midi focus of the sequenzes too a colored header only
So mulab is not to much colored ( i know christmas is coming )
It is personal for me, but other people might have other feelings about it

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

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?

[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?

[Bonteburg]

I tested the new improved MuPad and it works much better! I still found two things:

- I could assign a parameter of my Rock Organ patch nestling within Element 3 (Rotary Amount) to one of the meta parameters but it fails to show up on the MuPad front panel* (the 16 blank spaces) unless I click "edit" which pops up a window containing the knob.

-I assigned Meta Parameter 1 (now known as "Rotary Amt") to the PAN knob of my keyboard. I recorded automation and while the parameter automated is the correct one, it says "Pan" on the automation lane, potentially causing confusion**.


*edit: apparently closing theMuPad GUI and opening it again fixes this.

**edit02: The same thing happens with VST, racks and MU.LAB players.

[Bonteburg]

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.

[Bonteburg]

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.

[liquidsound]

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

[pljones]

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

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

[MuTools]

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?

[MuTools]

- I could assign a parameter of my Rock Organ patch nestling within Element 3 (Rotary Amount) to one of the meta parameters but it fails to show up on the MuPad front panel* (the 16 blank spaces) unless I click "edit" which pops up a window containing the knob.

Fixed in the next version.

I assigned Meta Parameter 1 (now known as "Rotary Amt") to the PAN knob of my keyboard. I recorded automation and 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.

Though i can understand that you may want that the parameter is recorded, not the mapped MIDI controller, right?