MuLab 10.0.85

[MuTools]

Um - so if I've got a MIDI Note Mapper after the MIDI Input, then the project level received note on-off counters are not going to be correct?

The core MIDI input monitoring, which includes those counters, is at the very MIDI input of the project before anything is dispatched / processed.
So the answer to your question is: No, a Note Mapper in the project modular area won't affect those counters.

The counters aren't shared by all instances, are they?

The core MIDI input monitoring, which includes those counters, is at the very MIDI input of the project. Each MuLab project = each MuLab Plugin instance has its own MIDI input monitoring, which includes those counters.

About the possible mismatches:
If you find a repeatable pattern, pls let me know.
I'll also keep an eye on it while working/playing with MuLab, just as i'm keeping an eye on as much as i can to keep improving MuLab day by day.

[SunnySedated]

Any idea when the finally version of MuLab10 will be released? Or is it a developers secret?

[MuTools]

ASAP!

Still to do:

• Finalize the beta testing = kill any remaining bugs + some final touches
• Update the docs
• Make video(s)

Anyway, MuLab 10 already is quite stable and usable, that's why it's already available on MuTools.com as pre-release.

Any specific reason why you're asking?

[SunnySedated]

no, no specific reason. Just want to spend some money

[MuTools]

The MuTools shop is open and MuLab 10 is available: https://www.mutools.com/shop.html

[syntonica]

Hi Jo,

Not a bug, but a minor annoyance. The Plugin Manager is a bit too tall. Older Intel MacBook Air with 1366 x 768 screen. I have to hide the Menu Bar AND Dock to see the buttons at the bottom, and then, only the top halves are visible. There's no way to resize the window.

Total edge case, I know. V8 was perfect, but v9 and v10 use taller window bars and the fields on the right are taller as well.

Perhaps making it resizeable and going back to the v8 proportions? Thanks.

[audiojunkie]

The MuTools shop is open and MuLab 10 is available: https://www.mutools.com/shop.html

Congratulations!!

[jd88]

Hi,

normally an oscillator is working like this:

Example: polyphonie-setting (maybe polysynth): 16

so after the 16 voice is reached (played) the osc will stop the first played (sounding) note and play the new one. So; in that case allways the first (oldest played) notes are stopped to be used for the new played. It's like a circle.

BUT in MuTools it did'nt work. If I reach (playing / holding or ADSR Release / Decay is long ) the maximum-polyphonie, no new voice will be played. They are silent.

I've to release the hold keys / played notes my own.

This is a bug and a problem if the user has to look (efficient) to CPU-Usage. The voicecounter never reset correctly while playing!

( sorry for ma crappy english )

In German:

Normalerweise arbeiten Oscillatoren wie folgt.

Beispiel:

Wenn man eine Polyphonie von 16 Voices eingestellt hat, stoppt der Counter automatisch nach Überschreiten der 16. Stimme die älteste(n) noch klingende(n) Note und nutzt diese freigewordenen Ocs für die neu gespielten Noten. Sprich die OCS rotieren entsprechend.

In MuTools werden über eingestellter Polyphonie (sprich: noch klingende Noten, z.B. weil sie gehalten werden, oder die Hüllkurve entsprechend eingestellt ist) gespielte Noten schlicht nicht gespielt. Erst, wenn man die klingenden Noten manuell stoppt (Taste loslassen bzw. Sustainpedal / Decay / Sustain...) werden wieder neue Noten gespielt.

Dies ist so aktuell leider ein Bug und schränkt die Nutzung des Synths ziemlich ein. Vor allem, wenn man auf effiziente CPU Nutzung achten muss (aber auch in anderen, z.B. Programmiertechnischen Situationen). Ein Problem im Counter?

Oder gibt es diesbezüglich eine Einstellung, welche ich übersehen habe?

Könnte dies bitte gefixt werden?

b.r. Jd

[pljones]

Another problem with Note Mapper: it doesn't treat polyphonic aftertouch as a note event. So whilst the Note Off (0x8*) and Note On (0x9*) messages get the same treatment, the accompanying Polyphonic Aftertouch (0xA*) messages come adrift and can no longer be processed with their related note message.

[MuTools]

Hi Jo,

Not a bug, but a minor annoyance. The Plugin Manager is a bit too tall. Older Intel MacBook Air with 1366 x 768 screen. I have to hide the Menu Bar AND Dock to see the buttons at the bottom, and then, only the top halves are visible. There's no way to resize the window.

Total edge case, I know. V8 was perfect, but v9 and v10 use taller window bars and the fields on the right are taller as well.

Perhaps making it resizeable and going back to the v8 proportions? Thanks.

The plugin manager has grown in size indeed because there are more editable options. As a short term solution for small screens note that you can move any window by right-click-drag the window titlebar or border.

[MuTools]

normally an oscillator is working like this:

Example: polyphonie-setting (maybe polysynth): 16

so after the 16 voice is reached (played) the osc will stop the first played (sounding) note and play the new one. So; in that case allways the first (oldest played) notes are stopped to be used for the new played. It's like a circle.

BUT in MuTools it did'nt work. If I reach (playing / holding or ADSR Release / Decay is long ) the maximum-polyphonie, no new voice will be played. They are silent.

I've to release the hold keys / played notes my own.

This is a bug and a problem if the user has to look (efficient) to CPU-Usage. The voicecounter never reset correctly while playing!

I can't repeat this.
Attached a little project with the Basic Synth set to polyphony 4.
A chord of 4 notes is played, then a bit later a 5th note is added and it plays fine by removing 1 of the earlier voices, as expected.
So please elaborate on what you mean.

[MuTools]

Another problem with Note Mapper

"Another"?
What's the other problem with the Note Mapper?

it doesn't treat polyphonic aftertouch as a note event. So whilst the Note Off (0x8*) and Note On (0x9*) messages get the same treatment, the accompanying Polyphonic Aftertouch (0xA*) messages come adrift and can no longer be processed with their related note message.

This will be improved in the next update.

[jd88]

normally an oscillator is working like this:

Example: polyphonie-setting (maybe polysynth): 16

so after the 16 voice is reached (played) the osc will stop the first played (sounding) note and play the new one. So; in that case allways the first (oldest played) notes are stopped to be used for the new played. It's like a circle.

BUT in MuTools it did'nt work. If I reach (playing / holding or ADSR Release / Decay is long ) the maximum-polyphonie, no new voice will be played. They are silent.

I've to release the hold keys / played notes my own.

This is a bug and a problem if the user has to look (efficient) to CPU-Usage. The voicecounter never reset correctly while playing!

I can't repeat this.
Attached a little project with the Basic Synth set to polyphony 4.
A chord of 4 notes is played, then a bit later a 5th note is added and it plays fine by removing 1 of the earlier voices, as expected.
So please elaborate on what you mean.

Hi, I Sent you some minutes ago an email whith Video. So you see what happens. Same happens if I record MIDI and play whith Mutools Sequencer.

this problem in MuTools happens only with MuTools synth-plug.

Maybe important: All AUi and VSTi plugs working fine in Mutools.

On another computer (Same Kind: apple IMac, OSX 10.15.7) we could confirm / recreate this problem.

And yes, your attached example is working. So, what happens?

[MuTools]

Same happens if I record MIDI and play whith Mutools Sequencer.

Please record it on a track and make sure the issue still is there upon playback then save the project and email me that MuProject file.

[jd88]

Same happens if I record MIDI and play whith Mutools Sequencer.

Please record it on a track and make sure the issue still is there upon playback then save the project and email me that MuProject file.

i sent it.

Really, it allways happens here.