MuLab 9.3.18 - VST3 plugin support

[ortseam]

Please elaborate, also with a concrete example. Thx.

Thank you for your attention to my question.

The problem appeared to be more special and slightly less critical then I thought it to be firstly.

There are two issues in fact (not related maybe):

- The first one is present with some vst3 plugins only. As an example let's take Fircomp_2 by Jon V Audio (you can get it here https://drive.google.com/file/d/1n-8K5M ... sp=sharing, it's potable and licensed to me, the only thing you need to make it work is to copy vst3 file to your drive).
This plugin has 0 spl latency with 'lookahead' mode OFF, and 64 spl latency with 'lookahead' mode ON.
When you change the mode in Fircomp_2, the change of plugin's latency isn't seen by Mulab until you switch Mulab's 'process' button OFF and then back ON.
With Reaper this plug works nice and PDC changes immediately after you change the 'lookahead' mode state.
Some other freeware examples showing the same thing:
PTEq-X by Ignite Amps
Molotok, Nova, Slick EQ by Tokyo Dawn Records*

- The second one. Mulab ignores manual plugin latency setting for VST3-s (I've tested this issue with ~10 different VST3-s from different manufacturers with the same result).
Here is Mulab project with Fircomp_2 plugin inserted and 1234 spl latency manually set for it. https://drive.google.com/file/d/1n7S8XL ... drive_link
This setting has no affect.

I'm on Windows10, my DAW is Reaper v7.02. If you need some more information on my system and DAW please let me know.

Thank you.

*UPD: with VST3-s from TDR latency parameter doesn't change to correct value even after "reloading" Mulab's 'process' button.

[MuTools]

Please do this:

* Repeat the issue
* Goto MuLab menu -> Tools -> Keep Log
* Goto your MuLab/User/LogFiles folder and email the most recent log to

[ortseam]

Please do this:

* Repeat the issue
* Goto MuLab menu -> Tools -> Keep Log
* Goto your MuLab/User/LogFiles folder and email the most recent log to

done

thank you

[RichardSemper]

A couple of issues related to plugin patch handling in mulab

1. Issue with the free VST3 synth GR-8 in mulab 9.3.18:

GR-8 synth patches are not loading and playing correctly. basically a new instance plays the default patch correctly, subsequently loading a different patch, the synth's display shows the parameters of that patch accurately, but the sound is wrong. Save the project file and reload, and that instance will show the actual parameters of this wrong sound. It's a bit odd, and seems hard to predict what you will get.
The synth's patch loading system works as expected in Bitwig Studio.
This is the only synth I have found which does this in mulab.

Project file link below which demonstrates, with comments added as explanation for each track.
https://drive.google.com/file/d/19k1TE3 ... sp=sharing

Link to GR-8 synth download page:
https://phuturetone.com/

2. Minor issue relating to CLAP version of Octasine in mulab - reports an error when using the synths patch dialog. Attached: Error logs from mulab and Octasine to show this. Does not happen with VST version.
Note that this has no noticeable effect in the synths operation.

3. FR: Is it possible to have patch saving/loading function for CLAP and VST3 (like there is for Vst2)?

[RichardSemper]

Spotted a few things testing Mulab Plugin:

1. on first loading a preset in mulab plugin the on-screen keyboard makes no sound. After mux Modular area has been opened it will play. (Bitwig/Cubase/Reaper tested)

2. Mux Front Panel - Rack module: when first added has transparency property set - causes visual overlay glitch when moving the component - corrects when background colour changed or if panel closed and re-opened. This also has similar problem in mulab DAW though not quite the same effect.

3. Parameter automation recording not working in Bitwig Studio. Plays back drawn automation. Works fine in other DAWs tested. Other VSTs record automation working fine in Bitwig.
Tested using default patch, automating exposed parameter 'filter depth'.

[ortseam]

Spotted a few things testing Mulab Plugin:
2. Mux Front Panel - Rack module: when first added has transparency property set - causes visual overlay glitch when moving the component - corrects when background colour changed or if panel closed and re-opened. This also has similar problem in mulab DAW though not quite the same effect.

+1
I'm having the same experience with Rack module in Mulab plugin under Reaper.

[MuTools]

Please do this:

* Repeat the issue
* Goto MuLab menu -> Tools -> Keep Log
* Goto your MuLab/User/LogFiles folder and email the most recent log to

done
thank you

Well received, thx.

From what i see in the log i have the impression that specific vst3 plugin is notifying the host (MuLab) about the latency change from a non user thread. That's invalid and probably the reason why the latency change is not detected. Please contact the plug dev about this issue.

[ortseam]

From what i see in the log i have the impression that specific vst3 plugin is notifying the host (MuLab) about the latency change from a non user thread. That's invalid and probably the reason why the latency change is not detected. Please contact the plug dev about this issue.

Thank you

Yes, certainly it depends on the plugin loaded, since the issue is not common for all plugins. On the other hand, with other (sub)hosts like Reaper or Excite Audio KSHMR Chain everything works fine. That seems a bit strange for me.
Could you please explore one more log with the same actions done to another plugin from more popular dev TDR? If so, I'll e-mail it to you.

And the question with manual latency settings also remains. MuLab ignores these settings for any VST3 plugun I've tested (two tries of setting this parameter should be seen in the log I've sent to you).

