MuTools

MuTools · Post by **MuTools** » Thu Nov 21, 2013 5:35 pm

A new MuLab 5.3.16 test version is available in http://www.mutools.com/mulab/everest

What's changed since M5.3.15:

Double-clicking the track icon opens the target editor again. (was not working anymore since a recent test version).
Fixed a button mismatch in the multi-sample player editor.
Samples: Added a "Create New Sample From Selection" function.
VST editors: When opening a VST plugin editor for the first time, and the vst editor is bigger than the screen, it could be that the window title bar was not visible. Tuned.
Support for cutting/deleting multiple modules at once.
Locators: Right-click "Delete" does not use a delete confirmation anymore.
Fixed a possible crash bug when previewing muclips.
Mixdown dialog: Added a button to quickly set the From-To to the composition loop.
When applying DSP functions on an entire sample, then Undo was not working. Fixed.

It's an app+ID only update, so quick & easy to install. Detailed install info in http://www.mutools.com/mulab/app-patch/Read%20Me.txt

Cheers!

liquidsound · Post by **liquidsound** » Sat Nov 23, 2013 3:00 am

Downloaded the 5.3.17 instead.

The Floating window bar:
There is a difference between a third party plugin and a MuLab plugin.
If I expand a minimized Plugin and then I click on its name button in the floating bar, it remains open, while a MuLab plugin close if on focus and the button disappear. Same for the Rack Desk.
So MuLab modules can't stay open upon clicking on their buttons in the bar when on focus.
On focus I mean being the top most window.

Once the floating window bar gets closed I can't find the command to reopen it again even if I minimize a plugin.

It would be even more useful IMO if when Right clicking on a minimized button, of an Expanded (open) window plugin, to just minimize it again so that we have the ability to switch between open windows plugins with the Left click and also to minimize, the ones we don't need open at the very moment, with the right click. All from the floating window area. Better workflow.

I love the Rack minimize option with recall, if it can be fixed.

Great upgrade as usual

MuTools · Post by **MuTools** » Sun Nov 24, 2013 8:21 pm

The next test version will have a finetuned Floating Windows Bar.

Some detailed replies:

liquidsound wrote:It would be even more useful IMO if when Right clicking on a minimized button, of an Expanded (open) window plugin, to just minimize it again so that we have the ability to switch between open windows plugins with the Left click and also to minimize, the ones we don't need open at the very moment, with the right click.

I'm not yet sure about this one. I'll give it some more time & thought.

I love the Rack minimize option with recall, if it can be fixed.

I don't understand what you mean with this. Please elaborate.

Thanks for your feedback!

liquidsound · Post by **liquidsound** » Mon Nov 25, 2013 1:37 am

The Rack desk when minimized was not showing up in the Floating window (as of 5.1.5). Now it does!

For the Right click option, I hope it was not confusing the way I wrote it.
In the floating bar buttons:
LMB = Show / Bring to front
RMB = Minimize

Maybe is good, maybe is not.

MuTools · Post by **MuTools** » Wed Nov 27, 2013 5:39 pm

A new MuLab 5.3.19 test version is available in http://www.mutools.com/mulab/everest

What's changed since M5.3.16:

New Floating Window Bar: Floating windows can be selected and managed more easily.
Audio Limiter: Finetuned parameter displays + added visual feedback in the editor.
New sequence function: Quantize Notes 50%
Fixed a bug that caused that MUX front panel background pictures were not found sometimes.
OSX version: Sometimes the window borders were not properly reflecting the active/focus state of a window. Fixed.
Level compressor and Audio Envelope Follower now also have an event input jack for parameter automation.
When the source component of a tooltip is deleted, the tooltip is deleted as well.
Fixed a potential crash bug when applying DSP functions on audio.
Automation parts: Play position line always visible, also after last point.
Copying multiple modules to clipboard didn't work as expected. Fixed.
Mono Echo module: The minimum delay of 1 sample is taken into account in the parameter display.
Added REX file support.

M5.3.19 is an app+ID only update, so quick & easy to install. Detailed install info in http://www.mutools.com/mulab/app-patch/Read%20Me.txt

About REX file support: As this is an app+ID only update, it is for now assumed that the REX library is already installed on your system.

Then REX files can be handled as any other audio file, for example dropping them on the composer will add a sliced drumloop. Previewing REX files will also automatically be done using the current tempo, etc.

Looking forward to your feedback!

Cheers!

pljones · Post by **pljones** » Wed Nov 27, 2013 7:04 pm

The bad news is installing the .exe and .ID means Mulab fails to start.

The good news is reverting to .16 fixed it.

Can you remind me how to turn logging on?

MuTools · Post by **MuTools** » Wed Nov 27, 2013 7:10 pm

pljones wrote:The bad news is installing the .exe and .ID means Mulab fails to start.

What message do you get? Do you have the REX dll on your system?

AndreasD · Post by **AndreasD** » Wed Nov 27, 2013 8:27 pm

Great update !!

- To all who use limiters, the Audio Limiter module seems to really limit now!
- Thanks for the 50% quantize

