I’m not sure if that has been reported already but there has been a bug with Explode/Reduce since it has been introduced, that I stumble across every once in a while and just haven’t gotten around to report it.
I sometimes work in a way that I need to reduce notes right before needing to explode them again. E.g. I’m collecting all notes from string harmonies that I then want to distribute differently to e.g. the woodwinds. For this task I select the notes in the strings, press Ctrl+C, select one staff in the woodwinds and reduce them to that staff as a placeholder. I then copy that selection again, select the individual woodwind staves and explode to these.
However in that process there is a bug that apparantly has to do with the selection. After reduction, the chords remain selected. However if I use that selection to copy and explode, the result will not be as expected with explode creating multiple notes where there shouldn’t be. To make it work I have to deselect after Reduction, Select again, Copy and then Explode.
It is not a huge deal but it would save me quite some time if it worked straight away without needing to deselect and reselect.
Robin

