MAX/MSP HELP - any of you guys use it?

[PROTO·DOME]

I'm irritated.

I've tried everything.

Basically. I'm wanting to implement a way to import MIDI type 1 (multitrack) and

explode the component MIDI channels so I can get MIDI data from each of

them. Each channel will be used to control a different synth.

[seq] is no good as it only deals with MIDI type 0.

[Detonate] seems promising, but I can't split the tracks individually. I can

only get one channel at a time out of it.

Do anyone know how to do this? Does anyone have a CLUE what I'm talking about?

[Fishy]

I cannot help, but I want express my deepest empathy for your Max troubles.

Been there. Done that. Never going back.

[Rozovian]

Not having used it I'm just guessing based on the routing stuff in Reaktor, but...

Can't you route the entire midi into multiple detonates and get different tracks out of each of them?

[PROTO·DOME]

  Rozovian said:

Not having used it I'm just guessing based on the routing stuff in Reaktor, but...

Can't you route the entire midi into multiple detonates and get different tracks out of each of them?

Ah see, this was my first solution, but each instance of detonate is the 'same', rather, they all share the same data. Whatever I change in one detonate it changes in all of them.

And thanks Cain, your sympathy is real useful. ;D

[avaris]

  Fishy said:

I cannot help, but I want express my deepest empathy for your Max troubles.

Been there. Done that. Never going back.

Seconded.

You just gotta read up on different modules to find the best one. Here is a site with custom coded Max objects you can download:

http://www.maxobjects.com/

Probably will have better luck finding something there.

[Fishy]

  PROTO·DOME said:

And thanks Cain, your sympathy is real useful. ;D

I aim to please.

Seriously though that program is terrifying. I made a wavetable synth in Max once. Every single sound from this is from my synth, check it:

http://fishy.escariot.net/public/CainDemoAfrica.wav

[Fishy]

Ok fine have some real advice.

  PROTO·DOME said:

Ah see, this was my first solution, but each instance of detonate is the 'same', rather, they all share the same data. Whatever I change in one detonate it changes in all of them.

If you save a bunch of individual patches with different detonator settings and then load them within your first patch you can get around that.

[PROTO·DOME]

  Fishy said:

If you save a bunch of individual patches with different detonator settings and then load them within your first patch you can get around that.

This may actually be my last resort.

Thanks dude, didn't think of that.

[WillRock]

  Fishy said:

I cannot help, but I want express my deepest empathy for your Max troubles.

Been there. Done that. Never going back.

This. So very this.

Also, DIDN'T I WARN YOU????

[ravendew]

I don't know if this would help, as I've never dealt with MIDI importing in Max, but just to throw it out there:

If MIDI events in your input have channel numbers attached to them, you might be able to use the [midiparse] object along with [select] objects to separate them based on channel. Though that deals with real-time MIDI events (e.g. MIDI controller input), and I have no clue if imported MIDI files behave the same way...

You might be able to get [poly~] to do something like that too.