My Whishlist :)

[reapperkeeper]

Hi everyone ;]

I'm totally new here so I hope this is the right place to post my whishlist for MU.Lab.

1. Program browser attached to the VST/VSTI window. The current one requires additional clicks to get to it and it doesn't allow to tweak the settings for the plugin while browsing the presets. It gets difficult to find the right sound.
2. Midi routing. I still haven't found a way to play two synths at once with the same keyboard.
3. More flexible audio routing. I have some synth (eg. DSK DrumZ) with a lot of outputs and it's annoying that I can't route them through the same rack the plugin is in.
4. A shortcut editor would be lovely ;] I like zooming with my mouse wheel, not scrolling.
5. I have some lovely transport buttons on my keyboard. It's a shame they cant be mapped to control MU.Lab.
6. An easy to use midi learn would be wonderful (eg. Ableton Live)

So here it is, I'll post more along the way ;] this is the 3rd time I've tried MU.Lab and it's finally getting closer to what I would use ;] The first three features requested are the most annoying problems to me so I really hope you will fix them soon ;]

Cheers!

[MuTools]

Hi everyone ;]

I'm totally new here so I hope this is the right place to post my whishlist for MU.Lab.

Sure.

1. Program browser attached to the VST/VSTI window. The current one requires additional clicks to get to it and it doesn't allow to tweak the settings for the plugin while browsing the presets. It gets difficult to find the right sound.

Will be evaluated.

2. Midi routing. I still haven't found a way to play two synths at once with the same keyboard.

Do you mean layering synths?

3. More flexible audio routing. I have some synth (eg. DSK DrumZ) with a lot of outputs and it's annoying that I can't route them through the same rack the plugin is in.

You can.

Right-click that plugin, choose "Connect Alternative Outputs", and choose whatever target for each output, eventually the same rack as the main outs.

4. I like zooming with my mouse wheel, not scrolling.

Hold [Control] to zoom in/out with the mousewheel. Also hold [Alt] to zoom the in other direction.

5. I have some lovely transport buttons on my keyboard. It's a shame they cant be mapped to control MU.Lab.

Added to the whishlist.

6. An easy to use midi learn would be wonderful (eg. Ableton Live)

It can't be more easy:

-> right-click the parameter, choose "Map MIDI Controller", give a little tweak to the MIDI controller, and MU.LAB will know which controller you mean.

or in case of a vst plugin:

-> give the vst parameter a little tweak, click the "Options" button, choose "Map MIDI Controller", and in the dialog you'll see that the vst parameter is already there, so just give a little tweak to the MIDI controller, and MU.LAB will know which controller you mean.

[reapperkeeper]

comments:

2. midi routing.

The idea is to be able to send midi data anywhere ;] eg.:
I have a synth in rack A. Have a midi arp. effect and another synth in rack B.
I want to play my keyboard with the synth in rack A and send the data to the arp and synth in rack B and still play some sequence through the synth in rack B simultaniuosly. (these kind of things give the weirdest ambient sounds with right effects )

3. No I can't ;] I can route outputs to anywhere possible EXCEPT the rack the synth is in ;] eg. DrumZ is in rack C. Can't select to route the outputs to rack C, only master and all the other racks ;]

4. No again. The vertical zoom with [ctrl] works (I seldom use it) but the horizontal zoom with alt doesn't work. Anyway, I don't want to hold alt while zooming ;]

6. I had the VST variant in mind. Well... hmm... sounds easy enough. Still kinda whish it was a visible button with no extra windows and less clicks.

Anyway, thanx for looking in ;] And I really whish the program selector would be implemented, it's the most annoying thing so far.

[MuTools]

2. midi routing.

The idea is to be able to send midi data anywhere ;] eg.:
I have a synth in rack A. Have a midi arp. effect and another synth in rack B.
I want to play my keyboard with the synth in rack A and send the data to the arp and synth in rack B and still play some sequence through the synth in rack B simultaniuosly. (these kind of things give the weirdest ambient sounds with right effects )

If i understand you well, then just do as you describe it:

-> plug in a send to rack B in rack A slot 1
-> plug in synth 1 in rack A slot 2
-> plugin midi arp in rack B slot 1
-> plugin synth 2 in rack B slot 2
-> put the midi focus on rack A
-> target some sequence to rack B

Thing is: a send from rack a to rack b also sends the events, not only the audio.

Is this what you want?

3. No I can't ;] I can route outputs to anywhere possible EXCEPT the rack the synth is in ;] eg. DrumZ is in rack C. Can't select to route the outputs to rack C, only master and all the other racks ;]

Yep, you're right, i forgot about something. (there is a technical reason for that)

2 good workarounds:

1) Put the vsti in rack a, connect alt outs to rack b, output rack a + b to rack c. Voila, so you have all audio output from the vsti into rack c.
(with the possibility to process the main and sub outs differently if you want)

2) Press F2 to open the MPA. Insert the vsti there, and connect all its outputs to whatever target you want, e.g. rack X. Now you can send any sequences straight to that vsti, while all audio out from that vsti will come into rack X, where it can be furtherly processed.

Another workaround would be to plugin the vsti into a MUX and collect all output there, but the above 2 solutions are better i think.

4. No again. The vertical zoom with [ctrl] works (I seldom use it) but the horizontal zoom with alt doesn't work. Anyway, I don't want to hold alt while zooming ;]

