Forums > MaxMSP

Max/MSP and MIDI Implementation

October 24, 2007 | 1:08 am

Hi,

I’m relatively new to programming in general, so I apologize for any simple things I may have missed; I’m a big fan of working things out for myself, but I’ve hit a bit of a wall and would be grateful for any pointers…

the background:
So, my idea is to build a series of small VSTi/AU devices to use in a sequencer program (ie, Ableton), that will control certain parameters of an external synth (ie, a Roland Fantom XR), on the specific MIDI channel the VSTi/AU is placed on in the sequencer

the problem:
I’m having a little trouble getting my head around the huge tables of MIDI Implementation in the back of the manual for the synth – I know the commands I want to send but am unsure how to break down/where to address the different numbers (if this is even necessary) or how to decipher them into something meaningful that can be sent from Max/MSP to cause the synth to change it’s parameters.

I managed to get my head around MSB and LSB for doing program changes (selecting different patches etc), and have no problems with CC messages and basic MIDI in general, but the MIDI Implementation stuff still foxes me every time.

Here’s an example showing the format of the table in the manual in question:
[img]index.php?t=getfile&id=941&private=0[/img]
The full manual is here: ftp://ftp.roland.co.uk/Manuals/FANTOM-XR_OM.pdf

Pretty sure I could figure it out if I had an example; if anyone would anyone be willing/able to talk me through what to do to go from the MIDI Implementation table to the synth via Max it would be much appreciated – there’s a file attached showing the format given for the MIDI Implementation tables in the particular manual in question; if more information is needed just let me know what is needed.

I have searched around for relevant information but to no avail, so if anyone knows of any decent reference material I could brush up on that would help wrt this sort of thing

Oh, and if I’ve missed something blindingly obvious, please let me know (and don’t hurt me too badly!)

thanks in advance!

Mindtrap


October 24, 2007 | 1:09 am

Hi,

I’m relatively new to programming in general, so I apologize for any simple things I may have missed; I’m a big fan of working things out for myself, but I’ve hit a bit of a wall and would be grateful for any pointers…

the background:
So, my idea is to build a series of small VSTi/AU devices to use in a sequencer program (ie, Ableton), that will control certain parameters of an external synth (ie, a Roland Fantom XR), on the specific MIDI channel the VSTi/AU is placed on in the sequencer

the problem:
I’m having a little trouble getting my head around the huge tables of MIDI Implementation in the back of the manual for the synth – I know the commands I want to send but am unsure how to break down/where to address the different numbers (if this is even necessary) or how to decipher them into something meaningful that can be sent from Max/MSP to cause the synth to change it’s parameters.

I managed to get my head around MSB and LSB for doing program changes (selecting different patches etc), and have no problems with CC messages and basic MIDI in general, but the MIDI Implementation stuff still foxes me every time.

Here’s an example showing the format of the table in the manual in question:
[img]index.php?t=getfile&id=941&private=0[/img]
The full manual is here: ftp://ftp.roland.co.uk/Manuals/FANTOM-XR_OM.pdf

Pretty sure I could figure it out if I had an example; if anyone would anyone be willing/able to talk me through what to do to go from the MIDI Implementation table to the synth via Max it would be much appreciated – there’s a file attached showing the format given for the MIDI Implementation tables in the particular manual in question; if more information is needed just let me know what is needed.

I have searched around for relevant information but to no avail, so if anyone knows of any decent reference material I could brush up on that would help wrt this sort of thing

Oh, and if I’ve missed something blindingly obvious, please let me know (and don’t hurt me too badly!)

thanks in advance!

Mindtrap


October 24, 2007 | 1:40 pm

Have you found sxformat and sysexin?

The former lets you make system exclusive messages for your synth. The
latter can be used to find out what the messages look like. To use sysexin
to learn these messages your synth must have a way to edit parameters from
its own control panel and these messages must be sent via the midi out of
the external device. Not all synths do this. Once you learn the format of
these messages, you can write things like below. It make program selection
in a bank of Proteus 1/2/3′s using device number, channel and a program
number that get parsed into bank/program messages.

