Dave Smith Instruments SYNTHESIZERS

I got my evolver desktop on Sunday, and love it, I am also excited to
get it up and running with my sequencing software.  I use Sonar 3, and
thus am attempting to write an insturment definition for the Evolver.
 Before I do all this work, has anyone else written an INS file for
the Evolver Ver 3?

I also use Sonar, but I've only made a very simplistic instrument 
definition with nothing but the bank and patch numbers... -It works, but 
I haven't even figured out how to get the bank numbers to be 1-4 instead 
of 0-3. :P

So if you do get your ins-file working, could you please share it? :)

Regards!
/Christian
-----------------
http://www.newmodernangels.com
http://www.myspace.com/newmodernangels

Trevor wrote:

>I got my evolver desktop on Sunday, and love it, I am also excited to
>get it up and running with my sequencing software.  I use Sonar 3, and
>thus am attempting to write an insturment definition for the Evolver.
> Before I do all this work, has anyone else written an INS file for
>the Evolver Ver 3?  
>
>
>  
>

I wanted to apologize for essisially posting this twice.

So far I have it worked out so that it has the correct patch and bank
number, however, I am still having difficulty with ironing out the
RPN's and the NRPN's.  I will be spending the better part of this week
getting those figured out, and hopefully working in Sonar, so things
like velocity and volume are controlled as well.

I posted asking about the RPN's and NPRN's last night in hopes that
someone in this group might already have them figured out.  When I get
it working I'll probably post it every where I can think of. :)

--- In DSI_Evolver@yahoogroups.com, Christian Andersson
<synth_christian@...> wrote:
>
> I also use Sonar, but I've only made a very simplistic instrument 
> definition with nothing but the bank and patch numbers... -It works,
but 
> I haven't even figured out how to get the bank numbers to be 1-4
instead 

> of 0-3. :P
> 
> So if you do get your ins-file working, could you please share it? :)
> 
> Regards!
> /Christian
> -----------------
> http://www.newmodernangels.com
> http://www.myspace.com/newmodernangels
> 
> Trevor wrote:
> 
> >I got my evolver desktop on Sunday, and love it, I am also excited to
> >get it up and running with my sequencing software.  I use Sonar 3, and
> >thus am attempting to write an insturment definition for the Evolver.
> > Before I do all this work, has anyone else written an INS file for
> >the Evolver Ver 3?  
> >
> >
> >  
> >
>

Hi!

I recently recieved my Evolver desktop synth (I traded a Microkorg and an  
Alesis Q2 in for it plus some cash) and am now looker for a useful remote/  
controller. I also use Ableton Live 5 and am wondering which one to get.  
The M-Audio Axiom looks sweet and very useable (lots of knobs etc.),  
however it does have a price tag. The Korg K25/Kxx have an attractive  
price, but not much going on in terms of knobs and controls. The Novation  
Remote SL would be cool, but it does have a hefty price tag. The M-Audio  
Oxygen range does have a useful amount of knobs it seems, and is  
comparatively inexpensive. Anybody have a clever suggestion?

Cheers,

John

Korg Kontrol 49 is the one I use and if you have Ableton live it has some great templates 
for that to control too. It also becomes a MIDI interface for your computer so together with 
a good audio card you're ready to go ... !

Martin

I second the Novation 25.  I bought one a year ago and upgraded the OS
to the X-Station.  It is an amazingly powerful synth (basically the
Novation K) and a great controller with lots of knobs and faders, and
templates for Ableton and a host of other applications.


--- In DSI_Evolver@...m, James Elliott <johans121@...> wrote:
>
> I just picked up a Novation Remote 25 - not the SL or LE version. It
is pretty sweet.
> 
> John Daly <Solaris23@...> wrote:  Hi!
> 
> I recently recieved my Evolver desktop synth (I traded a Microkorg
and an 
> Alesis Q2 in for it plus some cash) and am now looker for a useful
remote/ 
> controller. I also use Ableton Live 5 and am wondering which one to
get. 
> The M-Audio Axiom looks sweet and very useable (lots of knobs etc.), 
> however it does have a price tag. The Korg K25/Kxx have an attractive 
> price, but not much going on in terms of knobs and controls. The
Novation 
> Remote SL would be cool, but it does have a hefty price tag. The
M-Audio 

> Oxygen range does have a useful amount of knobs it seems, and is 
> comparatively inexpensive. Anybody have a clever suggestion?
> 
> Cheers,
> 
> John
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com
>

Same here. I've been working with a Novation25, Ableton Live, vst 
plugins(NI Photone and Vokator) and of course a mono evolver and i 
don't feel the need to look for anything else. I also have the 
V-STATION and i really like the simplicity versus power (distortion 
is the best have heard in a vst plugin so far). 

Simon

--- In DSI_Evolver@yahoogroups.com, "Seth" <luckydoglarry@...> wrote:
>
> I second the Novation 25.  I bought one a year ago and upgraded the 
OS
> to the X-Station.  It is an amazingly powerful synth (basically the
> Novation K) and a great controller with lots of knobs and faders, 
and
> templates for Ableton and a host of other applications.
> 
> 
> --- In DSI_Evolver@yahoogroups.com, James Elliott <johans121@> 
wrote:
> >
> > I just picked up a Novation Remote 25 - not the SL or LE version. 
It
> is pretty sweet.
> > 
> > John Daly <Solaris23@> wrote:  Hi!
> > 
> > I recently recieved my Evolver desktop synth (I traded a Microkorg
> and an 
> > Alesis Q2 in for it plus some cash) and am now looker for a useful
> remote/ 
> > controller. I also use Ableton Live 5 and am wondering which one 
to
> get. 
> > The M-Audio Axiom looks sweet and very useable (lots of knobs 
etc.), 
> > however it does have a price tag. The Korg K25/Kxx have an 
attractive 

> > price, but not much going on in terms of knobs and controls. The
> Novation 
> > Remote SL would be cool, but it does have a hefty price tag. The
> M-Audio 
> > Oxygen range does have a useful amount of knobs it seems, and is 
> > comparatively inexpensive. Anybody have a clever suggestion?
> > 
> > Cheers,
> > 
> > John
> > 
> > 
> > 
> > 
> > Yahoo! Groups Links
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around 
> > http://mail.yahoo.com
> >
>

As far as I am aware, the Evolver transmits neither RPN or NRPN's. It only transmits a few basic CC's, everything else is SYSEX. Programming SYSEX isn't terrible. You just need a BASIC understanding of the binary and hexidecimal notations. MIDIOX will help you see what your Evolver is transmitting and a simple scientific calculator (like the one provided with windows) will help translating between binary, hexidecimal, and decimal.
 
For example (and I'm at work at the moment, not home in front of my manual, I am doing this from "memory"), I believe "LFO 1 Amount" is Program Parameter #42 and it can accept values of 0 through 200. If you look in the manual, it will tell you how to format a SYSEX message for the transmission of a Program Parameter. It's definition is in binary, something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001 0XXX XXXX 0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different combinations 0's and 1's). The program parameter list is in decimal, ie 42, and can also be found in the manual. Your resulting SYSEX message needs to be in hexidecimal, ie F0 ..... F7.
 
