MU.LAB 3.1 test

[MuTools]

I'm focussing on a bug related to the display of audio files. Version 3.1.5 is an intermediate version i'm communicating about via email. It's not a 'finished' version that's why i didn't message about it. But it's ok using it, no prob.

[robenestobenz]

Minor FR -- in consistency with double click elsewhere, could double clicking on the timeline in the wave editor add a locator?

Could you check out the problem below, Jo?

Whenever I delete the Endorphin vst, Mulab crashes. It works fine in 2.7. Is this the VST's fault?

It actually crashes on exit or create new project as well, so it seems it must be something to do with unloading the vst. It worked fine for jpumphandle though, so maybe the issue lies between my PC, XP64 and something in MuLab 3.

[MuTools]

Based on these facts:

* almost all plugins don't have the problem
* even endorphin doesn't have the problem on all machines

i think it's an Endorphin related issue.

What does the Endorphin developer say?

[robenestobenz]

Based on these facts:

* almost all plugins don't have the problem
* even endorphin doesn't have the problem on all machines

i think it's an Endorphin related issue.

What does the Endorphin developer say?

Don't think they're supported any more, as the dev now works for Magix. I'll drop him a line anyway. In the meantime, I can always embed it in a vst host plugin.

[MuTools]

Minor FR -- in consistency with double click elsewhere, could double clicking on the timeline in the wave editor add a locator?

Sounds logical indeed, will check further, added a note on the WL.

Just a thought: This will slow down a single click on the time bar (to set the position) because system will have to wait a little bit so to see if it's a double-click. That's a typical disadvantage of the double-click system, wish there was a solution for that.

[robenestobenz]

Minor FR -- in consistency with double click elsewhere, could double clicking on the timeline in the wave editor add a locator?

Sounds logical indeed, will check further, added a note on the WL.

Just a thought: This will slow down a single click on the time bar (to set the position) because system will have to wait a little bit so to see if it's a double-click. That's a typical disadvantage of the double-click system, wish there was a solution for that.

D'oh, I didn't think of that. It's important for things to feel responsive, so maybe not such a good idea after all...

[MuTools]

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

To update your MU.LAB 3.1.4, simply replace the current MU.LAB application file with this new application file.

What's changed:

• Tuned: Whenever a progress bar is used, it's not in system modal window anymore, but in a more gentle floating window
• Tuned: New.MuSession is looked for in Mulab/User/Library/MuSession
• Tuned: A couple of other minor graphical tunings
• Fixed: A bug in the audio recording engine that could cause distorted audio where it should be silence
• Fixed: A bug in the audio file display system that could cause faulty displays

[pljones]

• Tuned: New.MuSession is looked for in Mulab/User/Library/MuSession

So not just drop the patch in but move any New.MuSession to its new home .

[MuTools]

Indeed

[liquidsound]

I inserted in the MUX a MuSynth and a Synthia.
I assigned to Synthia the first knob to the Level, Display = Label
I then assigned a new parameter, on a second knob, to the MuSynth Amplifier gain, Display = Gain

So far OK.
If I go back to the second knob and I change the target to the Synthia and choose Level. The display will not change but it will display Gain. It's targeting the right thing (Synthia Level) but it's displaying the MuSynth Gain control.

I don't think this is intended...

Jo, can you explain how can I get a value in "db" instead value in "%", if possible, out of device in the MUX or by itself?
Can this be transformed to get Level measurement in "db" rather then percentage (%)?

The only thing I can think of is to have the device target a Mixer strip, crank the device output to 100% and then adjust the Gain "db" in the strip from the knob.

How far off am I?

[MuTools]

I inserted in the MUX a MuSynth and a Synthia.
I assigned to Synthia the first knob to the Level, Display = Label

To which Synthia parameter?

I then assigned a new parameter, on a second knob, to the MuSynth Amplifier gain, Display = Gain

So far OK.
If I go back to the second knob and I change the target to the Synthia and choose Level. The display will not change but it will display Gain. It's targeting the right thing (Synthia Level) but it's displaying the MuSynth Gain control.

The meta parameter labels are defined by the user, they do not 'automatically' update. To rename a meta parameter: Click the meta parameter display in the middle of the knobs in the deep editor, or right-click the meta parameter knob.

Only when doing the very first assignment, MU.LAB auto fills in the name of that first target parameter.

Jo, can you explain how can I get a value in "db" instead value in "%", if possible, out of device in the MUX or by itself?
Can this be transformed to get Level measurement in "db" rather then percentage (%)?

The parameter units are not user definable.

FYI: If the target parameters of a meta parameter all have the same type of value display, then that value display is preserved. Else a generic 0-100 % value display is used.

[janamdo]

Mulab has modulations on two levels:

- sound construction level ( you make first the sound)
- performance level sound (realtime effects for the sound in a song)

All can be done by Midi controllers(midi mapping)(1)or by drawing controllercurves(2)or by knobs (3) (mouse) slider(4)(mouse)(limited use only parameters of the mixerstrip)

Adding some realtime xy controllers in MUlab should enhance the sonic possibilities maybe?

Indeed the automation documentation as topic for Mulab is not present

[MuTools]

Found a couple of issues in the MU.LAB 3.1.6 test patch, so here is a new MU.LAB 3.1.7 test patch: http://www.mutools.com/mulab/chestnut

More details on http://www.mutools.com/mulab31.html

The test alert dialog has been removed as this is MU.LAB 3.1 release candidate 1.

[MuTools]

MU.LAB 3.1.7 also features a skinnable position line.

The MU.LAB 3.1 release package will include a skinned position line, but you can also already drop the two files in the below zip into your Mulab/App/Graphics/LooxPhat/Common/Common/Formats subfolder for immediate effect:

http://www.mutools.com/mulab/chestnut/PositionLine.Zip

[cytone]

Getting a serious error red box if I ALT+mouse click anywhere in the piano roll which is not a note.