Just to be sure we're talking about the same: what editor are you talking about?

Note that to zoom in/out in the 'other' direction, you have to hold [Alt] and [Ctrl] at the same time <=> [Alt] to change direction, [Ctrl] to zoom.

If you don't like holding mods, you could also use the scrollbar buttons.

Specific, user-definable shortcut keys are on the whishlist (and already worked on in the mutools lab) but not yet ready for 2.0.

6. I had the VST variant in mind. Well... hmm... sounds easy enough. Still kinda whish it was a visible button with no extra windows and less clicks.

Note that it's the intention to keep the MU.LAB gui very easy on the eye. Adding many buttons and widgets for specific functions will rapidly clutter the gui, which is not what we want.

Anyway, thanx for looking in ;] And I really whish the program selector would be implemented, it's the most annoying thing so far.

I understand. Will be evaluated.

Thanks for your feedback so far!

[ApBTranCer]

Note that it's the intention to keep the MU.LAB gui very easy on the eye. Adding many buttons and widgets for specific functions will rapidly clutter the gui, which is not what we want.

True, but It seams that now there is plenty of blank space above the vst window where commonly used buttons and dropdowns wouldn't clutter the Gui.

Would it be possible to somehow let the user customize their windows? Kinda like Finder windows, or the Firefox toolbar, you have the option of adding specific buttons or tools that you often use. Something like this is probably too much to ask for at this point, but its just an idea I think the gui, the windowing system, and mulab itself is coming along nicely.

[reapperkeeper]

one bug in test D and two requests ;]

The bug: when you replace a vst instrument (using the replace menu option) the old synth window doesn't close.

The requests:
1. Allow to assign a midi channel to a rack. Eg. have the midi data from channel 1 played on rack A and channel 2 data played on rack B etc. despite the rack being not focused ;]
2. Allow to assign a midi controller to focus on a certain rack.

[MuTools]

True, but It seams that now there is plenty of blank space above the vst window where commonly used buttons and dropdowns wouldn't clutter the Gui.

That's true.

Would it be possible to somehow let the user customize their windows?

This is not planned/intented.

[MuTools]

when you replace a vst instrument (using the replace menu option) the old synth window doesn't close.

True. Also when deleting a vst plug. It's already fixed here, see Test E, which will be released tomorrow (normally).

Allow to assign a midi channel to a rack. Eg. have the midi data from channel 1 played on rack A and channel 2 data played on rack B etc. despite the rack being not focused

I assume it's because you want to play 2 or more plugs/racks at the same time with your MIDI keyboard(s), right?

Allow to assign a midi controller to focus on a certain rack

How would that work in practice? Not sure if i understand what you want to do.

[pljones]

Allow to assign a midi channel to a rack. Eg. have the midi data from channel 1 played on rack A and channel 2 data played on rack B etc. despite the rack being not focused

I assume it's because you want to play 2 or more plugs/racks at the same time with your MIDI keyboard(s), right?

Or equally if you have more than one MIDI performer on separate channels -- you need to be able to wire at the channel level, which we still can't do. M*z*s3 had it...

[MuTools]

Allow to assign a midi channel to a rack. Eg. have the midi data from channel 1 played on rack A and channel 2 data played on rack B etc. despite the rack being not focused

I assume it's because you want to play 2 or more plugs/racks at the same time with your MIDI keyboard(s), right?

Or equally if you have more than one MIDI performer on separate channels -- you need to be able to wire at the channel level, which we still can't do. M*z*s3 had it...

Yes, i think reapperkeeper meant the same, that's why my question, to be sure.

Will be there again, one day, doing my best.

[pljones]

I see E did gain one M*z*s3 feature: assigning tracks to racks. I think that's good. I never could see the need to assign events to racks, though - hopefully the solution for MIDI performance recording won't need it.

[reapperkeeper]

Sorry, I've been gone for a bit ;]

Yeah, the midi routing... I meant the stuff pljones and mutools said. And just a little more.

I WANT MIDI TO WORK!

I don't know what I'm doing wrong but I can't event get a simple plugin like Harmony Improvisator to work here. Or an arp. I even connected it to a synth pulled out of rack (in the modular plugin window) nada... no sound. How the hell do I get it done?

;]

[pljones]

I'm assuming you've got Sequence parts working with Synths in racks.

Have you got Sequence parts working with Synths in the MPA?

There are two kinds of signal in the MPA - audio and MIDI. But you can't (currently) connect the initial input of MIDI within the MPA, it's done in the Player area at the top of the screen.

In the MPA, you should be able to wire from a MIDI plugin to a MIDI synth, then take the synth's Audio output and wire it to Audio Out. Then set a Part's player to the MIDI plugin and you should hear the MIDI effect's response to the MIDI input, as processed by the synth.

If that doesn't work, retarget the Part at the Synth.

If that doesn't work, something's wrong with your wiring. Check that there is actually some MIDI input and you've got the audio routed to an active audio output.

[MuTools]

You can route the incoming MIDI to whatever plugin via that plugs' context menu -> Focus.

No need to setup a part or a track first.

So if you're experimenting in the MPA, and you want to route your MIDI keyboard to a plug, just focus it using the "Focus" function.

[pljones]

Ah, all these new-fangled features...