Here is a partial explaination of that binary string above. I am only going over the important parts as most of it will be a static hard coded value.
 
X
Ok, 0XXX XXXX represents the two bytes needed to convey what parameter you are using - in this example we are using #42. If you use the calculator provided by Windows, in scientific mode, 42 translates to '2A' in Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the first one matches the template above, the second one was added because 42 in binary is only 6 characters long and two bytes is composed of 8 characters, so the first is "given", the second is filler]).
 
Y & Z
Now for the fun part. If I am not mistaken 0000 YYYY represents the "least significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ represents the "most significant byte" (MS) of the Program Parameter Value. Let's use 198 as our Program Parameter Value. The way it is written in the sysex message is slightly backwards. For example the binary representation of 198 is "1100 0110" LS=0110 & MS=1100.  To break that down MS=The byte containing "anything" over 15. LS=The byte that contains 15 and under. Broken down even further MS='1100'==192 (128 + 64) and LS='0110'==6 (4 + 2)  MS (192) + LS (6) = 198.
 
So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }--> 0000 MS & 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
 
Now to put our sysex message together translate your binary to hexidecimal (two byte groupings)
 
1111 0000 = F,0
0000 0001 = 0,1
0010 0000 = 2,0
0000 0001 = 0,1
0000 0001 = 0,1
0010 1010 = 2,A  <<<<< Program Parameter for LFO Amount 1 = 42
0000 0110 = 0,6  <<<<< LS for 198  = 6
0000 1100 = 0,C  <<<<< MS for 198 = 192
1111 0111 = F,7
 
F0 01 20 01 01 2A 06 0C F7
 
Anyway, I hope this made sense. I know it looks daunting, however one thing to keep in mind is typically the only value you ever have to calculate is the Program Parameter, like LFO 1 Amount. The LS and MS are typically variables, so your editor will fill them in, you just tell it where they reside in the SYSEX string.
 
On my Novation Remote 25, it can only use values up to 127. So I can not go all the way up to 200 for my LFO 1 Amount. And on top of that, I can only have one variable in my SYSEX string. So I have to choose whether I want to turn my MS or LS into a variable and then hard code the other.
 
Here is what we are looking at:
LS can represent 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14, or 15
MS can represent 16,32,48,64,80,96,112,128,144,160,176,192,208,224, or 240
 
Since I can only use one variable and would have to hard code the other, I would choose to hard code LS and turn MS into a variable so I can have a wider range of control - so I could get any of the MS values plus the hard coded LS. Since LFO 1 Amount only goes to 200 it makes no sense to hard code the LS to anything other than 0-8, if I do, I will make my control even LESS granular then it already is!
 
So, on my novation, my SYSEX for LFO 1 Amount looks like:
f0 01 20 01 01 2a 0DV 00 f7.
0DV=variable=MS
00=hard coded=LS
 
If you already knew this, then sorry for the long winded answer. If you didn't I really hope you understood this. If you didn't then I will be glad to answer any additional questions. I hope I got it right myself!
 
Now for my rant....
I'm going to complain to Novation, their controllers are VERY EASY to program, however they aren't very flexable with SYSEX messages!!! 
 
It also sux that Dave Smith didn't implement NRPN for their granular controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS THERE FOR!!! YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T YOU USE NRPN!!
 
Sorry Dave, I DO love your products though!
 
-Jim
 
 
 
 
 
 
 
Ok, to help determine what is the LS and MS
----- Original Message ----
From: Trevor <nucleic_acid@...>
To: DSI_Evolver@yahoogroups.com
Sent: Wednesday, June 7, 2006 1:49:54 PM
Subject: Re: [Evolver] cakewalk INS files?


So far I have it worked out so that it has the correct patch and bank
number, however, I am still having difficulty with ironing out the
RPN's and the NRPN's. I will be spending the better part of this week
getting those figured out, and hopefully working in Sonar, so things
like velocity and volume are controlled as well.

I posted asking about the RPN's and NPRN's last night in hopes that
someone in this group might already have them figured out. When I get
it working I'll probably post it every where I can think of. :)

--- In DSI_Evolver@ yahoogroups. com, Christian Andersson
<synth_christian@ ...> wrote:
>
> I also use Sonar, but I've only made a very simplistic instrument 
> definition with nothing but the bank and patch numbers... -It works,
but 
> I haven't even figured out how to get the bank numbers to be 1-4
instead 

> of 0-3. :P
> 
> So if you do get your ins-file working, could you please share it? :)
> 
> Regards!
> /Christian
> ------------ -----
> http://www.newmoder nangels.com
> http://www.myspace. com/newmodernang els
> 
> Trevor wrote:
> 
> >I got my evolver desktop on Sunday, and love it, I am also excited to
> >get it up and running with my sequencing software. I use Sonar 3, and
> >thus am attempting to write an insturment definition for the Evolver.
> > Before I do all this work, has anyone else written an INS file for
> >the Evolver Ver 3? 
> >
> >
> > 
> >
>

Paragraphs and line breaks are your friends ;)
Best Regards, James


>As far as I am aware, the Evolver transmits neither RPN or NRPN's. It only transmits a few basic CC's, everything else is SYSEX. Programming SYSEX isn't terrible. You just need a BASIC understanding of the binary and hexidecimal notations. MIDIOX will help you see what your Evolver is transmitting and a simple scientific calculator (like the one provided with windows) will help translating between binary, hexidecimal, and decimal. For example (and I'm at work at the moment, not home in front of my manual, I am doing this from "memory"), I believe "LFO 1 Amount" is Program Parameter #42 and it can accept values of 0 through 200. If you look in the manual, it will tell you how to format a SYSEX message for the transmission of a Program Parameter. It's definition is in binary, something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001 0XXX XXXX 0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different combinations 0's and 1's). The program parameter list is in decimal, ie 42, and can also be found in the manual. Your resulting SYSEX message needs to be in hexidecimal, ie F0 ..... F7. Here is a partial explaination of that binary string above. I am only going over the important parts as most of it will be a static hard coded value. XOk, 0XXX XXXX represents the two bytes needed to convey what parameter you are using - in this example we are using #42. If you use the calculator provided by Windows, in scientific mode, 42 translates to '2A' in Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the first one matches the template above, the second one was added because 42 in binary is only 6 characters long and two bytes is composed of 8 characters, so the first is "given", the second is filler]). Y & ZNow for the fun part. If I am not mistaken 0000 YYYY represents the "least significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ represents the "most significant byte" (MS) of the Program Parameter Value. Let's use 198 as our Program Parameter Value. The way it is written in the sysex message is slightly backwards. For example the binary representation of 198 is "1100 0110" LS=0110 & MS=1100.  To break that down MS=The byte containing "anything" over 15. LS=The byte that contains 15 and under. Broken down even further MS='1100'==192 (128 + 64) and LS='0110'==6 (4 + 2)  MS (192) + LS (6) = 198. So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }--> 0000 MS & 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110. Now to put our sysex message together translate your binary to hexidecimal (two byte groupings) 1111 0000 = F,00000 0001 = 0,10010 0000 = 2,00000 0001 = 0,10000 0001 = 0,10010 1010 = 2,A  <<<<< Program Parameter for LFO Amount 1 = 420000 0110 = 0,6  <<<<< LS for 198  = 60000 1100 = 0,C  <<<<< MS for 198 = 1921111 0111 = F,7 F0 01 20 01 01 2A 06 0C F7 Anyway, I hope this made sense. I know it looks daunting, however one thing to keep in mind is typically the only value you ever have to calculate is the Program Parameter, like LFO 1 Amount. The LS and MS are typically variables, so your editor will fill them in, you just tell it where they reside in the SYSEX string. On my Novation Remote 25, it can only use values up to 127 .................................................................................................................................................................

