MU.LAB 3.1 test

[robenestobenz]

Ah, cool, thanks for considering the suggestion (and looking into the modular area slowdown).

Another thing, the event monitor module shows the wrong MIDI channel on my PC -- it's always one lower than the actual channel value. Also on the subject of MIDI channels, what's the rationale for every channel in MIDI Input Focuses form defaulting to focus rather than its own channel value?

It was my first time using this form actually, I reckon it might be helpful to label the right hand value -- as a first time user of this form I was confused as to what the value meant, given its value range from "Focus" to a numerical value well above the number of MIDI channels supported as standard.

[liquidsound]

WOW! I just noticed the polyphony indicator on the Process on/off of the Mu Devices!
Sorry but between work hours and toothpicks to keep my eyes open at night I must have missed the info somewhere.

But... I no longer have a 20/20 vision. Is there any control in the settings for me to increase those number's font size?

What a cool thing those numbers!

[MuTools]

Another thing, the event monitor module shows the wrong MIDI channel on my PC -- it's always one lower than the actual channel value.

Fixed in the next version.

Also on the subject of MIDI channels, what's the rationale for every channel in MIDI Input Focuses form defaulting to focus rather than its own channel value?

Because by default all input goes to the focussed module.

It was my first time using this form actually, I reckon it might be helpful to label the right hand value -- as a first time user of this form I was confused as to what the value meant, given its value range from "Focus" to a numerical value well above the number of MIDI channels supported as standard.

In the next versions, there are labels above these 2 columns.

[robenestobenz]

Because by default all input goes to the focussed module.

Not quite my point -- it's not the focus thing that I can't understand. The focus makes sense, it's just weird that all channels are converted to 1 by the default value of focus in the right hand column.

If someone is sending channel 2 MIDI data from their controller, why would they want this changed to 1?

[MuTools]

Imagine you have two MIDI keyboards, one sending on chan 1, the other on chan 2.

Now you want the first keyboard to follow the focussed module in MU.LAB, the second one you want to play a piano which you have loaded on channel 5 in say Kontakt, wich is plugged in some MU.LAB rack.

Now you can route your second keyboard, i.e. incoming channel 2, to Kontakt, channel 5 and play the piano, which will stay there, while keyboard one follows the focussed target module.

Hope this explains it well.

[robenestobenz]

Imagine you have two MIDI keyboards, one sending on chan 1, the other on chan 2.

Now you want the first keyboard to follow the focussed module in MU.LAB, the second one you want to play a piano which you have loaded on channel 5 in say Kontakt, wich is plugged in some MU.LAB rack.

OK, this bit is regarding destinations (left hand column) in the menu. The default setting of Focussed Target makes sense here.

Now you can route your second keyboard, i.e. incoming channel 2, to Kontakt, channel 5 and play the piano, which will stay there, while keyboard one follows the focussed target module. Hope this explains it well.

It's not really related to my question. I can understand how the feature works (except for the "Focus" value, which always just seemed to set channel to 1), it just seems odd to me that the default settings force MIDI data on channels 2-16 to 1.

[MuTools]

Ah, now i understand your question.

Well imagine a similar situation as i described above.

And you have a part playing that piano.

Now you click that part.

Now the piano will also be on your first keyboard. And it will send to Kontakt chan 5, i.e. the piano, as chan 5 is the focussed channel for that Kontakt plugin.

[Jake Jackson]

RESOLVED: I had apparently not copied my User settings over from the previous version. After I did so, the effects loaded fine. Sorry.



I'm having trouble getting vst effects to load. I have a 64 bit system, but in the past, in Mulab, 32 bit effects have loaded fine. Several effects still load, and the mux effects load, but most, including these, don't:

Multimodulator
Bluecat freq analyzer
Detectcomp
mjcompressor

I'm only trying to load a single effect in Rack A in the free version. What happens:

