thanks for the advice, it seems to confirm what I know, iow, outside of the cc's, it doesn't work very well. Even within the cc's, there's not enough of a value change to control what the evolver has, and unless the sysex are limited to under 7 value changes..it doesn't work at all. I bought the SL because it was the only midi controller with a keyboard that sent sysex..it does, but it's not fully implemented..really false advertising. afa as novation support..3 tries, no response. thanks Novation! good to know you don't feel up to helping to explain how your products don't work. so, it appears either a MEK to have direct control, or keep trying to figure out the puzzle of mixing cc's and sysex, albeit limited sysex, as anything with a lot of range is not available. One of the problems I see with a MEK though is that it won't control the combos..so i think a new question/topic. I wish i had the resources and $$ for a PEK, but that isn't in the cards. I will try a midiox look see afa the info dump, thanks for the tip. I also am having problems when trying to use the PER/soundtower editor/SL 37 combo..very strange things going on in the combo bank libraries when choosing a combo, the PER's values jump like crazy..and though I can hear the values change on the rack, it doesn't translate in the onscreen ST editor. There's probably a midi loop happening somewhere, but I haven't figured that out. This is all a shame really, as i have the SL doing some good things, starting the sequencer, changing the tempo, controlling certain parameters..it's just that I think it could do a lot more..and with the PER's being relatively inexpensive on the used market now, it's too bad there aren't any keyboard controllers that really are all that useful. I imagine the original use of the PER was NOT like the DT prophet, iow, it wasn't really meant as a stand alone, rather as an extension to the PEK, but..I know there are people using it as a stand alone, and I love the way the damn thing sounds. --- In DSI_Evolver@yahoogroups.com, "a33e" <yurkie@...> wrote: > > > > 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 jp
Attachments
- No local attachments were found for this message.