I don't know what happened!?!?

When I typed it up it was full of paragraph and line breaks! I am a programmer by trade, so white space IS my friend!! Maybe it is this new Yahoo Mail Beta.......

Wow, all that typing went to waste!

----- Original Message ----
From: Richard <richardscott@...>
To: DSI_Evolver@yahoogroups.com
Sent: Thursday, June 8, 2006 12:18:14 PM
Subject: Re: [Evolver] cakewalk INS files?

                              
wow!
  
 now i know for sure I'll never do any sysex programming!  :)
  
 Richard
  
    ----- Original Message ----- 
   From:    Carbon111 
   To: DSI_Evolver@yahoogroups.com    
   Sent: Thursday, June 08, 2006 5:12    PM
   Subject: Re: [Evolver] cakewalk INS    files?
   

      Paragraphs and line breaks are your friends ;)
Best Regards,    James

>As far as I am aware, the Evolver transmits neither RPN or    NRPN's. It only transmits a few basic CC's, everything else is SYSEX.    Programming SYSEX isn't terrible. You just need a BASIC understanding of the    binary and hexidecimal notations. MIDIOX will help you see what your    Evolver is transmitting and a simple scientific calculator (like the one    provided with windows) will help translating between binary, hexidecimal, and    decimal. For example (and I'm at work at the moment, not home in front of    my manual, I am doing this from "memory"), I believe "LFO 1 Amount" is Program    Parameter #42 and it can accept values of 0 through 200. If you look in the    manual, it will tell you how to format a SYSEX message for the transmission of    a Program Parameter. It's definition is in binary, something like 1111 0000    0000 0001 0010 0000 0000 0001 0000 0001 0XXX XXXX 0000 YYYY 0000 ZZZZ    1011 0111 (XYZ are variables for different combinations 0's and 1's).
 The    program parameter list is in decimal, ie 42, and can also be found in the    manual. Your resulting SYSEX message needs to be in hexidecimal, ie F0 .........    F7. Here is a partial explaination of that binary string above. I am only    going over the important parts as most of it will be a static hard coded    value. XOk, 0XXX XXXX represents the two bytes needed to convey what    parameter you are using - in this example we are using #42. If you use the    calculator provided by Windows, in scientific mode, 42 translates to '2A' in    Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the first one    matches the template above, the second one was added because 42 in binary is    only 6 characters long and two bytes is composed of 8 characters, so the first    is "given", the second is filler]). Y & ZNow for the fun    part. If I am not mistaken 0000 YYYY represents the "least significant    byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ
 represents the "most    significant byte" (MS) of the Program Parameter Value. Let's use 198 as    our Program Parameter Value. The way it is written in the sysex message is    slightly backwards. For example the binary representation of 198 is "1100    0110" LS=0110 & MS=1100.  To break that down MS=The byte containing    "anything" over 15. LS=The byte that contains 15 and under. Broken down even    further MS='1100'==192 (128 + 64) and LS='0110'==6 (4 + 2)  MS (192) + LS    (6) = 198. So to put it together: 198 = '1100    0110' }--> MS= 1100 LS=0110 }--> 0000 MS & 0000    LS }--> SYSEX LS MS == 0000 1100 0000 0110. Now to put our sysex    message together translate your binary to hexidecimal (two byte    groupings) 1111 0000 = F,00000 0001 = 0,10010 0000 = 2,00000 0001 =    0,10000 0001 = 0,10010 1010 = 2,A  <<<<< Program Parameter    for LFO Amount 1 = 420000 0110 = 0,6  <<<<< LS for    198  = 60000 1100 = 0,C  <<<<< MS for 198 = 1921111    0111 = F,7 F0 01 20 01 01 2A
 06 0C F7 Anyway, I hope this    made sense. I know it looks daunting, however one thing to keep in mind is    typically the only value you ever have to calculate is the Program Parameter,    like LFO 1 Amount. The LS and MS are typically variables, so your editor will    fill them in, you just tell it where they reside in the SYSEX string. On    my Novation Remote 25, it can only use values up to 127    ....................... ......... ......... ......... ......... ................. ......... ......... ......... ......... .............. ......... ......... ......... ......... ........... ......... .....

At 11:53 AM 6/8/06, you wrote:
>I don't know what happened!?!?
>When I typed it up it was full of paragraph and line breaks! I am a 
>programmer by trade, so white space IS my friend!


Came in fine and formatted on my Eudora pc email client:

>As far as I am aware, the Evolver transmits neither RPN or NRPN's. It only 
>transmits a few basic CC's, everything else is SYSEX. Programming SYSEX 
>isn't terrible. You just need a BASIC understanding of the binary and 
>hexidecimal notations. MIDIOX will help you see what your Evolver is 
>transmitting and a simple scientific calculator (like the one provided 
>with windows) will help translating between binary, hexidecimal, and decimal.
>
>For example (and I'm at work at the moment, not home in front of my 
>manual, I am doing this from "memory"), I believe "LFO 1 Amount" is 
>Program Parameter #42 and it can accept values of 0 through 200. If you 
>look in the manual, it will tell you how to format a SYSEX message for the 
>transmission of a Program Parameter. It's definition is in binary, 
>something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001 0XXX XXXX 
>0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different 
>combinations 0's and 1's). The program parameter list is in decimal, ie 
>42, and can also be found in the manual. Your resulting SYSEX message 
>needs to be in hexidecimal, ie F0 ..... F7.
>
>Here is a partial explaination of that binary string above. I am only 
>going over the important parts as most of it will be a static hard coded value.
>
>X
>Ok, 0XXX XXXX represents the two bytes needed to convey what parameter you 
>are using - in this example we are using #42. If you use the calculator 
>provided by Windows, in scientific mode, 42 translates to '2A' in 
>Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the first 
>one matches the template above, the second one was added because 42 in 
>binary is only 6 characters long and two bytes is composed of 8 
>characters, so the first is "given", the second is filler]).
>
>Y & Z
>Now for the fun part. If I am not mistaken 0000 YYYY represents the "least 
>significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ 
>represents the "most significant byte" (MS) of the Program Parameter 
>Value. Let's use 198 as our Program Parameter Value. The way it is written 
>in the sysex message is slightly backwards. For example the binary 
>representation of 198 is "1100 0110" LS=0110 & MS=1100.  To break that 
>down MS=The byte containing "anything" over 15. LS=The byte that contains 
>15 and under. Broken down even further MS='1100'==192 (128 + 64) and 
>LS='0110'==6 (4 + 2)  MS (192) + LS (6) = 198.
>
>So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }--> 0000 MS 
>& 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
>
>Now to put our sysex message together translate your binary to hexidecimal 
>(two byte groupings)
>
>1111 0000 = F,0
>0000 0001 = 0,1
>0010 0000 = 2,0
>0000 0001 = 0,1
>0000 0001 = 0,1
>0010 1010 = 2,A  <<<<< Program Parameter for LFO Amount 1 = 42
>0000 0110 = 0,6  <<<<< LS for 198  = 6
>0000 1100 = 0,C  <<<<< MS for 198 = 192
>1111 0111 = F,7
>
>F0 01 20 01 01 2A 06 0C F7
>
>Anyway, I hope this made sense. I know it looks daunting, however one 
>thing to keep in mind is typically the only value you ever have to 
>calculate is the Program Parameter, like LFO 1 Amount. The LS and MS are 
>typically variables, so your editor will fill them in, you just tell it 
>where they reside in the SYSEX string.
>
>On my Novation Remote 25, it can only use values up to 127. So I can not 
>go all the way up to 200 for my LFO 1 Amount. And on top of that, I can 
>only have one variable in my SYSEX string. So I have to choose whether I 
>want to turn my MS or LS into a variable and then hard code the other.
>
>Here is what we are looking at:
>LS can represent 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14, or 15
>MS can represent 16,32,48,64,80,96,112,128,144,160,176,192,208,224, or 240
>
>Since I can only use one variable and would have to hard code the other, I 
>would choose to hard code LS and turn MS into a variable so I can have a 
>wider range of control - so I could get any of the MS values plus the hard 
>coded LS. Since LFO 1 Amount only goes to 200 it makes no sense to hard 
>code the LS to anything other than 0-8, if I do, I will make my control 
>even LESS granular then it already is!
>
>So, on my novation, my SYSEX for LFO 1 Amount looks like:
>f0 01 20 01 01 2a 0DV 00 f7.
>0DV=variable=MS
>00=hard coded=LS
>
>If you already knew this, then sorry for the long winded answer. If you 
>didn't I really hope you understood this. If you didn't then I will be 
>glad to answer any additional questions. I hope I got it right myself!
>
>Now for my rant....
>I'm going to complain to Novation, their controllers are VERY EASY to 
>program, however they aren't very flexable with SYSEX messages!!!
>
>It also sux that Dave Smith didn't implement NRPN for their granular 
>controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS THERE FOR!!! 
>YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T YOU USE NRPN!!
>
>Sorry Dave, I DO love your products though!
>
>-Jim

James Elliott wrote:
> I don't know what happened!?!?
> 
> When I typed it up it was full of paragraph and line breaks! I am a 
> programmer by trade, so white space IS my friend!! Maybe it is this new 
> Yahoo Mail Beta.......
> 
>

It came out nice and spaced for me.....

$900 plus shipping and handling.
Very Good Condition with Software (editor), manual and upgraded to the 
most recent O.S. including firmware.

Email with any questions.

Will ship very carefully packed and insured.

PayPal is preferred but I will take USPS Money Orders and Cashier's 
Checks drawn on a known national bank.

Very Best Regards, James
-- 
http://www.carbon111.com

An excellent explanation Jim
I tried setting up a Remote 25 template before the CC's came out on 
the evo and got stuck on the fact that there was only one variable 
available. Your post has clarified things a lot. Thanks so much 
(archive this one people!!)I agree that the Remote 25's sysex 
implementation is terrible!

--- In DSI_Evolver@yahoogroups.com, James Elliott <johans121@...> 
wrote:
>
> As far as I am aware, the Evolver transmits neither RPN or NRPN's. 
It only transmits a few basic CC's, everything else is SYSEX. 
Programming SYSEX isn't terrible. You just need a BASIC understanding 
of the binary and hexidecimal notations. MIDIOX will help you see 
what your Evolver is transmitting and a simple scientific calculator 
(like the one provided with windows) will help translating between 
binary, hexidecimal, and decimal.
>  
> For example (and I'm at work at the moment, not home in front of my 
manual, I am doing this from "memory"), I believe "LFO 1 Amount" is 
Program Parameter #42 and it can accept values of 0 through 200. If 
you look in the manual, it will tell you how to format a SYSEX 
message for the transmission of a Program Parameter. It's definition 
is in binary, something like 1111 0000 0000 0001 0010 0000 0000 0001 
0000 0001 0XXX XXXX 0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables 
for different combinations 0's and 1's). The program parameter list 
is in decimal, ie 42, and can also be found in the manual. Your 
resulting SYSEX message needs to be in hexidecimal, ie F0 ..... F7.
>  
> Here is a partial explaination of that binary string above. I am 
only going over the important parts as most of it will be a static 
hard coded value.
>  
> X
> Ok, 0XXX XXXX represents the two bytes needed to convey what 
parameter you are using - in this example we are using #42. If you 
use the calculator provided by Windows, in scientific mode, 42 
translates to '2A' in Hexidecimal. (or 0010 1010 in binary [notice 
the leading 0's, the first one matches the template above, the second 
one was added because 42 in binary is only 6 characters long and two 
bytes is composed of 8 characters, so the first is "given", the 
second is filler]).
>  
> Y & Z
> Now for the fun part. If I am not mistaken 0000 YYYY represents 
the "least significant byte" (LS) of the Program Parameter VALUE. 
0000 ZZZZ represents the "most significant byte" (MS) of the Program 
Parameter Value. Let's use 198 as our Program Parameter Value. The 
way it is written in the sysex message is slightly backwards. For 
example the binary representation of 198 is "1100 0110" LS=0110 & 
MS=1100.  To break that down MS=The byte containing "anything" over 
15. LS=The byte that contains 15 and under. Broken down even further 
MS='1100'==192 (128 + 64) and LS='0110'==6 (4 + 2)  MS (192) + LS (6) 
= 198.
>  
> So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }--> 
0000 MS & 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
>  
> Now to put our sysex message together translate your binary to 
hexidecimal (two byte groupings)
>  
> 1111 0000 = F,0
> 0000 0001 = 0,1
> 0010 0000 = 2,0
> 0000 0001 = 0,1
> 0000 0001 = 0,1
> 0010 1010 = 2,A  <<<<< Program Parameter for LFO Amount 1 = 42
> 0000 0110 = 0,6  <<<<< LS for 198  = 6
> 0000 1100 = 0,C  <<<<< MS for 198 = 192
> 1111 0111 = F,7
>  
> F0 01 20 01 01 2A 06 0C F7
>  
> Anyway, I hope this made sense. I know it looks daunting, however 
one thing to keep in mind is typically the only value you ever have 
to calculate is the Program Parameter, like LFO 1 Amount. The LS and 
MS are typically variables, so your editor will fill them in, you 
just tell it where they reside in the SYSEX string.
>  
> On my Novation Remote 25, it can only use values up to 127. So I 
can not go all the way up to 200 for my LFO 1 Amount. And on top of 
that, I can only have one variable in my SYSEX string. So I have to 
choose whether I want to turn my MS or LS into a variable and then 
hard code the other.
>  
> Here is what we are looking at:
> LS can represent 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14, or 15
> MS can represent 16,32,48,64,80,96,112,128,144,160,176,192,208,224, 
or 240
>  
> Since I can only use one variable and would have to hard code the 
other, I would choose to hard code LS and turn MS into a variable so 
I can have a wider range of control - so I could get any of the MS 
values plus the hard coded LS. Since LFO 1 Amount only goes to 200 it 
makes no sense to hard code the LS to anything other than 0-8, if I 
do, I will make my control even LESS granular then it already is!
>  
> So, on my novation, my SYSEX for LFO 1 Amount looks like:
> f0 01 20 01 01 2a 0DV 00 f7.
> 0DV=variable=MS
> 00=hard coded=LS
>  
> If you already knew this, then sorry for the long winded answer. If 
you didn't I really hope you understood this. If you didn't then I 
will be glad to answer any additional questions. I hope I got it 
right myself!
>  
> Now for my rant....
> I'm going to complain to Novation, their controllers are VERY EASY 
to program, however they aren't very flexable with SYSEX messages!!! 
>  
> It also sux that Dave Smith didn't implement NRPN for their 
granular controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS 
THERE FOR!!! YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T 
YOU USE NRPN!!