This is Protpgmout

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P comment 24 228 88 196617 program select ->;
#P comment 376 263 88 196617 < - device select;
#P window setfont Helvetica 24.;
#P comment 276 73 132 1376280 Protpgmout;
#P window setfont "Sans Serif" 9.;
#P comment 277 104 121 196617 Author: Gary Lee Nelson;
#P newex 119 105 88 196617 unpack 0 0;
#P newex 119 83 48 196617 pack 0 1;
#P newex 240 193 40 196617 t i i i;
#P newex 197 169 34 196617 % 16;
#P newex 240 168 31 196617 / 16;
#P newex 197 140 27 196617 – 1;
#N comlet channel (1-96);
#P inlet 157 60 15 0;
#N comlet program number (0-191);
#P inlet 119 60 15 0;
#P newex 119 226 69 196617 pack 0 259 0;
#P newex 197 225 69 196617 pack 0 256 0;
#P user umenu 270 261 100 196647 1 64 277 1;
#X add ProteusA;
#X add ProteusB;
#X add ProteusC;
#X add ProteusD;
#X add ProteusE;
#X add ProteusF;
#P newex 197 293 43 196617 midiout;
#P newex 197 260 63 196617 ProtVoxPar;
#P comment 282 228 88 196617 < - bank select;
#P connect 8 0 10 0;
#P fasten 8 0 9 0 202 162 245 162;
#P connect 11 2 3 0;
#P connect 11 1 4 2;
#P connect 9 0 11 0;
#P connect 13 1 8 0;
#P fasten 3 1 2 0 365 285 202 285;
#P connect 1 0 2 0;
#P connect 4 0 1 0;
#P fasten 5 0 1 0 124 251 202 251;
#P connect 10 0 4 0;
#P fasten 11 0 5 2 245 217 182 217;
#P connect 7 0 12 1;
#P connect 13 0 5 0;
#P connect 12 0 13 0;
#P connect 6 0 12 0;
#P window clipboard copycount 18;

It uses a subpatch called ProtVoxPar where the system exclusive message is
formatted for the Proteus.

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P comment 24 228 88 196617 program select ->;
#P comment 376 263 88 196617 < - device select;
#P window setfont Helvetica 24.;
#P comment 276 73 132 1376280 Protpgmout;
#P window setfont "Sans Serif" 9.;
#P comment 277 104 121 196617 Author: Gary Lee Nelson;
#P newex 119 105 88 196617 unpack 0 0;
#P newex 119 83 48 196617 pack 0 1;
#P newex 240 193 40 196617 t i i i;
#P newex 197 169 34 196617 % 16;
#P newex 240 168 31 196617 / 16;
#P newex 197 140 27 196617 – 1;
#N comlet channel (1-96);
#P inlet 157 60 15 0;
#N comlet program number (0-191);
#P inlet 119 60 15 0;
#P newex 119 226 69 196617 pack 0 259 0;
#P newex 197 225 69 196617 pack 0 256 0;
#P user umenu 270 261 100 196647 1 64 277 1;
#X add ProteusA;
#X add ProteusB;
#X add ProteusC;
#X add ProteusD;
#X add ProteusE;
#X add ProteusF;
#P newex 197 293 43 196617 midiout;
#P newex 197 260 63 196617 ProtVoxPar;
#P comment 282 228 88 196617 < - bank select;
#P connect 8 0 10 0;
#P fasten 8 0 9 0 202 162 245 162;
#P connect 11 2 3 0;
#P connect 11 1 4 2;
#P connect 9 0 11 0;
#P connect 13 1 8 0;
#P fasten 3 1 2 0 365 285 202 285;
#P connect 1 0 2 0;
#P connect 4 0 1 0;
#P fasten 5 0 1 0 124 251 202 251;
#P connect 10 0 4 0;
#P fasten 11 0 5 2 245 217 182 217;
#P connect 7 0 12 1;
#P connect 13 0 5 0;
#P connect 12 0 13 0;
#P connect 6 0 12 0;
#P window clipboard copycount 18;

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

On 10/23/07 9:09 PM, "Mindtrap" wrote:

