nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unison bug in Massive X

Side Key

I found a annoying bug in Massive X.

When I try to automate the Unison On/Off parameter in Ableton Live, I correctly configure the Unison state on the timeline. However, as soon as I record the automation, Massive X automatically records the Voicing (number of voices) parameter instead, even though I never intended to automate it.

The problem is even worse: when I enable Unison, Massive X changes the Voicing parameter by itself and overwrites my automation lane. As a result, the automation no longer controls only the Unison On/Off state but also the number of voices, which is modified automatically.

It seems that the Unison and Voicing parameters are internally linked. As a result, Massive X automates the wrong parameter and modifies existing automation data without any user intervention.

Find more posts tagged with

Massive X

Ableton

Comments

chk071

When I try to automate the unison on/off parameter in Studio One, the sound simply cuts off, and there's no more sound after the unison is switched on.

That said, I never felt the need to automate that particular parameter though.

Side Key

I needed to automate the Voicing on/off on a funk bass line, and I was unpleasantly surprised to see the polyphony setting join the party ! 👻

Quick links

Unanswered questions