MuLab 10.0.85
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
OK, so the manual is the best place to go to read what's available. That, and download it and look in the supplied library and on MuLib for user contributions.
-
- KVRAF
- 7018 posts since 19 Apr, 2002 from Utah
Thanks! 
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.)
-
- KVRAF
- 8445 posts since 29 Sep, 2010 from Maui
Hmm, seem to be having a fair amount of trouble with MuLab and OpenGL, slow performance, crashes etc. My system is not the greatest, but MuLab seems to have the most trouble of any DAW.
Just sayin that there may be room for optimization still...
Just sayin that there may be room for optimization still...
-
- KVRAF
- 5377 posts since 25 Jan, 2014 from The End of The World as We Knowit
Better to upgrade your old system than deal with an old API from the 1990s like OpenGL.pekbro wrote: Mon May 12, 2025 12:21 am Hmm, seem to be having a fair amount of trouble with MuLab and OpenGL. My system is not the greatest
F E E D
Y O U R
F L O W
Y O U R
F L O W
-
- KVRAF
- 8445 posts since 29 Sep, 2010 from Maui
My system is not that old tbh, it's just not top of the line, i5 with integrated graphics. It's quite
capable surprisingly. It's also temporary if you must know.
Unfortunately, not all plugins give you the option to disable opengl.
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
MuLab, or any host DAW, only gives a child window to a plugin so a plugin can use that child window to show its editor. What a plugin does with its editor window is fully up to that plugin.
MuLab, or any host DAW, has nothing to do with the possible use of OpenGL inside a plugin window.
So i don't know which optimization you refer to.
MuLab, or any host DAW, has nothing to do with the possible use of OpenGL inside a plugin window.
So i don't know which optimization you refer to.
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Possible bug?
I have been working on some older projects and have found several times that no sound comes through. The cause seems to be random plugins. First it was u-he's Uhbik v2 beta VST2.4, so assumed it was those. But since then, I have had a Mux preset do it and now W1 Limiter VST3 v3 do the same. It's easily rectified, but it means I have to save the settings as a preset file before deleting and re-adding the plugin/preset.
I can disable the plugin and the sound then is ok, but enabling it seems to mute it. I haven't set any Mute/Solo either it's literally when the plugin is enabled that it mutes the sound on that Rack.
Yes the same settings are applied to the plugin, but I have no idea the actual cause. Is it a bug, or have I done something to cause it? Anyone have any thoughts on this?
Thanks.
EDIT: I backed up the project folder ready to send, then I thought I'd extract it and re-open it to reduce it down to that one track for easier emailing due to size. But it now works??? I've already corrected the original so that issue is no longer there. Next time it happens, I'll send it to you straight away.
EDIT: I went to another project and it's happened again. Seems to happen to previously saved projects that were ok? Here's a short gif of the issue in action:
Here you can see nothing is muted or soloed and all I am doing is enabling the instance of W1 Limiter VST3 plugin. This isn't tied to this one plugin though. As I said, it happens to MuX presets too and VST2 plugins.
Again, after restarting MuLab, the problem has gone.
I have been working on some older projects and have found several times that no sound comes through. The cause seems to be random plugins. First it was u-he's Uhbik v2 beta VST2.4, so assumed it was those. But since then, I have had a Mux preset do it and now W1 Limiter VST3 v3 do the same. It's easily rectified, but it means I have to save the settings as a preset file before deleting and re-adding the plugin/preset.
I can disable the plugin and the sound then is ok, but enabling it seems to mute it. I haven't set any Mute/Solo either it's literally when the plugin is enabled that it mutes the sound on that Rack.
Yes the same settings are applied to the plugin, but I have no idea the actual cause. Is it a bug, or have I done something to cause it? Anyone have any thoughts on this?
Thanks.
EDIT: I backed up the project folder ready to send, then I thought I'd extract it and re-open it to reduce it down to that one track for easier emailing due to size. But it now works??? I've already corrected the original so that issue is no longer there. Next time it happens, I'll send it to you straight away.
EDIT: I went to another project and it's happened again. Seems to happen to previously saved projects that were ok? Here's a short gif of the issue in action:
Here you can see nothing is muted or soloed and all I am doing is enabling the instance of W1 Limiter VST3 plugin. This isn't tied to this one plugin though. As I said, it happens to MuX presets too and VST2 plugins.
Again, after restarting MuLab, the problem has gone.
Last edited by sl23 on Sun Jun 01, 2025 3:46 pm, edited 1 time in total.
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I have another project that doesn't lose this mute issue when reloaded. Everytime I load the project it has MuX preset muting the track when it is enabled. Disabling the MuX preset unmutes the rack.
EDIT: Scrap that, it's gone again!
EDIT: Scrap that, it's gone again!
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Racks: Dragging and accidental dropping is moving the item in the rack slot to a new rack, is this intentional?
When reorganising within the same rack, I accidentally dropped the plugin between slots, which creates a new rack with that plugin. But I think it better in this instance that a plugin should simply return to it's original position in the same rack if accidentally dropped between slots.
When reorganising within the same rack, I accidentally dropped the plugin between slots, which creates a new rack with that plugin. But I think it better in this instance that a plugin should simply return to it's original position in the same rack if accidentally dropped between slots.
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
Yeah, that certainly looks odd -- it's not like the new rack's connected to the original rack or anything.
-
- KVRist
- 434 posts since 17 Nov, 2020
There is an issue with stereo width handling within mixer strip module. Insert an oscillator module into a rack slot and start adjusting the stereo width knob. Not only it stutters, the output volume is changed too, which I think shouldn't be the case. A really strange behaviour that I don't remember being present in M9. Also, when the master rack's width is set to 0, then adjusting the stereo panning knob on the sound source rack is stuttery too, when the value is changed off-center.
-
- KVRist
- 434 posts since 17 Nov, 2020
Improvement idea: when you drag a module inside a rack slot into another already occupied slot, swap the modules instead of replacing it as it currently is. It also makes more sense (at least for me ;p) if you want to get rid of a module, you just delete it; swapping modules indicates rearrangement.
-
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
Tricky... If I drag something from the browser on top of an occupied rack slot, I mean replace. If I drag it in from the modular area into an occupied rack slot, I mean replace. I'd say dragging and dropping onto the slot itself should always replace. But the rack area above and below should be "clever": for drops from modules occupying slots in the same rack, move the source rack slot to the drop zone; for drops from outside the rack, create a new rack slot. It means you need to leave a drop zone between your slots, if you're customising, of course.