Strange bug with tapin/out~, dac~ and set message

Hi,

I encountered a strange issue. A short sound coming in from the adc~, going through a delay pattern using several tapin~/tapout~, should trigger switching the output channel every time the input raises above a certain threshold. Not a big deal, but currently (Max 9.1.4 on MacOS 15.7.3), it gets stuck in an endless loop. I'm sure I've done it before without problems.

This is from a larger patch in which a hit on a microphone should trigger a jump to a random speaker in a multichannel environment. I attached a reduced version, that includes also a few findings from troubleshooting in the comments.

Or why don't I post the comments here anyway, maybe that's a known thing:

1. this test patch should simply play a rhythm upon start of the sfplay~, and with each hit of the vibes coming out from the tapout~ it should switch between channels. But most of the time it gets stuck in an endless loop (sometimes it stops, but most of the time it does not).

2. When that happens, there is no audio coming in into the peakamp~, but a flat value on at least one tapout~ (as you can see in the meter~). Sometimes there are values coming out from more than one tapout~

3. Severing any of the patchcords in the peakamp~ section stops the loop.

4. Moving the delay into gen~ works fine, as does replacing the set message with a gate~ object

5. Changing the vector size to something shorter also shortens the length of the looped sound

Thanks, Hans