MuLab 10.2.29 beta

[MuTools]

As i'm currently focused on M10 VST3 development, which is quite a job, i've not yet explored the new Windows MIDI Services. I had a quick look at the basic info now and it looks interesting at first sight. It also looks like the legacy MME MIDI system still is supported, which is consistent with Microsoft's tradition of respecting legacy APIs for quite a long time. So if you encounter any trouble with your MIDI setup first thing todo is check the MuLab log file. Look for the log lines around "Started the MIDI engine". Also try re-setting up your MuLab MIDI ins/outs via MuLab menu -> MIDI Setup.

[pekbro]

As i'm currently focused on M10 VST3 development, which is quite a job, i've not yet explored the new Windows MIDI Services. I had a quick look at the basic info now and it looks interesting at first sight. It also looks like the legacy MME MIDI system still is supported, which is consistent with Microsoft's tradition of respecting legacy APIs for quite a long time. So if you encounter any trouble with your MIDI setup first thing todo is check the MuLab log file. Look for the log lines around "Started the MIDI engine". Also try re-setting up your MuLab MIDI ins/outs via MuLab menu -> MIDI Setup.

Thanks jo

*Firmware update corrected the issue

[tiger001]

So my midi devices are not working as they used to, is it possible this has anything to do with the new midi services in win 11? Just trying to track the problem down, it's possible that I have not used some of the HW since before the midi services rollout.

Sending the clock out from mulab to the device no longer works for example.
I have verified that the new service is installed and working on this machine,
it was done with no involvement from me no less.

thx

this in dutch but i'm sure you get the idea:
https://synthforum.nl/threads/3832336/#post-4095676

from steinberg (forum)
https://forums.steinberg.net/t/the-micr ... fo/1025581


Jürgen Moßgraber YT channel:

2:52 Windows 11 MIDI 2.0 Issues & Workarounds
8:38 App SDK and Tools Release Candidate 3

[pekbro]

Thanks, all I needed (so far) was a firmware update fortunately. Jo was quite correct in my case.

[MuTools]

MuLab App M10.2.7 beta is available:

Update 27 March: Removed the link as a too serious bug has been discovered.
Stay tuned for the M10.2.8 update, coming soon.

What's changed:

• Virtual MIDI Keyboard now supports different MIDI channels.
  Use the option buttons to define a MIDI channel for the top keyboard and for each row.
  If a MIDI Channel is set to "Auto" then the focused MIDI channel of the target module is used.
• Virtual MIDI Keyboard: Together with adding channel support, the VMK now also uses the project's MIDI Input Channel Targets.
  These 2 enhancements work together and now allow the VMK to play various target modules in the project.
• The piano keyboard at the top-right of the project editor now has the exact same behavior as the piano keyboard at the top of the Virtual MIDI Keyboard, thus also using any defined MIDI channel. By default, things still work the same as before though, it will only make a difference if you explicitly set things up differently.
• "Display Focused MIDI Input Target" now shows the info in a steady alert, not in a temporary tooltip. The info now also includes the target module's focused MIDI channel.
• Improved upgrading of M8 projects that contain tempo events.
• Fixed a serious timing issue on the output events coming from a VST3 plugin.
• As of M10.2.1 the Modular Feedback Delay did not properly work until its On/Off switch was toggled. Fixed.
• Drag-dropping a composer or (Rack-)MUX to another modular area trashed the internal modular structure of that composer / MUX. Fixed.
• The project main module now is drawn in a bigger box to emphasize its importance.
• Fixed a couple of issues when editing clip/event times/lengths using their numeric display.
• Internal code refactorings in preparation of MuLab Plugin VST3.
• Other small improvements.

Attention: Due to the heavy developments wrt MuLab Plugin VST3 this update should be handled with care. Please do report any new issues with this update. Thx!

[ortseam]

Thank you for your work on MuLab Plugin. Looking forward to testing it!

Could you please make it more clear for me: whether MuLab Plugin VST3 will exist alongside MuLab Plugin VST2, or will VST2 be replaced by VST3?

[MuTools]

It has not yet been decided, but what i expect is that there will be a crossfade period where both will be available, but fading out the VST2 version.

[heks]

If MuLab goes vst3 I hope it will be made to be able to load vst2 plugins. I ask, as I have a few old vst2 plugins that I find "just work" for me and for "backward compatibility" with older projects that I have had to put to one side, to then hear with "new, fresh ears" .

