Sorry about near-to-zero-information-post but i wanted to say something supportive. :D I've been there many times, wanting to do something that should be possible and it has been looked that i am the only one in the world who tries to do that. I guess that the main problem is that when people get something challenging done and working well they don't always be motivated enough to share that information.. . . BTW. It might help to ask from other hardware editors groups, like Bitstream 3X or Peavey PC1600 groups. How about monitoring MIDI traffic that some software editors send when you are editing those parameters that you would like to add to your implementation? .433E - http://soundcloud.com/tvr --- In DSI_Evolver@yahoogroups.com, "justmullaya" <justmull@...> wrote: > > I can confirm that indeed the Novation sysex is not comprehensive enough to support the evolver. I was also possibly the original uploader of the novation cc template > It was 5 or 6 years ago when I tried but I seem to remember that the granularity with which the msb and lsb that the novation could specify was not sufficient ....cut... > > There is the one sysex template here, but it only covers the cc's. > > > > Anybody? > > >
Message
Re: Remote SL 37/DSI PolyEvolver Rack sysex programming/map
2011-04-02 by a33e