- REX2 files work mostly fine. It seems to work with Mulab means alone, so why the REX DLL?

Thanks

dakkra · Post by **dakkra** » Thu Nov 28, 2013 4:22 am

pljones wrote:The bad news is installing the .exe and .ID means Mulab fails to start.

Same here. It simply doesn't open. Do I need said .dll for Mulab to work? I've never used REX files before so I've never had a need for such items

pljones · Post by **pljones** » Thu Nov 28, 2013 7:12 am

mutools wrote:
pljones wrote:The bad news is installing the .exe and .ID means Mulab fails to start.
What message do you get? Do you have the REX dll on your system?

No message - the process doesn't show on Task Manager at all (at least, not long enough to be spotted). I do not have REX as far as I know.

MuTools · Post by **MuTools** » Thu Nov 28, 2013 10:32 am

Ok thanks for your feedback. Will recheck & tweak things and upload a new M5.3.20 later today.

Reincke · Post by **Reincke** » Thu Nov 28, 2013 11:12 am

Hi,
this morning I got strange effects with the new version 5.3.19:
After editing some meta parameter mappings I recognized this:
- MuLab no longer accepts any mouse action
- Keyboard shortcuts were still possible (play/stop, save, quit etc.)
- MuLab was disappeared from the task list (alt-tab in Win7), but still remains in Win7's task bar
- After "Quit" mulab.exe remains as process (task manager) and had to be killed

I launched MuLab again, started logging, reproduced the problem and got this log:

Code: Select all

83:24:32:569 Started Logging
83:24:32:569 MS Windows Home Edition
83:24:32:569 MuLab UL 5.3.19 - 32 bit
83:24:32:570 /C:/Applications/MuLab/MuLab.exe
83:25:20:490 BWindow[623]
83:25:20:490 BWindow[623]
83:25:20:490 BWindow[623]
83:25:20:490 BWindow[623]
83:25:20:492 BWindow[623]
83:25:51:170 BWindow[620]
83:25:51:171 BWindow[620]
83:25:51:171 BWindow[620]
83:25:51:171 BWindow[620]
83:25:51:171 BWindow[620]
83:26:08:571 BWindow[623]
83:26:08:571 BWindow[623]
83:26:08:571 BWindow[623]
83:26:08:571 BWindow[623]
83:26:08:571 BWindow[623]
83:26:43:214 BWindow[620]
83:26:43:214 BWindow[620]
83:26:43:214 BWindow[620]
83:26:43:214 BWindow[620]
83:26:43:214 BWindow[620]
83:26:52:987 BWindow[623]
83:26:52:987 BWindow[623]
83:26:52:999 BWindow[623]
83:26:53:007 BWindow[623]
83:26:53:007 BWindow[623]
83:26:53:066 Are you sure to close Stacked Lines and quit? => Quit without Save
83:26:54:731 Gonna shutdown MME engine

Any idea?
JR

Reincke · Post by **Reincke** » Thu Nov 28, 2013 12:41 pm

AndreasD wrote:- To all who use limiters, the Audio Limiter module seems to really limit now!

Didn't it before?

MuTools · Post by **MuTools** » Thu Nov 28, 2013 1:50 pm

Reincke wrote:Hi,
this morning I got strange effects with the new version 5.3.19:
After editing some meta parameter mappings I recognized this:
- MuLab no longer accepts any mouse action

I just tested M5.3.19 on Win7 64 bit and don't see anything wrong with the mouse. Please elaborate on this issue. You don't see a mouse cursor? Doesn't it move? Is this also the case when starting MuLab fresh, choose "New" i.e. not using any VSTs? Maybe there was a modal window open?

I launched MuLab again, started logging, reproduced the problem and got this log:
Code: Select all
83:25:20:490 BWindow[623]
83:25:51:170 BWindow[620][/quote]These 2 log types can be ignored, no problem. I've muted them in the next version to avoid confusion.

Reincke · Post by **Reincke** » Thu Nov 28, 2013 2:52 pm

mutools wrote:You don't see a mouse cursor? Doesn't it move? Is this also the case when starting MuLab fresh, choose "New" i.e. not using any VSTs? Maybe there was a modal window open?

When the prob occurs, I can see the mouse pointer. I can move it as normal. I had two or three windows open (e.g. Mux deep editor). Clicking on any of them doesn't have any effect. The window border remains grey instead of getting blue. There is no (visible) modal window.

I can switch to any other application and us it as normal. Selecting MuLab by win7's task bar activates MuLab's main window (border gets blue). Any keyboard shortcut works (play, save etc.). There are VSTs. I'm working on a netbook with Win7 Starter 32 bit), 1 GB RAM, Atom N450 CPU.

I will test a "virgin" session tomorrow and try to isolate the problem.

These 2 log types can be ignored, no problem. I've muted them in the next version to avoid confusion.

I have to admit I'm confused by any of these log types since I didn't understand most of them.

But that's no problem. Logs are not part of the PA.
JR

MuTools

KVR Audio

MuLab 5.3.25 Released