# VAP Synth: pop and clicks related to square wave LFO modulation

**URL:** <https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196>\
**Category:** Bug\
**Tags:** play-plus, synths-playplus, play, logged\
**Created:** [December 9, 2023, 11:30pm UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196 "2023-12-09T23:30:54Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![radfaraf](https://backstage.polyend.com/user_avatar/backstage.polyend.com/radfaraf/32/1296_2.png) [@radfaraf](https://backstage.polyend.com/u/radfaraf)\
**Post date:** [December 9, 2023, 11:30pm UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/1 "2023-12-09T23:30:54Z")

</div>

### Bug Description

I discovered a (VAP) synth patch settings that cause clicky and poppy noises and other distortions. The particular patch settings I used if I switch the Filter Type to other ones the problem still remains on what seems like each of them, but the amount of the issue varies a lot. In this case I noticed the problem goes away if I switch LFO 1 - waveform from square to something else like Triangle, or Random S&H as two examples. A quick test seems to indicate all filter types work fine after doing that. Check the other first related link for a recorded video example with another synth patch that sounds similar.

### Reproduction Steps

1. Sequence any pattern with the included “$ Pops and click.patch”
2. Press play and notice the distortions and clicky and poppy type noises.

### Occurrence

Always with the given sound patch file I made.

### Found in

_go to Config \> Firmware page on your device and copy version / build numbers below_

- **Version** : [1.0.1 beta]
- **Build** : [1376

### Attachments

[$ Pops and click.patch.zip](https://backstage.polyend.com/uploads/short-url/pubNHREU9yymQAGEwqwuk2j8SS5.zip) (580 Bytes)]

### Other synth sound issues possibly related they all produce similar sound issue

> [@FAT Synth: pop and clicks related to LP MG 24dB filter](https://backstage.polyend.com/t/play-a-fat-synth-patch-i-made-causes-sound-glitches-like-pop-and-clicks-related-to-lp-mg-24db-filter/6984):
>
> Bug Description I accidentally discovered a (FAT) patch settings that cause clicky and poppy noises and other distortions. The particular patch settings I used if I switch the filter from LP MG 24dB to another setting like LP OB 24dB the issue goes away. It also goes away if I take the LFO from Ramp Up to something else like Ramp Down. It doesn’t go away from changing LFO Retrigger settings. Trying the same filter on other synths also doesn’t instantly create the bug, but must have to do with ot…

> [@Artifacts with LP MG 24dB Filter when having fast Cutoff changes in lower frequency range](https://backstage.polyend.com/t/glitches-and-freezes-in-play/6950):
>
> Bug Description While playing glitches and freezes occur. It sounds like a processor overload. I can force more glitches and freezes when I load additional samples. Reproduction Steps Create a project with 3 synths and 8 audio tracks. Hit play. Occurrence The heavier a project the mor often it happens. Found in Version: 1.0.0 Build: 1354 Attachments I am not allowed to

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [December 10, 2023, 3:01am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/2 "2023-12-10T03:01:15Z")

</div>

Thanks for sharing your .patch. Gonna load it up in a bit and will report my finding.

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [December 10, 2023, 3:47am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/3 "2023-12-10T03:47:09Z")

</div>

Hey @radfaraf, thanks for logging your bug. Something I’d like you to try to see if you can replicate what I’m experiencing.  
Having your patch loaded and some notes playing to hear the gliches

1. Go into the VAP engine assigned to your patch.
2. Go into edit patch and scroll all the way down to the -----Modulation----- secition of the patch editor.  
You should see that your Src 1 is assigned to LFO 1 with Amt 1 set at 200%
3. Select the Amt 1 parameter currently set at 200% and bring the amount down. Does the glitching go away for you when you go lower than about 150%?

I’m gathering that this is part of Polyend releasing the firmware with the patch editor in a public beta form that is not fully optimized for a full firmware release. I’m seeing all of the Amt destinations in the Mod matrix going up to 400% and that for me looks more like a testing range rather than something that would be implemented in a more stable non-beta firmware. Anything over 100% seems a bit bizarre on a mod matrix level unless each of the sources had their own amount level which is not the case in the synth engine.

---

<div class="post-metadata">

**Author:** ![radfaraf](https://backstage.polyend.com/user_avatar/backstage.polyend.com/radfaraf/32/1296_2.png) [@radfaraf](https://backstage.polyend.com/u/radfaraf)\
**Post date:** [December 10, 2023, 4:02am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/4 "2023-12-10T04:02:34Z")

</div>

I see if I put all the matrix stuff there to 100% for that sound instead of 3 of them I set to 200% the issue still occurs, but way less of it, and on most filters not at all. I have no idea why it lets those big values either, but since it lets me I did it! Plus it sounded like it was helping the sound up until some point till it didn’t 😃

Still hearing it a bit on LP OB 24dB and LP OB 12dB for that sound. With the the 3 modulation sources all set to 100%. 150% seems too high hear a lot more of it at that level even with just 1 modulation source set to 150% and the rest 100%

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [December 10, 2023, 4:12am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/5 "2023-12-10T04:12:33Z")

</div>

Thanks for sharing your findings If you have the time to go through the specific steps I outlined previously it would help quite a bit. I’m pretty sure the problem is specific to the modulation on Src 1 going past a certain threshold. Would love to know if keeping your original patch as it is and only decreasing the Amt 1 of Src 1 lower than 150% removes those glitches for you.

---

<div class="post-metadata">

**Author:** ![radfaraf](https://backstage.polyend.com/user_avatar/backstage.polyend.com/radfaraf/32/1296_2.png) [@radfaraf](https://backstage.polyend.com/u/radfaraf)\
**Post date:** [December 10, 2023, 4:19am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/6 "2023-12-10T04:19:54Z")

</div>

It seems like you’re thinking I am talking about something else, but we are talking about the same thing (I did what you said). I did only the one mentioned at first and since it didn’t work completely I did the others, and all 3 isn’t even enough to fix it though it is hugely better.

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [December 10, 2023, 4:25am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/7 "2023-12-10T04:25:21Z")

</div>

Sorry, maybe I’m misunderstanding somewhere;

> [@radfaraf](#):
>
> I see if I put all the matrix stuff there to 100% for that sound instead of 3 of them I set to 200% the issue still occurs, but way less of it, and on most filters not at all. I have no idea why it lets those big values either, but since it lets me I did it! Plus it sounded like it was helping the sound up until some point till it didn’t 😃

I’m having trouble to read where in this txt you’re going through the step by step that I described. Sorry if I am misunderstanding something.

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [December 10, 2023, 4:29am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/8 "2023-12-10T04:29:19Z")

</div>

Could you share that patch with your adjustments that are better but don’t work completely?

---

<div class="post-metadata">

**Author:** ![radfaraf](https://backstage.polyend.com/user_avatar/backstage.polyend.com/radfaraf/32/1296_2.png) [@radfaraf](https://backstage.polyend.com/u/radfaraf)\
**Post date:** [December 10, 2023, 4:35am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/9 "2023-12-10T04:35:19Z")

</div>

[$Pops and clic2.patch.zip](https://backstage.polyend.com/uploads/short-url/gKs4j2mqVusoTyyik0IAwIGbg92.zip) (577 Bytes)  
Here’s the file I changed all 3 modulation settings that were at 200% to 100% in this one. Still hear the issue, but a lot less.

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [December 10, 2023, 4:47am UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/10 "2023-12-10T04:47:16Z")

</div>

Cheers! That helped alot and is concurrent with my findings.

If you go into the -----Filter------ section and bring down your cutoff frequency, I think your problems should be solved.

The current synth engine seems to have an issue to deal with values above the max. Cutoff Frequency. In your patches, the Cutoff is almost fully open, and sending high levels of modulation that brings it much higher than it’s max setting, and I think that is what is causing the erratic behaviour.

---

<div class="post-metadata">

**Author:** ![radfaraf](https://backstage.polyend.com/user_avatar/backstage.polyend.com/radfaraf/32/1296_2.png) [@radfaraf](https://backstage.polyend.com/u/radfaraf)\
**Post date:** [December 10, 2023, 2:35pm UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/11 "2023-12-10T14:35:21Z")

</div>

For the things mentioned in this comment I setup my notes just using 4 notes equally spaced with note length set to 3.00. Then I set them to minor chord using the “sample start” knob button. Using chords makes the issue a bit worse because more notes at the same time.

Still running into the issue with much lower cutoff frequency, for instance I still get it with 3.10kHz (max is 19.3kHz) and with LP OB 12dB. Even quite a bit lower, but it does become really hard to tell at some point where exactly it stops because the lower the cutoff the less of the issue is heard.

Still using the above note settings:  
24dB filters also make it trigger more easily.  
I also see for instance if I change Filter type to LP MG 24dB it will keep sounding extremely bad even at the lowest of 20Hz on the filter cutoff and with both chords and no chords being used. This one actually seems to get much better at a real high cutoff. Other 24dB filters also seem to need higher cutoff and not lower.

---

<div class="post-metadata">

**Author:** ![miropoly](https://backstage.polyend.com/user_avatar/backstage.polyend.com/miropoly/32/45_2.png) [@miropoly](https://backstage.polyend.com/u/miropoly)\
**Post date:** [December 11, 2023, 5:36pm UTC](https://backstage.polyend.com/t/vap-synth-pop-and-clicks-related-to-square-wave-lfo-modulation/7196/14 "2023-12-11T17:36:44Z")

</div>

Hi @radfaraf , thanks for reporting this bug with so much detail. We’re sorry you’re having issues with our products. We’ll let you know if we can improve this behavior and fine tune the ranges to avoid these more extreme settings. Thank for your support!