>
> Hi,
>
> I’m relatively new to programming in general, so I apologize for any simple
> things I may have missed; I’m a big fan of working things out for myself, but
> I’ve hit a bit of a wall and would be grateful for any pointers…
>
> the background:
> So, my idea is to build a series of small VSTi/AU devices to use in a
> sequencer program (ie, Ableton), that will control certain parameters of an
> external synth (ie, a Roland Fantom XR), on the specific MIDI channel the
> VSTi/AU is placed on in the sequencer
>
> the problem:
> I’m having a little trouble getting my head around the huge tables of MIDI
> Implementation in the back of the manual for the synth – I know the commands I
> want to send but am unsure how to break down/where to address the different
> numbers (if this is even necessary) or how to decipher them into something
> meaningful that can be sent from Max/MSP to cause the synth to change it’s
> parameters.
>
> I managed to get my head around MSB and LSB for doing program changes
> (selecting different patches etc), and have no problems with CC messages and
> basic MIDI in general, but the MIDI Implementation stuff still foxes me every
> time.
>
> Here’s an example showing the format of the table in the manual in question:
> [img]index.php?t=getfile&id=941&private=0[/img]
> The full manual is here: ftp://ftp.roland.co.uk/Manuals/FANTOM-XR_OM.pdf
>
> Pretty sure I could figure it out if I had an example; if anyone would anyone
> be willing/able to talk me through what to do to go from the MIDI
> Implementation table to the synth via Max it would be much appreciated -
> there’s a file attached showing the format given for the MIDI Implementation
> tables in the particular manual in question; if more information is needed
> just let me know what is needed.
>
> I have searched around for relevant information but to no avail, so if anyone
> knows of any decent reference material I could brush up on that would help wrt
> this sort of thing
>
> Oh, and if I’ve missed something blindingly obvious, please let me know (and
> don’t hurt me too badly!)
>
> thanks in advance!
>
> Mindtrap


October 25, 2007 | 6:07 pm

Um, looks like you pasted the same patch in twice – recursive sub-patching !
;-)
Cheers
Roger

On 24/10/07 14:40, "Gary Lee Nelson" wrote:

> Have you found sxformat and sysexin?
>
> The former lets you make system exclusive messages for your synth. The
> latter can be used to find out what the messages look like. To use sysexin
> to learn these messages your synth must have a way to edit parameters from
> its own control panel and these messages must be sent via the midi out of
> the external device. Not all synths do this. Once you learn the format of
> these messages, you can write things like below. It make program selection
> in a bank of Proteus 1/2/3′s using device number, channel and a program
> number that get parsed into bank/program messages.
>
> This is Protpgmout
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P comment 24 228 88 196617 program select ->;
> #P comment 376 263 88 196617 < - device select;
> #P window setfont Helvetica 24.;
> #P comment 276 73 132 1376280 Protpgmout;
> #P window setfont "Sans Serif" 9.;
> #P comment 277 104 121 196617 Author: Gary Lee Nelson;
> #P newex 119 105 88 196617 unpack 0 0;
> #P newex 119 83 48 196617 pack 0 1;
> #P newex 240 193 40 196617 t i i i;
> #P newex 197 169 34 196617 % 16;
> #P newex 240 168 31 196617 / 16;
> #P newex 197 140 27 196617 – 1;
> #N comlet channel (1-96);
> #P inlet 157 60 15 0;
> #N comlet program number (0-191);
> #P inlet 119 60 15 0;
> #P newex 119 226 69 196617 pack 0 259 0;
> #P newex 197 225 69 196617 pack 0 256 0;
> #P user umenu 270 261 100 196647 1 64 277 1;
> #X add ProteusA;
> #X add ProteusB;
> #X add ProteusC;
> #X add ProteusD;
> #X add ProteusE;
> #X add ProteusF;
> #P newex 197 293 43 196617 midiout;
> #P newex 197 260 63 196617 ProtVoxPar;
> #P comment 282 228 88 196617 < - bank select;
> #P connect 8 0 10 0;
> #P fasten 8 0 9 0 202 162 245 162;
> #P connect 11 2 3 0;
> #P connect 11 1 4 2;
> #P connect 9 0 11 0;
> #P connect 13 1 8 0;
> #P fasten 3 1 2 0 365 285 202 285;
> #P connect 1 0 2 0;
> #P connect 4 0 1 0;
> #P fasten 5 0 1 0 124 251 202 251;
> #P connect 10 0 4 0;
> #P fasten 11 0 5 2 245 217 182 217;
> #P connect 7 0 12 1;
> #P connect 13 0 5 0;
> #P connect 12 0 13 0;
> #P connect 6 0 12 0;
> #P window clipboard copycount 18;
>
> It uses a subpatch called ProtVoxPar where the system exclusive message is
> formatted for the Proteus.
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P comment 24 228 88 196617 program select ->;
> #P comment 376 263 88 196617 < - device select;
> #P window setfont Helvetica 24.;
> #P comment 276 73 132 1376280 Protpgmout;
> #P window setfont "Sans Serif" 9.;
> #P comment 277 104 121 196617 Author: Gary Lee Nelson;
> #P newex 119 105 88 196617 unpack 0 0;
> #P newex 119 83 48 196617 pack 0 1;
> #P newex 240 193 40 196617 t i i i;
> #P newex 197 169 34 196617 % 16;
> #P newex 240 168 31 196617 / 16;
> #P newex 197 140 27 196617 – 1;
> #N comlet channel (1-96);
> #P inlet 157 60 15 0;
> #N comlet program number (0-191);
> #P inlet 119 60 15 0;
> #P newex 119 226 69 196617 pack 0 259 0;
> #P newex 197 225 69 196617 pack 0 256 0;
> #P user umenu 270 261 100 196647 1 64 277 1;
> #X add ProteusA;
> #X add ProteusB;
> #X add ProteusC;
> #X add ProteusD;
> #X add ProteusE;
> #X add ProteusF;
> #P newex 197 293 43 196617 midiout;
> #P newex 197 260 63 196617 ProtVoxPar;
> #P comment 282 228 88 196617 < - bank select;
> #P connect 8 0 10 0;
> #P fasten 8 0 9 0 202 162 245 162;
> #P connect 11 2 3 0;
> #P connect 11 1 4 2;
> #P connect 9 0 11 0;
> #P connect 13 1 8 0;
> #P fasten 3 1 2 0 365 285 202 285;
> #P connect 1 0 2 0;
> #P connect 4 0 1 0;
> #P fasten 5 0 1 0 124 251 202 251;
> #P connect 10 0 4 0;
> #P fasten 11 0 5 2 245 217 182 217;
> #P connect 7 0 12 1;
> #P connect 13 0 5 0;
> #P connect 12 0 13 0;
> #P connect 6 0 12 0;
> #P window clipboard copycount 18;
>
> Cheers
> Gary Lee Nelson
> Oberlin College
> http://www.timara.oberlin.edu/GaryLeeNelson
>
>
> On 10/23/07 9:09 PM, "Mindtrap" wrote:
>
>>
>> Hi,
>>
>> I’m relatively new to programming in general, so I apologize for any simple
>> things I may have missed; I’m a big fan of working things out for myself, but
>> I’ve hit a bit of a wall and would be grateful for any pointers…
>>
>> the background:
>> So, my idea is to build a series of small VSTi/AU devices to use in a
>> sequencer program (ie, Ableton), that will control certain parameters of an
>> external synth (ie, a Roland Fantom XR), on the specific MIDI channel the
>> VSTi/AU is placed on in the sequencer
>>
>> the problem:
>> I’m having a little trouble getting my head around the huge tables of MIDI
>> Implementation in the back of the manual for the synth – I know the commands
>> I
>> want to send but am unsure how to break down/where to address the different
>> numbers (if this is even necessary) or how to decipher them into something
>> meaningful that can be sent from Max/MSP to cause the synth to change it’s
>> parameters.
>>
>> I managed to get my head around MSB and LSB for doing program changes
>> (selecting different patches etc), and have no problems with CC messages and
>> basic MIDI in general, but the MIDI Implementation stuff still foxes me every
>> time.
>>
>> Here’s an example showing the format of the table in the manual in question:
>> [img]index.php?t=getfile&id=941&private=0[/img]
>> The full manual is here: ftp://ftp.roland.co.uk/Manuals/FANTOM-XR_OM.pdf
>>
>> Pretty sure I could figure it out if I had an example; if anyone would anyone
>> be willing/able to talk me through what to do to go from the MIDI
>> Implementation table to the synth via Max it would be much appreciated -
>> there’s a file attached showing the format given for the MIDI Implementation
>> tables in the particular manual in question; if more information is needed
>> just let me know what is needed.
>>
>> I have searched around for relevant information but to no avail, so if
>> anyone
>> knows of any decent reference material I could brush up on that would help
>> wrt
>> this sort of thing
>>
>> Oh, and if I’ve missed something blindingly obvious, please let me know (and
>> don’t hurt me too badly!)
>>
>> thanks in advance!
>>
>> Mindtrap
>
>
>


October 25, 2007 | 6:18 pm

