new version of Bonk~ not creating index of detected sounds
I am performing an older patch that uses bonk~. With the update it no longer worked so I downloaded an updated 64 bit version by Volker Bohm. I was able to implant it and it everything worked except for the "index of detected sounds" that previously came from the cooked output. Before this would count up on each strike in training mode but it no longer behaves this way. The help file still shows this is the way it should work but I cannot get this port to work this way anymore. Any help would be appreciated.
Hello, it should report a new index on each new sound (not each strike).
A quick check against Pd's [bonk~] seems to confirm that.
Did the old [bonk~] behave differently?
Hi Volker,
I was hoping I would get to you here. I figured since you created this version you would be the best help. First of all thank you for the 64 bit version. Here is the issue specific to the piece. When I enter training mode in the previous version. I would strike the drum 10 times to train it and the yellow box would count up from 0, 1, 2, 3, 4 etc. On this specific patch I do this 3 times. I strike the drum 10 times (0-9), I scrape the drum 10 times( 10-19) I strike the rim 10 times (20-29). Then through out the piece when when it recognizes a 0-9 sound it triggers a certain sound and when it recognizes a 20-29 sound it triggers something different.
In your version port 2 (the cooked output) does not give me a counting up list. It jumps back and forth between an number between 1 and 10. This is true in the help file and in the patch I am using. They are both set up the same from cooked port with a $1 message leading to an integer box. When I do a print object from the second port I get a single digit between 1 and 10 followed by 2 numbers with decimal points. I assume the first single digit should count up in order but it does not. It seems random.
Any ideas?
When I enter training mode in the previous version. I would strike the drum 10 times to train it and the yellow box would count up from 0, 1, 2, 3, 4 etc. On this specific patch I do this 3 times. I strike the drum 10 times (0-9), I scrape the drum 10 times( 10-19) I strike the rim 10 times (20-29). Then through out the piece when when it recognizes a 0-9 sound it triggers a certain sound and when it recognizes a 20-29 sound it triggers something different.
Sorry, don't have time for extenisve help currently, but this doesn't sound like the intended behavior of the object to me. Did you write that patch yourself (can you send it?) and which version of bonk~ is it originally using?