M8.5.4

Official support for: mutools.com
RELATED
PRODUCTS

Post

32-Bit here too ...
         _/_/       _/_/_/
    _/_/_/_/_/_/_/
FEMALE VOICE MuX demo :phones: more by SUNFLOWER LAP ORCHESTRA

Post

M8.5.2 is available in http://www.mutools.com/mulab/beta/

This update contains several bug fixes.
Now also the Windows 32 bit beta version is available.

How to update:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

Post

Also MUX Modular Plugin 8.5.2 beta is available in http://www.mutools.com/mux/beta/

How to update:
Windows: Replace the current MUX DLL and ID files by the new versions. (4 files in total)
MacOS: Replace the MUX .VST file by the new version (assumes you already have installed the complete MUX 8 zip)

Post

On my new pc, only using mulab in 64 bit but also have mux that I use both 32 bit and 64 bit. The 32 bit mux is only until audiomulch gets updated to 64 bit after that it's byebye. Got a macbook too but it's all 64 bit.

Anyway thanks for the update, really digging the new filter options in musynth, sampler,ect.
Stuck in Aperture Laboratories for a 2nd time!

Post

Oh yes
> The MuEcho and MuVerb devices now are fully editable MUX patches.
Does this mean that MuVerb as a separate VST is no more, as of 8.5? (Not that it's been updated lately - I'm just assuming it's not going to get upgraded to 8.5?)

Post

MuVerb VST still is available in its last version. No short term plans to change that.

Post

MuLab 8.5.3 is available in http://www.mutools.com/mulab/beta/
MUX Plugin 8.5.3 is available in http://www.mutools.com/mux/beta/

What's changed:
  • The Initial Event Generator module now also supports a note length.
  • Fixed a load-save bug regarding certain front panel sizes.
How to update MuLab:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

How to update MUX Plug-in:
Windows: Replace the current MUX DLL and ID files by the new versions. (4 files in total)
MacOS: Replace the MUX .VST file by the new version (assumes you already have installed the complete MUX 8 zip)

Post

Using the Initial Event Generator module in Cubase 10.5.12 gives me an unhandled exception in Cubase when I try to change the length parameter for the Note event. It does it too if I select another event type an then try to select the note event again. The arrows of the note length selection keep staying on the GUI of Initial Event Generator.

BTW: 8.5.2 didn't have this issue.

Stay healthy!

Post

Confirmed bug. Thx for reporting this! Will be fixed soon.

Post

MuLab 8.5.4 is available in http://www.mutools.com/mulab/beta/
MUX Plugin 8.5.4 is available in http://www.mutools.com/mux/beta/

This update fixes a potential crash bug in the Initial Event Generator editor.

How to update MuLab:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

How to update MUX Plug-in:
Windows: Replace the current MUX DLL and ID files by the new versions. (4 files in total)
MacOS: Replace the MUX .VST file by the new version (assumes you already have installed the complete MUX 8 zip)

Post

Great! Try it asap.

Post

Well. Now no crash, but obviously it does not work as I expected, Probably I misunderstand its function. I tried to use it as trigger for the step sequence of mux or an arpeggiator (HY-MPS or kirnu cream) as trigger or long note. But those animals don't run.

Post

The Initial Event Generator is practical for MUX patches that need a very first (note) event in order to work as expected, eg. to trigger a looped envelope.

The defined event is sent out whenever this module (re)starts processing:
  • When it is inserted into a MUX patch
  • When it is loaded from a preset file
  • When its process switch (the green on/off led) is switched back on

Post

If it triggers when it's inserted into a MUX patch, it won't be connected to anything. Can that be replaced by "when it's connected to another module"? (Yes, the third point provides a workaround but this would make its usage more obvious.)

Post

Indeed the first case may be rather useless but i've listed it for completeness. Thanks for your suggestion but even when you connect it to another module your modular patch may not yet be ready. So i suggest you simply toggle the Initial Event Generator's process switch when your modular patch is ready so you can test the complete MUX patch. Then whenever that MUX patch is loaded, the initial event will be sent out.

Post Reply

Return to “MuTools”