M3 Tests

[fceramic]

fridtjof, do you have any news on the MIDI output issue you reported?
(cfr my question on this some posts ago)

Curious for your answer.

What was the question?

I got strange midi behavior when I had both midi outputs selected. Like a little click when playing a note. This was in Reaktor.

Xils Le just opens with the default preset, so there shouldnt be any strange routing.
The developer said it ran fine in Mulab so good for him! Then he told me he had heard of that bug before and that it would be fixed in a future version!
So I'm just deleting it off my HD.

[MuTools]

What was the question?

This one:

Also another annoying bug is that Mulab cant seem to decide weather to use my keyboard's midi output B and A, so I have to change the midi settings back and fourth.

In MU.LAB's MIDI Setup (Edit menu), your MIDI keyboards out A and B should have different names, right.

Now if you set the first output to Out A and the second output to Out B, then this should not change. Are you saying it does change there?

So are you saying it does change there?

[MuTools]

(deleted 2 posts from myself; to be continued tomorrow)

[Jazz Franco]

(deleted 2 posts from myself; to be continued tomorrow)

Erm... I downloaded and installed v3.0.23 (OSX), it's no more on the server -- anything wrong with it?
Anyway, I ran a quickie test: dragging files from the finder to MultiSampla's zone editor works flawlessly. I noticed that floating hints in VST wrapper say 'open VST file/save VST file' instead of (obviously) 'open/save fxb/fxp' which is a bit misleading. And no, I couldn't reproduce that dreaded Xils-free crash so many people are reporting here. It eats CPU seriously, but works OK, no feedback, no glitches, even when changing presets on the fly.

Old PPC iBook G4 OSX10.4 with all bells and whistles (airport, bluetooth etc) switched off.

[MuTools]

(deleted 2 posts from myself; to be continued tomorrow)

Erm... I downloaded and installed v3.0.23 (OSX), it's no more on the server -- anything wrong with it?

No, not really 'wrong' but i noticed some last minute things which i wanted to correct. Feel free to use M 3.0.23, it should be ok. M 3.0.24 will be there tomorrow.

[fceramic]

Tried all different ways but Xils still doesnt work in Mulab.
Works flawlessly in Logic and Live.

Why am I having all this bad luck with Mulab! It did seem too good to be true...

[MuTools]

MU.LAB test 3.0.24 is available in http://www.mutools.com/mulab/azalea

It's recommended to make a full new install because the folder structure has changed.

If you want to preserve your current settings, then copy the files in your previous Mulab/Settings to the new Mulab/User/Settings before running MU.LAB.

What's changed in MU.LAB test 3.0.24: http://www.mutools.com/mulab/azalea/mul ... hanges.txt

Now there are some things i would like to ask:

Gui Focus Box

Because of the new shortcut system in M3, it's more important to know which part of the GUI will process the keys you press.

Example: Assume we've mapped [R] to "Rename".
When gui-focus is on composer, with sequencepart selected => R will rename a sequence.
When no sequence is selected, R will rename composition.
When gui-focus is on a track, R will rename that track (if that track has no specific target).
When gui-focus is on a rack, R will rename that rack.
Etc...

So that's why i've finetuned MU.LAB so that the GUI Focus Box is prominent visible.

Note that you can hide the GUI Focus Box if you want:

* Quit MU.LAB
* Open Mulab/User/Settings/Mulab.Txt
* Ensure the line "DrawGuiFocusBox=0" (without the quotation marks)
* Save Mulab.Txt and restart MU.LAB

You could also set it to 50, then the focus box will be 50% visible.

(Note to skin developers: Focus box color is skinnable via Common/Pictures/FocusBoxColor.Png)

The defaut is 100% visible.

Gui Focus Shifts On Hover

Note that MU.LAB automatically shifts the gui-focus on hovering (holding the mouse over) a component that is focussable.

This is non-standard software behaviour but i think it's a comfortable thing.

For example, you can hover a rack slider and start pressing [Arrow Up] and [Arrow Down] to change the slider.

Another example: You can simply hover a track to get the focus and then press a track shortcut key to trigger a track function.

