composer rom in command station - missing patchcords ?
2013-01-10 by jezfez
Yahoo Groups archive
Archive for xl7.
Index last updated: 2026-03-30 01:19 UTC
Thread
2013-01-10 by jezfez
the patch cords for my composer rom are not mapped correctly the amp decay and amp release knobs are patched to lfo2 amt and lfo2 rate i assume this is because the composer rom is from the proteus 2000 which only has 12 knobs? anyone else notice this with their composer rom ? thanks
2013-01-10 by D F Tweedie
2013-01-10 by jezfez
yes it is easy to remap the knobs and save as a user preset, just a bit annoying when browsing presets that might benefit from some release it is odd, surely they could have used the same cc#s for the lfo knobs maybe my composer rom is corrupt i would love to hear from anyone with a composer rom in their cs - do your lfo2 knobs work or are they moved to sustain/release ? thanks!
2013-01-10 by D F Tweedie
2013-01-10 by steve_the_composer
I don't have time for a lengthy reply here, but as others have suggested, there are a few different things: 1. The CC values that are set in master/global for MidiA --> MidiP. 2. The patchcords that assign synth engine functions to MidiA --> MidiP [and therefore the CCs they are assigned]. 3. The labels for the knobs that are printed on the unit itself. As pointed out, the 12-controller ROMs and the 16-controller ROMS have different function assignments in the patchcords. Also, different ROMs have different conventions for making use of patchcord and functions. Therefore, the names on the panel do not apply to all ROMs. Is this what you are talking about? Sorry for the brevity here. If this doesn't help, I will have more time later. Steve --- In xl7@yahoogroups.com, "jezfez" wrote: > > the patch cords for my composer rom are not mapped correctly > > the amp decay and amp release knobs are patched to lfo2 amt and lfo2 rate > > i assume this is because the composer rom is from the proteus 2000 which only has 12 knobs? > > anyone else notice this with their composer rom ? > > thanks >
2013-01-11 by jezfez
i understand, thanks for your help better engineering could have had these knobs mapped to their correct labels and skipping the others jamming away while trying to remember what preset is from what rom to know which knob to turn is a bit of a drag do you know what roms support the cs 16 knobs by default ? thanks guys!
2013-01-12 by D F Tweedie
2013-01-12 by D F Tweedie
2013-01-13 by steve_the_composer
Footnote: If you are familiar with the "syxer" program I have mentioned, one advanced (in the way future) idea is what I call the "parametizer." I have never coded it, buts have some developmental plans. One of the features would be the ability to store and recall preferred parameters, such as patchcord sets. So if someone designed some 12-controller or 16-controller setups they liked, they could apply them as a template of user parameters to build presets. However, in order to build the software, I would need detailed info about all the ROMs and I just do not have the time to mine and map each of the ROMS. Just like syxer can change ROM IDs in a bank of presets, it would be cool to swap in a template of preferred patchcords. I suppose it would be possible to extrude a set of patchcords from one designated preset and apply that to a whole bank of user presets. There is no guaranteeing what it would sound like, though, just like switching ROM IDs. 1. Extrude one set of layer level patchcords (4 layers) from a known 16-controller preset. 2. Apply it to a bank of 12-controller presets. 3. Listen to the bank for any useful results. 4. Tweak any promising presets and save. Could probably do something (no range checking or anything) in syxer. Of course, if anyone else wants to code this, I'd be happy to contribute what I could. Steve By the way, I don't know, but I assume all the ROMs that were not specifically included with gear have presets on board that were designed for the least common denominator--12 controllers. I only have the Protozoa, and that's for 12 controllers (Still more than the original P/1/2/3s. --- In xl7@yahoogroups.com, D F Tweedie wrote: > > I'd add, that the Ensoniq Halo appears to be the only keyboard model with only 12 patch cords (4 knobs with three switches), so that ROM is presumably for 12 patch cords only. > > DF > > > Â > CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication. > > > ________________________________ > From: steve_the_composer > To: xl7@yahoogroups.com > Sent: Friday, January 11, 2013 2:53 PM > Subject: [xl7] Re: composer rom in command station - missing patchcords ? > > > Â > See below. > > --- In xl7@yahoogroups.com, "jezfez" wrote: > > > > i understand, thanks for your help > > > > better engineering could have had these knobs mapped to their correct labels and skipping the others > > My understanding is that they ARE mapped to the correct label for each ROM that is native to a specific box. In order words, the XL-7 labels match the XL-7 ROM presets, the XL-1 labels, match the XLEAD ROM presets, etc. > > The problem (if you want to think of it as a problem as opposed to an opportunity to really delve into the architecture of the gear)comes in when people put non-native ROMS in their boxes, such as a P2K Composer ROM in a Command Station (or supplemental ROMS that could be purchased separately). > > Unfortunately, the boxes were so well designed that many people don't go beyond the default settings and will just tweak presets as opposed to design their own from scratch. I found it was a fun challenge to zero out all of the patch cords and build a set of presets from scratch. > > Yes, there is a lot to learn, and if you accept the challenge you will surely will be able to do things beyond what you first imagined. I would encourage such exploration. You really get to know what's what. > > I agree for starters, it is nice that MidiA is Filter Cutoff, MidiB is Resonance, etc. Even after all these years, I don't change a number of these default assignments. Its just a very handy convenience. > > Oh, by the way you might find that even with the factory designed presets any particular knob will control different sound shaping parameters via patchcords on different layers in the same preset. I would encourage you to dissect some presets to see what the sound designers did to get the various effects. That way you will have insights into making the box do what you want. > > > jamming away while trying to remember what preset is from what rom to know which knob to turn is a bit of a drag > > I use pen and paper, sometimes an index card. Also, if you tweak (or design) presets or just reorganize the factory presets you like, you can use some naming conventions to make it easier to find presets. (I will see if I can find some posts that describe some of the naming convents I use--such as 001: and 002: as prefixes for families of repated presets, using CaPs, etc. > > > > > do you know what roms support the cs 16 knobs by default ? > > I started a table and tried to get members here to contribute basic info about each ROM, including whether each was a 12-controller ROM or a 16-controller ROM. Not a whole lot of people contributed. The table as I put it together in May is in a folder called TEMP in the files section. Its called ROMS pdf. Its probably about 7% complete. I'd be happy to fill it in if people here want to supply the information about each ROM they have that's not already in the table. > > Steve >