[MuTools]

Yes, certainly it depends on the plugin loaded, since the issue is not common for all plugins. On the other hand, with other (sub)hosts like Reaper or Excite Audio KSHMR Chain everything works fine. That seems a bit strange for me.

The typical "implementation jitter" on a SDK API.
The VST3 SDK clearly states that latency changes has to be reported via the main user thread.
Please forward this to the plug dev.

And the question with manual latency settings also remains. MuLab ignores these settings for any VST3 plugun I've tested (two tries of setting this parameter should be seen in the log I've sent to you).

You're right, that's a bug in MuLab. Also for CLAP plugins. Will be fixed in the next update. Thx for reporting this.

[ortseam]

The typical "implementation jitter" on a SDK API.
The VST3 SDK clearly states that latency changes has to be reported via the main user thread.
Please forward this to the plug dev.

ok, thanks

You're right, that's a bug in MuLab. Also for CLAP plugins. Will be fixed in the next updated. Thx for reporting this.

thanks once again
have a nice day!

[FSM77]

I've recently jumped into the vst3 universe and I can report that all except one of my purchased instruments/effects works perfectly.

The Sonic Projects OPX-II Pro is the one that doesn't work. It freezes as soon as I start using it.

Should I contact Sonic Projects about this?

Does anyone else here use this product as a VST3?

[heks]

Sonic Projects OP-X-POR-II vst3 seems to be working fine here. It does seem to be installed "unconventionally " as the vst3 is in "Contents" folder not "Plugins" folder.

[MuTools]

Issue with the free VST3 synth GR-8 in mulab 9.3.18:

I've forwarded the issue to Sasha of PhutureTone.

Minor issue relating to CLAP version of Octasine in mulab - reports an error when using the synths patch dialog. Attached: Error logs from mulab and Octasine to show this. Does not happen with VST version.

Fixed in the next update.

[MuTools]

1. on first loading a preset in mulab plugin the on-screen keyboard makes no sound. After mux Modular area has been opened it will play. (Bitwig/Cubase/Reaper tested)

I can't repeat this. Please elaborate, maybe with a screen video.

Mux Front Panel - Rack module: when first added has transparency property set - causes visual overlay glitch when moving the component - corrects when background colour changed or if panel closed and re-opened. This also has similar problem in mulab DAW though not quite the same effect.

Fixed in the next update.

[Odd Fella]

Just a question: Why was the rendering stuff moved into the Settings menu (judging from the gearwheel symbol, which is commonly used for settings)? Rendering/Exporting had always been in the Project menu up until version 9.