MuLab 10.0.85

[MuTools]

MuLab App 9.6.0 beta for Windows 64 bit is available on

https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• VST3 Plugins: New "Open VST3 Preset" and "Save VST3 Preset" functions.
  Available via the buttons in the VST3 editor top control section, as well as via the context menu.
• VST2 Plugins: New "Upgrade To VST3..." function which can be used to migrate a VST2 plugin to its VST3 version.
  This function can be used via a VST2 plugin's context menu (recommended), and is also a rescue option when opening projects/presets with unfound VST2 plugins (not recommended).
  When migrating a VST2 to VST3 MuLab copies the plugin data so to preserve the sound, but it depends on the plugin whether that succeeds.
  MuLab also copies the MIDI Controller Map and Note Key Names, though parameters IDs are not (yet) remapped and need manual updating.
  As some VST2 to VST3 matching is based on vendor + product name, and as this info was not yet cached in the plugin database, a full rescan of the plugin database will increase the chance on automatic VST2 to VST3 matching. If an automic match is not found, you can choose the proper VST3 from the VST3 plugin popup list.
• Enhanced VST3 plugin engine with better protection against buggy plugins.
• Fixed a little mismatch when saving VST2 presets.
• When a plugin editor got keyboard focus and then using MuLab shortcuts that would delete the plugin (eg. Open or Revert Project, Quit, ...) this could lead to a crash. Fixed.
• Multi-Form Oscillator: Vector Waveforms now use a single vector waveform instead of a start-end vector waveform.
  To morph a vector waveform from A to B, like in M9.5, simply use 2 vector waveforms after eachother.
  This new method is more intuitive and more flexible.
• Copy-pasting the MIDI Channel Remapper did not always preserve the map. Fixed.
• In some specific cases dragging a recorder module to the + track button could cause a crash. Fixed.
• FLAC audio export bug fix.
• Other small improvements.

[Jonathan Shepherd]

Good work man, thanks-

[TorresBob88]

I couldn't load my current project from the last MuLab version, even after upgrading everything. So I finally narrowed it down to a few things, but specifically 2rule synth3 vst3.

So I guess this is the new badly coded VST3 protection.
After removing that from the project, I got it to load.

But the issue is that while trying to isolate this, the new 9.6 MuLab will tell me that it cant load 2Rule synth 3, MOST of the time. And then sometimes it WILL load it. And if you save the project with it loaded, you wont be able to reload the project. So it might create an issue, if it loads something once, and then doesn't want to load it again after you save it.

Edit, the problem is actually repeating when I try to swap any VST3 into the track where 2 rule synth was. It doesn't seem to be just 2 rule synth.

Also scanning my VST folder does not give any errors regarding any of these VST's.
They appear to scan succesfully. I'll continue to test further.

Edit, I seem to be getting the same error, with a fresh install of 9.6, over a fresh download of 9.5.34. A project will not reload, after loading a VST3 successfully, and saving a project. With one VST3 and nothing else. Maybe I have to reinstall my operating system. Codecs or something? I have to safely assume that you would have tested for such a behavior.

[MuTools]

You're right, there is a bug in M9.6.0.
Due to a last minute change i forgot to doublecheck.
The M9.6.0 download has been removed.
Projects/presets saved with M9.6.0 will load fine in M9.6.1, which will be available asap.

[MuTools]

That load bug has been fixed in M9.6.1 beta which is available on
https://www.mutools.com/mulab/app/lates ... /beta.html

Sorry for the mistake. Thx for reporting it! Goodnight.

[TorresBob88]

No problem. I'm just glad to see that you are still mastering this product.
Whether the problem was on my end or your end, this is the kind of product that is worth figuring it out and keeps getting greater.

[MuTools]

Thanks

[MuTools]

MuLab App M9.6.2 beta for Windows 64 bit is available on https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Due to the M9.6 safety patch wrt using key shortcuts inside plugin editors, pressing the composer start/stop shortcut key (by default the spacebar) or other composer shortcut keys inside a plugin editor did not work anymore. Fixed.
• Composer has extra shortcut option "Toggle Event Recording Grid Active" so to quickly switch recording grid on or off.
• Enhanced support for Windows trackpads: Scrolling using gestures did not always work correctly. Fixed.

[StanislavDudik]

Mutools 32 bit had issues with a lot of 32 bit vst plugins when i tried it

[pljones]

Mutools 32 bit had issues with a lot of 32 bit vst plugins when i tried it

I think you have the wrong thread.

[MuTools]