>  
> Sorry Dave, I DO love your products though!
>  
> -Jim

Thanks for the detailed explanation.  I will definitely have to study
it, as working with sysex is new to me.  The math seems relatively
simple, but doable.  I have to echo the final sentiment in you post,
which is part of the reason I had convinced myself that there just had
to be more parameters, given who designed the synth.  It seemed almost
inconceivable that a person who was such a dominant figure in Midi,
would design a synth that is not compatible with current midi
standards.  Love the synth, but this sysex thing is driving me nuts.   


--- In DSI_Evolver@yahoogroups.com, John Pascuzzi <johnp@...> wrote:
>
> At 11:53 AM 6/8/06, you wrote:
> >I don't know what happened!?!?
> >When I typed it up it was full of paragraph and line breaks! I am a 
> >programmer by trade, so white space IS my friend!
> 
> 
> Came in fine and formatted on my Eudora pc email client:
> 
> 
> >As far as I am aware, the Evolver transmits neither RPN or NRPN's.
It only 
> >transmits a few basic CC's, everything else is SYSEX. Programming
SYSEX 
> >isn't terrible. You just need a BASIC understanding of the binary and 
> >hexidecimal notations. MIDIOX will help you see what your Evolver is 
> >transmitting and a simple scientific calculator (like the one provided 
> >with windows) will help translating between binary, hexidecimal,
and decimal.
> >
> >For example (and I'm at work at the moment, not home in front of my 
> >manual, I am doing this from "memory"), I believe "LFO 1 Amount" is 
> >Program Parameter #42 and it can accept values of 0 through 200. If
you 
> >look in the manual, it will tell you how to format a SYSEX message
for the 
> >transmission of a Program Parameter. It's definition is in binary, 
> >something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001
0XXX XXXX 
> >0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different 
> >combinations 0's and 1's). The program parameter list is in
decimal, ie 
> >42, and can also be found in the manual. Your resulting SYSEX message 
> >needs to be in hexidecimal, ie F0 ..... F7.
> >
> >Here is a partial explaination of that binary string above. I am only 
> >going over the important parts as most of it will be a static hard
coded value.
> >
> >X
> >Ok, 0XXX XXXX represents the two bytes needed to convey what
parameter you 
> >are using - in this example we are using #42. If you use the
calculator 
> >provided by Windows, in scientific mode, 42 translates to '2A' in 
> >Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the
first 
> >one matches the template above, the second one was added because 42 in 
> >binary is only 6 characters long and two bytes is composed of 8 
> >characters, so the first is "given", the second is filler]).
> >
> >Y & Z
> >Now for the fun part. If I am not mistaken 0000 YYYY represents the
"least 
> >significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ 
> >represents the "most significant byte" (MS) of the Program Parameter 
> >Value. Let's use 198 as our Program Parameter Value. The way it is
written 
> >in the sysex message is slightly backwards. For example the binary 
> >representation of 198 is "1100 0110" LS=0110 & MS=1100.  To break that 
> >down MS=The byte containing "anything" over 15. LS=The byte that
contains 
> >15 and under. Broken down even further MS='1100'==192 (128 + 64) and 
> >LS='0110'==6 (4 + 2)  MS (192) + LS (6) = 198.
> >
> >So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }-->
0000 MS 
> >& 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
> >
> >Now to put our sysex message together translate your binary to
hexidecimal 
> >(two byte groupings)
> >
> >1111 0000 = F,0
> >0000 0001 = 0,1
> >0010 0000 = 2,0
> >0000 0001 = 0,1
> >0000 0001 = 0,1
> >0010 1010 = 2,A  <<<<< Program Parameter for LFO Amount 1 = 42
> >0000 0110 = 0,6  <<<<< LS for 198  = 6
> >0000 1100 = 0,C  <<<<< MS for 198 = 192
> >1111 0111 = F,7
> >
> >F0 01 20 01 01 2A 06 0C F7
> >
> >Anyway, I hope this made sense. I know it looks daunting, however one 
> >thing to keep in mind is typically the only value you ever have to 
> >calculate is the Program Parameter, like LFO 1 Amount. The LS and
MS are 
> >typically variables, so your editor will fill them in, you just
tell it 
> >where they reside in the SYSEX string.
> >
> >On my Novation Remote 25, it can only use values up to 127. So I
can not 
> >go all the way up to 200 for my LFO 1 Amount. And on top of that, I
can 
> >only have one variable in my SYSEX string. So I have to choose
whether I 
> >want to turn my MS or LS into a variable and then hard code the other.
> >
> >Here is what we are looking at:
> >LS can represent 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14, or 15
> >MS can represent 16,32,48,64,80,96,112,128,144,160,176,192,208,224,
or 240
> >
> >Since I can only use one variable and would have to hard code the
other, I 
> >would choose to hard code LS and turn MS into a variable so I can
have a 
> >wider range of control - so I could get any of the MS values plus
the hard 
> >coded LS. Since LFO 1 Amount only goes to 200 it makes no sense to
hard 
> >code the LS to anything other than 0-8, if I do, I will make my
control 
> >even LESS granular then it already is!
> >
> >So, on my novation, my SYSEX for LFO 1 Amount looks like:
> >f0 01 20 01 01 2a 0DV 00 f7.
> >0DV=variable=MS
> >00=hard coded=LS
> >
> >If you already knew this, then sorry for the long winded answer. If
you 
> >didn't I really hope you understood this. If you didn't then I will be 
> >glad to answer any additional questions. I hope I got it right myself!
> >
> >Now for my rant....
> >I'm going to complain to Novation, their controllers are VERY EASY to 
> >program, however they aren't very flexable with SYSEX messages!!!
> >
> >It also sux that Dave Smith didn't implement NRPN for their granular 
> >controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS THERE
FOR!!! 

