The Sumu 1.1 update is out, bringing MPE support as well as a bunch of bug fixes and enhancements. These include:
- gui: fix scrolling after setting default in popup dials
- gui: fix missing update bug when pasting registration
- osc: fix zipper noise in AM mod index
- AU wrapper: fix Obj-C namespace collisions
- fix UI scale bug with muliple displays of different scales
- allow slower LFO times
- increase LFO popup dials precision
- adjust text position for negative numbers in Dials
- increase pulses ratio dial precision
- fix slow LFO sync
- improve host clock sync
- reset pulses hi scale offsets when adjusting past zero
- fixed issue loading state saved by beta version
- added MIDI learn for dials via popup menu
- added main […] menu with gui and input settings
- gui : added numbers on / off menu
- gui : added scroll normal / reverse menu
- input: added protocol [MIDI / MPE] menu
- input: added MPE bend range [ 0 / 12 / 24 / 48 / 96 ] menu
- input: reduced latency of gate and pitch in patcher
- input: added MPE mode
- input: don't reset voice time in unison mode legato
- partials: add interpolation to time dial
NOTE: we are still working on meeting the latest requirements for Windows code signing. Windows will claim that the Sumu installer may be dangerous and you will need to click "Keep anyway" a few times. We'll update the installer as soon as we can address this.
unfortunately the update broke mojave/logic 10.5.1 compatibility -> crashed validation
Are there any optimisations for CPU usage in this release?
Edit - Also unable to run this on Mojave. Message 'Failed to initialize the plugin' running Renoise 3.5.2.
p.s.:
i have a validation report of logic, in case of interest
yes please email me the validation report!
there are no CPU optimizations. that will be my focus for the next update.
No problem at home with the AU version under MOTU Digital Performer 11.35 under Sequoia _
I've tested 1.1 on Max 8.5.7, Bidule 0.9790 and Renoise 3.5.2. Plugin will not load on any of them under Mojave, both VST3 and AU.
Thanks for the info. It looks like there's some validation issue with older systems. I'm investigating.
OK, I still have a 10.13 Mac and I have reproduced this. I have an idea about what might be wrong. I had to switch to a new version of the VST3 SDK and it seems likely that it (or the way I’m using it) has stopped older systems from opening the plugin.
I don't have a way to open a VST3 on this computer, but it should be the same fix as the AU issue.