MuLab 10.0.85

[MuTools]

Previous post edited to post the GIF.

Oh, ok, i see.

Fixed in M10.0.60, available here:
https://www.mutools.com/mulab/app/lates ... /beta.html

Thx!

[MuTools]

Tip: The easiest way to change number of stairs or cycles is with the mouse wheel. Note that also any value display, knob or slider, also at other places, can be tweaked step by step using mouse wheel. I'm sure you knew that already, but it doesn't hurt adding the info here again.

[FabBad]

Thanks for your quick response!
----

Tip: The easiest way to change number of stairs or cycles is with the mouse wheel. Note that also any value display, knob or slider, also at other places, can be tweaked step by step using mouse wheel. I'm sure you knew that already, but it doesn't hurt adding the info here again.

Tips are always welcome For sure some users would get it useful.
-----

A question, I noticed that those native automations are not Audiorate or it has a some kind of ramping to make it smoother.. It's ok for certain cases but I think that it should be at least an option to bypass that ramping to make it 100% audiorate.
Is possible to make it optional? at least in the future?

[MuTools]

Where do you notice any ramping?
Please share a project.

Cause in fact it should be one of the main strengths of this enhanced curve system: Virtual perfection (audio rate) sound-wise, yet still cpu-friendly (not audio rate).
And at the curve segments where it matters, MuLab automatically switches to audio rate so to not compromise the sound quality!

[FabBad]

Where do you notice any ramping?
Please share a project.

Yes, automating Rack's fader for example, the value changes are not sharp as it should if those envelopes are at audiorate.

I made a little project that demonstrates this by automating the level on a pure DC sample.

Warning that is DC involved

Cause in fact it should be one of the main strengths of this enhanced curve system: Virtual perfection (audio rate) sound-wise, yet still cpu-friendly (not audio rate).
And at the curve segments where it matters, MuLab automatically switches to audio rate so to not compromise the sound quality!

I didn't know that it auto switches to AR... but even (besides that it sounds different against the original project version 9), It still has a some kind of ramping.

[MuTools]

Parameter automation is done using events.
Events are not working at audio rate but at a much lower rate.
For that reason all internal parameter automations, both from the composer and from MIDI input, are always slightly smoothed to avoid small staired changes in the sound at the event times. IIRC it's around a 1 ms smoothing. If that subtle smoothing would not be done then you would hear slight little clicks on the parameter event times, depending on the type of parameter, but for a gain this is called "zipper noise". That does not sound nice, the subtle smoothing is necessary and good.

Now i understand that there are musical cases where you don't want any smoothing, where want perfect sharp edges, where you want the cristal clear quality of the new curves.
That's why i've already been thinking of adding another type of clip: Modulation Clips. These would look alike Automation Clips but the big difference is that automation clips use events = the blue signal lines and blue signal jacks, while modulation uses the green signal lines and green signal jacks which are suited to do high precission modulations, even at audio rate.
Modulation clips would, just like any other modulation in the modular area, not change the parameter value itself, but add to the parameter value. Also that aspect could have extra advantages if it was available from composer clips.

This is just draft open thinking i share here. I did not yet research it.
But it does feel like something natural and wanted.

Conclusion: If you would like to test the accuracy of the new curve system, go into the modular area and use green signals to setup such test.

[MuTools]

PS: Attached is an example project that demonstrates the accuracy of the curve system. It generates a block wave by modulating a gain, like you did, but this time using green signals.
Attention: instantly generates a full level block wave, watch your volume before opening project.

[FabBad]

MANY thanks Jo, that complete my puzzle, I had the suspicious that those envelopes were related with the before mentioned (a post made a couple of weeks or so), MIDI events.

The idea is nice, as for old project compatibility is necessary to add another type of automation... or maybe extend those that uses green paths...?

whatever, I gonna let to the modulation generators and processors do that job.

Also, I know that is requested and in the to-do list, but what about converting the recorded automations to the standard ones?

Also again, will be another way to automate at audiorate 3rd party plugins?

Writing this post and submitting, it just appears your latest post where I just wrote haha.

[MuTools]

Pushing the limits in above example:
Now attached project generates a 750 Hz block wave simply using modulations, no oscillator involved. You can easily further increase the pitch by increasing the LFO curve's Num Cycles.
It keeps sounding right, even at high modulation pitches, even 10 KHz and higher, where even sonic aliasing starts to occur as this is not a band-limited oscillator like MuLab's real oscillators. I've doublechecked the rendered audio file, looks all right to me.