> >YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T YOU USE NRPN!!
> >
> >Sorry Dave, I DO love your products though!
> >
> >-Jim
>

I wrote a very long letter earlier today to Novation explaining their poor SYSEX implementation and how it would benefit them as well as the rest of us if they added a couple additional parameters to their message. I will share their response with the group - if and when I get it.
 
-Jim


----- Original Message ----
From: Trevor <nucleic_acid@...>
To: DSI_Evolver@yahoogroups.com
Sent: Friday, June 9, 2006 2:02:05 PM
Subject: Re: [Evolver] cakewalk INS files?


Thanks for the detailed explanation. I will definitely have to study
it, as working with sysex is new to me. The math seems relatively
simple, but doable. I have to echo the final sentiment in you post,
which is part of the reason I had convinced myself that there just had
to be more parameters, given who designed the synth. It seemed almost
inconceivable that a person who was such a dominant figure in Midi,
would design a synth that is not compatible with current midi
standards. Love the synth, but this sysex thing is driving me nuts. 

--- In DSI_Evolver@ yahoogroups. com, John Pascuzzi <johnp@...> wrote:
>
> At 11:53 AM 6/8/06, you wrote:
> >I don't know what happened!?!?
> >When I typed it up it was full of paragraph and line breaks! I am a 
> >programmer by trade, so white space IS my friend!
> 
> 
> Came in fine and formatted on my Eudora pc email client:
> 
> 
> >As far as I am aware, the Evolver transmits neither RPN or NRPN's.
It only 
> >transmits a few basic CC's, everything else is SYSEX. Programming
SYSEX 
> >isn't terrible. You just need a BASIC understanding of the binary and 
> >hexidecimal notations. MIDIOX will help you see what your Evolver is 
> >transmitting and a simple scientific calculator (like the one provided 
> >with windows) will help translating between binary, hexidecimal,
and decimal.
> >
> >For example (and I'm at work at the moment, not home in front of my 
> >manual, I am doing this from "memory"), I believe "LFO 1 Amount" is 
> >Program Parameter #42 and it can accept values of 0 through 200. If
you 
> >look in the manual, it will tell you how to format a SYSEX message
for the 
> >transmission of a Program Parameter. It's definition is in binary, 
> >something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001
0XXX XXXX 
> >0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different 
> >combinations 0's and 1's). The program parameter list is in
decimal, ie 
> >42, and can also be found in the manual. Your resulting SYSEX message 
> >needs to be in hexidecimal, ie F0 ..... F7.
> >
> >Here is a partial explaination of that binary string above. I am only 
> >going over the important parts as most of it will be a static hard
coded value.
> >
> >X
> >Ok, 0XXX XXXX represents the two bytes needed to convey what
parameter you 
> >are using - in this example we are using #42. If you use the
calculator 
> >provided by Windows, in scientific mode, 42 translates to '2A' in 
> >Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the
first 
> >one matches the template above, the second one was added because 42 in 
> >binary is only 6 characters long and two bytes is composed of 8 
> >characters, so the first is "given", the second is filler]).
> >
> >Y & Z
> >Now for the fun part. If I am not mistaken 0000 YYYY represents the
"least 
> >significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ 
> >represents the "most significant byte" (MS) of the Program Parameter 
> >Value. Let's use 198 as our Program Parameter Value. The way it is
written 
> >in the sysex message is slightly backwards. For example the binary 
> >representation of 198 is "1100 0110" LS=0110 & MS=1100. To break that 
> >down MS=The byte containing "anything" over 15. LS=The byte that
contains 
> >15 and under. Broken down even further MS='1100'==192 (128 + 64) and 
> >LS='0110'== 6 (4 + 2) MS (192) + LS (6) = 198.
> >
> >So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }-->
0000 MS 
> >& 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
> >
> >Now to put our sysex message together translate your binary to
hexidecimal 
> >(two byte groupings)
> >
> >1111 0000 = F,0
> >0000 0001 = 0,1
> >0010 0000 = 2,0
> >0000 0001 = 0,1
> >0000 0001 = 0,1
> >0010 1010 = 2,A <<<<< Program Parameter for LFO Amount 1 = 42
> >0000 0110 = 0,6 <<<<< LS for 198 = 6
> >0000 1100 = 0,C <<<<< MS for 198 = 192
> >1111 0111 = F,7
> >
> >F0 01 20 01 01 2A 06 0C F7
> >
> >Anyway, I hope this made sense. I know it looks daunting, however one 
> >thing to keep in mind is typically the only value you ever have to 
> >calculate is the Program Parameter, like LFO 1 Amount. The LS and
MS are 
> >typically variables, so your editor will fill them in, you just
tell it 
> >where they reside in the SYSEX string.
> >
> >On my Novation Remote 25, it can only use values up to 127. So I
can not 
> >go all the way up to 200 for my LFO 1 Amount. And on top of that, I
can 
> >only have one variable in my SYSEX string. So I have to choose
whether I 
> >want to turn my MS or LS into a variable and then hard code the other.
> >
> >Here is what we are looking at:
> >LS can represent 0,1,2,3,4,5, 6,7,8,9,10, 11,12,13, 14, or 15
> >MS can represent 16,32,48,64, 80,96,112, 128,144,160, 176,192,208, 224,
or 240
> >
> >Since I can only use one variable and would have to hard code the
other, I 
> >would choose to hard code LS and turn MS into a variable so I can
have a 
> >wider range of control - so I could get any of the MS values plus
the hard 
> >coded LS. Since LFO 1 Amount only goes to 200 it makes no sense to
hard 
> >code the LS to anything other than 0-8, if I do, I will make my
control 
> >even LESS granular then it already is!
> >
> >So, on my novation, my SYSEX for LFO 1 Amount looks like:
> >f0 01 20 01 01 2a 0DV 00 f7.
> >0DV=variable= MS
> >00=hard coded=LS
> >
> >If you already knew this, then sorry for the long winded answer. If
you 
> >didn't I really hope you understood this. If you didn't then I will be 
> >glad to answer any additional questions. I hope I got it right myself!
> >
> >Now for my rant....
> >I'm going to complain to Novation, their controllers are VERY EASY to 
> >program, however they aren't very flexable with SYSEX messages!!!
> >
> >It also sux that Dave Smith didn't implement NRPN for their granular 
> >controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS THERE
FOR!!! 

> >YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T YOU USE NRPN!!
> >
> >Sorry Dave, I DO love your products though!
> >
> >-Jim
>

I've now listed the Poly Evolver Rack on eBay - free shipping w/ BIN of 
$995:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=7422393831

Best Regards, James
--
http://www.carbon111.com

Hi,

 

I just got a new remote SL, super duper Automap, most advanced
controller ever. Blah, blah, blah.

 

It still works the same with SYSEX as the old models, so basically
pretty useless.

 

Andy

 

________________________________

From: DSI_Evolver@yahoogroups.com [mailto:DSI_Evolver@yahoogroups.com]
On Behalf Of James Elliott
Sent: 09 June 2006 20:39
To: DSI_Evolver@yahoogroups.com
Subject: Re: [Evolver] Novation/Evolver SYSEX: was cakewalk INS files?

 

