MuLab 10.0.85

[Bax9]

I have several short vocal recordings/takes on one track: Is it possible to render a new audio clip that start at the left loop position and ends at the right loop position ? like a full stem, to be clear
by now, the new audio clip starts at the first recording

Sorry for the delayed reply.
Simply select all clips you want to be included in the render, then do Render As New Audio Clip.
This will result in a new audio clip that includes all selected clips.

thanks for nice reply
I understood this ... the point is that I have several wav takes and I would like to have a wav file starting from left locator, so I could have two or more vocal mixdown for external processing (i.e. vocal alignment)

what about my issue of very slow exporting of a single, unprocessed track in a new clip when the project is busy ? seems that unused/muted plugins weights on the process

in attachment, you see that export clips starts always from the first wav position

[MuTools]

I understood this ... the point is that I have several wav takes and I would like to have a wav file starting from left locator, so I could have two or more vocal mixdown for external processing (i.e. vocal alignment)

Add an empty clip (whatever type) at the left loop start marker and also select it before doing "Render Clips As New Audio Clip".

[MuTools]

MuLab App M10.0.78 beta (all versions) is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.78 beta (all versions) is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed since M10.0.76:

• MuLab Plugin: Improved MIDI input recording.
• MuLab Plugin: Improved sync to host, especially wrt. hosts sending a negative play position, like Cubase 14.
• Multi-Form Oscillator: When modulating the wave index at sample rate while there are panned layers (ie. resulting in stereo sound) the resulting sound was wrong. Fixed.
• Micro improvement in the envelope renderer when working at sample rate.

[MuTools]

MuLab App M10.0.79 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.79 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Applied an optimization in the plugin latency compensation system so to avoid possible little audio clicks/gaps when doing edits, like switching modules on or off, that do not impact the latency compensation.
• PolySynth: Improved voice stealing algorithm.

[humanboeing]

There's a minor bug with oscilloscope and spectrum analyzer, it is possible to power them off via rack's power button, but the power button does not turn off the light, I assume it shouldn't be possible to turn those modules off to begin with, as it was in previous versions

[MuTools]

Will be fixed in the next update.
Thx for spotting this

[MuTools]

MuLab App M10.0.80 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.80 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• PolySynth: Further improved voice stealing algorithm. Thanks to jd88.
• Deleting the last audio/event input/output in a MUX inside a rack slot could also delete the last audio/event in/out of that rack slot, which was not intended as rack slots are intended to have at least 1 audio+event in+out. Fixed.
• Little bug fix in the latency compensation optimization of the previous M10.0.79.
• Clicking the on/off of an oscilloscope in a rack slot could switch off the oscilloscope, which was not intended. Fixed.

[WoF2302]

Just one question: Which beta version is the one you uploaded to the forum yesterday, 10.0.80 or 10.0.81? When I open it, 10.0.81 is displayed.

[MuTools]

MuLab App M10.0.82 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.82 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• PolySynth: Further improved voice stealing algorithm.
• Fixed an issue with automatically sending a Sustain Pedal Off upon stop when a Sustain Pedal On is was played without a Sustain Pedal Off.

[pljones]

Fixed an issue with automatically sending a Sustain Pedal Off upon stop when a Sustain Pedal On is was played without a Sustain Pedal Off.

Out of interest, is there a list of MIDI events despatched on play stop, along with any conditions that trigger them?

[MuTools]

Out of interest, is there a list of MIDI events despatched on play stop, along with any conditions that trigger them?

There are no automatic MIDI events dispatched on stop except for the mentioned Sustain Pedal Off if there is a pending Sustain Pedal On. And obviously also note-off events for pending note-on events. Besides that, whenever the play position is moved in the time line composition, MuLab tracks any MIDI CC and parameter automations before that new play position and sends out the last value so that the new play position starts playing with MIDI CC + parameter values as if you were playing from the start.

[pljones]

I was wondering if an All Notes Off or the other pedal controllers - why would a plugin necessarily need Sustain Pedal Off any more than any other controller?
https://drive.google.com/file/d/1ewRrvM ... 0sz0c/view

[MuTools]

I'm afraid i don't understand the question. Can you please rephrase?

I can already say that if MuLab would not send out a Sustain Pedal Off on stop for any pending Sustain Pedal On, then any new live notes played on the keyboard would be sustained. Also when returning to start and the user did not explicitly add a Sustain Pedal Off at the start (99.9% chance) then when stopping in between sustain on and off then returning to a position before sustain on would also sustain all played notes which is not what the user would expect. So some special treatment of the sustain pedal is best. Agree?

[jd88]

I'm afraid i don't understand the question. Can you please rephrase?

I can already say that if MuLab would not send out a Sustain Pedal Off on stop for any pending Sustain Pedal On, then any new live notes played on the keyboard would be hold. Or when returning to start and the user did not explicitly add a Sustain Pedal Off at the start (99.999% chance) then when stopping in between sustain on and off then returning to a position before sustain on would also sustain all played notes which is not what the user would expect. So some special treatment of the sustain pedal is relevant.
Right?

- - - - -

thx for the UD 1.82

- - - - -

It's not a big thing, because if happens I stop and start again:

but please can you doublecheck same with notes that are playing? (needs noteoff if going to start before noteoff came).

I'm not really shure:

Sometimes, if I'm going back to begin of that notes before played noteoff (key left), it seems / it sounds sometimes, same notes are added again, while same old notes not stopped.
I think I'm Hearing a phasing like notes double played. And sometimes it seems too, the notecounter counts over polyphoniesettings because those effect??. Can you look into it with an OSC-Notecounter in sourcecode??).

I can not allways reproduce this, but randomly it's there.

- - - - -

Following I'm looking for because it happens sometimes too (maybe here note-offs going lost and then s.o. counter gone wrong or something like that?):

while liveplaying (maybe fast riffs) sometomes notes gone lost or sounding extremly short (example, if I'm playing 8th allways same bassnotes / -riff left hand and right hand some chords or impro.)

If I'll find a rule or can reproduce it allways, I'll send you.


Later I'll look deeper into it.

- - - - -

[MuTools]

I'm not really shure:
Sometimes, if I'm going back to begin of that notes before played noteoff (key left), it seems / it sounds sometimes, same notes are added again, while same old notes not stopped.
I think I'm Hearing a phasing like notes double played. And sometimes it seems too, the notecounter counts over polyphoniesettings because those effect??. Can you look into it with an OSC-Notecounter in sourcecode??).
I can not allways reproduce this, but randomly it's there.

If I'll find a rule or can reproduce it allways, I'll send you.

Yes, i'll need more specific and repeatable steps.