MU.LAB 3.1 test

[Calum]

[*]Fixed: OSX: Double-click didn't work

Confirmed, working now. Thanks.

[sorohanro]

Embedding samples and even audio recordings is one of the most important features IMO, please don't discard it

+1
It's useful when want to share a track.

Would be a great feature to be able to embed audio files in Musynth files also.
Just imagine how easy would be sharing sample packs, not like now, copy the patch, then copy the folder then put the folder into... etc... etc... too many things that can go wrong.

[liquidsound]

The "New.MuSession" is not working....
It's located in the MULAB/User/Library/MuSession.
Any Idea?

v3.1.14

[MuTools]

It works fine here. Anyone else having a prob with this?

[liquidsound]

What was the last version good for your patches?

[MuTools]

Last main test package version = 3.1.3
Last test patch version = 3.1.14

[Simon Posford]

Sorry, forgot to answer that question.

If you're eager to use it now then 1) else 2)

1) Open the zip file and drag-drop the 2 files in it to the Mulab/App/Graphics/LooxSkinName/Common/Common/Formats subfolder.

2) Soon MU.LAB 3.1 will be released and things will be up to date in the release package, so you won't have to worry about it.

Thank you jo for the answer!

[Improviser]

The "New.MuSession" is not working....

and

It works fine here. Anyone else having a prob with this?

No problems here, on Windows 7 (64-bit), using the mulab-3-1-14-win-patch in the MULAB folder of the full mulab-3-1-3-win test version.

Les J.

[MuTools]

I also got confirmation via email that it's working ok.

Liquid, can you please doublecheck on your side, maybe a typo somewhere or saved in the wrong folder or maybe a MU.LAB version issue.

Before 3.1.6 => New.MuSession in Mulab folder itself
From 3.1.6 on => New.MuSession in Mulab/User/Library/Musession folder

Hope this helps.

[bpblog]

back on the forum after a while. i have a lot of catching up to do with so many new posts around. :]

anyway, here's a question, couldn't find a clear answer to it via search.

can mulab receive midi clock? as in sync to another host's tempo and start/stop playback messages?

[MuTools]

MU.LAB can send MIDI clock out but does not support syncing to MIDI clock input.

[liquidsound]

I also got confirmation via email that it's working ok.

Liquid, can you please doublecheck on your side, maybe a typo somewhere or saved in the wrong folder or maybe a MU.LAB version issue.

Before 3.1.6 => New.MuSession in Mulab folder itself
From 3.1.6 on => New.MuSession in Mulab/User/Library/Musession folder

Hope this helps.

I tried at work with the same MULAB folder from home and it's fine.
Trust me, I spent hours last night and I put the New.MuSession everywhere.
It was working until the last patch.

I'll manage. It's definitely my PC issue now.

Thank you.

[MuTools]

The new MU.LAB 3.1.16 test patch is available in http://www.mutools.com/mulab/chestnut

What's changed:

• Tuned: Finetuned code in order to minimize graphical animation jitter
• Tuned: Finetuned code in order to have a more solid play cursor while scrolling/zooming an editor
• Tuned: When copying parts to the clipboard, the current target module is properly copied too (track or part target)
• Tuned: Record events + selected part + cancel => also had to cancel new name dialog (2x cancel)
• Tuned: Default audio recording channel format = stereo
• Tuned: Finetuned the composer and sequence editor regarding the new double-click detector (there was a little issue on slower systems)
• Fixed: OSX: Audio error when using an oscillator's AIPS feature together with fatness
• Fixed: When selecting a track/part, then it could be that its target rack was not properly made visible in a wide rack desk
• Fixed: Problem with pasting parts into another composition
• + some minor tunings

If you already have installed MU.LAB 3.1.4 or later, then simply replace the current MU.LAB application file with the new application patch file.

This is MU.LAB 3.1 release candidate 5.

[liquidsound]

Finetuned code in order to have a more solid play cursor while scrolling/zooming an editor

Now it works better than any sequencer!
That's coding!

[pljones]

Tuned: When copying parts to the clipboard, the current target module is properly copied too (track or part target)

Ah... Not when the track is overriding the part at the destination of the copy... OK, I now see it.

Yes, if I have the source part on a track set to Part's target, copying the part takes the Part's target. When the source part is on a track set to a Track target, copying the part takes the Track target as the destination part target.

Would it make sense when copying to an empty track with a Track target set, to change the Track target, too?

This is via drag-n-drop. Is there a "copy to clipboard" somewhere I'm not seeing, though? Would that allow copying between MuSessions?