Release 1.9.0-RC2

[falkTX]

Hello all. This is a bugfix for the previous 1.9 release candidate.

We made a few fixes since RC1, some that need a bit more testing,
Everyone that has 1.9-RC1 build installed, please update as soon as possible.
Those who are beta testers will get this upgrade in their mod-ui notification panel.

Please refer to the RC1 topic to read the changes made in 1.9:

Release 1.9.0-RC1

Hi there everyone, another major release is here - v1.9.0-RC1 aka “The X marks the spot”. This release finally enables the Duo X CV and EXP ports. We added a couple more things surrounding CV as well, so Duo users also have a reason to update. Please note that this is a release candidate. That means it might be stable, but needs more testing first to make sure. If no issues are found in around 2 weeks we’ll release it as stable, otherwise we’ll do a RC2. So, what’s new? CV …

Here’s the changelog for RC2:

• add LED animation for Duo bank navigation with footswitches
• fix some plugin knobs rendering incorrectly on Google Chrome
• fix Duo X device volume and CV labels displaying old values
• fix parameter toggles and bypass not working with CV out addressings
• fix preset addressing causing slowdowns or device lockup
• fix MIDI DIN handling of active sensing messages
• reduce cpu load from the new smooth peak-meters
• support mod:volts as parameter unit

---

Here’s the manual download link:
Duo: http://download.moddevices.com/releases/testing/modduo-v1.9.0.1173-RC2.tar
Duo X: http://download.moddevices.com/releases/testing/modduox-v1.9.0.1172-RC2.tar

The upgrade procedure is explained at the top of our releases page, here:
http://wiki.moddevices.com/wiki/Releases

---

We hope you’re enjoying your MOD Duo and/or MOD Duo X.
Let us know if you find any issues.

[aspiers]

reduce cpu load from the new smooth peak-meters

I guess this will fix the high CPU we were seeing?

[plutek]

side-note: having done a bunch of work now with the new meters, i’m finding they’re working nicely for me!

[plutek]

one weird thing which i have noticed on this release:

when editing a pedalboard in the browser GUI, the virtual pedalboard graphic display often jumps down to a very small size (showing in the top-left corner of the virtual pedalboard space in the browser winder) right after adding a plugin. then, within less than a second, it jumps back out to regular size.

…not a big deal; everything still works. it’s just an annoying little oddity!

anyone else seeing this?
i’m editing in firefox on manjaro linux.

[falkTX]

when editing a pedalboard in the browser GUI, the virtual pedalboard graphic display often jumps down to a very small size (showing in the top-left corner of the virtual pedalboard space in the browser winder) right after adding a plugin. then, within less than a second, it jumps back out to regular size.

It is not new for this release, it is something that changed in Firefox that is causing this behaviour.
There was the same issue regarding zooming to plugins, for which I added a workaround. Need to find a way to correct for this too…