Another big advantage of the automatic focus shift is that you don't have to take care too much of the focus as most of the time the mouse is in the zone you're working with and so the gui focus is likely to be there too.

Note that this behaviour was alrady there in MU.LAB 2.7 (and before) but now it has also become a preference "GuiFocusOnHover" and you can change it in Mulab.Txt cfr above. Values are 0 (Off) or 1 (On). The default is On.

Your opinion

As you will see, the focus shift on hover, the focus box and the shortcut system are all very related to eachother.

I've set the defaults how i think it will work best.
In fact it works the same as in MU.LAB 2.7 with exception that the focus box now is more prominent visible for the reasons given above, and i've also finetuned several aspects.

But now i'm curious of what you think of all this as a musician.

Do you think it's all OK now? Or is the focus box in the way of your musical creativity?

Would you rather set "DrawGuiFocusBox=0" as the default?

Would you rather set "GuiFocusOnHover=0" as the default?

Please try it out before deciding as one also has to FEEL how it works.

Enough words.

Looking forward to your feedback!

[fceramic]

Now Xils 3 Le doesnt even import into Mulab, just get a fatal error message.

[Nielzie]

Tried all different ways but Xils still doesnt work in Mulab.
Works flawlessly in Logic and Live.

Why am I having all this bad luck with Mulab! It did seem too good to be true...

Hang on... I had some troubles too in the beginning with Surge and some other little stability issues, but Jo has fixed them all so it seems and the latest builds are very stable for me now

Could the eLicenser protection of XILS LE giving the troubles now or is that out of the question?

[fceramic]

YAHOOOOOO! The multi timbral midi problem is fixed. Thanks!

[MuTools]

fridtjof, regarding Xils 3 Le: as other users reported here it sounds like a problematic plugin. I'm afraid i can't do anything about it. Isn't there a more stable plug that can fill in your musical whishes?

[pquenin]

hello, I have been busy but i'm back.
The DrawGuiFocusBox and GuiFocusOnHover defaults are ok for me.
But Mulab shifts the gui-focus on hovering a bit too slowly, perhaps it's only on my system (Pentium 4 3Ghz HT) with XP.

[MuTools]

hello, I have been busy but i'm back.
The DrawGuiFocusBox and GuiFocusOnHover defaults are ok for me.
But Mulab shifts the gui-focus on hovering a bit too slowly, perhaps it's only on my system (Pentium 4 3Ghz HT) with XP.

Currently a mouse hover is triggered after 700ms.

It also defines when a tooltip appears etc.

No problem changing this value. What do others think?

[Nielzie]

hello, I have been busy but i'm back.
The DrawGuiFocusBox and GuiFocusOnHover defaults are ok for me.
But Mulab shifts the gui-focus on hovering a bit too slowly, perhaps it's only on my system (Pentium 4 3Ghz HT) with XP.

Currently a mouse hover is triggered after 700ms.

It also defines when a tooltip appears etc.

No problem changing this value. What do others think?

Good point. A little bit faster would be nice imo Maybe 500ms?

[liquidsound]

fridtjof, regarding Xils 3 Le: as other users reported here it sounds like a problematic plugin. I'm afraid i can't do anything about it. Isn't there a more stable plug that can fill in your musical whishes?

Maybe not...

I tried Xils 3 demo on MuLab 3.0.20 inside the MUX and I had 20 minutes of trouble free play, just going through the presets.
Then I just loaded it as usual in a rack and everything went fine too.

I noticed though that when the CPU meter (MuLab built in) reaches around 70% to max 75% then I can't stop Xils from overloading the system and I have to go back and forth in order to change the intense preset because the mouse is no longer working right. The PC is choking.
Beside this the 3.0.2 seems to handle it.

I am using a very old Laptop dHell Pentium 4 M 1.7ghz!! XP SP3.

Last time I used Mu 3.0.5? at work, so now it's different.

So , no problems, so far, with MuLab and Xils in demo situation.

"fridtjof"
could you tell me how I should test Xils in order to understand what's happening to you?
I kind of like this synth...I would not mind getting one.