MuLab 10.0.85

[MuTools]

Well received, thx.
I replied via email, lets continue there.

[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.

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.

Mac won't allow you too drag a menu bar above the top of the screen. No worries though. Like I said, this is an edge case and I rarely need to go in there except for the first time when I add all the plugins at once.

[MuTools]

Mac won't allow you too drag a menu bar above the top of the screen.

Right

No worries though. Like I said, this is an edge case and I rarely need to go in there except for the first time when I add all the plugins at once.

I've taken note for some future update.

[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.

i sent it.
Really, it allways happens here.

Thanks Jd88 for all additional info via email.
I could finally repeat the issue here and so i could properly research it.
It indeed is a bug in the case notes are played live (not repeatable via sequence playback) and go beyond the Max Polyphony. Bug will be fixed in the next MuLab 10.0.49 update.
Thanks for reporting this

[pljones]

What's the other problem with the Note Mapper?

It's still not clear which notes have already been mapped. Yes, if I select a note, it shows what that note is already mapped to and yes, it remembers the last note touched. But I still have to touch each note to see if I already mapped it. Having shading of some kind on the already mapped keys really was what I thought you'd meant was going to be there. Sorry, I didn't mention that earlier (too many other confusing things happening that I couldn't track everything).

[bibz1st]

During VST scanning Mulab crashed a couple of times, one alert said that a vst had got corrupted, and the other said Mulab was having a problem with another vst, both were followed by Mulab exiting.
The corrupted one I wasnt bothered about and got rid of it, the other is both vst2 and 3, I tried in Cakewalk and both worked fine.
The vst3 one seems to work in Mulab but not the vst2.
Other vst2's seem to work but its the crashing that is a possible issue.
There is also an issue when using PG8X synth as reported here viewtopic.php?t=620061 by sl23.

[sl23]

PG-8X isn't available as VST3 is it?

[bibz1st]

No, I was referring to a different plugin

[sl23]

ah ok

[MuTools]

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

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

What's changed:

• Project menu now includes an extra diagnostic function "Monitor MIDI Input Events". It's in the Project->Tools submenu, together with "Monitor MIDI Input Notes". Both these project event input monitors show the events at the very MIDI input of a project before any dispatching or processing is done.
• The Event Monitor now has an explicit "Clear" button to reset it.
• Hovering the Focused Module Keyboard now shows info about the module that currently has MIDI input focus.
• Experiment: The LFO play dot now gets smaller or even invisible when the LFO rate goes up. This to avoid nonsense animations that only bloat/distort the GUI. So basically the LFO play dot is only fully visible at lower rates. Is this a good move? Opinions welcome!
• The LFO play dot could still be visible when the LFO was on a hidden Tab Frame. Fixed.
• Note Mapper now also properly remaps incoming poly-pressure events.
• Playing live MIDI notes while also using sustain pedal caused an issue in the PolySynth voice stealing. Fixed.
• When dragging a rack slot module with aux ins-outs to another rack slot, then the updated aux in-out module boxes lost their position in the modular area. Fixed.

[FabBad]

Hi Jo, In this case I came with a little suggestion, nothing urgent, just a QoL one.

On a MUX workspace, In the menu and where it says "New MUX from selection", it should be Grayed if actually there's selected modules.

Reason: this could be confusing on complex workspaces with docens of modules and cables, that menu seems to saying that I have a selection somewhere.

[sl23]

What's the lfo dot?

[MuTools]

On a MUX workspace, In the menu and where it says "New MUX from selection", it should be Grayed if actually there's selected modules.

See the next M10.0.50

[jd88]

Feature Request: (So, really not important. Only will be fine if maybe you can do this. I understand If not, because really; MuTools and MUX is very complex and cool like it is I only missed those functions while testing MUX / Polysynth):

01. "Freerun" LFO's withing Polysynth ". Actually it seems that LFO working allways in KS mode - reset for each new note (maybe if I cut/mute the "Event" stream like it works outside of Polysynth. There Freerun works fine. But I cannot route the Moddata into Polysynth)

02. Balance between 2 Moddatastreams (green cables). Actually we've this for Audio. I didn't find this inside.

03. A/B - Switch (maybe more: c/d ... for Modulationdata - green cables) to change between source data and route to different targets.

04. Combined switches with more then one Destination (like the knobs above in MUX) that can send one or more Data, so that I can send a block of Mod- or Parameter Data. We can do this outside of Polysynth with the Drumpads.

05. Controller-Filter for each OSC in Polysynth. As example: Actually we cannot Filter CC64 for the Noise OSC or one separate OSC (btw: their / an Envelope).

06. Keyfollow in Envelopes.

OK, only wishes. No must-have.

- - - - -

Thx for your quick Bugfix. Perfect support.

reg.

[MuTools]

01. "Freerun" LFO's withing Polysynth ". Actually it seems that LFO working allways in KS mode - reset for each new note (maybe if I cut/mute the "Event" stream like it works outside of Polysynth. There Freerun works fine. But I cannot route the Moddata into Polysynth)

You can do that by indeed putting an LFO outside the PolySynth.
Then add a Modulation Input inside the PolySynth.
Then connect the outer LFO to the mod in jack of the PolySynth.
Now inside the PolySynth you can use that modulation input, which comes from the outer LFO to modulate things.
Attached a draft example preset.