Thanks for chiming in on this, Bruno! I was thinking of you as I read the P2K threads on this last night.
Funny how the "new and improved" workaround came about. After a fair amount of testing I decided to put some test patches in the 000^0 to 009^0 range because my evolution keyboard has buttons 0 -> 9 which send out Program Changes.
One dummy preset (non-sounding) is Syn:ExtInt=02 (Button 8), another is Syn:ExtInt=12 (Button 9). So after bouncing bank and forth between these and 3 presets with different Intervals stored (Buttons 0->3), for some reason I just hit Button 0 (000^0 has the preset where the Interval set to 12) and it worked!!!!! :-)
Yes, well worth finding the workaround--even 9 years later. Since the keyboard just sends out midi data, I can't see any reason why it wouldn't work from any source (hardware or software).
---------------
Command Station 2.0 Addendum, page 20:
• Arp Extension Interval Bug Fixed - When switching presets, arp extension interval is now correctly loaded.
In the back of my mind over the past day or two, I seemed to remember something official about the issue being fixed and there it was!!!
This morning, I tested my P2500. The arp extension interval did indeed load correctly. Evidently the fix did not make it into OS 2.26 for the P2K variants.
---------------
Regarding the possibility of hidden patchcord destinations and the potential to access any that might be there via sysex, your questions are excellent.
> Now there are only two questions:
> a) does it actually work?
> b) how it is being represented on the Edit Preset screen?
Based on my method for mining the hidden (and known) Remote Control sysex commands, I have been thinking of testing ALL possible destinations.
Toward that end, I will be making a spreadsheet with the destinations from the E-Mu X Softsynths and all the published values from the sysex manual to systematically test and track the results. A few months ago, I started a spreadsheet with all the published sysex parameters with the goal of correcting the manual systematically. (I already had some corrections on my paper printout from years ago!)
The sysex parameter spreadsheet has the old and new notes plus, I have cut-and-paste sysex!! So, I can just put it into midi-ox, send it, see what happens, change test values, and repeat until my mind can't take any more!!!
I mention this in case you will be getting out your sysex PC and are interested in testing a range of parameters. If so, PM me; I can put the spreadsheet on my website and give you access to it.
Two other things: (1) let me know if you come up with different results re: Arp Ext Interval on the CS, and (2) since I am planning to do more with arps starting in a couple of week, I would be interested in knowing more of what others are already doing with arps. I was already planning to look though already "published" ideas (websites, manuals, previous Tricks and Tips done by rEalm, etc. and was wondering if there are other ideas people use that couple be compiled into a new Tips & Tricks.
BTW:
-- page 68 of the sysex manual also has destination 51: 'Chorus Position ITD. The X series has that!!!!
-- I have a handwritten note I did some time, "76 = VEnvSus"
-- the X softsynths have a realtime resonance destination, not available to hardware users; but:
---- I recall rEalm saying something to the effect that the realtime resonance [in the hardware] was cool and he would liked to have seen it in the released version of the OS upgrade.
Oh how I wish someone would make a sampling Command Station Ultra that all the features of the X series softsynths--compatible (of course) with both EOS/EIV Ultra Samplers and the P2K/CS ROMplers--but with 21st century improvements (including full remote control that works with MIDI 1.0 and MIDI 2.0).
For what its worth, here are the layer-level patchcord destinations from the softsynths:
Attachments
- No local attachments were found for this message.