MuLab 10.0.85

[focusrite]

When there is am audio sequence you have multiple lanes. I would like to assign an input to each lane to be able to process them with different fx.

Ok i now clearly understand your question.
Such feature is currently not yet in there, but i expect it to be realized at some point, it would be logical, natural and fun.

Ok thank you, I noticed you can have input 1 2 3 4 etc. in the rack mux

[MuTools]

Ok thank you, I noticed you can have input 1 2 3 4 etc. in the rack mux

Indeed, which is one of the many advantages of the new modular racks.
And that feature is a step forward to your feature request regarding the audio sequences.
Step by step. (sorry for the slowness)

[MuTools]

MuLab App M10.0.9 beta for Windows 64 bit is available on https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• EQ/Filterbank: The individual filter curves can now also be tweaked using a control point on the spectrum graph. Clicking such filter curve control point without dragging highlights that band's parameter frame.
• EQ/Filterbank: Better default values for the frequency parameters.
• EQ/FilterBank and other filter modules: When editing the frequency parameter via a text box, this text box now also accept MIDI keys like "C4", "G#5", etc.which will then be converted to their frequency in Hz.
• Editing envelope segments while they're being played now is more instantely reflected in the playback.
• When switching from rack modular area to rack front panel, it only showed the rack front panel without the other standard rack controls. Fixed.
• When loading a project with a missing VST3 plugin, then the "Couldn't find VST3 plugin" alert did not mention the VST3 plugin name anymore. Fixed.
• Dropping a sample on the composer and choosing Pitched Sample did not select that sample in the newly create MuSampla. Fixed. Similar bug fix for Add MuSampla track.
• Rack in separate window can now be resized.
• Rack Desk -> Options -> Default Rack Slot Width: Edits were not always immediately reflected. Fixed.
• MuDrum Editor: When scrolling the rack desk the cables were not following anymore. Fixed.
• Drop sample on composer as pitched sample:
  If there is a "Sample Player Rack.Mux" in your Mux/Racks or Mux/Racks/New Rack Templates subfolder that MUX preset will be used.
  Else if there is a "Sample Player.Mux" in your Mux/Instruments/Templates subfolder that MUX preset will be used in a new default rack.
• Drop sample on composer as sliced multi-sample:
  If there is a "Sliced MultiSample Player Rack.Mux" in your Mux/Racks or Mux/Racks/New Rack Templates subfolder that MUX preset will be used.
  Else if there is a "Sliced MultiSample Player.Mux" in your Mux/Instruments/Templates subfolder that MUX preset will be used in a new default rack.
• Other small improvements.

[PelletProject]

Glad to see attention being drawn to user friendliness for the EQ. I could see it becoming much more powerful with future subsequent updates.

I did encounter some unexpected behavior concerning it though. When deactivating unused bands then reactivating them, upon pressing the FLAT button, instead of returning to where they typically would reset in the ends of the spectrum, their positions are set to the middle, where M5 also happens to be located, resulting in three nodes on top of each other. It looks like trying to separate them always results in low, then M5, then high being moved in that order, even though visually the high node is on top of the others

In addition to fixing this, perhaps it would be good to have an indication which node you are going to select upon mouse hover in case nodes are on top of each other, maybe a colored outer ring corresponding to whichever one you'll end up selecting?

[masterjoe]

The V10 additions look pretty nice.
Are there any planned changes to the composer module as well?

I would love to see the following additions to the Note Action Maps:

- define and use named regions for playback / loop ("intro", "chorus", "bridge", ...)
- define any number of playlists per composer with multiple named regions + repeats per region
- playlists shall also be usable either as a global playback mode for a composer OR for the Note Action Map as something you can trigger by will; multiple playlists shall be usable

This would allow a lot easier defintion and triggering of user defned snippets from a composer arrangement.

Another thing I am looking for is that ANYTHING can be "pooled" / be a shared copy. Audio / Clips / Automation / ... so that you can re-use really ANY stuff.

THX

[nenneb]

Hi there,
could someone compare CPU-usage between M9 and M10 please?

I got myself a new motherboard with an i7-13700 which should be 10x faster than my 12-year-old i7. And after tweaking some UEFI-parameters it is! But I dont see that much improvement on MuLab's CPU-meter and in addition I achieve a difference between M9 and M10 with a MuLab-only project (no VST nor CLAP):