I wrote a very long letter earlier today to Novation explaining their
poor SYSEX implementation and how it would benefit them as well as the
rest of us if they added a couple additional parameters to their
message. I will share their response with the group - if and when I get
it.

 

-Jim

----- Original Message ----
From: Trevor <nucleic_acid@hotmail.com>
To: DSI_Evolver@yahoogroups.com
Sent: Friday, June 9, 2006 2:02:05 PM
Subject: Re: [Evolver] cakewalk INS files?

Thanks for the detailed explanation. I will definitely have to study
it, as working with sysex is new to me. The math seems relatively
simple, but doable. I have to echo the final sentiment in you post,
which is part of the reason I had convinced myself that there just had
to be more parameters, given who designed the synth. It seemed almost
inconceivable that a person who was such a dominant figure in Midi,
would design a synth that is not compatible with current midi
standards. Love the synth, but this sysex thing is driving me nuts. 

--- In DSI_Evolver@ yahoogroups. com
<mailto:DSI_Evolver%40yahoogroups.com> , John Pascuzzi <johnp@...>
wrote:
>
> At 11:53 AM 6/8/06, you wrote:
> >I don't know what happened!?!?
> >When I typed it up it was full of paragraph and line breaks! I am a 
> >programmer by trade, so white space IS my friend!
> 
> 
> Came in fine and formatted on my Eudora pc email client:
> 
> 
> >As far as I am aware, the Evolver transmits neither RPN or NRPN's.
It only 
> >transmits a few basic CC's, everything else is SYSEX. Programming
SYSEX 
> >isn't terrible. You just need a BASIC understanding of the binary and

> >hexidecimal notations. MIDIOX will help you see what your Evolver is 
> >transmitting and a simple scientific calculator (like the one
provided 
> >with windows) will help translating between binary, hexidecimal,
and decimal.
> >
> >For example (and I'm at work at the moment, not home in front of my 
> >manual, I am doing this from "memory"), I believe "LFO 1 Amount" is 
> >Program Parameter #42 and it can accept values of 0 through 200. If
you 
> >look in the manual, it will tell you how to format a SYSEX message
for the 
> >transmission of a Program Parameter. It's definition is in binary, 
> >something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001
0XXX XXXX 
> >0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different 
> >combinations 0's and 1's). The program parameter list is in
decimal, ie 
> >42, and can also be found in the manual. Your resulting SYSEX message

> >needs to be in hexidecimal, ie F0 ..... F7.
> >
> >Here is a partial explaination of that binary string above. I am only

> >going over the important parts as most of it will be a static hard
coded value.
> >
> >X
> >Ok, 0XXX XXXX represents the two bytes needed to convey what
parameter you 
> >are using - in this example we are using #42. If you use the
calculator 
> >provided by Windows, in scientific mode, 42 translates to '2A' in 
> >Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the
first 
> >one matches the template above, the second one was added because 42
in 
> >binary is only 6 characters long and two bytes is composed of 8 
> >characters, so the first is "given", the second is filler]).
> >
> >Y & Z
> >Now for the fun part. If I am not mistaken 0000 YYYY represents the
"least 
> >significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ 
> >represents the "most significant byte" (MS) of the Program Parameter 
> >Value. Let's use 198 as our Program Parameter Value. The way it is
written 
> >in the sysex message is slightly backwards. For example the binary 
> >representation of 198 is "1100 0110" LS=0110 & MS=1100. To break that

> >down MS=The byte containing "anything" over 15. LS=The byte that
contains 
> >15 and under. Broken down even further MS='1100'==192 (128 + 64) and 
> >LS='0110'== 6 (4 + 2) MS (192) + LS (6) = 198.
> >
> >So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }-->
0000 MS 
> >& 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
> >
> >Now to put our sysex message together translate your binary to
hexidecimal 
> >(two byte groupings)
> >
> >1111 0000 = F,0
> >0000 0001 = 0,1
> >0010 0000 = 2,0
> >0000 0001 = 0,1
> >0000 0001 = 0,1
> >0010 1010 = 2,A <<<<< Program Parameter for LFO Amount 1 = 42
> >0000 0110 = 0,6 <<<<< LS for 198 = 6
> >0000 1100 = 0,C <<<<< MS for 198 = 192
> >1111 0111 = F,7
> >
> >F0 01 20 01 01 2A 06 0C F7
> >
> >Anyway, I hope this made sense. I know it looks daunting, however one

> >thing to keep in mind is typically the only value you ever have to 
> >calculate is the Program Parameter, like LFO 1 Amount. The LS and
MS are 
> >typically variables, so your editor will fill them in, you just
tell it 
> >where they reside in the SYSEX string.
> >
> >On my Novation Remote 25, it can only use values up to 127. So I
can not 
> >go all the way up to 200 for my LFO 1 Amount. And on top of that, I
can 
> >only have one variable in my SYSEX string. So I have to choose
whether I 
> >want to turn my MS or LS into a variable and then hard code the
other.
> >
> >Here is what we are looking at:
> >LS can represent 0,1,2,3,4,5, 6,7,8,9,10, 11,12,13, 14, or 15
> >MS can represent 16,32,48,64, 80,96,112, 128,144,160, 176,192,208,
224,
or 240
> >
> >Since I can only use one variable and would have to hard code the
other, I 
> >would choose to hard code LS and turn MS into a variable so I can
have a 
> >wider range of control - so I could get any of the MS values plus
the hard 
> >coded LS. Since LFO 1 Amount only goes to 200 it makes no sense to
hard 
> >code the LS to anything other than 0-8, if I do, I will make my
control 
> >even LESS granular then it already is!
> >
> >So, on my novation, my SYSEX for LFO 1 Amount looks like:
> >f0 01 20 01 01 2a 0DV 00 f7.
> >0DV=variable= MS
> >00=hard coded=LS
> >
> >If you already knew this, then sorry for the long winded answer. If
you 
> >didn't I really hope you understood this. If you didn't then I will
be 
> >glad to answer any additional questions. I hope I got it right
myself!
> >
> >Now for my rant....
> >I'm going to complain to Novation, their controllers are VERY EASY to

> >program, however they aren't very flexable with SYSEX messages!!!
> >
> >It also sux that Dave Smith didn't implement NRPN for their granular 
> >controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS THERE
FOR!!! 
> >YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T YOU USE
NRPN!!

> >
> >Sorry Dave, I DO love your products though!
> >
> >-Jim
>

That sux! Sorry man!


----- Original Message ----
From: Andrew Capon <acapon@...>
To: DSI_Evolver@yahoogroups.com
Sent: Monday, June 12, 2006 2:35:35 PM
Subject: RE: [Evolver] Novation/Evolver SYSEX: was cakewalk INS files?


Hi,
 
I just got a new remote SL, super duper Automap, most advanced controller ever. Blah, blah, blah.
 
It still works the same with SYSEX as the old models, so basically pretty useless.
 
Andy
 



