MuLab 10.0.85

[RichardSemper]

M9.6.5: A couple of new observations:
1.1 Adding a module in the mux modular area cannot undo, but deleting it can.
1.2 Drawing a new connection can be undone, but not moving it's source or destination. Redo then puts it back to original source and destination, taking no account of any intermediate routing changes.

2.1 Move Track not undoable
2.2 Undo add track/automation sub track etc. If a track has been moved to a sub track since created, the undo add track does nothing, further redo puts it where originally created. Same with moving a sub track out to track level.

[pekbro]

Hmm, latest beta refused to load a project created with it for some reason.

"0x00000924 02:34:40:372 MpuStp[1857] couldn't load plug Vst3
0x00000924 02:34:40:372 MpuStp[1857] couldn't load plug rack
0x00000924 02:34:40:373 MpuStp[1857] couldn't load plug CmpU"

[MuTools]

That's odd.
I doublechecked saving & reloading a project with a VST3, works ok here with M9.6.5.
Please email me the complete log file.
If possible also email me the project file, zipped.
And add as much info as possible, also a step-by-step if you find one.

[pekbro]

That's odd.
I doublechecked saving & reloading a project with a VST3, works ok here with M9.6.5.
Please email me the complete log file.
If possible also email me the project file, zipped.
And add as much info as possible, also a step-by-step if you find one.

log sent

[MuTools]

Replied. Looks like a plugin issue to me. Lets continue the talk about this via email.

[MuTools]

M9.6.5: A couple of new observations:
...

Thanks Richard!

[MuTools]

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

What's changed:

• Add new module in modular area now is undoable.
• Reconnecting a modular cable now is undoable.
• Moving tracks now is undoable.
• Deleting samples now is undoable.
• Stepping thru samples, eg in MuSampla or for sample events, now is undoable.
• Sample players: When switching to another sample, the undo that, the sample display range was not matching the restored sample. Fixed.
• Deleting multi-samples now is undoable.
• Drop Rack preset on rack desk now is undoable.
• When a rack slot module editor is shown, then deleting the rack closes that editor, but undo + reopen editor + redo didn't close that editor. Fixed.

[MuTools]

2a. New Issue - File browser-Samples-This Project: 'Delete unused' no longer works for multi-sample preset samples after preset removed: Deleted all tracks and nothing on the timeline, but all samples previously loaded remain in the browser. Also survives save and reload. So every sample loaded in multi-samples during the session is added to the project file and not removed either by removing the instance or through undo.

2b. Using the 'delete unused' option as above also removes all undo history.

I can't repeat these 2 ones.

I tested this:

* New project
* Add new rack and insert Classic Piano
* Rightclick the piano multi-sample -> Delete
* Browser -> Samples + This Project
* Browser options -> Delete Unused

The piano samples are properly deleted from the project.

Note that this indeed clears the undo-redo history as Delete Unused is also intended to clear RAM and so it should be about a real delete, not an undoable delete. Maybe an alert should be shown?

Can you still repeat the issue on your side?
Do you have a step by step?

[RichardSemper]

I tested this:

* New project
* Add new rack and insert Classic Piano
* Rightclick the piano multi-sample -> Delete
* Browser -> Samples + This Project
* Browser options -> Delete Unused

The piano samples are properly deleted from the project.

Following your steps above the samples are indeed properly deleted. However:

* New project
* Add new rack and insert Classic Piano
* UNDO, or Delete the Classic Piano module (rather than the multi-sample itself) or delete the rack
* Browser -> Samples + This Project
* Browser options -> Delete Unused

Result - the samples remain in the project browser 'This Project' as I described.

I see now what I was missing - to clear the samples left behind after the Undo I need to first remove the relevant multi-sample in the project browser. I always seem to forget that.

Re: Delete Unused clears Undo history - Perhaps rather than an alert, add warning to the menu text e.g. "Delete Unused (Clears Undo)" but I don't think it is critical.

[kmonkey]

Applied the latest beta. Saving the VST3 preset works however loading them does not. Am I doing something wrong?

Example: load VST3 effect. Save VST3 preset. Go to Mulab browser and find that preset wherever you saved it.

Drag and drop to the rack slot (where you usually can drag and drop effects) and I get the message:

"Could not recognize PLUGINNAME.vstpreset as a DLL" message and nothing happens.

It appears as if I can not drag and drop VST3 presets to load specific plugin and their settings. And MuLab tries to search for a DLL even though VST3 plugins have different extensions?

I just tried Cubase, Reason 12, Reaper - all three literally can do that for the Syntsh and FX plugins. You save VST3 presets and they even can be shared among DAWs based on that VST3 preset. Save in one DAW VST3 preset and specific plugin types and values, load into other DAW - can be loaded perfectly from their browsers.

Hence my question, am I doing something wrong, or at this point, this is not possible?

I am aware that I can open the top bar (where I save VST3 presets) and there is an option "Open VST3 preset" that works but it is workflow pissing to load the plugin, open the top bar, open a specific menu item and point to the folder which contains preset when you actually work with browser from which you should be able to drag and drop.

[TorresBob88]

I'm getting an error in sample player,
when I have a sample in, and then attempt to select "none" in the slot menu to make it empty,
I get a big red "A serious error has occurred" and shutdown.

Should be easy to check?
I get the same thing with an empty project and no Vst's

[RichardSemper]

I'm getting an error in sample player,
when I have a sample in, and then attempt to select "none" in the slot menu to make it empty,
I get a big red "A serious error has occurred" and shutdown.

Should be easy to check?
I get the same thing with an empty project and no Vst's

Confirmed - same here.
This does not happen in M9.5

[MuTools]

Thanks for reporting that!
Will be fixed in the next M9.6.7, which is almost ready.

[MuTools]

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

What's changed:

• Project browser -> Delete unuseds now pops up a question "Delete N unuseds? (No undo)".
• Project browser -> Delete unused samples: Now also asks to first delete unused multi-samples, if any.
• Sample players: Selecting "None" caused a crash. Fixed.
• When using the undo-redo system, there could be memory leaks. Fixed.
• When drawing a new clip, the clip type selector dialog was not taking scaling into account. Fixed.
• When dropping an audio file on the composer, the audio method selector dialog was not taking scaling into account. Fixed.
• Another step forward in vectorizing the whole GUI.
• Other small improvements.

[RichardSemper]

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

What's changed:

• Project browser -> Delete unuseds now pops up a question "Delete N unuseds? (No undo)".
• Project browser -> Delete unused samples: Now also asks to first delete unused multi-samples, if any.

This solution works great!