Adding Polyphony incorrectly initializes Synth voices excluding parameters assigned to Macro7 (Velocity)

Bug
, , , , , ,
1

Bug Description

UPDATE:

I started a simple patch from scratch to nail down the problem.
Its highly possible other engines are affected too, but for a reproducable report i simplified the process.

Description:
When you assign filter cutoff to m7 velocity with a definded amount and change polyphony, it breaks the dialed in amount and sets it to zero.

Steps to Reproduce

  1. In synth engine set polyphony to 1.
  2. In FAT engine set the sustain to 50% so you hear a sustaining note when holding any pad.
  3. Go to M7 and assign Filter cutoff to Parameter 2, set the amount to something like 0.15 to open the filter a bit.
  4. Change polyphony to 2 and back to 1
  5. Press pad, filter is closed.
  6. Go back to m7 and turn the amount for filter cutoff a tiny bit. Filter suddenly opens up again to reflect the dialed in amount.

Another observation, it only happens when polyphony is changed upwards. Doesnt happen from 2 to 1 or 3 to 2 but always 1-2 or 2-3 etc.

Occurrence / Frequency

Always

Found in Firmware

Tracker+

  • Version: 1.0.3
  • Build: 1138

Play+

  • Version: 1.2.0
  • Build: 1928

Attachments

–

2

I got it i think, it affects M7 Parameter 2 Filter Cutoff in the Velocity Macro.
Is this a normal behaviour or should it be unaltered when changing polyphony?

3

CONGRATULATIONS! :tada: You win award for best bug title 2025 :trophy:

5 Likes
5

I will change it to a more reasonable description as soon as i know what exactly causes the issue.:grinning_face_with_smiling_eyes:

6

I found it..finally. will change my bug report.

7

Hi @Patrick , thank you for the detailed bug report! After analysis, it seems that this behavior is not limited to just the Filter Cutoff parameter in M7, but appears to affect all parameters assigned to the Velocity macro (7). Interestingly, this bug doesn’t seem to affect other Macros (1-6).

Also, as you mentioned, the problem happens when you add Polyphony = only to new synth voices. We’ll have to investigate this further to confirm the root cause, but your report helps narrow down the issue.

Thank you for your persistence and patience! We really appreciate your effort and will send an update when this is resolved.

1 Like
8

P.s. I updated the title to reflect this, because of course, I miss the “italo” part :italy: :musical_notes: :wink:

1 Like
11

You guys rock!:heart: I’m also going to take a look this evening. Perhaps there’s something more to narrow it down.

Well …this tight italo helped me to nail it down.
Aaand out..

1 Like
12

The issue also applies to latest Play+ release 1.2.0.1928

But not to latest Synth 1.3.0.1846, as it recipes Velocity info with the pads, so they seem to play correctly

I’ll update the tags and versions/builds

2 Likes