Here’s the second one ProtVoxPar

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 45 116 57 196617 pack 0 0 0;
#P window linecount 2;
#P newex 45 147 273 196617 sxformat 240 24 4 / is $i3 / 3 / is $i2&127 / /
is ($i2>>7)&127 / / is $i1&127 / / is ($i1>>7)&127 / 247;
#N comlet parameter number;
#P inlet 68 86 15 0;
#P window setfont Helvetica 24.;
#P window linecount 1;
#P comment 151 70 132 1376280 ProtVoxPar;
#P window setfont "Sans Serif" 9.;
#P comment 152 101 121 196617 Author: Gary Lee Nelson;
#N comlet Device ID;
#P inlet 92 86 15 0;
#N comlet parameter value;
#P inlet 45 86 15 0;
#N comlet connect to midiout;
#P outlet 45 199 15 0;
#P newex 334 43 46 196617 loadbang;
#P newex 334 115 86 196617 print ProtVoxPar;
#P message 334 78 146 196617 requires connection to midiout;
#P connect 0 0 1 0;
#P connect 2 0 0 0;
#P connect 5 0 10 2;
#P connect 8 0 10 1;
#P connect 9 0 3 0;
#P connect 10 0 9 0;
#P connect 4 0 10 0;
#P window clipboard copycount 11;

On 10/25/07 2:07 PM, "Roger Carruthers"
wrote:

> Um, looks like you pasted the same patch in twice – recursive sub-patching !
> ;-)
> Cheers
> Roger
>
>
> On 24/10/07 14:40, "Gary Lee Nelson" wrote:
>
>> Have you found sxformat and sysexin?
>>
>> The former lets you make system exclusive messages for your synth. The
>> latter can be used to find out what the messages look like. To use sysexin
>> to learn these messages your synth must have a way to edit parameters from
>> its own control panel and these messages must be sent via the midi out of
>> the external device. Not all synths do this. Once you learn the format of
>> these messages, you can write things like below. It make program selection
>> in a bank of Proteus 1/2/3′s using device number, channel and a program
>> number that get parsed into bank/program messages.
>>
>> This is Protpgmout
>>
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P comment 24 228 88 196617 program select ->;
>> #P comment 376 263 88 196617 < - device select;
>> #P window setfont Helvetica 24.;
>> #P comment 276 73 132 1376280 Protpgmout;
>> #P window setfont "Sans Serif" 9.;
>> #P comment 277 104 121 196617 Author: Gary Lee Nelson;
>> #P newex 119 105 88 196617 unpack 0 0;
>> #P newex 119 83 48 196617 pack 0 1;
>> #P newex 240 193 40 196617 t i i i;
>> #P newex 197 169 34 196617 % 16;
>> #P newex 240 168 31 196617 / 16;
>> #P newex 197 140 27 196617 – 1;
>> #N comlet channel (1-96);
>> #P inlet 157 60 15 0;
>> #N comlet program number (0-191);
>> #P inlet 119 60 15 0;
>> #P newex 119 226 69 196617 pack 0 259 0;
>> #P newex 197 225 69 196617 pack 0 256 0;
>> #P user umenu 270 261 100 196647 1 64 277 1;
>> #X add ProteusA;
>> #X add ProteusB;
>> #X add ProteusC;
>> #X add ProteusD;
>> #X add ProteusE;
>> #X add ProteusF;
>> #P newex 197 293 43 196617 midiout;
>> #P newex 197 260 63 196617 ProtVoxPar;
>> #P comment 282 228 88 196617 < - bank select;
>> #P connect 8 0 10 0;
>> #P fasten 8 0 9 0 202 162 245 162;
>> #P connect 11 2 3 0;
>> #P connect 11 1 4 2;
>> #P connect 9 0 11 0;
>> #P connect 13 1 8 0;
>> #P fasten 3 1 2 0 365 285 202 285;
>> #P connect 1 0 2 0;
>> #P connect 4 0 1 0;
>> #P fasten 5 0 1 0 124 251 202 251;
>> #P connect 10 0 4 0;
>> #P fasten 11 0 5 2 245 217 182 217;
>> #P connect 7 0 12 1;
>> #P connect 13 0 5 0;
>> #P connect 12 0 13 0;
>> #P connect 6 0 12 0;
>> #P window clipboard copycount 18;
>>
>> It uses a subpatch called ProtVoxPar where the system exclusive message is
>> formatted for the Proteus.
>>
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P comment 24 228 88 196617 program select ->;
>> #P comment 376 263 88 196617 < - device select;
>> #P window setfont Helvetica 24.;
>> #P comment 276 73 132 1376280 Protpgmout;
>> #P window setfont "Sans Serif" 9.;
>> #P comment 277 104 121 196617 Author: Gary Lee Nelson;
>> #P newex 119 105 88 196617 unpack 0 0;
>> #P newex 119 83 48 196617 pack 0 1;
>> #P newex 240 193 40 196617 t i i i;
>> #P newex 197 169 34 196617 % 16;
>> #P newex 240 168 31 196617 / 16;
>> #P newex 197 140 27 196617 – 1;
>> #N comlet channel (1-96);
>> #P inlet 157 60 15 0;
>> #N comlet program number (0-191);
>> #P inlet 119 60 15 0;
>> #P newex 119 226 69 196617 pack 0 259 0;
>> #P newex 197 225 69 196617 pack 0 256 0;
>> #P user umenu 270 261 100 196647 1 64 277 1;
>> #X add ProteusA;
>> #X add ProteusB;
>> #X add ProteusC;
>> #X add ProteusD;
>> #X add ProteusE;
>> #X add ProteusF;
>> #P newex 197 293 43 196617 midiout;
>> #P newex 197 260 63 196617 ProtVoxPar;
>> #P comment 282 228 88 196617 < - bank select;
>> #P connect 8 0 10 0;
>> #P fasten 8 0 9 0 202 162 245 162;
>> #P connect 11 2 3 0;
>> #P connect 11 1 4 2;
>> #P connect 9 0 11 0;
>> #P connect 13 1 8 0;
>> #P fasten 3 1 2 0 365 285 202 285;
>> #P connect 1 0 2 0;
>> #P connect 4 0 1 0;
>> #P fasten 5 0 1 0 124 251 202 251;
>> #P connect 10 0 4 0;
>> #P fasten 11 0 5 2 245 217 182 217;
>> #P connect 7 0 12 1;
>> #P connect 13 0 5 0;
>> #P connect 12 0 13 0;
>> #P connect 6 0 12 0;
>> #P window clipboard copycount 18;
>>
>> Cheers
>> Gary Lee Nelson
>> Oberlin College
>> http://www.timara.oberlin.edu/GaryLeeNelson
>>
>>
>> On 10/23/07 9:09 PM, "Mindtrap" wrote:
>>
>>>
>>> Hi,
>>>
>>> I’m relatively new to programming in general, so I apologize for any simple
>>> things I may have missed; I’m a big fan of working things out for myself,
>>> but
>>> I’ve hit a bit of a wall and would be grateful for any pointers…
>>>
>>> the background:
>>> So, my idea is to build a series of small VSTi/AU devices to use in a
>>> sequencer program (ie, Ableton), that will control certain parameters of an
>>> external synth (ie, a Roland Fantom XR), on the specific MIDI channel the
>>> VSTi/AU is placed on in the sequencer
>>>
>>> the problem:
>>> I’m having a little trouble getting my head around the huge tables of MIDI
>>> Implementation in the back of the manual for the synth – I know the commands
>>> I
>>> want to send but am unsure how to break down/where to address the different
>>> numbers (if this is even necessary) or how to decipher them into something
>>> meaningful that can be sent from Max/MSP to cause the synth to change it’s
>>> parameters.
>>>
>>> I managed to get my head around MSB and LSB for doing program changes
>>> (selecting different patches etc), and have no problems with CC messages and
>>> basic MIDI in general, but the MIDI Implementation stuff still foxes me
>>> every
>>> time.
>>>
>>> Here’s an example showing the format of the table in the manual in question:
>>> [img]index.php?t=getfile&id=941&private=0[/img]
>>> The full manual is here: ftp://ftp.roland.co.uk/Manuals/FANTOM-XR_OM.pdf
>>>
>>> Pretty sure I could figure it out if I had an example; if anyone would
>>> anyone
>>> be willing/able to talk me through what to do to go from the MIDI
>>> Implementation table to the synth via Max it would be much appreciated -
>>> there’s a file attached showing the format given for the MIDI Implementation
>>> tables in the particular manual in question; if more information is needed
>>> just let me know what is needed.
>>>
>>> I have searched around for relevant information but to no avail, so if
>>> anyone
>>> knows of any decent reference material I could brush up on that would help
>>> wrt
>>> this sort of thing
>>>
>>> Oh, and if I’ve missed something blindingly obvious, please let me know (and
>>> don’t hurt me too badly!)
>>>
>>> thanks in advance!
>>>
>>> Mindtrap
>>
>>
>>
>
>

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


Viewing 5 posts - 1 through 5 (of 5 total)