MuLab 10.1.25

[oldcastle]

Jo, if you ignore your user base for minute, what direction do you want to take Mulab? What are your priorities?

Essentially: Everything that juices sound, everything that inspires sequencing, and everything that catalyzes the chemistry between sound & sequencing.

So i'd love to further grow MuLab's own modular sound engine, both sound-wise as sequencing-wise, and the interesting crossover in between.

All this with a rather minimalistic yet inspiring GUI that leaves a lot of fresh air for the creative brain.

I'm certainly also interested in connecting to interesting technologies like MPE, ARA, though i first need to explore them more before i can say more about that.

Maybe i'll also explore making parts of MuLab available as a separate plugin, if that would be interesting.

Anyway, the very next priorities are:

• Take a kind of holiday break. That's a too long time ago. I'll be making a road trip, but will calmly continue some works on the laptop.
• MuLab Plugin as VST3 / CLAP / ...
• More tutorial videos

You forgot the native Linux version

[sl23]

Roland VST3's are a long-standing issue within MuLab, but the issue seems to be with Roland, not MuLab.

For a while I couldn't even get Roland standalone versions to start up, let alone run inside a DAW... Roland and VST isn't somewhere I'd want to go again.

Yeah it's a shame, I like their sounds, but I have an MC-707 that uses the ZenCore which is great! There are so many emulations that it's probably not worth the hassle or the money buying from Roland anyway.

[syntonica]

As for the redux issue on macOS, it's actually a Redux plugin problem. The Renoise Redux.vst3 directory is missing the binary file `Pkginfo` to be seen as a bundle. I've copied the Pkginfo from the Contents directory of the Waldorf Largo 2 plugin to the Contents directory of the Renoise Redux, and now the Redux can be seen and opened by MuLab. I've seen this problem before, some hosts don't mind, but MuLab does, so try this and it should work as expected.

This might also work for the Roland VSTs, but I don't own'em, so can't try that out.

I'm sooooo tired of this. Some of the Arturia plugins suffer from this and I've reported it. Needless to say, it's never been fixed, or if so, only after several years. And such a stupidly simple fix--just add the file to the build script, duh. Anyway, it's a simple right byte file you can make yourself: "APPL????" if I recall correctly.

[tiger001]

none of us are getting what we want, not everything I mean

I don't think that will ever be possible, or that it's even a good thing.
We are in KVR, a consumer marketplace with social media that encourages posts which follow economic delusions of more demand, more supply and more competition.
KVR is not an artistic community. I rarely see users asking for software to be more musically rewarding and emotionally satisfying, as Jo describes above.
Yet we humans live in a world full of limits, and the role of artists is to show the delusion of "more" by showing creative ways to turn limits into advantages.

sorry i don't agree at all

the only limitation in this world is your senses ; they arrange everything that happens (all at once!) in a sequential way
the role of artists is to show that, rebel against any limitations and rules and regulations and certainly not play along in the consumer marketplace you describe

[syntonica]

Some FRs will have to go onto the wait list as lower priority. It is a side effect of the Law of Single Dev. I'm sure if you offered $1 million in recompense, things would be different.

[sl23]

none of us are getting what we want, not everything I mean

I don't think that will ever be possible, or that it's even a good thing.
We are in KVR, a consumer marketplace with social media that encourages posts which follow economic delusions of more demand, more supply and more competition.
KVR is not an artistic community. I rarely see users asking for software to be more musically rewarding and emotionally satisfying, as Jo describes above.
Yet we humans live in a world full of limits, and the role of artists is to show the delusion of "more" by showing creative ways to turn limits into advantages.

sorry i don't agree at all

the only limitation in this world is your senses ; they arrange everything that happens (all at once!) in a sequential way
the role of artists is to show that, rebel against any limitations and rules and regulations and certainly not play along in the consumer marketplace you describe

I repeat: FR's are never more important than workflow! Poor workflow stifles creativity, not supports it. Lack of features can and often is good for creativity.

[tiger001]

Some FRs will have to go onto the wait list as lower priority. It is a side effect of the Law of Single Dev. I'm sure if you offered $1 million in recompense, things would be different.

well i'm no millionaire myself but surely wouldn't mind to pay for certain FRs fruitified

but then we'll maybe get a bidding war from more or less rich users who'd want their FR (or issues) resolved first

jo, are you listening?

[MuTools]

Yes i'm reading.
Might be an idea for 2026..?
The short term todos still stay the same though.

[sl23]

You could show the full list and people could pay one dollar, pound, euro, on their favourite and that will get implemented! Lol

[kejkz]

Anyway, it's a simple right byte file you can make yourself: "APPL????" if I recall correctly.

Yes, it's that simple: `BNDL????` as far as I can see. Stupid, but works. Lot of plugins are suffering from this issue.

[MuTools]

As for the redux issue on macOS, it's actually a Redux plugin problem. The Renoise Redux.vst3 directory is missing the binary file `Pkginfo` to be seen as a bundle. I've copied the Pkginfo from the Contents directory of the Waldorf Largo 2 plugin to the Contents directory of the Renoise Redux, and now the Redux can be seen and opened by MuLab. I've seen this problem before, some hosts don't mind, but MuLab does, so try this and it should work as expected.

Yes, it's that simple: `BNDL????` as far as I can see. Stupid, but works. Lot of plugins are suffering from this issue.

This triggered some thinking, and i checked the code about something.
It might be related to some legacy carbon related code that still is in MuLab's Mac specific code for connecting to a plugin library. This code may be better removed and maybe that will avoid this issue. Don't know, lets try it out in a next beta update, later. I've taken note about it.

In fact it might be interesting if someone can send me a MuLab 10.1.23 for Mac log file after having tried inserting a plugin that failed due to this missing 'BNDL????' in the plugin.

[syntonica]

I believe that if you are using Cocoa to look at the Info.plist for bundle information, the Pkginfo file is required, but if you just read the bundle file in manually, everything works fine regardless. That's why some hosts don't care and others do.

[MuTools]

Here is a MuLab 10.1.24 for Mac test version were some legacy code lines were removed that were still related to Carbon:

https://www.mutools.com/mulab/app/lates ... 64-app.zip

Does this improve things on Mac, plugin-wise?

[ApexSoundMusic]

Well I can try out to reach Reason, see if that yields any results..
Hopefully it gets resolved one way or another, because I use the Reason Rack plugin a lot! Being able to use Mulab and that one together is the killer combination for me. Unfortunately just not yet now. In the meantime I also logged a support ticket at Reason.

Please do this short test to create a MuLab log file:

* Restart MuLab 10.1.23.
* Insert Reason Rack and open-close its editor until the issue has repeated itself.
* Goto MuLab menu -> Tools -> Copy Log and paste the log data in a reply here or in an email to

That may help in narrowing it down.

E-mail sent. Hope it helps!

[dayvyg]

Minor bug. Duplicated automation clips don't show the curve in the duplicates. If you open the clips, the same automation points and values are present.