MuLab 9.1.27 [released]

[robert_p]

Being small has disadvantages but also advantages.

The biggest advantage is that you have created one of the most useful piece of software I have ever had:))

[MuTools]

Thanks!

[syntonica]

Being small has disadvantages but also advantages.

The biggest advantage is that you have created one of the most useful piece of software I have ever had:))

I've never cussed it out. And I swear a lot!

I do have a few minor quibbles, but for 95% of my usage, Mulab works exactly how I think a DAW should work. I'm constantly battling Logic and Reaper...

[robert_p]

I do have a few minor quibbles, but for 95% of my usage, Mulab works exactly how I think a DAW should work.

Good for you! As a Windows user I found that MuLab App doesn't perform very well on my system.

Audio Setup -> Num Audio Processor Threads = 1

1_Thread.jpg

---
Audio Setup -> Num Audio Processor Threads = 8

8_Threads.jpg

---

It seems that the overall CPU load increases x6 when the multithreading is active.
---

Audio_Setup.jpg

---
P.S. In Studio One I can run 16 CPU intensive VST instruments and the CPU Load is 30% - similar to running just one native instrument in MuLab App. (256 samples buffer size)

[Michael L]

Re: "Arp Backed Keys" preset -- if the envelope in the Keys extends much beyond the next note in the arp, polyphony can increase quickly.

[robert_p]

Re: "Arp Backed Keys" preset -- if the envelope in the Keys extends much beyond the next note in the arp, polyphony can increase quickly.

True. I use this preset as a "stress test".

P.S. Despite of the questionable performance of MuLab App on my system - I'm quite happy with MuLab Plugin that allows me to overcome some of my DAW's limitations (I can easily crate a MUX to combine my MIDI effects and modulators with VST instruments within a single track).

[syntonica]

I do have a few minor quibbles, but for 95% of my usage, Mulab works exactly how I think a DAW should work.

Good for you! As a Windows user I found that MuLab App doesn't perform very well on my system.

Audio Setup -> Num Audio Processor Threads = 1
1_Thread.jpg
---
Audio Setup -> Num Audio Processor Threads = 8
8_Threads.jpg
---

It seems that the overall CPU load increases x6 when the multithreading is active.
---
Audio_Setup.jpg
---
P.S. In Studio One I can run 16 CPU intensive VST instruments and the CPU Load is 30% - similar to running just one native instrument in MuLab App. (256 samples buffer size)

I'm running on Mac, so I don't have to futz with ASIO clients and such, but that's usually where poor CPU performance comes from. Jo and/or other Windows users can probably help you out here better than I'm able to.

(As an aside, your CPU is ooooold and slooooow. I just moved up from a 4th gen i5 that was a bit slower than yours to a new M1. I feel like a king now with all that horsepower! )

[MuTools]

As a Windows user I found that MuLab App doesn't perform very well on my system.

The figures you're showing are not relevant, as explained on https://www.mutools.com/info/M9/docs/mu ... setup.html

In Studio One I can run 16 CPU intensive VST instruments and the CPU Load is 30% - similar to running just one native instrument in MuLab App. (256 samples buffer size)

Please give all details of this comparison test.

[robert_p]

(As an aside, your CPU is ooooold and slooooow.

I know it's old and slow! But believe me, I still can manage quite a large session with it. I work with Studio One since version 1 (I switched from Logic 5.5 PC when it was sold to Apple). Do you remember how slow the computers were back in 2000? Yet, people were able to produce some good tunes using them;))

[MuTools]

MuLab App 9.1.24 is available in https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin 9.1.24 is available in https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• When saving front panel data, some data was not properly saved. Fixed.
  Info: Files saved with phantom version M9.1.23 will still open, but it might be that some front panel color data was lost, but only when saved with phantom version M9.1.23 and only for parameter items.
  Note that you can quickly copy-paste the looks of a panel parameter to others by using a shortcut key to "Paste Looks".
• When searching for audio, projects, presets, ... and the search was wide and deep (eg. searching a complete drive) then MuLab could crash. Fixed.
• Front Panel Module Slot: Copy-Paste Looks only worked partially. Fixed.
• Front Panel Drum Note Processor: Copy-Paste Looks only worked partially. Fixed.
• MIDI Channel Remapper: Copy to clipboard didn't preserve the channel map. Fixed.
• Upgrade Projects / Presets: A progress bar is shown instead of a spinning wait cursor. Supports Esc to abort.
• List MuTools Files Version: After the initial search for matching files, a progress bar is shown instead of a spinning wait cursor. Supports Esc to abort.

[robert_p]

Please give all details of this comparison test.

Studio One - VST Instruments playing simultaneously:

1x Geist2 (Drums), 8 MUXes with MIDI effects and modulators (1xZebra HZ, 2xZebra2, 2xSpire, 2xSylenth, 1xDune3), 2xHalion7, 1xScaler, 3xNora Multichannel Polyphonic Arpeggiator + some audio loops.

CPU Load: 32% (45% Peak caused by screenshot App.)
---

CPU_Performance.jpg

[MuTools]

Ok i understand what you meant.
The answer is the same: Using the Windows task manager figures is not relevant for measuring MuLab's performance.
Please see https://www.mutools.com/info/M9/docs/mu ... setup.html

[robert_p]

Video (running OBS Studio made CPU Load higher)
---

[robert_p]

Ok i understand what you meant.
The answer is the same: Using the Windows task manager figures is not relevant for measuring MuLab's performance.
Please see https://www.mutools.com/info/M9/docs/mu ... setup.html

So, you mean that I should transfer this setup from Studio One to MuLab App to make the comparison? I still can't understand why running Reaper, Cakewalk and Bitwig makes task manager figures similar to Studio One results.

[syntonica]

(As an aside, your CPU is ooooold and slooooow.

I know it's old and slow! But believe me, I still can manage quite a large session with it. I work with Studio One since version 1 (I switched from Logic 5.5 PC when it was sold to Apple). Do you remember how slow the computers were back in 2000? Yet, people were able to produce some good tunes using them;))

I used Logic 5 on an old 800Mhz G4 iBook. I had to freeze/render each individual track as I completed it. If I had to touch up any fx, it was a pain to unfreeze and refreeze. My latest MBA is about 100x faster! No more freezing, even if I run something like Diva. Now, if they'd only make Neon for the ARM processor...