MuTools

MuTools · Post by **MuTools** » Wed Dec 28, 2011 10:18 am

Trancit wrote:Jo,

I have some problems here with the Auto-naming feature in MuLab...

Especially with modules, like the Supermodulator or others, which can load patches...
No matter if I give the module a name before or not...as soon as I load a preset, it gets autorenamed to the presets name...not good...

Agreed, so i've changed that behaviour, see next version.

Note however that if you save Super Modulator "SM1", then rename it to something else, then you load that file again, it will be renamed to "SM1" again, as that's the name of the Super Modulator that is stored in the file. That's normal and logical. It's not the same as the current behaviour which autorenames to the filename. That was not good indeed.

Trancit · Post by **Trancit** » Wed Dec 28, 2011 11:31 pm

mutools wrote: Note however that if you save Super Modulator "SM1", then rename it to something else, then you load that file again, it will be renamed to "SM1" again, as that's the name of the Super Modulator that is stored in the file. That's normal and logical. It's not the same as the current behaviour which autorenames to the filename. That was not good indeed.

totally agree to that behaviour, you described here...

> DiGiT < · Post by **> DiGiT <** » Thu Dec 29, 2011 3:44 pm

mutools wrote:DiGiT, Nielzie, you don't have to buy a Mulab 4 UL User License, i'll make sure you get a free upgrade. Thanks for your continued support and feedback here on the forum! Hope you'll enjoy M4!

NB: If you guys are really rich and buying a M4 User License doesn't hurt you at all, then feel free to financially support the project of course.

i will most certainly pay the upgrade fee. jo youre too modest!

MuTools · Post by **MuTools** » Sat Dec 31, 2011 11:41 am

Thanks DiGiT!

AndreasD · Post by **AndreasD** » Sat Dec 31, 2011 1:04 pm

It could just be my system, so i want to check with others.

I'm using a Win7/64 Home Premium system with (2) Microsoft mouse.
When I am zooming in with the mousewheel in Mulab 4, any zoom in will end up with a full zoom out. Any scroll down long lists will end up at the top of the list.

I have an Acer, Logitech, and Genius mouse, where things work fine.
Just the Microsoft ones don't 'wheel' correct in M4. And only M4.

Anyone with a similar setup has the same phenomenon?

> DiGiT < · Post by **> DiGiT <** » Sat Dec 31, 2011 1:33 pm

i have had all types of scrolling devices mess up on me in the past in some capacity. i vote its your mouse.

MuTools · Post by **MuTools** » Sun Jan 01, 2012 6:04 pm

Trancit wrote:As I mentioned before, there are some things, I get in trouble with...:
...
New Synth devices like Musynth and MuDrum are restricted to one output...especially the MuDrum needs min 4 outputs
...

Eventhough i think the MuDrum can do almost all mixes internally, i agree that there are indeed situations where you want/need separate outs, for example when you want to use a send effect that is also used somewhere else outside a MuDrum. So see latest version: MuDrum with multi outs is there

pljones · Post by **pljones** » Sun Jan 01, 2012 6:08 pm

4.0.87

1) In the initial menu, could the demos please be at the bottom (as once used, they'll probably not be what the user wants mostly). Also, in addition to "Open", can we have "New Session" (yes, escape works but "obviousness"

)?

2) I got (twice) "Unknown shortcut to ..." something when starting a new session from the initial menu ... but when I tried to reproduce it a third time, it wouldn't. I assume whatever setting was unrecognised got unset eventually...

Bonteburg · Post by **Bonteburg** » Sun Jan 01, 2012 6:58 pm

Happy New 2012 to all of you!

Just testing my new Kurzweil keyboard/stage piano with MU.LAB 3 and 4-0-76.

This is my first ever proper piece of MIDI kit so bear with me.

-it seems that the audio from the Kurzweil is only streamed to MULAB when you're actually playing but sequences fail to trigger the keyboard sounds when you play them back or draw in notes/click them in the graphical keyboard.

-Unlike in M3, there doesn't seem to be a way to set up the Kurzweil as a target player or choose a MIDI channel to be used.

MuTools · Post by **MuTools** » Mon Jan 02, 2012 8:33 am

