MuLab 10.0.85
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
So it must have been some odd caching issue somewhere, indeed most probably on server side.
Well, glad it's past.
Well, glad it's past.
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Dunno. I did try refreshing the page, which normally works, but this time it didn't.
Is there any chance of extending the update check with an auto-update feature?
Is there any chance of extending the update check with an auto-update feature?
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
I agree that would be better, of course. But maybe later.
There are more important prios which will keep me busy for quite some time.
Currently implementing multi-plug per file support, which is quite a job.
Then one of the next high prios is to make MuLab Plugin available at least as VST3, but ideally also as CLAP and AU.
There are more important prios which will keep me busy for quite some time.
Currently implementing multi-plug per file support, which is quite a job.
Then one of the next high prios is to make MuLab Plugin available at least as VST3, but ideally also as CLAP and AU.
-
- KVRAF
- 8446 posts since 29 Sep, 2010 from Maui
The HOFA system plugin (demo-able) has 26 plugins in one, if you need a hard test. No clap tho. Anyway, just saying.
The main plugin is labeled as a shell, dunno
if it’s the same thing, probably. Mulab cannot
see them currently at any rate.
*There is also a free version, dunno if that includes the shell.
The main plugin is labeled as a shell, dunno
if it’s the same thing, probably. Mulab cannot
see them currently at any rate.
*There is also a free version, dunno if that includes the shell.
Last edited by pekbro on Fri Sep 05, 2025 9:09 pm, edited 1 time in total.
-
- KVRAF
- 7017 posts since 19 Apr, 2002 from Utah
These both are high priorities on my list as well.MuTools wrote: Fri Sep 05, 2025 8:07 pm I agree that would be better, of course. But maybe later.
There are more important prios which will keep me busy for quite some time.
Currently implementing multi-plug per file support, which is quite a job.
Then one of the next high prios is to make MuLab Plugin available at least as VST3, but ideally also as CLAP and AU.
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
-
- KVRist
- 434 posts since 17 Nov, 2020
Factory preset "Audio Seq One" isn't working as it should
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
Thanks for reporting this.humanboeing wrote: Sat Sep 06, 2025 1:21 pm Factory preset "Audio Seq One" isn't working as it should
Will be fixed in the next update.
-
- KVRist
- 121 posts since 7 Apr, 2008 from germany
Hi,
Did you receive my "LOAD BUG" emails including videos, or did they end up in your spam folder again?
A)
I found a rule for the loading problem (sent video):
1. Select "new project"
2. Now "open recent" and load a project that only contains a "customizable rack." (you can test it with my "Jd-SyComb") ass loading recent. This will NOT actually load a new project or replace the open one, but will add the "customizable rack" to the already open project.
B)
1. "New Project"
2. Open the "Basic Synth."
3. Go to Modular Edit mode.
4. Double-click a cable. Drag the mute window into the workspace, or the parameters window (volume, etc.).
5. Double-click the amp and drag it into the workspace.
6. Select a new project again.
7. All cable connection windows of the previous project remain open. Amp, on the other hand, is closed with the old project.
So: The problem of "windows remaining open" seems to only affect the cable connections.
C)
You can close the MUX plug-in if the default program loader window is open. This window then remains open and can only be closed by reloading or reopening the plug-in.
However, you cannot close the plug-in if you want to open a sound via the MuLab browser.
Is it possible to at least add a checkmark to close the default sound opener window? (By this window, I mean the window that opens when you select "Current Sound" via the drop-down menu.)
reg.
Did you receive my "LOAD BUG" emails including videos, or did they end up in your spam folder again?
A)
I found a rule for the loading problem (sent video):
1. Select "new project"
2. Now "open recent" and load a project that only contains a "customizable rack." (you can test it with my "Jd-SyComb") ass loading recent. This will NOT actually load a new project or replace the open one, but will add the "customizable rack" to the already open project.
B)
1. "New Project"
2. Open the "Basic Synth."
3. Go to Modular Edit mode.
4. Double-click a cable. Drag the mute window into the workspace, or the parameters window (volume, etc.).
5. Double-click the amp and drag it into the workspace.
6. Select a new project again.
7. All cable connection windows of the previous project remain open. Amp, on the other hand, is closed with the old project.
So: The problem of "windows remaining open" seems to only affect the cable connections.
C)
You can close the MUX plug-in if the default program loader window is open. This window then remains open and can only be closed by reloading or reopening the plug-in.
However, you cannot close the plug-in if you want to open a sound via the MuLab browser.
Is it possible to at least add a checkmark to close the default sound opener window? (By this window, I mean the window that opens when you select "Current Sound" via the drop-down menu.)
reg.
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
Yes i received your emails, thanks.
Will follow up one of the days.
Currently full focus on the last steps in developing support for multiple plugs per file.
Will follow up one of the days.
Currently full focus on the last steps in developing support for multiple plugs per file.
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
Taken note, will be fixed in the next update.jd88 wrote: Sat Sep 13, 2025 9:10 pm "Copy Looks" don't copy / paste the setting of "Slim Title Bar".
-
- KVRist
- 121 posts since 7 Apr, 2008 from germany
... and Framecolor will not be copied too ...
And maybe it will be very helpfull if all parameters from curves (example modulation-cable edit window) will be copied at once. Not only the first parameter. (Or I'm missing something?)
often you need same curves for same kind of parameter.
-
- KVRAF
- 5572 posts since 30 May, 2006 from Hollow Earth
Hi Jo, I have a question:
In Reaper, when I use FL Studio-VST, FL Piano-roll has a command “Copy to MIDI clipboard”.
So I can copy the MIDI notes to that “clipboard” and then paste them in Reaper as a MIDI Item.
So far, I tried several DAWs and no one can do this but Reaper.
Is this something that could be implemented in MuLab in the future?
In Reaper, when I use FL Studio-VST, FL Piano-roll has a command “Copy to MIDI clipboard”.
So I can copy the MIDI notes to that “clipboard” and then paste them in Reaper as a MIDI Item.
So far, I tried several DAWs and no one can do this but Reaper.
Is this something that could be implemented in MuLab in the future?
ABEFLGMOPPRRST 