This is why we chose not to change the LFO’s behavior for now. You shouldn’t have this issue on the official release.
That’s disappointing. I understand this could be an issue for previous projects. Including mine btw and other people who mentioned this issue. But is still a bug and it doesn’t work as it should. Hope it would be fixed finally. If it would have some “old-style” button, well, that would be great to keep projects as is. But now its just not working LFO.
You can still use the beta with the subdivision fix if you prefer. This is the only change from the beta. Unfortunately the LFO subdivision fix could not be added without altering how the LFO resets so it has to be addressed in a future firmware.
that’s all I wanted to hear! Thanks)
Hello all!
I was experiencing this issue using Tracker + Firmware 1.2.0. I re-flashed the firmware to an earlier version, tested, and found it worked as expected, then re-flashed back to 1.2.0, and it’s now working.
I only tested using a project I created using 1.2.0, and haven’t tested a project from a previous firmware version to see if there are any issues.
Andrew
@mitch im on 1.92 and its not consistent among all destinations. will this be changed to consistent behavior across all destinations for the og tracker? please?
brrrrrrrrrokennnnnnn
just to be clear, i need lfos to restart on every note! there may be a case where people want it not to restart, in which case the PROPER fix would be to add a switch for one behavior or the other!
DUH
Yeah totally.
Sometimes restart on note.
Sometimes not restart on note.
If both are achievable then just add a switch and we’re all good.
Me and @pointandclicksystems talked a lot about this over DM, and myself as well would really welcome this feature. In the older manuals it was clearly laid out what was retriggered and what was not. In recent manuals that information has been dropped and I contend that I would also like to see a resolution to this issue.