MU.LAB 2 Test A

[Bonteburg]

Reinstalled MU.LAB, moved it to the applications folder, didn't rename it, saving weirdness *seems* to be gone...

Normally MU.LAB isn't so fussy about directory stuff, is it? so I'd still think it was weird behaviour for it to act that way.

[Bonteburg]

WTF... Multisampla rocks!!!


Marco

[Bonteburg]

Mixdown/Sampla:

1. Mix down to sample

2. Navigate to the sample using the Sampla GUI

3. There is no visible waveform in the sample editor eve though the sample plays back O.K.

[Bonteburg]

GUI Weirdness:

I couldn't resize the window anymore between some edits and tweaks and only noticed it when I had to (OSX Dock getting in the way).

On subsequent restarts the GUI got bigger still and now half of the mixing desk is out of bounds.

edit:A hack into "MULAB.txt" fixes this.

[toxicoh]

The Sampla and MultiSampla work well and sound great.

Both load the .MuSynth files in Library/MuSynth and Library/Synthia folders. The .wav files in the Library/Waveforms folder aren't seen by the file browser. Is that how it's supposed to work?

The Library/Sampla folder is empty. Is this a place to save new work?

I'm not having Bonte's problems with GUI, but the wierd VST screen drawing isn't going away....

[Bonteburg]

The Library/Sampla folder is empty. Is this a place to save new work?

I think it could be the place where your multisamples and .ovw files go? I can't look just now.

And I just noticed I was probably being imprecise when I said "couldn't resize". The GUI just got so big I couldn't gab its ends with the mouse anymore, so there wasn't really a redraw problem but only the size problem.

[toxicoh]

The Library/Sampla folder is empty. Is this a place to save new work?

I think it could be the place where your multisamples and .ovw files go? I can't look just now.

And I just noticed I was probably being imprecise when I said "couldn't resize". The GUI just got so big I couldn't gab its ends with the mouse anymore, so there wasn't really a redraw problem but only the size problem.

I'm running on 1440x900 rez in "millions of colors". The expanded main window nicely fill the screen. If I use this, the VST display thing isn't seen so much. But I like to run in a smaller window usually so the VST(s) can be seen while working.

[Bonteburg]

a few inconsistencies -

-I was unable to automate/assign midi controllers to the more intricate parametres in sampla and multisampla (like decay time in the envelope section). On the other hand, some parametres show up twice for no apparent reason (Gain, "Pan" and "Stereo Pan" etc.


-Multisampla: Keyboard should default to C3 or something similar for a scroll position. C-2 is way too low IMO.

[Bonteburg]

two crash reports I had just now:

http://www.fileden.com/files/2007/5/13/ ... ostion.txt

http://www.fileden.com/files/2007/5/13/ ... roject.txt



OSX 10.4.11

[MuTools]

Jo -- will the 2.0 final support 1.x sessions? This test version does seem able to read 1.1's MuSession files.

MU.LAB 2.0 does open MU.LAB 1.1 sessions.

Some general info:

A new MU.LAB version will open sessions made in it's immediate precessor version, but normally not sessions in older versions, in which case you just have to open+save the session in the intermediate MU.LAB versions so to upgrade the MuSession file step by step to the newest MU.LAB version.

Note that it's always possible that a newer version does not 100% sound the same as a previous version, there might be sonic differences.

Of course best is done to offer as much compatibility as possible, but if it's about important productional work, it's recommended to keep the different MU.LAB versions on file so that you can open a musession in it's original MU.LAB if necessary.

In MultiSampla, deleting a zone could be easier. It should feel more like click a Part, hit Delete (key), gone.

That's supported!

Doesn't it work on your system?

Also, the zone isn't removed from the display when deleted, until - e.g. - you try to select it.

True in case of delete via the context menu. Will be fixed.

Thanks.

[MuTools]

MultiSampla patches: how easy are they to share? They get stored in MULAB\Library\MultiSampla -- but where do the samples live? What if they're in a different place on someone else's machine? Etc...

Samples are stored as references by default, so paths muts match.

But you can always choose to "Embed" a sample via the sample's context menu.

[MuTools]

The Tools button only seems to do one thing: "Add a sample"

True, but "Tools" will be furtherly enriched lateron, normally.

Atoh, i guess "Add A Sample" could also be placed in "File".

You're right, it needs some more attention.

Something VERY BAD happens when opening LFX-1310, SR202, DS404 VSTs for OSX: 1 good VST like normal, but some screen drawing overwrites duplicate image behind the Mu.Lab main window top left corner! I've never seen this before.

Can you please email me a screenshot. Thanks.

Choosing an external audio editor doesn't show in the Edit/Preferences/ like before...

On OSX it's not yet supported.

[MuTools]

Should I be able to move the pre/post fader marker in a rack? If so, how / I can't...

A bug, will be fixed.

[MuTools]

OSX 10.4.11
Strange goings-on - 2 files appeared on my desktop I positively didn't create or put there...

Strange, don't know how they came there...

Crash log: http://www.fileden.com/files/2007/5/13/ ... .crash.log

Thanks. Will research.

I keep the test version in a folder named "MULAB 2.0 test" on my desktop.

the MULAB 1.0 folder curently resides in my documents folder renamed to "MULAB_aktuelle_Version" ("proper version") to avoid conflict.

Having 2 or more mulab folders is perfectly ok.

But having a . (dot) in the folder name may cause problems, maybe the cause of the strange files, the small window etc...

Please rename it to "MULAB 2 test" and see how that goes.

I'll investigate wether i can make mulab more compatible 'dot-wise'.

[MuTools]

saving weirdness...

I'm quite sure it's all related to the dot in the folder name...