Matrix 1000 Sysex Real Time Parmeter Edit Not Working
2009-08-05 by stublito
Yahoo Groups archive
Index last updated: 2026-04-28 23:39 UTC
Thread
2009-08-05 by stublito
Can't seem to get my new (to me) M1000 to respond to sysex paramter changes embedded in a MIDI track. I do have the bank select sysex working perfectly, the bank unlock also. The manual says it's F0 10 06 06 <parameter> <value>. No luck. For instance, F0 10 06 06 54 00 7F has no effect on Env 1 decay. I'm an experienced sysex programmer, I have my Roland analog stuff obeying my every whim. Any suggestions? Thanks Stublito
2009-08-05 by bernard.escaillas
You have to send a message once to enable 'remote sysex'. This message is F0 10 06 05 F7 Note: the Matrix1000 has some bugs... Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm Be careful no to send sysex messages to fast or you will crash the Matrix... Even if MIDI bauds are always the same, today midi port buffers are a lot faster than in the 80's ;) Have fun
2009-08-05 by ogusa@lava.net
Thank you. Do you send the message every time you change a patch or once when you power up the synth? Peter Quoting "bernard.escaillas" <bernard@midimetric.com>:
> You have to send a message once to enable 'remote sysex'. > > This message is F0 10 06 05 F7 > > Note: the Matrix1000 has some bugs... > Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm > > Be careful no to send sysex messages to fast or you will crash the > Matrix... Even if MIDI bauds are always the same, today midi port > buffers are a lot faster than in the 80's ;) > > Have fun > > > > ------------------------------------ > > Yahoo! Groups Links > > > >
2009-08-05 by ogusa@lava.net
I just tried it, but still no luck. At the beginning of each sequence, I'm sending the bank select sysex, then the program change etc. Does the enable go before the bank select? Where did you get that sysex string? I can't find it documented anywhere on the web or in the manual. Does the software rev have anything to do with it? Thank you, Stublito Quoting "bernard.escaillas" <bernard@...>:
> You have to send a message once to enable 'remote sysex'. > > This message is F0 10 06 05 F7 > > Note: the Matrix1000 has some bugs... > Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm > > Be careful no to send sysex messages to fast or you will crash the > Matrix... Even if MIDI bauds are always the same, today midi port > buffers are a lot faster than in the 80's ;) > > Have fun > > > > ------------------------------------ > > Yahoo! Groups Links > > > >
2009-08-05 by Margus Kliimask
Wrong. This is a command from Matrix-6/6R sysex implementation, M-1000 is different. On an M-1000 you need not do this, nor does this command get processed on M-1000. check out the page you referred. Regards, Margus
On Wed, Aug 5, 2009 at 3:53 PM, bernard.escaillas<bernard@...> wrote: > > > You have to send a message once to enable 'remote sysex'. > > This message is F0 10 06 05 F7 > > Note: the Matrix1000 has some bugs... > Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm > > Be careful no to send sysex messages to fast or you will crash the Matrix... > Even if MIDI bauds are always the same, today midi port buffers are a lot > faster than in the 80's ;) > > Have fun > >
2009-08-05 by Margus Kliimask
hmm... aren't you intermixing hex and decimal here? M-1000
documentation shows the parameter numbers in DEC. your sysex string
below should affect parameter 54 HEX (84 DEC, 'LFO 1 Initial
Amplitude'). 54 DEC ('Env 1 Initial Release Time') is 36 HEX so the
command F0 10 06 06 36 00 F7 (Note! F7 not 7F!) should do the trick.
i guess i need to add hex codes to my page as well
(http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm).
hope this helped,
margusOn Wed, Aug 5, 2009 at 6:59 AM, stublito<ogusa@...> wrote: > > > Can't seem to get my new (to me) M1000 to respond to sysex paramter changes > embedded in a MIDI track. > > I do have the bank select sysex working perfectly, the bank unlock also. > > The manual says it's F0 10 06 06 <parameter> <value>. No luck. For instance, > F0 10 06 06 54 00 7F has no effect on Env 1 decay. > > I'm an experienced sysex programmer, I have my Roland analog stuff obeying > my every whim. Any suggestions? > > Thanks > > Stublito > >
2009-08-05 by ogusa@lava.net
Can you offer an explanation as to why I can get the bank change sysex to work and not the parameter adjustment? For example, I am sending F0 10 06 06 54 00 F7 to try to get Env. 1 release time to zero. I note that the manual says that the values are "sign extended from 6 bit to 7 bit". Does that mean the value byte is not literal? Thank you. Peter Quoting Margus Kliimask <margus.kliimask@...>:
> Wrong. This is a command from Matrix-6/6R sysex implementation, M-1000 > is different. On an M-1000 you need not do this, nor does this command > get processed on M-1000. check out the page you referred. > > Regards, > Margus > > On Wed, Aug 5, 2009 at 3:53 PM, > bernard.escaillas<bernard@...> wrote: >> >> >> You have to send a message once to enable 'remote sysex'. >> >> This message is F0 10 06 05 F7 >> >> Note: the Matrix1000 has some bugs... >> Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm >> >> Be careful no to send sysex messages to fast or you will crash the Matrix... >> Even if MIDI bauds are always the same, today midi port buffers are a lot >> faster than in the 80's ;) >> >> Have fun >> >> > > > ------------------------------------ > > Yahoo! Groups Links > > > >
2009-08-05 by Margus Kliimask
On Wed, Aug 5, 2009 at 10:54 PM, <ogusa@...> wrote: > > > Can you offer an explanation as to why I can get the bank change sysex > to work and not the parameter adjustment? maybe that's because the bank number can go from 0 to 9 - in this range hex numbers are the same as decimal :) > For example, I am sending F0 10 06 06 54 00 F7 to try to get > Env. 1 release time to zero. I note that the manual says that the > values are "sign extended from 6 bit to 7 bit". Does that mean the > value byte is not literal? 'sign extended' is related to how 6-bit values of the parameters (most of them) are converted to 7-bit for processing inside M-1000. 6-bit parameter values go from 0 to 63. 7-bit parameters are treated as -64 to +63, not 0 to 127. regards, margus
> > Thank you. > > Peter > > Quoting Margus Kliimask <margus.kliimask@...>: > >> Wrong. This is a command from Matrix-6/6R sysex implementation, M-1000 >> is different. On an M-1000 you need not do this, nor does this command >> get processed on M-1000. check out the page you referred. >> >> Regards, >> Margus >> >> On Wed, Aug 5, 2009 at 3:53 PM, >> bernard.escaillas<bernard@...> wrote: >>> >>> >>> You have to send a message once to enable 'remote sysex'. >>> >>> This message is F0 10 06 05 F7 >>> >>> Note: the Matrix1000 has some bugs... >>> Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm >>> >>> Be careful no to send sysex messages to fast or you will crash the >>> Matrix... >>> Even if MIDI bauds are always the same, today midi port buffers are a lot >>> faster than in the 80's ;) >>> >>> Have fun >>> >>> >> >> >> ------------------------------------ >> >> Yahoo! Groups Links >> >> >> >> > >
2009-08-05 by ogusa@lava.net
Thank you so much. This is a bit different than the Roland sysex. Stublito Quoting Margus Kliimask <margus.kliimask@...>:
> On Wed, Aug 5, 2009 at 10:54 PM, <ogusa@...> wrote: >> >> >> Can you offer an explanation as to why I can get the bank change sysex >> to work and not the parameter adjustment? > > maybe that's because the bank number can go from 0 to 9 - in this > range hex numbers are the same as decimal :) > >> For example, I am sending F0 10 06 06 54 00 F7 to try to get >> Env. 1 release time to zero. I note that the manual says that the >> values are "sign extended from 6 bit to 7 bit". Does that mean the >> value byte is not literal? > > 'sign extended' is related to how 6-bit values of the parameters (most > of them) are converted to 7-bit for processing inside M-1000. 6-bit > parameter values go from 0 to 63. 7-bit parameters are treated as -64 > to +63, not 0 to 127. > > regards, > margus > >> >> Thank you. >> >> Peter >> >> Quoting Margus Kliimask <margus.kliimask@...>: >> >>> Wrong. This is a command from Matrix-6/6R sysex implementation, M-1000 >>> is different. On an M-1000 you need not do this, nor does this command >>> get processed on M-1000. check out the page you referred. >>> >>> Regards, >>> Margus >>> >>> On Wed, Aug 5, 2009 at 3:53 PM, >>> bernard.escaillas<bernard@...> wrote: >>>> >>>> >>>> You have to send a message once to enable 'remote sysex'. >>>> >>>> This message is F0 10 06 05 F7 >>>> >>>> Note: the Matrix1000 has some bugs... >>>> Read more here: http://wolzow.mindworks.ee/analog/m1k-firmware.htm >>>> >>>> Be careful no to send sysex messages to fast or you will crash the >>>> Matrix... >>>> Even if MIDI bauds are always the same, today midi port buffers are a lot >>>> faster than in the 80's ;) >>>> >>>> Have fun >>>> >>>> >>> >>> >>> ------------------------------------ >>> >>> Yahoo! Groups Links >>> >>> >>> >>> >> >> > > > ------------------------------------ > > Yahoo! Groups Links > > > >
2009-08-07 by Margus Kliimask
done. added hex values (in brackets) for easy reference (see http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm ). regards, margus On Wed, Aug 5, 2009 at 10:51 PM, Margus Kliimask<margus.kliimask@...> wrote:
> hmm... aren't you intermixing hex and decimal here? M-1000
> documentation shows the parameter numbers in DEC. your sysex string
> below should affect parameter 54 HEX (84 DEC, 'LFO 1 Initial
> Amplitude'). 54 DEC ('Env 1 Initial Release Time') is 36 HEX so the
> command F0 10 06 06 36 00 F7 (Note! F7 not 7F!) should do the trick.
>
> i guess i need to add hex codes to my page as well
> (http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm).
>
> hope this helped,
> margus
>
> On Wed, Aug 5, 2009 at 6:59 AM, stublito<ogusa@lava.net> wrote:
>>
>>
>> Can't seem to get my new (to me) M1000 to respond to sysex paramter changes
>> embedded in a MIDI track.
>>
>> I do have the bank select sysex working perfectly, the bank unlock also.
>>
>> The manual says it's F0 10 06 06 <parameter> <value>. No luck. For instance,
>> F0 10 06 06 54 00 7F has no effect on Env 1 decay.
>>
>> I'm an experienced sysex programmer, I have my Roland analog stuff obeying
>> my every whim. Any suggestions?
>>
>> Thanks
>>
>> Stublito
>>
>>
>2009-08-07 by ogusa@lava.net
Excellent, thank you. Peter Quoting Margus Kliimask <margus.kliimask@gmail.com>:
> done. added hex values (in brackets) for easy reference (see
> http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm ).
>
> regards,
> margus
>
> On Wed, Aug 5, 2009 at 10:51 PM, Margus
> Kliimask<margus.kliimask@gmail.com> wrote:
>> hmm... aren't you intermixing hex and decimal here? M-1000
>> documentation shows the parameter numbers in DEC. your sysex string
>> below should affect parameter 54 HEX (84 DEC, 'LFO 1 Initial
>> Amplitude'). 54 DEC ('Env 1 Initial Release Time') is 36 HEX so the
>> command F0 10 06 06 36 00 F7 (Note! F7 not 7F!) should do the trick.
>>
>> i guess i need to add hex codes to my page as well
>> (http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm).
>>
>> hope this helped,
>> margus
>>
>> On Wed, Aug 5, 2009 at 6:59 AM, stublito<ogusa@...> wrote:
>>>
>>>
>>> Can't seem to get my new (to me) M1000 to respond to sysex paramter changes
>>> embedded in a MIDI track.
>>>
>>> I do have the bank select sysex working perfectly, the bank unlock also.
>>>
>>> The manual says it's F0 10 06 06 <parameter> <value>. No luck. For
>>> instance,
>>> F0 10 06 06 54 00 7F has no effect on Env 1 decay.
>>>
>>> I'm an experienced sysex programmer, I have my Roland analog stuff obeying
>>> my every whim. Any suggestions?
>>>
>>> Thanks
>>>
>>> Stublito
>>>
>>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>2009-08-07 by ogusa@lava.net
I was reading the page and noted the real time parameter stuff. What's the optimum way to do filter sweeps? I'm guessing map a controller to the Filter Freq. If you use the Controller 99 (non-reg MSB) will you get "zipper noise" from using only the coarse values? Thanks again so much, Stublito <margus.kliimask@...>:
> done. added hex values (in brackets) for easy reference (see
> http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm ).
>
> regards,
> margus
>
> On Wed, Aug 5, 2009 at 10:51 PM, Margus
> Kliimask<margus.kliimask@...> wrote:
>> hmm... aren't you intermixing hex and decimal here? M-1000
>> documentation shows the parameter numbers in DEC. your sysex string
>> below should affect parameter 54 HEX (84 DEC, 'LFO 1 Initial
>> Amplitude'). 54 DEC ('Env 1 Initial Release Time') is 36 HEX so the
>> command F0 10 06 06 36 00 F7 (Note! F7 not 7F!) should do the trick.
>>
>> i guess i need to add hex codes to my page as well
>> (http://wolzow.mindworks.ee/analog/m1k-midi-spec.htm).
>>
>> hope this helped,
>> margus
>>
>> On Wed, Aug 5, 2009 at 6:59 AM, stublito<ogusa@...> wrote:
>>>
>>>
>>> Can't seem to get my new (to me) M1000 to respond to sysex paramter changes
>>> embedded in a MIDI track.
>>>
>>> I do have the bank select sysex working perfectly, the bank unlock also.
>>>
>>> The manual says it's F0 10 06 06 <parameter> <value>. No luck. For
>>> instance,
>>> F0 10 06 06 54 00 7F has no effect on Env 1 decay.
>>>
>>> I'm an experienced sysex programmer, I have my Roland analog stuff obeying
>>> my every whim. Any suggestions?
>>>
>>> Thanks
>>>
>>> Stublito
>>>
>>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>