1. I double-click in rack A, click on Effects\VST.
2. I navigate to and dc on the vst dll.
3. The message about the full version offering more tracks pops up.
4. I click on Maybe Later.

The ad screen vanishes, but the vst effect isn't loaded. No error message appears.

Is it just me? Is my 64 bit system to blame?

RESOLVED: See at top of message.

[Trancit]

The MU.LAB 3.1.2 test version is available in http://www.mutools.com/mulab/chestnut

What's changed:

• New: You can create shortcuts for "Select Previous Preset" and "Select Next Preset"

How and for what does this work???
The only place I find it is in the Rack area of the shortcuts...I made a shortcut tried with "ROM" Instruments...nothing
tried with VSTi...nothing happens...???????????


Trancit

[Jake Jackson]

Well, hell. All of the effects came in fine, but the ADSR envelopes, unlike all of the others, including the mux Note-Gater, don't seem to do anything.

Just considering Note-Gater: I've tried every configuration I can think of:

1. In a rack, before the instrument.
2. In a rack, after the instrument.
3. In the Modular area, before the rack.
4. In the Modular area, before the rack, and with both audio and event input on top of it and connected.
5. In the Modular area, after the rack and before the Master, with connections to both.

Turning the knobs has no effect. Going into the deep editor, knobs also have no effect.

I'm probably doing something wrong, but I don't see it.

Must admit that the name "Note-Gater" confuses me a bit: does the envelope control the amplitude or the gating? In other words, does the Attack knob control the rate of the gating or is just an amp attack knob, which is what I want? But I've listened for Note-Gater to be either, and there's just no effect on the sound.

[liquidsound]

The MU.LAB 3.1.2 test version is available in http://www.mutools.com/mulab/chestnut

What's changed:

• New: You can create shortcuts for "Select Previous Preset" and "Select Next Preset"

How and for what does this work???
The only place I find it is in the Rack area of the shortcuts...I made a shortcut tried with "ROM" Instruments...nothing
tried with VSTi...nothing happens...???????????


Trancit

General Category> Select Next Preset
Specific Category> Modular Module> Select Next Preset

Do you have MU.LAB 3.1.2?

[Trancit]

General Category> Select Next Preset
Specific Category> Modular Module> Select Next Preset

Do you have MU.LAB 3.1.2?

Yes 3.1.2 and yes for the Modular Module it works with the Rom presets...but what for are the next/previous shortcuts for the racks???

Trancit

[liquidsound]

General Category> Select Next Preset
Specific Category> Modular Module> Select Next Preset

Do you have MU.LAB 3.1.2?

Yes 3.1.2 and yes for the Modular Module it works with the Rom presets...but what for are the next/previous shortcuts for the racks???

Trancit

Don't work for me either

[MuTools]

Yes 3.1.2 and yes for the Modular Module it works with the Rom presets...but what for are the next/previous shortcuts for the racks???

Where do you see these "next/previous shortcuts for the racks" ?

[MuTools]

Well, hell. All of the effects came in fine, but the ADSR envelopes, unlike all of the others, including the mux Note-Gater, don't seem to do anything.

Just considering Note-Gater: I've tried every configuration I can think of:

1. In a rack, before the instrument.
2. In a rack, after the instrument.
3. In the Modular area, before the rack.
4. In the Modular area, before the rack, and with both audio and event input on top of it and connected.
5. In the Modular area, after the rack and before the Master, with connections to both.

Turning the knobs has no effect. Going into the deep editor, knobs also have no effect.

I'm probably doing something wrong, but I don't see it.

Must admit that the name "Note-Gater" confuses me a bit: does the envelope control the amplitude or the gating? In other words, does the Attack knob control the rate of the gating or is just an amp attack knob, which is what I want? But I've listened for Note-Gater to be either, and there's just no effect on the sound.

The Note Gater preset lets the audio pass on note on, and mutes it on note off. Handy to make that typical trance gate effect.