MuTools

MuTools · Post by **MuTools** » Sun Jan 08, 2012 9:53 pm

Drenholm wrote:
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.

Not at all!

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.

Thanks + i understand.

MuTools · Post by **MuTools** » Sun Jan 08, 2012 10:04 pm

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

You meant that when double-clicking the MIDI Output module then the port list gets longer and longer each time you did MIDI Setup, right?

That bug has been fixed in the latest M4.0.91 cfr http://www.kvraudio.com/forum/viewtopic ... 35#4788635

The only remaining issue i see is that sometimes MIDI input is not properly opened. This seems to be an OSX system dependent issue. That's why i added more logging info when opening the the OSX MIDI ports, hope that will give me more insight.

If you have a spare minute:

1) Launch MuLab 4.0.91
2) Goto MULAB menu -> Help -> Start Logging
3) Quit MuLab
4) Launch MuLab -> Continue Logging? -> Yes/OK
5) Quit MuLab
6) Email me the newest Log-YYYYMMDD-HHMMSS.Txt in your MuLab 4091 folder.

The launch-quit-launch-quit is necessary to first enable logging then to log things while the MIDI engine is started on launch.

Bonteburg · Post by **Bonteburg** » Tue Jan 10, 2012 1:28 pm

Finally got around to sending them!!

I hate to tell you this but there's something wrong with the Kurzweil too as of 4-0-91.

It works in 4-0-87 (except for the forgetting thing of course) but I can't play it at all in 4-0-91.

Maybe the logs will help.

MuTools · Post by **MuTools** » Wed Jan 11, 2012 2:55 pm

Thanks for the logs! It's strange, they don't reveal any error, so i'll have to hunt further for the 'MIDI input forget' problem.

Bonteburg wrote:I hate to tell you this but there's something wrong with the Kurzweil too as of 4-0-91. It works in 4-0-87 (except for the forgetting thing of course) but I can't play it at all in 4-0-91.

I have no problem here with MIDI input in M4.0.91 OSX.
But will check on another OSX system too one of the days.

MuTools · Post by **MuTools** » Fri Jan 13, 2012 10:24 am

Wrt the OSX MIDI input problems:

I've 2 confirmed probs on file now:

1) Sometimes, when launching MuLab, you need to go to MIDI Setup in order to get MIDI input working. From then on it works. This is system dependent.

2) In M4.0.91 MIDI input is not working, or only rarely. While in M4.0.87 it does work, besides prob 1).

I've found that problem 2) is the consequence of a bug in the apple tools or gcc compiler. Incredibly crazy situation. Now i'm trying to find a solution/workaround for that.

When that's done i'll continue on prob 1) which was also there in M3.

MuTools · Post by **MuTools** » Fri Jan 13, 2012 6:25 pm

There is a new version M4.0.95 in http://www.mutools.com/mulab/cedar

This is what's changed:

Finetuned startup session selector dialog.
Support for template sessions.
Finetuned 'open session' menu functions.
Removed the separate 'Save As New' menu item, can be done via Save As Template.
Finetuned conversion from M3 MultiSampla to M4 MultiSampla.
OSX version: Bypassed a GCC compiler bug which caused MIDI input to not always work since M4.0.91.
Finetuned MuDrum graphics.
New way of indicating that multiple sessions are opened, using a auto-hide alert.
More severe avoiding of feedback loops between modules.
Plug slots now also accept dropped .MuSynth files (MuLab 3)
Fixed crash bug when loading certain M3 patches.
Fixed a redraw issue when rearranging MUX meta-parameters.
MultiSampla now supports detailed Amp ADSR editing.
Finetuned several aspects in the factory library.
Patch info text now is done via a plain text file in same folder as, and same name as the patch file. Also .html is supported.
Fixed: The "New Patch" context function did not reset any Play Editor customization.
Finetuned left-/right-click behaviour for rack slots.
Fixed a crash bug when rearranging MUX meta-parameters.
Fixed: When dragging things around, the drag rectangle was not drawn as intended, not explicit enough.

Marco & co, can you please confirm that MIDI input bug nr 2 has gone in this version.

I'll test this version on other OSX machines wrt MIDI input bug nr 1.

