Glide Time doesn't work in any synth engine for Aftertouch/Pressure when assigned.

Bug Description

Assigning glide time in any synth engine that has it and applying it to the aftertouch/pressure doesn’t seem to work for me at all no matter the value. Glide time does work if i manually do it from the parameter knob without applying it to the aftertouch/pressure section though.

Steps to Reproduce

Click main encoder by screen and go to macros

Then go down to aftertouch/pressure

then in slot 1 hit set parameter middle button under screen

Now tap your engine button until you see glide time on your screen and then tap that glide time knob

Now glide time is set to slot 1 on aftertouch/pressure

Adjust your values down or up, but nothing happens when playing.
You should be hearing the gliding between notes when applying pressure to the pads but nothing…

Occurrence / Frequency

Always

Found in Firmware

  • Version: Synth_v1.3.0.1842beta
  • Build: 1842

Attachments

@Sandroid @3xm @Dann @miropoly @Mitch could any of you test and confirm? Would like to know if 100% bug or my unit or user error :stuck_out_tongue:

Before i test it. i‘m curious if this should even work.

So if i understand you correctly, your testcase is the following:

  1. You press one pad and engage glide via aftertouch
  2. And then you expect glide if you press a secondary pad

But.. wouldn‘t glide time be reset until you reach aftertouch and thereby never trigger?

I mean either this is the reason why it doesn‘t work, or may even be the answer why it doesn‘t work :grinning_face:

1 Like

Hmm if it wouldn’t work why make parameter available for aftertouch/pressure is my question lol.

Very good question. Let’s see if the team can provide us with an answer :smiling_face_with_three_hearts:

1 Like

Hi @BROCKSTAR Thanks for reporting this! No need to tag us directly — just posting the bug is enough and we’ll take a look when we find time. We always reply to every repot. Appreciate your help in tracking this one down! :blush:

2 Likes

Thank you and sorry for the tagging. Glad it was a bug and just not user error or my unit :smiley: