MuTools

Bonteburg · Post by **Bonteburg** » Wed Jan 04, 2012 5:30 pm

Jo, I'm not sure if this one is really worth it - this is about using a specific keyboard on a specific system and I can always go back to 10.4.11 on the other computer and still use M4 or try aforementioned solutions.

Happy coding!

MuTools · Post by **MuTools** » Wed Jan 04, 2012 8:19 pm

If EXT & Repear & other apps have problems too (right?), and if only a certain keyboard seems to cause the problems (right?), then all this seems to say that it indeed is a system specific problem, and then i'm afraid i can't do much.

That said, the 'MuLab forgets MIDI setup' problem is a confirmed MuLab issue and i'll check & fix that asap.

Bonteburg · Post by **Bonteburg** » Wed Jan 04, 2012 8:27 pm

yeah and the double/triple keyboard in the modular area also seems to be a MU.LAB problem.

MuTools · Post by **MuTools** » Wed Jan 04, 2012 9:19 pm

Which MuLab version are you using?

Drenholm · Post by **Drenholm** » Wed Jan 04, 2012 11:18 pm

The fact that a single track can no longer contain parts targeting different effect strips is a loss to me, as I am poor and have had to stick with the free version, and v3 was usable for my basic music as the feature meant I could get around the four-track limit by switching instruments. Now I seem to be restricted to four tracks, each using the same instrument throughout. I guess I will stick with v3 for now! :/

AndreasD · Post by **AndreasD** » Sat Jan 07, 2012 10:06 am

@Drenholm:
There is actually a way to get similar results than in M3:
You can put sequence parts on top of each other and they all play. Say you stack sequences in track 1 which is routed to rack 1. Set the Midi channel of track 1 to None. Set the midi channels of the stacked sequence parts to chan 1, 2 etc.

Now you have 2 possibilties:
1) Add a MUX in rack 1 and put all your Mulab patches or VSTs inside this MUX and add a Midi Channel Splitter after the Event Input and route the respective midi channel to the instruments.
Downside: you have to mix inside the MUX.

2) In rack 1 you set up as many sends as you have stacked sequences. The sends target rack 2, rack 3 etc. The trick here is that sends send midi as well!
In rack 2, 3, .. insert the instruments you need.
All racks now receive all the data of all the stacked parts on track 1. If your instrument allows to choose the midi channel, set it as required. Otherwise add a MUX in the first slot that has nothing but an Event input and a Midi Channel Splitter that connects the correct midi channel to the Event output.

Now you can use the full power of the racks.

MuTools · Post by **MuTools** » Sat Jan 07, 2012 11:17 am

AndreasD wrote:@Drenholm:
There is actually a way to get similar results than in M3:
You can put sequence parts on top of each other and they all play. Say you stack sequences in track 1 which is routed to rack 1. Set the Midi channel of track 1 to None. Set the midi channels of the stacked sequence parts to chan 1, 2 etc.

Please note that multi MIDI channels per track is a MuLab UL feature only, cfr http://www.mutools.com/mulab/docs/intro ... free-xt-ul

Well, to be precise: You can use multiple MIDI channels per track in MuLab Free and XT but then you'll get a regular voice alert saying "Please upgrade your MuLab".

Drenholm, i'm sorry that i try to survive business-wise.
Otherwise there can be no MuLab future, it's as simple as that.

MuTools · Post by **MuTools** » Sat Jan 07, 2012 11:59 am

mutools wrote:
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, on second thought i think the original behaviour was ok.
Please explain me what's wrong with the fact that if you load patch "MyBass.Mux" then the patch is named "MyBass"? Theoretically you can indeed have a different name for the patch (in ram) and the patch file (on disk) like it is possible in many VSTs to have a different name for the program and the .fxp file. But that's not really recommended as it introduces confusion.

So i think it's best to revert to orignal behaviour. Any further thoughts?

Bonteburg · Post by **Bonteburg** » Sat Jan 07, 2012 3:59 pm

Hey,

RE: the triple Kurzweil Problem, it doesn't seem to happen in 4-0-87.

mutools wrote:Which MuLab version are you using?

Bonteburg · Post by **Bonteburg** » Sat Jan 07, 2012 4:05 pm

I'm not sure if it is a bug:

I created two tracks with the Kurz as a target. I set track 1 two MIDI-Channel 1 and track 2 to MIDI-channel 2. When I click on track 2 and play the keyboard I'me hearing a Rhodes sound (expected). However when clicking track 1 I can hear a piano (expected) PLUS the rhodes sound.

This happens only during playing (performance). I can sequence them without any problems.

4-0-87

Bonteburg · Post by **Bonteburg** » Sat Jan 07, 2012 4:13 pm

I have a track pointing to a MU.LAB generator (Baldax patch) with a part playing some notes. On another track not targetting anything in particular, I can still hear Baldax when I move the part there.

I seem to remember you saying that this wasn't supposed to be so (?).

fedexnman · Post by **fedexnman** » Sun Jan 08, 2012 1:08 am

FR: It'd be cool to have a vst version of Mulab4 (like energy xt), to open in another host instead of using rewire, maybe make it in the pay version only . Cool product by the way !! Congrads on the hard work and soon to be released Mulab4.

MuTools · Post by **MuTools** » Sun Jan 08, 2012 12:49 pm

Bonteburg wrote:I'm not sure if it is a bug:

I created two tracks with the Kurz as a target. I set track 1 two MIDI-Channel 1 and track 2 to MIDI-channel 2. When I click on track 2 and play the keyboard I'me hearing a Rhodes sound (expected). However when clicking track 1 I can hear a piano (expected) PLUS the rhodes sound.

This happens only during playing (performance). I can sequence them without any problems.

4-0-87

Sounds like the Kurz is in 'Local On'.
Set it to 'Local Off' will get you where you want i think.

Some info on Local On/Off: http://www.iu.edu/~emusic/361/localcontrol.htm

MuTools · Post by **MuTools** » Sun Jan 08, 2012 1:14 pm

Bonteburg wrote:I have a track pointing to a MU.LAB generator (Baldax patch) with a part playing some notes. On another track not targetting anything in particular, I can still hear Baldax when I move the part there.
I seem to remember you saying that this wasn't supposed to be so (?).

Ok, i finally found how to repeat it. Will fix.

Drenholm · Post by **Drenholm** » Sun Jan 08, 2012 3:06 pm

mutools wrote:Drenholm, i'm sorry that i try to survive business-wise.
Otherwise there can be no MuLab future, it's as simple as that.

I'm not unrealistic enough to deny the economics of developing a program such as MU.LAB, not was I in any way implying that it's something that you should apologise for, nor am I self-important to expect anyone to do anything because I ask them to! I hope it didn't actually seem as though I were any of these things.

Honestly, half of the reason I said anything was in case I'd missed a feature that was in the free version, but I see now that I haven't.

Let me be clear, since I apparently wasn't sufficiently so the last time around: I've always wished the best for your products, and MU.LAB is near the top of the list for when I have enough money to buy a sequencer/DAW. All I meant was that I can't do so at this point in time, and therefore I'll use MU.LAB 3 if I have to.

MuTools

KVR Audio

M4 Test