MuLab App M9.6.3 alpha for Windows 64 bit is available on https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Enhanced Undo-Redo:
  • Many more actions that insert/drag-drop/move/copy/paste modules around between racks, module slots and modular ares are undoable actions now.
    This not only has the advantage of being undoable, it also avoids several "Are you sure? (No undo)" popup questions, which obviously enhances the musical workflow.
    This enhancement was also necessary for the integrity of the whole undo-redo system because upon specific combinations of module related actions, using undo/redo could cause a crash.
  • Add new rack now is undoable.
  • Drop parameter as new automation track now is undoable.
  • Drop module/plugin on the [+] track button now is undoable.
  • Optimized undo-redo for drawing new envelope points.
  • Module->Replace and VST2->Migrate To VST3 are both undoable functions now.
  • Modular Area + MuDrum Pad Set: Drawing new connection now is undoable.
  • Drag-drop a parameter on an automation clip to set the target parameter now is undoable.
  • Choosing another audio/event output for a rack desk rack now is undoable.
    And if you would have edited that rack output connection properties (eg. audio gain, pan, ...) in the modular area, now those connection properties are also preserved.
  • New preferences to define the depth of the Undo/Redo history: Max Num Undo/Redo Steps and Max Num Undo/Redo Bytes.
    And the defaults for these preferences have been more than doubled compared to M9.5.
• VST3 plugins: Extra context function "Try Import VST2 Preset" which tries to import an FXB/FXP file into the VST3 plugin.
  Only use this for VST2 presets that correspond to the VST3 plugin. And even then it depends on the VST3 plugin developer whether this works or not.
  It can also be that the VST3 plugin supports importing FXB but not FXP.
• Right-click project name display now has the option Show In File Explorer / Finder.
• When editing audio cable properties (doubleclick cable -> tweak gain/pan), this could result in a small memory leak. Fixed.
• When GUI Scale was not 100% then the launch dialog size wasn't right. Fixed.
• Dropping a MUX preset on the [+] Rack button did not yet set the default width for that new rack. Fixed.
  FYI: Default rack width = Average of existing widths; If no racks yet it's the "Default Rack Width" preference.
• In rather exceptional cases, there could be a crash which originates in the bezier curve sub-system due to IEEE754 float 64 bit calculation limits. Fixed.

It's called an alpha version because it needs more testing.
If you have a bit of spare time and want to help testing please have a jam with MuLab 9.6.3 and use undo-redo often enough and see if everything works smooth and solid, and post your experience here. Thx!

[Jonathan Shepherd]

Nice, I'll check it this weekend. I appreciate how you tackle changes/improvements from different angles, thinking it out through and through, in this case undo and redo.

[Scrubbing Monkeys]

No problem. I'm just glad to see that you are still mastering this product.
Whether the problem was on my end or your end, this is the kind of product that is worth figuring it out and keeps getting greater.

Yes...yes...yes....thank you

[RichardSemper]

Been giving it a try. Some initial observations:-

1. The unexpected -
Add New Track is not undoable. Delete new track is.
Drop presets from browser to add track + is not undoable.
Drop Midi files is not undoable.

Drop Muclips onto a track is undoable, however, if 'update target module' is selected a new rack is created and the track reassigned to it. When the action is undone the new rack remains and the track is not rerouted back to the original rack.

Drop presets (from factory library) from browser to replace instrument in slot 1 of a rack is not undoable, but using the context menu 'replace' for the same purpose is undoable.

Drop sample from browser to new track - undo removes the sample but not the track.
Drop sample to pitched sample (sample player) undo removes the clip but leaves the sample player with the sample still loaded.
Drop sample to sliced sample clip - undo removes the clip and samples but leave the sample player intact.

2. Other actions not undoable: (not unexpected)
mute/unmute tracks, edit VST2 VST3 CLAP parameters, replacing samples in sample player or multisample player.

3. Suggestion: When an action is not undoable, undo will naturally apply to the previously recorded undo, thus it is really useful to use the menu rather than keyboard shortcut, to help keep track of what the undo action is. It would be even more useful to offer the undo history in a list form, and be able to select a point in the undo history to return to from the list.

So far I have experienced no crashes or problems while mucking about with this. I hope the above is useful.

[pekbro]

Since many of us are on the lifetime plan, maybe Jo could have a priority support avenue, where we could pay a nominal fee for him to make time and investigate non-critical support issues like plugin compatibility.

E.g. a specific plugin could be investigated and either fixed if possible or the user would be provided some technical assistance with communicating the issue to the plugin vendor. Not many plugin manufacturers list MuLab as being officially supported, so they are not going to go out of their way to look into it ime.

Jo would likely have to install and investigate demos so this would take some time out of whatever he happens to be working on, hence a response fee is not unreasonable.
I also think many issues would turn out to be small and addressable in a lot of cases.

Anyway, just an idea that might be worth some extra income for Jo and help for those having issues with plugins they need. With the lifetime licenses, there are few options for us to support Jo beyond spreading the word. A thread could be maintained to track compatibility status and whatnot.  

*On another note the beta seems to be deleting plugins from channels on it's own.
Possibly when changing out a plugin, extras are deleted, even from other tracks.
For me anyway...