pljones wrote:4.0.87
1) In the initial menu, could the demos please be at the bottom (as once used, they'll probably not be what the user wants mostly). Also, in addition to "Open", can we have "New Session" (yes, escape works but "obviousness" )?

You mean when you run MuLab for the very first time?
But then if you have copied your previous user settings, this popup menu should not come, does it?
Or i'm missing something?

I got (twice) "Unknown shortcut to ..." something when starting a new session from the initial menu.

Yes i also got that alert saturday adternoon (CET) while i was testing the package on another system. So i fixed that and refreshed the packages around 1900 last saturday. I assume you've downloaded the M4.0.87 package before then, right?

but when I tried to reproduce it a third time, it wouldn't. I assume whatever setting was unrecognised got unset eventually...

If MuLab encounters a shortcut to an unknown function, it tells you so and then removes the shortcut. That's why the message only comes once, which is good. Strange that you say that you got it twice. Are you sure it was about the same shortcut?

MuTools · Post by **MuTools** » Mon Jan 02, 2012 8:43 am

Bonteburg wrote:Happy New 2012 to all of you!

And to you too Marco!

Just testing my new Kurzweil keyboard/stage piano with MU.LAB 3 and 4-0-76.

This is my first ever proper piece of MIDI kit so bear with me.

-it seems that the audio from the Kurzweil is only streamed to MULAB when you're actually playing but sequences fail to trigger the keyboard sounds when you play them back or draw in notes/click them in the graphical keyboard.

-Unlike in M3, there doesn't seem to be a way to set up the Kurzweil as a target player or choose a MIDI channel to be used.

It sounds like the two issues are related, right?

To send MIDI out from MuLab 4:

1) Make sure you have enabled the MIDI outs in MuLab menu -> MIDI Setup.
2) In the Session Modular Area: Make sure you have a MIDI Output module for each MIDI port you wanna target.

Then you can use that MIDI Output module as a target for the tracks.

This is the same as in M3.

pljones · Post by **pljones** » Mon Jan 02, 2012 9:12 am

mutools wrote:
pljones wrote:4.0.87
1) In the initial menu, could the demos please be at the bottom (as once used, they'll probably not be what the user wants mostly). Also, in addition to "Open", can we have "New Session" (yes, escape works but "obviousness" )?
You mean when you run MuLab for the very first time?
But then if you have copied your previous user settings, this popup menu should not come, does it?
Or i'm missing something?

Every time I run MULAB.EXE, I get the splash screen and a menu appears over it allowing selection of a Demo or "Open...". Is that not intended? (I've yet to save a session, so I may have no "most recent" list.)

mutools wrote:
I got (twice) "Unknown shortcut to ..." something when starting a new session from the initial menu.
Yes i also got that alert saturday adternoon (CET) while i was testing the package on another system. So i fixed that and refreshed the packages around 1900 last saturday. I assume you've downloaded the M4.0.87 package before then, right?

Yes...

mutools wrote:
but when I tried to reproduce it a third time, it wouldn't. I assume whatever setting was unrecognised got unset eventually...
If MuLab encounters a shortcut to an unknown function, it tells you so and then removes the shortcut. That's why the message only comes once, which is good. Strange that you say that you got it twice. Are you sure it was about the same shortcut?

...Don't know, that's why I tried to get the message again

.

MuTools · Post by **MuTools** » Mon Jan 02, 2012 9:30 am

mutools wrote:To send MIDI out from MuLab 4:

1) Make sure you have enabled the MIDI outs in MuLab menu -> MIDI Setup.
2) In the Session Modular Area: Make sure you have a MIDI Output module for each MIDI port you wanna target.

Then you can use that MIDI Output module as a target for the tracks.

This is the same as in M3.

In the next version: After doing MIDI Setup, MuLab automatically makes sure that a session has the relevant MIDI Output modules for the opened MIDI ports. So step 2 is done automatically from next version on.

MuTools · Post by **MuTools** » Mon Jan 02, 2012 9:36 am

pljones wrote:Every time I run MULAB.EXE, I get the splash screen and a menu appears over it allowing selection of a Demo or "Open...". Is that not intended? (I've yet to save a session, so I may have no "most recent" list.)

As soon as you open or save a session, MuLab will memorize that session as the last one. So if you open one, that demo list will be gone too on startup.

mutools wrote:Are you sure it was about the same shortcut?
...Don't know, that's why I tried to get the message again

I see

Bonteburg · Post by **Bonteburg** » Mon Jan 02, 2012 11:39 am

Jo, thanks I'll try out the suggestions.

BTW I've been forgetting about this ever since the betatest came out - shame on me:

MU.LAB keeps forgetting the MIDI-setup and you have to reset it on each startup. As with M3 it's not really a showstopper which is why I kept procrastinating on it but for the sake of thorough testing, here it is.

Marco

MuTools

KVR Audio

M4 Test