ronso0
ronso0
Sure! Sorry, I though that was clear looking at the caveats with 'calibration', even though it looks OT. 1. FWIW with #14124 it'll be much easier for mapping developers to...
The CO is `xFaderCalibration` so 🤷 Right now it's neither documented nor appears in the preferences GUI (and there are no plans to expose it there, and even then I'd...
Did someone try to reproduce this? Both the loop anchor option and the slip waveform are very nice features, but tbh I consider this conflict a blocker since it creates...
I'm using rolling loops with the IN anchor. Just noticed this while the anchor was still set to END from a test routine. I think that's it: just set the...
This bug occurs with 2.5 and #13422 was for main where I don't see the slip mode wave at all.
I merged 07113fdf314afdf09998f79d8d7571f041877c68 into 2.5 and it still looks like this, the original wave is offset by the loop size with LoopOut anchor. 
> I'm not sure whether this is expected behaviour or actually an issue. As it stands, the exit point is exclusive, so when you set the loop with anchor=exit, you...
Yeah probably, I'll try the loop/slip stuff in real sessions and come back when I have ideas / proposals ready.
Let's remove it from the 2.5.2 milestone.
I didn't pay attention to the slip waveform lately when using rolling loops or reverse slip. We can close this and reopen if someone notices an issue.