[MuTools]

Also, I know that is requested and in the to-do list, but what about converting the recorded automations to the standard ones?

Yes i know, that's a too long time on the wishlist already.
Hope to find time & resources. You & others can help by promoting MuLab on your socials so to increase the sales and the necessary resources.

Next steps are about finishing and releasing MuLab 10.0.
The new curve system added another unexpected big delay on MuLab 10's release.
But i could not accept M10 being released with that improper splitting of automation clips.
Reworking that took a lot more time than expected. But happy and proud with the result.

Progressing step by step.

[FabBad]

Pushing the limits in above example:
Now attached project generates a 750 Hz block wave simply using modulations, no oscillator involved. You can easily further increase the pitch by increasing the LFO curve's Num Cycles.
It keeps sounding right, even at high modulation pitches, even 10 KHz and higher, where even sonic aliasing starts to occur as this is not a band-limited oscillator like MuLab's real oscillators. I've doublechecked the rendered audio file, looks all right to me.

Yeah that's what I did many times before, squish it to the limits, this is what I like on this DAW, you can do many things from "nothing" and knowing well how use that, it opens to new creative paths which is on spot as MuLab is intended philosophy.

Yes i know, that's a too long time on the wishlist already.
Hope to find time & resources. You & others can help by promoting MuLab on your socials so to increase the sales and the necessary resources.

Next steps are about finishing and releasing MuLab 10.0.
The new curve system added another unexpected big delay on MuLab 10's release.
But i could not accept M10 being released with that improper splitting of automation clips.
Reworking that took a lot more time than expected. But happy and proud with the result.

Progressing step by step.

I do the possible to make MuLab more recognition as possible, which I made but I'm not into those social media like Tickt, Faceb, X, etc only youtube and I already posted some comment videos where is necessary to be there... you know, those for example, "I tried make a track on all daws aviable..." or something like that, One replayed that he even didn't knew MuLab exist.
Also, I'm not an expert at promotions, even my own music is super buried on bandcamp.

Yes, happy to see this DAW is progressing healthy and constant, this gonna be rewards for sure

[MuTools]

I do the possible to make MuLab more recognition as possible, which I made but I'm not into those social media like Tickt, Faceb, X, etc only youtube and I already posted some comment videos where is necessary to be there... you know, those for example, "I tried make a track on all daws aviable..." or something like that

Thank you!

Also your help with testing is very helpful !

One replayed that he even didn't knew MuLab exist.

I'm convinced this indeed is a serious issue: MuLab is way too unknown.
That's why soon after M10's release i'll invest time in making more videos. It will take time and it will slow down MuLab's development a bit, but it's really necessary.

Also, I'm not an expert at promotions, even my own music is super buried on bandcamp.

What's the link to your Bandcamp.

[FabBad]

Also your help with testing is very helpful !

One replayed that he even didn't knew MuLab exist.

I'm convinced this indeed is a serious issue: MuLab is way too unknown.
That's why soon after M10's release i'll invest time in making more videos. It will take time and it will slow down MuLab's development a bit, but it's really necessary.

As you running a one man project, is quite obvious that the things progress slowly. Some others could start a group company or sort kind of grow / expansion...
But is your decision and I respect that.

What's the link to your Bandcamp.

/fabrecord
I have been registered since 2010 but in 2015 just released the first album.
and the latest one was on 2023 ... or so... and SLOWLY preparing the next release.
There's various projecs in there. with different styles and pseudonyms.

[syntonica]

Hi Jo,

I just opened a medium sized project that used to play with only a drop out of two in the most complex area. However, now Mulab can barely crawl through any of it. Mulab at idle with an empty project open seems to take up twice the CPU power it used to.

Have you made any changes to the audio engine that might cause this? Or, do I need to lay the blame at Apple's doorstep for their "security" updates?

Mac Intel, Big Sur, original project created in Mulab 8, since tested in 9 and 10. Unfortunately, the project file has been updated to 9, so I can't go back and get on 8 again to confirm.

[MuTools]

As you're talking about a Mac, it's not about the new curve system, which currently is a Windows only beta. So we can exclude that aspect. (eventhough the new curve system does not use more cpu as before, while increasing its sound quality)

So which MuLab version are you using?

Generally: M10 does not use more cpu than M9.
If you say that there is a huge difference, it feels like some setup aspect somewhere.
Is your Mac setup the same? Is your MuLab setup the same? Any background tasks that are draining off your Mac? Just draft questions.