robin.meier

what's the easiest way to load and play a type 1 or type 0 midifile with different meters and tempos inside max?

i know detonate and seq, but these don't seem to be able to jump to a certain bar inside the midifile.

i also had a look at seqplayer which seemed perfect but doesn't interpret my tempo-map correctly it seems: when goingn from 3/4 to 3/8 + tempo change things get weird.

there would be ftm too, but i'd prefer not to install it for this simple application...

sequencer-in-max

Unfortunately I don't think there is anything else out there. I would love to have an 

object that would parse a MIDI file so that I could advance to a particular point

in the performance. That seems to be the missing piece that no one has tackled yet.

I am hoping Max5 will have some decent support for this.

> what's the easiest way to load and play a type 1 or type 0 midifile with different meters and tempos inside max?

> i know detonate and seq, but these don't seem to be able to jump to a certain bar inside the midifile.

> i also had a look at seqplayer which seemed perfect but doesn't interpret my tempo-map correctly it seems: when goingn from 3/4 to 3/8 + tempo change things get weird.

> there would be ftm too, but i'd prefer not to install it for this simple application...

Unfortunately I don't think there is anything else out there. I would love to have an 
object that would parse a MIDI file so that I could advance to a particular point
in the performance. That seems to be the missing piece that no one has tackled yet.
I am hoping Max5 will have some decent support for this.

---- "robin.meier"  wrote: 
>
> hello,
>
> what's the easiest way to load and play a type 1 or type 0 midifile with different meters and tempos inside max?
>
> i know detonate and seq, but these don't seem to be able to jump to a certain bar inside the midifile.
>
> i also had a look at seqplayer which seemed perfect but doesn't interpret my tempo-map correctly it seems: when goingn from 3/4 to 3/8 + tempo change things get weird.
>
> there would be ftm too, but i'd prefer not to install it for this simple application...
>
> any ideas?
> thanks,
> robin


it reads and writes type 0 and I midifiles and gives you all raw midi- 

events for you to build your own sequencer.

it's in the package for the timegrid app here:

it reads and writes type 0 and I midifiles and gives you all raw midi- 
events for you to build your own sequencer.

Unfortunately it is for Mac only. I can not open the DMG file, do 

you know if it includes any source for the external?

> it reads and writes type 0 and I midifiles and gives you all raw midi- 

> events for you to build your own sequencer.

> it's in the package for the timegrid app here:

Unfortunately it is for Mac only. I can not open the DMG file, do 
you know if it includes any source for the external?

