Yeah or overlap and lock amp attack to a short value so it doesn’t “restart”.
There’'s also a AMP ENV reset on/off button on amp page 2. But I don’t use it as much. It seems a bit bugged out, but I have to dive more into that to make sure. It looked like odd behaviour but maybe I used it wrong sometime.
In similar cases i just hit func - yes. Bring bpm down, live record the automation at zen buddha speed and bring bpm up again after your automation recording. Not satisfied hit func no and start over. Be the lfo.
On trig page set LFO.T to OFF
On LFO page set LFO SPH to 90, LFO trig mode to TRG or ONE or HALF depending on desired fade result. Set wave to TRI. Set speed/mult according to your desired length, and have AMP volume at 110 (default) set LFO destination to amp vol, depth to 127.
On pattern p-lock LFO.T to on for just the first step, you should hear your pattern fading in, then just afjust speed and mult to get desired result.
Let me know if it works.
Edit: if you don’t want the start to be silent try lowering LFO depth to around 80.
Not at my DN to check now, but I was wondering whether the arp triggers the LFO on every “played” note even if there’s only one initial trig in the sequencer. Because that would reset the LFO back down to the minimum value on every note and cause nothing to be heard.
For a simple fade in I don’t see why not using Attackk parameter.
I opened a thread about LFOs some time ago as i find the parameters very conter-intuitive. The drawings of the shapes on the OT don’t make sense at all.
In general the time i found correct parameters is enough to forget what was the idea… but i have a really bad short term memory as i was about to react saying something totally different and forgot it as well
Saving LFO presets would earn a lot of time, especially whenever you want a Sine wave.