Hi everyone, I am working on a fairly large environment mostly having to do with the Audio Objects in the Audio Mixer - I have added several features, including an Audio Object Link that links the audio objects in any combination with a presets option, an FX mute button that turns all Effect slots on/off returning them to the last position you left them, a Sends mute on/off, an up/down buttons feature to move any Audio object function up or down in any incrememnt, an A/B comparison for all audio object functions, and several other features I want to be able to control in Logic by clicking on it or from my keyboard controller. I have posted before with some generous replies from the likes of Len, John Pitcairn, and Hendrik in regards to cable limits and the point where the information stops short as it is being sent down several environment objects. Basically, I realize now, that my problem is not how far down the info is snet, but how *much* info can be sent simultaneously. For example, I can do an A/B comparison of almost all otf the Audio object features *simultaneously* in one click on the button, without having (as an alternative) to create two buttons and use an alternating split ultimately using one button to click twice to capture everything that needs to be sent. I have since experimented with how much info can be passed simultaneously with small test environments using just one MIDI channel, and the more objects you have, Logic tries to distribute the limited amount of messages that can be sent across the new info highways (cables) to the new cabled objects draining the messages that are supposed to make it to the original object you cabled them to in the first place. This is not to be confused with a cable limit or environment object limit issue. Now, I am just wondering, how much of an impact MIDI channels have in regards to *preserving* the messages that are being sent in all driections from one main object such as the Audio object (sent simultaneously). I have actually only used MIDI channel 1 for everything up until now, simply because when I first started the environment I didnt see any need for sending the info out on different MIDI channels. Which is why I am asking anyone who has already had the experience if going back and doing a complete re-haul on my environment will be worth the effort, or does the limited amount of messages (note-on, Control, any kind of message) still cut short when being initiated by just one fader button. Or will I still end up with having to send info on two or more fader buttons to get the whole array of messages across? Thanks in advance for any advice, Rick Shorey

--- In logic-users@y..., "rick_7777us" <rick_shorey@h...> wrote: I have since experimented > with how much info can be passed simultaneously with small > test environments using just one MIDI channel, and the more > objects you have, Logic tries to distribute the limited amount of > messages that can be sent across the new info highways > (cables) to the new cabled objects draining the messages that > are supposed to make it to the original object you cabled them > to in the first place. This is not to be confused with a cable limit > or environment object limit issue. It sure sounds like the cable limit problem to me, which is more subtle than it sounds. The limit is not the total number of cables as such, but the number of cables that any single event must pass through, _including_ any copies of that event generated via multiple cable outputs from objects, or by the "copy events" transformer. It can add up really fast if you're trying to distribute one trigger event to lots of objects. The good news is that there are a couple of techniques to avoid it, the bad news is that it genrally requires a rethink of how you communicate with lots of objects. Rather than trying to narrow it down in the abstract like this, do you want to compress the offending environments (.zip or .sit please) and email them to me? John Pitcairn ------------------------------------------------------------------ Midi controller learn in Logic. Soft takeover. Lots of memories. Tracks remember control assignments. Write track automation. Fadermapper demo: http://www.revolver.co.nz/fadermapper/ ------------------------------------------------------------------