---- "jasch  "  wrote: 
> check out the [icst.midifile] object.
>
> it reads and writes type 0 and I midifiles and gives you all raw midi- 
> events for you to build your own sequencer.
>
> it's in the package for the timegrid app here:
>
> http://www.icst.net/downloads/
>
> hth
>
> /*j
>


> Unfortunately it is for Mac only. I can not open the DMG file, do

> you know if it includes any source for the external?

> Unfortunately it is for Mac only. I can not open the DMG file, do
> you know if it includes any source for the external?

I tried converting the DMG file using MagicISO but it does not like this file for some reason. 

Is there another way I can open a DMG file? Alternately, if someone could save the DMG as a zip file

> > Unfortunately it is for Mac only. I can not open the DMG file, do

> > you know if it includes any source for the external?

I tried converting the DMG file using MagicISO but it does not like this file for some reason. 
Is there another way I can open a DMG file? Alternately, if someone could save the DMG as a zip file
I would be most grateful. 

---- Emmanuel Jourdan  wrote: 
> On 2 janv. 08, at 18:23,
>  > wrote:
>
> > Unfortunately it is for Mac only. I can not open the DMG file, do
> > you know if it includes any source for the external?
>
>
> Sources are included.
>
> ej
>


I got it open on a Mac and started it up. It looks interesting but there are

I imported a type 0 midi file and all that showed up in the coll was the

file type MThd. It does say "import raw" but who has raw midi files

anymore? I didn't see anything that looked like a reader for type 1 files.

The was "import XML." Is there a patch that can export a midi file as XML?

On 1/2/08 2:07 PM, "apalomba@austin.rr.com" wrote:

> I tried converting the DMG file using MagicISO but it does not like this file

> Is there another way I can open a DMG file? Alternately, if someone could save

I got it open on a Mac and started it up. It looks interesting but there are
no instructions.  

I imported a type 0 midi file and all that showed up in the coll was the
file type MThd.  It does say "import raw" but who has raw midi files
anymore?  I didn't see anything that looked like a reader for type 1 files.

The was "import XML."  Is there a patch that can export a midi file as XML?

Cheers
Gary Lee Nelson
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson

On 1/2/08 2:07 PM, "apalomba@austin.rr.com"  wrote:

> I tried converting the DMG file using MagicISO but it does not like this file
> for some reason. 
> Is there another way I can open a DMG file? Alternately, if someone could save
> the DMG as a zip file
> I would be most grateful.
>
>
>
>
> Anthony


I used just the external that came with it (icst.midifile); I put 

that object in a patch and connected it to a print object, then sent 

it a read command, pointed that dialog to a MIDI file, then saw the 

MIDI file spit out to the Max window - looked like it worked 

At 3:10 PM -0500 1/2/08, Gary Lee Nelson wrote:

>I got it open on a Mac and started it up. It looks interesting but there are

>I imported a type 0 midi file and all that showed up in the coll was the

>file type MThd. It does say "import raw" but who has raw midi files

>anymore? I didn't see anything that looked like a reader for type 1 files.

>The was "import XML." Is there a patch that can export a midi file as XML?

>On 1/2/08 2:07 PM, "apalomba@austin.rr.com" wrote:

>> I tried converting the DMG file using MagicISO but it does not 

>> Is there another way I can open a DMG file? Alternately, if 

202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 

I used just the external that came with it (icst.midifile); I put 
that object in a patch and connected it to a print object, then sent 
it a read command, pointed that dialog to a MIDI file, then saw the 
MIDI file spit out to the Max window - looked like it worked 
perfectly for that example...

At 3:10 PM -0500 1/2/08, Gary Lee Nelson wrote:
>I got it open on a Mac and started it up. It looks interesting but there are
>no instructions. 
>
>I imported a type 0 midi file and all that showed up in the coll was the
>file type MThd.  It does say "import raw" but who has raw midi files
>anymore?  I didn't see anything that looked like a reader for type 1 files.
>
>The was "import XML."  Is there a patch that can export a midi file as XML?
>
>Cheers
>Gary Lee Nelson
>Oberlin College
>www.timara.oberlin.edu/GaryLeeNelson
>
>
>On 1/2/08 2:07 PM, "apalomba@austin.rr.com"  wrote:
>
>>  I tried converting the DMG file using MagicISO but it does not 
>>like this file
>>  for some reason.
>>  Is there another way I can open a DMG file? Alternately, if 
>>someone could save
>>  the DMG as a zip file
>>  I would be most grateful.
>>
>>
>>
>>
>>  Anthony
>
>
>

-- 
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 
Malfunction
http://www.defectiverecords.com
http://www.jackosx.com


Quote: robin.meier wrote on Wed, 02 January 2008 06:34

----------------------------------------------------

> i know detonate and seq, but these don't seem to be able to

There's also John MacCallum's javas external, midifile, at:

Quote: robin.meier wrote on Wed, 02 January 2008 06:34
----------------------------------------------------
> hello,
>
> what's the easiest way to load and play a type 1 or type 0 midifile with different meters and tempos inside max?
>
> i know detonate and seq, but these don't seem to be able to 

Here's a zip for you. 6.4MB, done uploading in a sec.

http://danwinckler.com/files/Timegrid_0.3.zip

Here's a zip for you.  6.4MB, done uploading in a sec.

http://danwinckler.com/files/Timegrid_0.3.zip


Sent: Wednesday, January 02, 2008 4:11 PM

> Here's a zip for you. 6.4MB, done uploading in a sec.

----- Original Message ----- 
From: "Dan Winckler" 
To: 
Sent: Wednesday, January 02, 2008 4:11 PM
Subject: Re: [maxmsp] sequencer in max

> Hi Anthony,
>
> Here's a zip for you.  6.4MB, done uploading in a sec.
>
> http://danwinckler.com/files/Timegrid_0.3.zip
>
>
>
>


When I select a file from the read dialog, it prints to the max window as

The last four lines are obiously midi events (noteon and notoff). The first

line is data from the header obviously but what exactly. 96 looks like a

0 0 1 15 96 means type 1 file with 15 tracks?

What are the first two numbers in the event message?

> I used just the external that came with it (icst.midifile); I put

> that object in a patch and connected it to a print object, then sent

> it a read command, pointed that dialog to a MIDI file, then saw the

> MIDI file spit out to the Max window - looked like it worked

When I select a file from the read dialog, it prints to the max window as
you say.  The output looks like this.

print: header 0 0 0 1 96
print: begin 0 0 0 
print: event 47 47 144 65 81
print: event 17 64 144 65 0
print: event 32 96 144 69 81
print: event 17 113 144 69 0

The last four lines are obiously midi events (noteon and notoff).  The first
line is data from the header obviously but what exactly.  96 looks like a
clock resolution.

> I used just the external that came with it (icst.midifile); I put
> that object in a patch and connected it to a print object, then sent
> it a read command, pointed that dialog to a MIDI file, then saw the
> MIDI file spit out to the Max window - looked like it worked
> perfectly for that example...
>
> Dan


>The last four lines are obiously midi events (noteon and notoff). The first

>line is data from the header obviously but what exactly. 96 looks like a

>0 0 1 15 96 means type 1 file with 15 tracks?

>What are the first two numbers in the event message?

It's been a while since I've pored over MIDI file structure, but if 

memory serves, this site is one of, if not the, best:

http://www.borg.com/~jglatt/tech/miditech.htm

>print: header 0 0 0 1 96
>print: begin 0 0 0
>print: event 47 47 144 65 81
>print: event 17 64 144 65 0
>print: event 32 96 144 69 81
>print: event 17 113 144 69 0
>
>The last four lines are obiously midi events (noteon and notoff).  The first
>line is data from the header obviously but what exactly.  96 looks like a
>clock resolution.
>
>0 0 1 15 96 means type 1 file with 15 tracks?
>
>What are the first two numbers in the event message?

It's been a while since I've pored over MIDI file structure, but if 
memory serves, this site is one of, if not the, best:

Dan
-- 
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 
Malfunction
http://www.defectiverecords.com
http://www.jackosx.com


i'm sorry if i've mislead anybody: timegrid is not a midi-sequencer, 

it's an application for work with tempo-polyphony making use of the 

icst.midifile for export only. read more about it here: 

www.icst.net/files/ICST_Tempopolyphony_ICMC07.pdf

and let me state the following regarding [icst.midifile]:

- of course there exists a windows build of icst.midifile.

- we _do_ have a helpfile and some examples for it.

- and YES: it will be published with sources under the LGPL in the 

i'm sorry if i've mislead anybody: timegrid is not a midi-sequencer,  
it's an application for work with tempo-polyphony making use of the  
icst.midifile for export only. read more about it here:  http:// 
www.icst.net/files/ICST_Tempopolyphony_ICMC07.pdf

and let me state the following regarding [icst.midifile]:
- of course there exists a windows build of icst.midifile.
- we _do_ have a helpfile and some examples for it.
- and YES: it will be published with sources under the LGPL in the  
near future.

I did look up the MThd chunk in my midi file format reference. The last

unsigned short Format; (type 0 or 1, sometimes 2)

unsigned short NumTracks; (always 1 for type 0)

unsigned short Division; (varies with application. Most applications

So this is type 0 with 1 track and subdivision of 96.

The last three numbers in these note events are status, key and velocity.

The first two numbers seem to be action time - perhaps beat and subdivision

computed from delta times in the midi file. This file was played in so the

subdivisions are slightly off from multiples of 16 which would indicates

The first two numbers are delta and action time. Sum the second number of a

line with the first number of the next and you get the second number of the

>> The last four lines are obiously midi events (noteon and notoff). The first

>> line is data from the header obviously but what exactly. 96 looks like a

>> 0 0 1 15 96 means type 1 file with 15 tracks?

>> What are the first two numbers in the event message?

> It's been a while since I've pored over MIDI file structure, but if

> memory serves, this site is one of, if not the, best:

> I'm sure the answer is there somewhere.

I did look up the MThd chunk in my midi file format reference. The last
three numbers are

   unsigned short Format; (type 0 or 1, sometimes 2)
   unsigned short NumTracks; (always 1 for type 0)
   unsigned short Division; (varies with application. Most applications
                                convert to their subdivision.)

print: header 0 0 0 1 96
print: begin 0 0 0 

The last three numbers in these note events are status, key and velocity.
The first two numbers seem to be action time - perhaps beat and subdivision
computed from delta times in the midi file.  This file was played in so the
subdivisions are slightly off from multiples of 16 which would indicates
beats divided into 8.

The first two numbers are delta and action time.  Sum the second number of a
line with the first number of the next and you get the second number of the
next.

print: event 47 47 144 65 81
print: event 17 64 144 65 0
print: event 32 96 144 69 81
print: event 17 113 144 69 0
print: event 32 145 144 65 81
print: event 17 162 144 65 0
print: event 33 195 144 72 81
print: event 15 210 144 72 0
print: event 34 244 144 65 81
print: event 15 259 144 65 0
print: event 32 291 144 77 75
print: event 49 340 144 53 78
print: event 2 342 144 76 75

>> print: header 0 0 0 1 96
>> print: begin 0 0 0
>> print: event 47 47 144 65 81
>> print: event 17 64 144 65 0
>> print: event 32 96 144 69 81
>> print: event 17 113 144 69 0
>>
>> The last four lines are obiously midi events (noteon and notoff).  The first
>> line is data from the header obviously but what exactly.  96 looks like a
>> clock resolution.
>>
>> 0 0 1 15 96 means type 1 file with 15 tracks?
>>
>> What are the first two numbers in the event message?
>
> It's been a while since I've pored over MIDI file structure, but if
> memory serves, this site is one of, if not the, best:
>
> http://www.borg.com/~jglatt/tech/miditech.htm
>
> I'm sure the answer is there somewhere.
>
> Dan


> I've been poking around with icst.midifile this morning and it looks great!

> I have been able to parse the output into several data structures that allow

> me to finally play and control type 1 files. I look forward to the help

> file, examples and source. I gather there is some syntax for writing midi

> > i'm sorry if i've mislead anybody: timegrid is not a midi-sequencer,

> > it's an application for work with tempo-polyphony making use of the

> > icst.midifile for export only. read more about it here: 

> > www.icst.net/files/ICST_Tempopolyphony_ICMC07.pdf

> > and let me state the following regarding [icst.midifile]:

> > - of course there exists a windows build of icst.midifile.

> > - we _do_ have a helpfile and some examples for it.

> > - and YES: it will be published with sources under the LGPL in the

---- Gary Lee Nelson  wrote: 
> Thanks, Jasch.
>
> I've been poking around with icst.midifile this morning and it looks great!
> I have been able to parse the output into several data structures that allow
> me to finally play and control type 1 files.  I look forward to the help
> file, examples and source.  I gather there is some syntax for writing midi
> data into icst.midifile.
>
> Cheers
> Gary Lee Nelson
> Oberlin College
> www.timara.oberlin.edu/GaryLeeNelson
>
>
> On 1/3/08 9:01 AM, "jasch  "  wrote:
>
> > hello,
> >
> > i'm sorry if i've mislead anybody: timegrid is not a midi-sequencer,
> > it's an application for work with tempo-polyphony making use of the
> > icst.midifile for export only. read more about it here:  http://
> > www.icst.net/files/ICST_Tempopolyphony_ICMC07.pdf
> >
> > and let me state the following regarding [icst.midifile]:
> > - of course there exists a windows build of icst.midifile.
> > - we _do_ have a helpfile and some examples for it.
> > - and YES: it will be published with sources under the LGPL in the
> > near future.
> >
> > a little patience please
> >
> > best regards
> >
> > /*j
> >
>
>
>
>


How did you parse off the data in the situation you described? I'm not particularly great with Max, and knowing this would solve my current problem.

In particular I'm looking for a way to extract the time signature, which is the 5th line outputted into the print window (if loading a sequenced MIDI file created in Logic, say). This will be used to control the counter of a drum machine.

Many thanks (had to register myself to the forums for this post!)