jvkr

A midi file with at least two tempo changes an a few meter changes will not be read properly by the detonate object. There's not an easy way to test it. But exporting an existing file will affect it's total duration. This patch and midi file help to investigate.

bug-detonate

I didn't really properly describe the problem, sorry. What I see is that upon the first tempo change, the old tempo will be used to calculate time values.

(btw. how did it happen that a few objects generated hundreds of lines of code in the first post?)

It's the [detonate] instance that produce all this code. Look at the .maxpat, the [detonate] description has a very big "name" field, it looks like it contains the file you imported.

jvkr wrote on Thu, 05 March 2009 09:06(btw. how did it happen that a few objects generated hundreds of lines of code in the first post?)

Ah, of course, I should have re-instantiated the object. This is shorter. Thanks.

Quote:It's the [detonate] instance that produce all this code. Look at the .maxpat, the [detonate] description has a very big "name" field, it looks like it contains the file you imported.

Is there a way to know about the tempo (bpm) of a midi file or it's duration?

Hi!
Is there a way to know about the tempo (bpm) of a midi file or it's duration?

dont know about tempo, but this is what I use to reckon a file's duration {input: file-path, output: time in seconds (f)}:

[bug?] detonate