( cfr http://www.kvraudio.com/forum/viewtopic ... 52#4794152 )

Bonteburg · Post by **Bonteburg** » Fri Jan 13, 2012 6:58 pm

Everything is running smoothly so far!

I don't know how you did this but the OSX-10.6.8-Oxygen-only problem also seems to have disappeared. You're awesome!

If you're on 10.6.8 with an M-Audio keyboard, MU.LAB is as of now the only sequencer in the sub-100 Euro range that workks correctly.

the new dialogue on startup is a real improvement, too.

Marco

DHR53 · Post by **DHR53** » Fri Jan 13, 2012 9:20 pm

Yo Jo... I changed the preferences for mouse wheel scrolling in the MULAB.Txt file to Value=MouseWheelScrolls and it keeps zooming? I'm on a Mac, although I'm not sure if that has anything to do with it?

DHR53 · Post by **DHR53** » Fri Jan 13, 2012 9:47 pm

Just DLd the new version... still can't change that pref? Hmmm... what am I doing wrong here.

DHR53 · Post by **DHR53** » Fri Jan 13, 2012 11:53 pm

Er, I fixed it somehow? I thought I did the same thing before but maybe I was tired... Ha! Onward to MuDrum. Speaking of, I've noticed that if I save the drum preset on the right side (of interface) it doesn't save the preset... I guess I'm missing something about the MuDrum. Is the right side of the plug a seperate module? Saving the preset on the left side saved the whole drum preset? Hmmm...

MuTools · Post by **MuTools** » Sat Jan 14, 2012 10:55 am

Bonteburg wrote:Everything is running smoothly so far!

I don't know how you did this but the OSX-10.6.8-Oxygen-only problem also seems to have disappeared. You're awesome!

If you're on 10.6.8 with an M-Audio keyboard, MU.LAB is as of now the only sequencer in the sub-100 Euro range that workks correctly.

the new dialogue on startup is a real improvement, too.

Marco

Well that's good news.
I expect though that the 'midi input forget' problem still is there, isn't it?

MuTools · Post by **MuTools** » Sat Jan 14, 2012 11:02 am

DHR53 wrote:Er, I fixed it somehow? I thought I did the same thing before but maybe I was tired... Ha!

To change MuLab's mouse wheel behaviour from zooming to scrolling:
When MuLab is not running, put this line in User/Settings/MuLab.txt

Code: Select all

EditorNavigation=MouseWheelScrolls

Onward to MuDrum. Speaking of, I've noticed that if I save the drum preset on the right side (of interface) it doesn't save the preset...

Why do you think it doesn't save the preset?

I guess I'm missing something about the MuDrum. Is the right side of the plug a seperate module? Saving the preset on the left side saved the whole drum preset? Hmmm...

The MuDrum has 12 MuPads. The right side shows the MuPad editor for the focussed pad. You can open/save a complete MuDrum set via the leftside top panel, or open/save an individual MuPad using the right side top panel.

Also see Trancit's nice intro doc on the MuDrum:
http://www.mutools.com/mulab/cedar/MuDrum.pdf

Bonteburg · Post by **Bonteburg** » Sat Jan 14, 2012 12:37 pm

mutools wrote:I expect though that the 'midi input forget' problem still is there, isn't it?

Yes - though I would put it lower on the priority list.

Nielzie · Post by **Nielzie** » Sat Jan 14, 2012 1:05 pm

One thing that I still can't get used to compared to M3 is the fact that when I insert an effect after an instrument with internal sequencer (like MicroTonic), that sequencer stops playing and I have to restart it.

I guess that everytime an effect is added to the rack, there is some kind of "reset" happening which makes the instrument stop.

MuTools · Post by **MuTools** » Sat Jan 14, 2012 1:24 pm

Nielzie wrote:One thing that I still can't get used to compared to M3 is the fact that when I insert an effect after an instrument with internal sequencer (like MicroTonic), that sequencer stops playing and I have to restart it.

I guess that everytime an effect is added to the rack, there is some kind of "reset" happening which makes the instrument stop.

Yes, that's correct about the reset. And i don't see a solution for that, the reset is necessary.

MuTools

KVR Audio

M4 Test