by John Bowen » Wed Apr 01, 2020 3:33 pm
Thank you for the video.
I fallow also the Solaris Sysex documentation and the table "Parameter Changed" page 7
I wanted to control the Env6 Attack, so I founded address low mid and high are 13 50 03,
00 12 34 for Manufacturer ID,
00 for Device ID,
10 for Solaris ID,
13 for Function: Parameter Changed.
So after different tests I wrote F0 00 12 34 00 10 13 13 50 03 DT F7 in the A-Pro Editor, with Data type adjustment on DT1: 4bit/4bit, min value=0, max value=12 and it pretty much works. When I move the selected cursor of the A-500pro, the env6 attack move from 0.0ms to 19.85s in the Solaris.
I have to move the cursor very finely because its stroke is short between 0.0ms and 19.85s ! But I can refine and make the handling more pleasant by reducing the max value to 2 for example. By cons in this case I can only adjust from 0.0ms to 3.47s ...
For the Data type adjustment in the A-Pro I have the choice between:
DT0: 7-bit 1 octet min=0 max=127
DT1: 4-bit/4-bit 2 octets min=0 max=15
DT2: 7-bit/7-bit (MSB/LSB) 2 octets min=0 max=127
DT3: 7-bit/7-bit (LSB/MSB) 2 octets min=0 max=127
DT4: 4-bit/ 4-bit/4-bit/4-bit 4 octets min=0 max=255
Did I done the good choice with DT1 ?
I was also able to control the sysex message sent from the Solarium editor by placing Gmidimonitor between the Solarium and the Solaris. But in this case I find messages more in line with the table in the Solaris Sysex documentation, with 3 bit for the DT like this for the Attack at 0.0ms : F0 00 12 34 00 10 13 13 50 03 00 00 00 F7
It is more conform with the 3 parameters, dd Parameter value bits 14 - 20, ee Parameter value bits 7 - 13 and ff Parameter value bits 0 - 6 that I founded in Solaris Sysex documentation with "Parameter Changed" page 7 ...
Thank you for the video.
I fallow also the Solaris Sysex documentation and the table "Parameter Changed" page 7
I wanted to control the Env6 Attack, so I founded address low mid and high are 13 50 03,
00 12 34 for Manufacturer ID,
00 for Device ID,
10 for Solaris ID,
13 for Function: Parameter Changed.
So after different tests I wrote F0 00 12 34 00 10 13 13 50 03 DT F7 in the A-Pro Editor, with Data type adjustment on DT1: 4bit/4bit, min value=0, max value=12 and it pretty much works. When I move the selected cursor of the A-500pro, the env6 attack move from 0.0ms to 19.85s in the Solaris.
I have to move the cursor very finely because its stroke is short between 0.0ms and 19.85s ! But I can refine and make the handling more pleasant by reducing the max value to 2 for example. By cons in this case I can only adjust from 0.0ms to 3.47s ...
For the Data type adjustment in the A-Pro I have the choice between:
DT0: 7-bit 1 octet min=0 max=127
DT1: 4-bit/4-bit 2 octets min=0 max=15
DT2: 7-bit/7-bit (MSB/LSB) 2 octets min=0 max=127
DT3: 7-bit/7-bit (LSB/MSB) 2 octets min=0 max=127
DT4: 4-bit/ 4-bit/4-bit/4-bit 4 octets min=0 max=255
Did I done the good choice with DT1 ?
I was also able to control the sysex message sent from the Solarium editor by placing Gmidimonitor between the Solarium and the Solaris. But in this case I find messages more in line with the table in the Solaris Sysex documentation, with 3 bit for the DT like this for the Attack at 0.0ms : F0 00 12 34 00 10 13 13 50 03 [color=#0000FF]00 00 00[/color] F7
It is more conform with the 3 parameters, dd Parameter value bits 14 - 20, ee Parameter value bits 7 - 13 and ff Parameter value bits 0 - 6 that I founded in Solaris Sysex documentation with "Parameter Changed" page 7 ...