From: DSI_Evolver@yahoogroups.com [mailto:DSI_Evolver@yahoogroups.com] On Behalf Of James Elliott
Sent: 09 June 2006 20:39
To: DSI_Evolver@yahoogroups.com
Subject: Re: [Evolver] Novation/Evolver SYSEX: was cakewalk INS files?
 
I wrote a very long letter earlier today to Novation explaining their poor SYSEX implementation and how it would benefit them as well as the rest of us if they added a couple additional parameters to their message. I will share their response with the group - if and when I get it.
 
-Jim
----- Original Message ----
From: Trevor <nucleic_acid@...>
To: DSI_Evolver@yahoogroups.com
Sent: Friday, June 9, 2006 2:02:05 PM
Subject: Re: [Evolver] cakewalk INS files?
Thanks for the detailed explanation. I will definitely have to study
it, as working with sysex is new to me. The math seems relatively
simple, but doable. I have to echo the final sentiment in you post,
which is part of the reason I had convinced myself that there just had
to be more parameters, given who designed the synth. It seemed almost
inconceivable that a person who was such a dominant figure in Midi ,
would design a synth that is not compatible with current midi
standards. Love the synth, but this sysex thing is driving me nuts. 

--- In DSI_Evolver@ yahoogroups. com, John Pascuzzi <johnp@...> wrote:
>
> At 11:53 AM 6/8/06, you wrote:
> >I don't know what happened!?!?
> >When I typed it up it was full of paragraph and line breaks! I am a 
> >programmer by trade, so white space IS my friend!
> 
> 
> Came in fine and formatted on my Eudora pc email client:
> 
> 
> >As far as I am aware, the Evolver transmits neither RPN or NRPN's.
It only 
> >transmits a few basic CC's, everything else is SYSEX. Programming
SYSEX 
> >isn't terrible. You just need a BASIC understanding of the binary and 
> >hexidecimal notations. MIDIOX will help you see what your Evolver is 
> >transmitting and a simple scientific calculator (like the one provided 
> >with windows) will help translating between binary, hexidecimal,
and decimal.
> >
> >For example (and I'm at work at the moment, not home in front of my 
> >manual, I am doing this from "memory"), I believe "LFO 1 Amount" is 
> >Program Parameter #42 and it can accept values of 0 through 200. If
you 
> >look in the manual, it will tell you how to format a SYSEX message
for the 
> >transmission of a Program Parameter. It's definition is in binary, 
> >something like 1111 0000 0000 0001 0010 0000 0000 0001 0000 0001
0XXX XXXX 
> >0000 YYYY 0000 ZZZZ 1011 0111 (XYZ are variables for different 
> >combinations 0's and 1's). The program parameter list is in
decimal, ie 
> >42, and can also be found in the manual. Your resulting SYSEX message 
> >needs to be in hexidecimal, ie F0 ..... F7.
> >
> >Here is a partial explaination of that binary string above. I am only 
> >going over the important parts as most of it will be a static hard
coded value.
> >
> >X
> >Ok, 0XXX XXXX represents the two bytes needed to convey what
parameter you 
> >are using - in this example we are using #42. If you use the
calculator 
> >provided by Windows, in scientific mode, 42 translates to '2A' in 
> >Hexidecimal. (or 0010 1010 in binary [notice the leading 0's, the
first 
> >one matches the template above, the second one was added because 42 in 
> >binary is only 6 characters long and two bytes is composed of 8 
> >characters, so the first is "given", the second is filler]).
> >
> >Y & Z
> >Now for the fun part. If I am not mistaken 0000 YYYY represents the
"least 
> >significant byte" (LS) of the Program Parameter VALUE. 0000 ZZZZ 
> >represents the "most significant byte" (MS) of the Program Parameter 
> >Value. Let's use 198 as our Program Parameter Value. The way it is
written 
> >in the sysex message is slightly backwards. For example the binary 
> >representation of 198 is "1100 0110" LS=0110 & MS=1100. To break that 
> >down MS=The byte containing "anything" over 15. LS=The byte that
contains 
> >15 and under. Broken down even further MS='1100'==192 (128 + 64) and 
> >LS='0110'== 6 (4 + 2) MS (192) + LS (6) = 198.
> >
> >So to put it together: 198 = '1100 0110' }--> MS=1100 LS=0110 }-->
0000 MS 
> >& 0000 LS }--> SYSEX LS MS == 0000 1100 0000 0110.
> >
> >Now to put our sysex message together translate your binary to
hexidecimal 
> >(two byte groupings)
> >
> >1111 0000 = F,0
> >0000 0001 = 0,1
> >0010 0000 = 2,0
> >0000 0001 = 0,1
> >0000 0001 = 0,1
> >0010 1010 = 2,A <<<<< Program Parameter for LFO Amount 1 = 42
> >0000 0110 = 0,6 <<<<< LS for 198 = 6
> >0000 1100 = 0,C <<<<< MS for 198 = 192
> >1111 0111 = F,7
> >
> >F0 01 20 01 01 2A 06 0C F7
> >
> >Anyway, I hope this made sense. I know it looks daunting, however one 
> >thing to keep in mind is typically the only value you ever have to 
> >calculate is the Program Parameter, like LFO 1 Amount. The LS and
MS are 
> >typically variables, so your editor will fill them in, you just
tell it 
> >where they reside in the SYSEX string.
> >
> >On my Novation Remote 25, it can only use values up to 127. So I
can not 
> >go all the way up to 200 for my LFO 1 Amount. And on top of that, I
can 
> >only have one variable in my SYSEX string. So I have to choose
whether I 
> >want to turn my MS or LS into a variable and then hard code the other.
> >
> >Here is what we are looking at:
> >LS can represent 0,1,2,3,4,5, 6,7,8,9,10, 11,12,13, 14, or 15
> >MS can represent 16,32,48,64, 80,96,112, 128,144,160, 176,192,208, 224,
or 240
> >
> >Since I can only use one variable and would have to hard code the
other, I 
> >would choose to hard code LS and turn MS into a variable so I can
have a 
> >wider range of control - so I could get any of the MS values plus
the hard 
> >coded LS. Since LFO 1 Amount only goes to 200 it makes no sense to
hard 
> >code the LS to anything other than 0-8, if I do, I will make my
control 
> >even LESS granular then it already is!
> >
> >So, on my novation, my SYSEX for LFO 1 Amount looks like:
> >f0 01 20 01 01 2a 0DV 00 f7.
> >0DV=variable= MS
> >00=hard coded=LS
> >
> >If you already knew this, then sorry for the long winded answer. If
you 
> >didn't I really hope you understood this. If you didn't then I will be 
> >glad to answer any additional questions. I hope I got it right myself!
> >
> >Now for my rant....
> >I'm going to complain to Novation, their controllers are VERY EASY to 
> >program, however they aren't very flexable with SYSEX messages!!!
> >
> >It also sux that Dave Smith didn't implement NRPN for their granular 
> >controls instead of SYSEX! HELLO DAVE, THAT IS WHAT NRPN IS THERE
FOR!!! 

> >YOU HELPED CREATE THE MIDI SPECIFICATION, SO WHY DIDN'T YOU USE NRPN!!
> >
> >Sorry Dave, I DO love your products though!
> >
> >-Jim
>