This is mainly a thread to verify a limitation in the detonate module I have found, as it seems there is no workaround inside of Max that I know of.
What I am trying to do is to load a MIDI file into detonate in MAX, and then have it start at some place other than the very beginning. The closest command to accomplishing this seems to be the "nth" command, where sending an integer causes detonate to output the information for the event at that note number, but the problem here is that after it does that, it does not continue to the next note afterwards (using the next command), instead it goes back to the beginning.
There is also the "startat" command, however this is not very useful, since it looks for event parameter arguments that can quite easily apply to more than one note in the file – in this case it finds the first note in chronological order to hold the parameters described in the arguments, but what if one wishes to call the 2nd, 3rd, 4th, etc. note that holds those parameters, and not the first?
Anyways, my work around is to pre-process the MIDI file I am importing so that everything before the place I want to start working with the file I chop off, but this is frustrating because I don’t feel it should be necessary.
If only there was a way to combine the nth and startat messages, and have the file startat the note number you specify with nth, and then continue onwards from there!
I would develop this feature into the detonate module myself gladly, but alas, it appears we are only able to create new objects for MAX, not modify existing ones, at least as far as I can tell.
To rebuild detonate entirely from the ground up including the feature I desire would be more trouble than it’s worth, I am sure!
Anyways, thanks for anyone who can help me verify this limitation, or perhaps propose another workaround. If I am wrong in assuming this limitation based on the experimentation I have already done, I will be very pleasantly surprised!