[Cochrane]

Yes, please do not remove VST2 plugins hosting: a lot of old projects could depend on it.

[MuTools]

My answer was about MuLab Plugin VST2, not about hosting VST2 plugins.
I expect that hosting VST2 plugins will survive longer.
Not sure how long though.

By the way: It's recommended to upgrade all your projects to the MuLab 10 file format.
MuLab has some helper functions for that, see https://www.mutools.com/info/M10/docs/m ... jects.html
Maybe meanwhile you could replace some VST2s by VST3s?
Especially on Mac older VST2s could get into compatibility problems when Apple applies another drastic change in MacOS.

[MuTools]

MuLab App M10.2.8 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Fixed a recent new crash bug when using an Event Delay module.
  That's the case in almost all MuDrum MUX presets and MuClips.
  This crash bug originated in M10.2.7 as a consequence of the internal refactorings in preparation of MuLab Plugin VST3.
• Virtual MIDI Keyboard: Each row can now be set to "Always Active" which makes that row active even if the Virtual MIDI Keyboard is not on screen.
  So such Always Active keys work as soon as the project is loaded. May also be handy for live setups.
  Memo: Now that the VMK keys can also be set to a specific MIDI channel, you can map VMK keys to any module in the project by also using the MIDI Input Channel Targets.
• Virtual MIDI Keyboard: The GUI Key can now be edited per key pad by clicking it. Presets still are available per row.
• Virtual MIDI Keyboard: Right-click key pad for MIDI channel and Always Active settings for that individual key pad.
• Virtual MIDI Keyboard: All setup data now is stored in the project.
  Previously the keyboard keys were stored in the app settings, the MIDI keys in the project. That could feel confusing/inconsistent, and so that's past now. The same for VMK preset files, they now include all data.
• Modular Areas: Cable editors now have an integrated signal monitor for quickly monitoring/diagnosing the signal flow. No more need to insert a Audio Mixer Strip / Event Monitor / Modulation Monitor for that purpose.
• Modular cable editors now store their position+size in the project/preset file.
• Changing the project's Main Module did not immediately redraw the relevant modular areas. Fixed.
• Other small improvements.

[pljones]

> Modular Areas: Cable editors now have an integrated signal monitor for quickly monitoring/diagnosing the signal flow. No more need to insert a Audio Mixer Strip / Event Monitor / Modulation Monitor for that purpose.

Fantastic!

> Changing the project's Main Module did not immediately redraw the relevant modular areas. Fixed.

That reminds me... I've sometimes found changing the main module messes up the front panel that's shown. I've found it incredibly hard to reproduce reliably, hence no bug report... But just so you know there's maybe something weird there.

[pljones]

Slight gotcha on the cable signal monitors. If I open the top level modular area and right-click Edit on an event input, the mini-monitor pops up. But it doesn't show events. The event monitor module I have at the end of the cable from the Project event input does, though (with some nice enhancements I'd not noticed before). I tried it on the cable joining that to the input of the Composer module. Still nothing. So I went into the Composer modular area and clicked edit on the event input there. That one showed events.

[MuTools]

Changing the project's Main Module did not immediately redraw the relevant modular areas. Fixed.

That reminds me... I've sometimes found changing the main module messes up the front panel that's shown. I've found it incredibly hard to reproduce reliably, hence no bug report... But just so you know there's maybe something weird there.

Note that the project editor always shows the editor of the project's Main Module.
The most typical case is that the project's main module is a composer module and hence the project editor shows the composer editor, which all looks like a typical DAW.

But the project's main module can be any module, and as of M10.2 it can be a module on any modular level. Changing the project's main module will update the project editor to show the editor of that new main module.

Does this clarify it?

[MuTools]

Slight gotcha on the cable signal monitors. If I open the top level modular area and right-click Edit on an event input, the mini-monitor pops up. But it doesn't show events. The event monitor module I have at the end of the cable from the Project event input does, though (with some nice enhancements I'd not noticed before). I tried it on the cable joining that to the input of the Composer module. Still nothing. So I went into the Composer modular area and clicked edit on the event input there. That one showed events.

Please see this doc page:
https://www.mutools.com/info/M10/docs/m ... uting.html