Demo-project "Embrace" (only opened, no run, no key pressed):
M9.6.7: 3% avg, 9% max
M10.0.8: 11% avg, 19% max

[MuTools]

MuLab App M10.0.10 beta for Windows 64 bit is available on https://www.mutools.com/mulab/app/lates ... /beta.html

This is a quick fix for a new bug that caused a crash upon dropping a sample as audio sequence.

[MuTools]

I did encounter some unexpected behavior concerning it though. When deactivating unused bands then reactivating them, upon pressing the FLAT button, instead of returning to where they typically would reset in the ends of the spectrum, their positions are set to the middle, where M5 also happens to be located, resulting in three nodes on top of each other. It looks like trying to separate them always results in low, then M5, then high being moved in that order, even though visually the high node is on top of the others

I suppose you have been reloading a M10.0.8 project in which all band frequencies indeed defaulted to a center frequency, which was not ideal. These default values have been enhanced in M10.0.9. You can reset a parm to its default value by alt+clicking it.[/quote]

[MuTools]

Hi there,
could someone compare CPU-usage between M9 and M10 please?

I got myself a new motherboard with an i7-13700 which should be 10x faster than my 12-year-old i7. And after tweaking some UEFI-parameters it is! But I dont see that much improvement on MuLab's CPU-meter and in addition I achieve a difference between M9 and M10 with a MuLab-only project (no VST nor CLAP):

Demo-project "Embrace" (only opened, no run, no key pressed):
M9.6.7: 3% avg, 9% max
M10.0.8: 11% avg, 19% max

Same demo project, same no play, no key case, same audio setup.
M9.5: 11%
M10: 11%

There is a tiny little cpu increase in M10 due to the modular racks but that's around 0.1%.

[Stephan326]

I have a key for 9. Says I need one for 10. How do I go about that?

Thanks, Steve

[dakkra]

I have a key for 9. Says I need one for 10. How do I go about that?

Thanks, Steve

viewtopic.php?p=8990328#p8990328

[MuTools]

I have a key for 9. Says I need one for 10. How do I go about that?

As you already have a MuLab user key you can request a temporary M10 test user key via
If you have MuLab For Life then your personal MuLab 10 user keys will be sent to you, for free of course, around the official MuLab 10 release.
If you don't yet have MuLab For Life you can upgrade to MuLab For Life via https://www.mutools.com/shop.html

Attention: If you would use the M10 test user key to make valuable projects and you don't upgrade to MuLab For Life, then you won't be able to reload those M10 projects after the temporary M10 test user key timed out.

[PelletProject]

Now i suppose you have been reloading a M10.0.8 project in which all band frequencies indeed defaulted to a center frequency, which was not ideal. These default values have been enhanced in M10.0.9. You can reset a parm to its default value by alt+clicking it.

I can confirm that this is happening in M10.0.10 in a new project with a new instance of the EQ, the low and high bands are congregating to the frequency of the M5 band. This is what results in them being stacked on top of one another upon pressing FLAT.



I should also add that adding a new rack with the button on the rack desk no longer works.

[MuTools]

I can confirm that this is happening in M10.0.10 in a new project with a new instance of the EQ, the low and high bands are congregating to the frequency of the M5 band. This is what results in them being stacked on top of one another upon pressing FLAT.

First of all, i was wrong about FLAT only resetting the gains. FLAT completely resets the EQ.

That said, now i see what you mean about the low & high frequencies being reset to the center, this bug only happens after an "Activate All Bands". Will be fixed.

I should also add that adding a new rack with the button on the rack desk no longer works.

Indeed, if there are no custom rack presets. In such case a default rack must be added of course. Will be fixed.

Thanks for reporting these issues.

[MuTools]

MuLab App M10.0.11 beta for Windows 64 bit is available on https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• EQ / Filterbank: After Activate All Bands, the low/high frequency default value was wrong. Fixed.
• Rack desk -> Add rack didn't work anymore without rack presets. Fixed.
• Fixed a bug in the event signal system which caused that, in certain cases, events could have a wrong MIDI channel.