When the LFO 1 or LFO 2 retrigger parameter is selected as a destination for the applied value given by the respective macro knob, the LFO retrigger setting (Note-One Shot-Free Running) does not shift as the macro’s value changes.
Currently, I have only tested this on the WTFM synth. Though the bug may persist in other synth engines, the following steps assume the use of a WTFM patch.
Steps to Reproduce
Open a new project and load an inital patch and set an LFO to an audible parameter (e.g. Filter Cutoff)
Set the LFO’s retrigger behavior to “Note”
Within the synth settings, select “Edit Macros” and select an empty macro to set the modulating LFO’s “Retrigger” to Parameter 1.
Set Amount 1 to any positive value, but for all intents and purposes, use .50
Place a few notes on a track that allow for the LFO’s modulation to be heard
Adjust the respective macro to change the behavior from “Note” to “One Shot”
When this adjustment is made, the user will not experience the change in behavior in the same way as if it were adjusted from within the patch settings. Instead, the behavior stays the same, as if no value had been applied to it at all.
Did you check whether changing the Retrigger via Macro is audible with a synth patch longer than the “init” one? Other than that, did you select the track you want to apply the change to ?
While I didn’t cross-check my findings with an explicitly longer patch, I did initially run into it while creating one and decided to revert back to the “Init” patch to test it before handing it over to you all for inspection. I am 99% sure I had the track selected while making adjustments to the macro also, but it has been a minute since I’ve looked into this and mistakes do happen.
I have some extra time today, so I’ll retest the issue with these things in mind and get back to you. If there’s anything else I can do, just let me know and I’ll do my best to give a hand.
Thanks for taking a look at this for me. It seems I set my values for the macros too low in the patch that I was working on, possibly in an attempt to only shift from one to another vs all three, which lead to the parameter not shifting at all. In a new project, I loaded up the Init patch for the FAT, VAP, and WTFM patches and extended the DRs for each envelope and gave considerable note length so that I could hear each LFO as I increased their respective retrigger values via a macro (with the track selected) and it worked like a charm.
I know that in the initial comment, there was mention that the LFO retrigger settings weren’t actually meant to be adjustable by macros, but since they are, I’d like to leave my 2 cents about it, if you don’t mind. As someone who loves designing with the Polyend synths, a big part of my design philosophy is to find the balance of pragmatism and experimentation. While it may seem like a lesser used parameter for the macros, being able to “flip” retriggering is a great way to get new sounds out of old settings, especially with the VAP and WTFM dual LFOs. I’m sure you already know all this but, just in case it’s on the chopping block, I’d like to put a good word in for it’s use case.
Thank you so much for taking the time to share your feedback!
Sorry for the confusion caused by the change to my earlier comment We had a little discussion here about retrigger and whether it makes sense to keep it as a macro destination. Now that we’ve confirmed it works as intended, I think we’re going to leave it as is. Thanks again for sharing your use case – it’s always nice to hear that users are making the most of their devices.
) and it worked like a charm.
We had a little discussion here about retrigger and whether it makes sense to keep it as a macro destination. Now that we’ve confirmed it works as intended, I think we’re going to leave it as is.