Launch Patch Type from M4L w/ Type 1 Standard Midi Files (SMF)?
I'm building a device heavily focused on the use of type 1 SMF.
All of the details aside, does anyone know of a way to load any type of patch, create a new track, etc. in Live from M4L?
The type of functionality I'm trying to recreate exists in Garageband, Logic, and Reason, and probably many more(these are the only ones I've tested). When you open up a type 1 SMF (like the one attached), it will choose appropriate patches based on the track metadata.
If you have any insight to Type 1 SMF or know of ways to handle tracks and patches in M4L that relate to this feature, please let me know! :)
If a type 1 SMF is loaded in Live it creates multiple tracks with corresponding clips. The patch number (program change) of each clip is stored in the 'Program' field of the notes tab. But for some reason this number cannot be accessed with M4L.
Hmm, yea thats what I thought too. I found a device that seems to do some interesting things with displaying what patches/plugins you have, and supposedly PRG Changes, but not having much luck with it either.
http://www.maxforlive.com/library/device/2432/preseter
I've just checked the device you mentioned. It works for me when mapped to the chain selector of an instrument rack. With this method the instrument selection is done dynamically if the clip starts playing.
Yea, I got that to work too, but I suppose what I'm hoping for is maybe not possible at this point. Ideally it would call some type of patch from the library rather than an instrument rack.
Something that would suffice is simply getting the program change number from each track, then I could just make text labels with the instrument name associated with that patch PGM Chng#.
It looks like it actually comes back to this thread that I saw you post in: https://cycling74.com/forums/how-to-know-which-program-changes-are-used-in-a-midi-file/
I did check out the external ‘ajm.midi2coll’ from Adam Murray. However I'd ideally like to construct this for use by the majority of M4L users at some point, w/out redirecting to externals that require java lib files.
Heres a start to represent the basic idea....(not really working yet) But do you think it might work to allocate detonate's tracks to 16 potential seq's?
> Something that would suffice is simply getting the program change number from each track, then I could just make text labels with the instrument name associated with that patch PGM Chng#.
Remember that If a midi file is loaded in Live, you can see the program change number from each track in the 'Program' field of the corresponding clip.
Of course... haha man sorry, I checked that out when you said it at first but it didn't work with the track i was looking at...but is showing now.
Well, bummer! so there definitely is now way to retrieve that number? oh well, I'm wanting to load it all in through max, anyhow.
hmm.. in another thread I saw someone reccomend analyzing the midi file w/ the [filein] object in Max.
I may start looking into that.
Thanks for your help Broc!
Okay I was able to Get the Program Change Header Data from FileIn.
Heres a very rudimentary way. Still working to integrate this to my device, but its well on the way!
Thanks again!