Closed SchittBull closed 5 months ago
Thanks for your report! I was able to replicate this bug. NB "lower number" refers to the destination track number, so in order to replicate, the second send needs to go to a lower track number than the first
Fixed and deployed, thanks again for your report – feel free to sync and confirm fix here
Thank you for the quick fix :)!
When adding a send to a track that already has a send applied with a lower number, the send settings are applied to the send with the highest number instead of the newly created one. reaper_ojMPIDvjna.webm