MuLab 10.2.29 beta

[MuTools]

Some plugins output a very low level signal to avoid denormalised floats.
Just as a test, try increasing the threshold to eg. -90 dB.
Does that make a difference?

Also note that the process LED dimming is very subtle.

[MuTools]

"Fixed a serious timing issue on the output events coming from a VST3 plugin." <-
BUT: in the actual version 10.2.17 (MAC) it isn'nt fixed. (Tested with STEPIC-VST from Devicemeister). The same bug like I wrote you a long time ago. (delayed Midi-Output while MuLab is in recordmode)

Then it must be about a different issue.
I'll try to find the time to check it.

[Grizzellda]

Hey, MuTools, just keep up the thankless work, will ya?

Super Sonic!!

[RichardSemper]

It seems that from Mulab 10.2.17 onwards mulab is less tolerant of older files. I cannot load anything saved before about April 2022. Loading and resaving these files in mulab 10.2.16 or earlier seems to fix this. These are files which I had previously upgraded using mulab 8.
This is the mesage I am getting:

Clipboard 3.jpg

Clipboard 2.jpg

[mgiambro]

Some plugins output a very low level signal to avoid denormalised floats.
Just as a test, try increasing the threshold to eg. -90 dB.
Does that make a difference?

Also note that the process LED dimming is very subtle.

Thanks. That has worked. Also, it was an older project I was having the issue with, started with version 10.1 I think. I had to re-load the plugins for the change to be recognised.

[MuTools]

It seems that from Mulab 10.2.17 onwards mulab is less tolerant of older files. I cannot load anything saved before about April 2022. Loading and resaving these files in mulab 10.2.16 or earlier seems to fix this. These are files which I had previously upgraded using mulab 8.
This is the mesage I am getting:
Clipboard 3.jpgClipboard 2.jpg

Thanks for reporting this Richard!
I indeed have been working on something version related, something future oriented, but so it turns out i missed a legacy case. Will be fixed in the next update.

[MuTools]

Some plugins output a very low level signal to avoid denormalised floats.
Just as a test, try increasing the threshold to eg. -90 dB.
Does that make a difference?

Also note that the process LED dimming is very subtle.

Thanks. That has worked. Also, it was an older project I was having the issue with, started with version 10.1 I think. I had to re-load the plugins for the change to be recognised.

Glad to hear it's resolved.
But i'm a bit confused by your last sentence.
Is that about a change in "Threshold Time" or in "Silent Output Threshold dB" ?
Can you please explain the (unexpected) need for reload in more detail.

[mgiambro]

Some plugins output a very low level signal to avoid denormalised floats.
Just as a test, try increasing the threshold to eg. -90 dB.
Does that make a difference?

Also note that the process LED dimming is very subtle.

Thanks. That has worked. Also, it was an older project I was having the issue with, started with version 10.1 I think. I had to re-load the plugins for the change to be recognised.

Glad to hear it's resolved.
But i'm a bit confused by your last sentence.
Is that about a change in "Threshold Time" or in "Silent Output Threshold dB" ?
Can you please explain the (unexpected) need for reload in more detail.

Sure. Sorry for the lack of detail. So, initially I had an existing project with five tracks/racks with synth plugins - Repro x 2, Zebra, Hive, Diva. The smart bypass was not kicking in at all. I then followed your suggestion of changing the Plugin Silent Output Threshold value to -90dB. The smart bypass still did not happen when the synths were idle. I then tried copying the racks to a brand new project to see if that made a difference. Still didn't work. I then isolated one rack and replaced the synth plugin i.e. reloaded a new instance of the same plugin. The smart bypass then worked. I had to do this for each of the five plugins.

I hope that clarifies it.

[MuTools]

Thx for your reply.

I made a project in MuLan 9.5 using a VST3 and setup its Auto Bypass to 500 ms. Auto Bypass worked as expected.
I then opened that project in MuLab 10.2.18.
The VST3 plugin's Auto Bypass also worked as expected just like in in MuLab 9.
So i'm still confused about what steps i have to take to repeat the case you encountered.
I'm zooming in on this as it is unexpected that you have to reload plugins in order to make the Auto Bypass to work.

[mgiambro]

Thx for your reply.

I made a project in MuLan 9.5 using a VST3 and setup its Auto Bypass to 500 ms. Auto Bypass worked as expected.
I then opened that project in MuLab 10.2.18.
The VST3 plugin's Auto Bypass also worked as expected just like in in MuLab 9.
So i'm still confused about what steps i have to take to repeat the case you encountered.
I'm zooming in on this as it is unexpected that you have to reload plugins in order to make the Auto Bypass to work.

I think it was version 10.1.23 I created the project with. The plugins are all CLAP. I tried creating a new project in 10.2.18 and adding a CLAP plugin rack and it worked fine. I'll keep an eye on it and if I can find consistent steps to reproduce, I'll let you know.

[MuTools]

Alright, thx for the update.

[jd88]

(rant --> google translatet)

Did you add PkgInfo to the Redux folder to fix it? Isn’t that what you want? It’s faster than posting!

Oh, I forgot to mention that I'm aware of this and the plugin has been working for me in MuLab for a long time?

However, in forums and user requests, I keep reading that many other users simply don't know this (just like with other things within MuLab) and wouldn't need to ask/know it if MuLab simply adhered to a few more standards. For example (in this case) , taking the "Info.plist" into account on Macs (increasingly replacing the Pkg file on Macs).

-> PS (simply formulated:): I also like it if there is currently still a pkg, because it is more obvious on MAC-OS that it is a VST. <-

[MuTools]

MuLab does not look for a PkgInfo or Info.plist.
MuLab uses CFBundleCreate with the plugin file path and uses the returned CFBundleRef to continue opening the plugin.
If CFBundleCreate fails because of a missing PkgInfo while info.plist could also identify the folder as a bundle then isn't that an issue in MacOS's CFBundleCreate function?

[jd88]

MuLab does not look for a PkgInfo or Info.plist.
MuLab uses CFBundleCreate with the plugin file path and uses the returned CFBundleRef to continue opening the plugin.
If CFBundleCreate fails because of a missing PkgInfo while info.plist could also identify the folder as a bundle then isn't that an issue in MacOS's CFBundleCreate function?

For simplicity's sake:

When testing within 14 DAWs (MAC-OS), I have actually found another DAW that seems to be a bit sensitive in terms of missing pkginfo.

Before we all puzzle and thus a possibly necessary fix within these DAWs has time:

ReNoise (Eduard) has agreed: With the next "ReNoise Redux" update, this plug will install a pkg.info again.

[Grizzellda]

Zebralette 3, CLAP version does not communicate mouse movements at all...but the VST3 version works.