M3 Tests

[liquidsound]

"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.

Well this synth costs 20 bucks so it's no big loss.

It might not like how Mulab works with Snow Leopard.
It works flawlessly in Live, RAX and Logic (except for the CPU spikes), so it's only a problem in AUlab and Mulab.

One issue might be the audio input of Xils. Maybe some soft of delay or click is causing the feedback. Trust me its nasty and it happens almost every time.

After installing the latest build, Xils 3 LE doesnt even import into Mulab.
Fatal Error it says. So clearly its not communicating well.

I LOVE the sound of this synth as well. The only software synth I've heard since Oddity that has that sweet analog character.

OK.
I was testing the full version, a massive synth.
Did you tried Zebra 2.5? It should run perfectly in MuLab.

Sorry for this is not the appropriate place for these posts. (last)

[fceramic]

Well since it works in other major hosts it is slightly relevant. Like I said it doesnt even import into Mulab so it seems like theres some major conflict. People wont use this great DAW if some their beloved plugins do not work.
I did email the developer who said he would try to fix it.

[Jazz Franco]

@fridtjof
I still think this is OS dependent problem As I posted here before, Xils LE edition (the $20 one) runs finely here in OSX10.4, PPC Mac

[MuTools]

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

[MuTools]

Quickfix:

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

What's changed: http://www.mutools.com/mulab/azalea/mul ... hanges.txt

If you have already installed 3.0.24, you can simply apply the latest patch.

This is one of the last test versions.

Please report any left bugs!

Thanks!

[Eggu]

grid snap issue:
if a short cut is defined for toggle-grid-snap (e.g. ALT-S),
this shortcut works in midi-editor-view,
but not in composition/part view (when moving parts).
permanent view of current grid/snap setting also would be nice.

jump to start:
what about former function: right click into position window -> jump to start (1.1), any alternative which is as fast as before ?

[sorohanro]

Downloading... let's see how's going

[MuTools]

grid snap issue:
if a short cut is defined for toggle-grid-snap (e.g. ALT-S),
this shortcut works in midi-editor-view,
but not in composition/part view (when moving parts).

I can't repeat that here, it works fine here.

There was such issue a couple of versions ago.

Are you sure using the latest version 3.0.26?

jump to start:
what about former function: right click into position window -> jump to start (1.1), any alternative which is as fast as before ?

Added to the whishlist.

[Eggu]

grid snap issue:
if a short cut is defined for toggle-grid-snap (e.g. ALT-S),
this shortcut works in midi-editor-view,
but not in composition/part view (when moving parts).

I can't repeat that here, it works fine here.

There was such issue a couple of versions ago.

Are you sure using the latest version 3.0.26?

Yes, version 3.0.26

pressing ALT-S in note editor shows "Snap OFF" or "Snap ON"
in the small info window (lower right corner) and snap toggles,

but pressing ALT-S in the part editor has no effect
(no message in the small window, no snap toggle)

new question:
to enter "pencil mode" now you have to mouse double click
(in mulab 2.x middle mouse button), ok.
But is it possible to select a part of a midi controller track,
e,g, a section of pitch events ? (lower part in note editor) ?
There you are always in "pencil mode".

[MuTools]

Yes, version 3.0.26

pressing ALT-S in note editor shows "Snap OFF" or "Snap ON"
in the small info window (lower right corner) and snap toggles,

but pressing ALT-S in the part editor has no effect
(no message in the small window, no snap toggle)

Can anyone repeat this?

I've completely no idea what's going on, so some generic questions:

Are you on OSX or Windows?

Is it in all sessions/compositions that it does not work?

new question:
to enter "pencil mode" now you have to mouse double click
(in mulab 2.x middle mouse button), ok.

FYI: You can also hold [Ctrl] to pencil faster.

But is it possible to select a part of a midi controller track,
e,g, a section of pitch events ? (lower part in note editor) ?
There you are always in "pencil mode".

Hold [Shift].

[MuTools]

Yes, version 3.0.26

pressing ALT-S in note editor shows "Snap OFF" or "Snap ON"
in the small info window (lower right corner) and snap toggles,

but pressing ALT-S in the part editor has no effect
(no message in the small window, no snap toggle)

Still very amazed by this one.

I checked this on 3 computers, all working fine.

Strange thing.

Some extra questions:

* Do all other shortcuts work fine?

* What if you use e.g. [A] as the key for Toggle Snap On/Off? Does it work fine then? I mean: Is it key related?

Looking forward to your answers.

[robenestobenz]

Re. Eggu's snap problem -- I also had this, but only in parts in which the grid is set to "no grid" on project open.

This is OK, because if the grid res is set to "no grid" snap toggle should of course have no effect. The odd behaviour is that in this case shortcuts to alter the grid resolution do not work until you change the grid res from the context menu. After this, no grid works as usual even if you set the part to "no grid" and reopen the part.

//Open any part in intro.musession for an example of this.

[Improviser]

Yes, version 3.0.26

pressing ALT-S in note editor shows "Snap OFF" or "Snap ON"
in the small info window (lower right corner) and snap toggles,

but pressing ALT-S in the part editor has no effect
(no message in the small window, no snap toggle)

Can anyone repeat this?

So far, I haven't played a lot with shortcut preferences (maximum of 16 in Test version, MULAB Free), but just had a quick try to repeat this.

Perhaps the reult is dependent on whether you are choosing 'Toggle Snap ON/OFF' from the "Generic" list or the "Specific" list. Here (in M.3.0.26, on Windows), if I select via "Specific->Sequence Part->Toggle Snap ON/OFF" I can get the behaviour Eggu mentions. If I select via "Generic->Toggle Snap ON/OFF", I get the shortcut working ok in both the Composer and the Note Editor windows.

Not sure whether that's of any help ?

Les J.

[MuTools]

Re. Eggu's snap problem -- I also had this, but only in parts in which the grid is set to "no grid" on project open.

This is OK, because if the grid res is set to "no grid" snap toggle should of course have no effect. The odd behaviour is that in this case shortcuts to alter the grid resolution do not work until you change the grid res from the context menu. After this, no grid works as usual even if you set the part to "no grid" and reopen the part.

//Open any part in intro.musession for an example of this.

I even can't repeat this one!

This is what i did in MU.LAB 3.0.26 FREE:

* I opened Intro.MuSession.
* Opened Shortcuts dialog, deleted F1+F2, mapped Alt+S to Generic->Toggle Snap On/Off
* In Composer, Alt+S works fine
* I open first KraftLine sequence, Alt+S works fine

So i still can't follow

PS: You're right about the Inro.MuSession having no grid settings here and there. Will finetune this.

[MuTools]

So far, I haven't played a lot with shortcut preferences (maximum of 16 in Test version, MULAB Free), but just had a quick try to repeat this.

Perhaps the reult is dependent on whether you are choosing 'Toggle Snap ON/OFF' from the "Generic" list or the "Specific" list. Here (in M.3.0.26, on Windows), if I select via "Specific->Sequence Part->Toggle Snap ON/OFF" I can get the behaviour Eggu mentions. If I select via "Generic->Toggle Snap ON/OFF", I get the shortcut working ok in both the Composer and the Note Editor windows.

Not sure whether that's of any help?

Yes, that could indeed explain what Eggu encounters.

But then i hope you see the logic:

If you assign a shortcut to Sequence Part->Toggle Snap ON/OFF, then it only works for sequence parts of course, that's exactly what the specific list is for.

By default, i would recommend to use the Generic shortcuts, but in some cases you might need to define shortcuts more Specificly to avoid ambiguities.