MuLab 10.1.25

[tiger001]

small bug: when i enter a tempo (in the tempo track) below 61.5 (like 55 or 22) it reverts to 61.5
-seems 61.5 is the slowest ML will go ?

Tempo 246 is the fastest ML will set?
-it doesn't accept faster tempo's it seems

[tiger001]

something funny going on with tempo changes:

a smaller tempo will result in a compressed (faster?) audio stream while a (very fast) tempo will have the audio stream(s) smeared over
-that doesn't seem logical to me

what i want to accomplish is have certain passages have (e.g.) play double tempo while they were not recorded as such
-i thought setting a few tempo changes would accomplish that
(but does not seem to work with audio streams)
(could be that i'm reading / interpreting the composer display wrong though)

audio sequences are stretched and keep their relative positions (to the original timeline)

it looks like with the same loop length, a faster tempo results in less audio, slower tempo and the same loop length results in longer piece of audio
if you write it like this, it seems logic but to me it isn't
i thought that a faster tempo would result in faster play and that the loop markers would still play the same piece of audio etc etc
(but in the faster or slower tempo, the audio keeps its original pitch etc)

i've got some audio but it is too big and too propriety to share, will send you a link

[MuTools]

small bug: when i enter a tempo (in the tempo track) below 61.5 (like 55 or 22) it reverts to 61.5
-seems 61.5 is the slowest ML will go ?

Tempo 246 is the fastest ML will set?
-it doesn't accept faster tempo's it seems

First of all:
Essentially all tempi in a MuLab project are relative to the project tempo.
The project tempo is defined in the project modular area / main composer.
In MuLab Plugin the project tempo is defined by the host.

Ok now when editing tempi inside a MuLab project it still shows/edits an absolute BPM tempo value as that's what the user wants, but under the hoods it's a relative tempo value.
In a tempo track envelope you can automate tempi from 50% to 200% of the composer tempo.

So based on what you wrote i assume your main tempo is 123 BPM.
Hence the limits you encounter.

[MuTools]

a smaller tempo will result in a compressed (faster?) audio stream while a (very fast) tempo will have the audio stream(s) smeared over

Audio streams don't follow the tempo.
The stream the original audio from the audio file.
An audio stream can be many hours long, no prob, it's not loaded in RAM.

If you want audio that follows the tempo use Audio Sequences.

[tiger001]

then if i want to accomplish above i need to split the audio stream and transfer it to a audio sequence?

-is there an easy way to transfer like 8 audio streams into 1 sample?

[MuTools]

it looks like with the same loop length, a faster tempo results in less audio, slower tempo and the same loop length results in longer piece of audio
if you write it like this, it seems logic but to me it isn't
i thought that a faster tempo would result in faster play and that the loop markers would still play the same piece of audio etc etc

No, audio stream clips are quite simple.
Their strength is the fact that they can be very long, no RAM limits.
If you play an audio clip at half tempo the absolute time length of that clip (eg. in seconds) will be double and hence more audio will be played. That's how it works now.

[tiger001]

Ok now when editing tempi inside a MuLab project it still shows/edits an absolute BPM tempo value as that's what the user wants, but under the hoods it's a relative tempo value.
In a tempo track envelope you can automate tempi from 50% to 200% of the composer tempo.

ok, makes sense
could you display the tempo in the tempo track as a % then ?
(now it is confusing)

2025-11-06 20_05_43-MuLab App _ FBF_A.jpg

[MuTools]

-is there an easy way to transfer like 8 audio streams into 1 sample?

Draft thought:
1) Convert them all 8 from audio stream clip to audio sequence clip.
2) Merge all these 8 clips.

But you won't have 8 lanes i'm afraid.
So maybe better to cut-paste the sample events of clips 2-8 into clip 1.
Then you can paste the sample events on a separate lane.

[MuTools]

could you display the tempo in the tempo track as a % then ?

There is no such option atm.
Users requested absolute BPM tempi.

[MuTools]

NB: Note that each and every (audio) sequence clip also has its own Speed factor which you can use to play that clip at eg. half or double speed.

[tiger001]

little bug ?

when 1 track solo'd (so all other tracks are muted) and you drop a new audio stream/track, that is not muted and plays along with the solo'd track

[pekbro]

Is there any way to save presets for the button graphics? Some file I can edit even...

*nvm, I'll just use a text file, no biggie.

[ortseam]

Hello! I'd like to ask if it's possible to add an option of storing the windows set for Mulab Plugn - so that all windows of VST plugins and Mulab modules (open and/or folded to Mulab project bottom line) could automatically be restored after closing and reopening Mulab Plugin GUI?

Thank you!

[tiger001]

excuse for the newB question but when i de-activate the rack, don't see any VU metering but i'm still hearing the track playing, what is going on / i'm doing wrong ?
track is playing an audio stream that is going directly to the rack...

2025-11-08 16_22_57-MuLab App _ FBF_A.jpg

[tiger001]

another thing about the tempo (track)
sorry to continue to bash on this topic

when i stop the composer midway (e.g.) the tempo display jumps back to the initial/start value, while i was thinking the tempo display would still show the tempo at the location of the ruler, no?
(so the tempo display is only 'correct' while playing)