M4 Test

[MuTools]

M 4-0-99:

Mixdown reimported into a new musession won't play any more than the first bar (incidentally the loop end point) in the arranger window, even with 'play entire file' (ie all of it is visible) activated.

Moving the loop end point fixes this. Putting the loop end point to its default position (end of bar 1) doesn't repeat the proeblem.

OSX 10.6.8

Researched this. I assume you were mixing down to the same audio file that was just imported after a previous mixdown, right? Next version has improved behaviour in this case.

No - it just happened with the „New" template and a random audio file that wasn't created with MULAB. Again, I could solve the problem by moving the loop point once. (BTW it appears to work with both default loop points).

Is this repeatable?

[Bonteburg]

Yes - seems to happen every time and with any file, in every new session (ie not on every new startup).

Moving any of the default loop points fixes it.

[pquenin]

Hello, I'm still testing M4, and I want to assign the modulation wheel of my keyboard to the pich lfo of the Musynth, but it has no effect, any idea ?

[AndreasD]

Hi PQ,
Assign the LFO parameter to one of the 3 top meta parameter and assign the modwheel to this meta parameter.
This should work as long as you have the MuSynth (rack) focused.
Has to do with midi focus, i think.

If you need it session wide, use the Session MiDi Controller Map in the Session menu.

[Nielzie]

It may be a dumb question, sorry about that, but how do I unmap a MIDI control from a parameter? Can't find it

It might be helpful to have an "unmap midi control" option in the right click menu too

[MuTools]

Hi Jo,
I got a reproducable problem when upgrading any session (like "cappuccino") from 3.2.14 to 4.0.99. While upgrading, several popups telling me everything is okay ("Upgraded 1 sessions, 0 failed", "Stopped logging"). After that there is no more window visible, but the process still occurs in task manager. The log file seems to be okay. This will happen even if I cancel the upgrade from the select sessions folder dialog. Opening a M3 session with 4.0.99 still works. Version 4.0.97 also works fine. Any idea?

Jochen.

Fixed & finetuned in the next version! Thanks!

[MuTools]

It may be a dumb question, sorry about that, but how do I unmap a MIDI control from a parameter? Can't find it

It might be helpful to have an "unmap midi control" option in the right click menu too

Map the parameter to "None". That should do it, right?

[Nielzie]

It may be a dumb question, sorry about that, but how do I unmap a MIDI control from a parameter? Can't find it

It might be helpful to have an "unmap midi control" option in the right click menu too

Map the parameter to "None". That should do it, right?

Ahh yes indeed Still it would be a faster to select just "unmap" directly from the menu. I'm spoiled with "Midi Learn" and "Midi Unlearn" of most synths and effects I guess

But I can't get the mapping to work properly with my midi controller. When I for instance select the filter frequency knob of the MuSynth and then select "Map Midi Controller" and then turn the knob on my controller so it gets automatically selected (which indicates that it does receive midi messages from my controller) and then choose "Done", then still nothing happens when I turn the knob afterwards.

Another question, how do I quickly open an empty MUX session window?

[MuTools]

But I can't get the mapping to work properly with my midi controller. When I for instance select the filter frequency knob of the MuSynth and then select "Map Midi Controller" and then turn the knob on my controller so it gets automatically selected (which indicates that it does receive midi messages from my controller) and then choose "Done", then still nothing happens when I turn the knob afterwards.

It's because the MIDI focus is on the synth, not on the filter. That's a consequence of the modular design. I'll see how this can be finetuned in the future.

Solution: Map the cutoff to the MuSynth meta-parm on top. This can be easily done by drag-dropping the cutoff parm onto that meta-parm! Then assign a MIDI controller to that meta-parm. That will work whenever the MuSynth has MIDI focus as the meta-parms belong to the MuSynth, the cutoff is a filter module parameter, not a MuSynth parameter. I admit this is a confusing consequence of the modular system. Added a note on the wishlist.

Another question, how do I quickly open an empty MUX session window?

For example: Load the "Basic Effect" patch into an empty rack slot.

[Nielzie]

But I can't get the mapping to work properly with my midi controller. When I for instance select the filter frequency knob of the MuSynth and then select "Map Midi Controller" and then turn the knob on my controller so it gets automatically selected (which indicates that it does receive midi messages from my controller) and then choose "Done", then still nothing happens when I turn the knob afterwards.

It's because the MIDI focus is on the synth, not on the filter. That's a consequence of the modular design. I'll see how this can be finetuned in the future.

Solution: Map the cutoff to the MuSynth meta-parm on top. This can be easily done by drag-dropping the cutoff parm onto that meta-parm! Then assign a MIDI controller to that meta-parm. That will work whenever the MuSynth has MIDI focus as the meta-parms belong to the MuSynth, the cutoff is a filter module parameter, not a MuSynth parameter. I admit this is a confusing consequence of the modular system. Added a note on the wishlist..

Ahhh now I understand.. Thanks for the explanation

Another question, how do I quickly open an empty MUX session windowFor example: Load the "Basic Effect" patch into an empty rack slot.

Great, I see now that "Basic Synth" (and effect) is in fact meant as some kind of MUX "template" instead of an actually instrument. Maybe it would be more obvious if it was called/categorized like that in the menu

[MuTools]

But I can't get the mapping to work properly with my midi controller. When I for instance select the filter frequency knob of the MuSynth and then select "Map Midi Controller" and then turn the knob on my controller so it gets automatically selected (which indicates that it does receive midi messages from my controller) and then choose "Done", then still nothing happens when I turn the knob afterwards.

It's because the MIDI focus is on the synth, not on the filter. That's a consequence of the modular design. I'll see how this can be finetuned in the future.

Solution: Map the cutoff to the MuSynth meta-parm on top. This can be easily done by drag-dropping the cutoff parm onto that meta-parm! Then assign a MIDI controller to that meta-parm. That will work whenever the MuSynth has MIDI focus as the meta-parms belong to the MuSynth, the cutoff is a filter module parameter, not a MuSynth parameter. I admit this is a confusing consequence of the modular system. Added a note on the wishlist..

Ahhh now I understand.. Thanks for the explanation

To tell you more: You could also use it in an alternative way:

Instead of using a meta-parm, just assign a MIDI controller to that cutoff, as you intended, then whenever you want to control that filter module, drag-drop the filter module's title (in the MuSynth) to the Focused Module Panel on the top, this way you can get MIDI focus to any module!

You can even drop a parameter onto the Focused Module Panel, this will focus the module of that parameter.

[janamdo]

I thought you can drag the parameters from the racks to the automation tracks, something like that?..i did a while ago
I do it now: add a subtrack and drag a parameter rectangle from a rackmodule to the subtrack .. it seems to be another way of "targetting"parameters

More easy.. take a racksound and a take modular parameter..tweak the knob during recording it, but thr problem here is a parameter use in a midi controller?

[MuTools]

You can do it eve faster: Jus drag-drop a parameter on the [+] button

[janamdo]

You can do it eve faster: Jus drag-drop a parameter on the [+] button

You can do this only for a top-level module ?..the sound with the main parameters

But if you should take a filtermodule from that sound and this showing up the panel, than there is red sign when you try to drag, but if go further with dragging direction of a subtrack, than it becomes a square with a hand and the name of the parameter is written on the sub track and the parameter is assigned too. Now you can record this parameter.

So now comes up the question what is the meaning of the red sign..what suggests that there is no dragging of this parameter is possible?

[MuTools]

This is standard: The red sign or 'no go' drag icon appears whenever you are over a UI component that can't do anything with the dragged object.

When you're hovering a relevant component, then the drag picture will become something real.