Hi Joris, > I notice a lot of wishes, questions about what LA already can > do. Current development at Emagic, on audio automation and virtual instruments, will have ramifications on the Environment. (Unless it is bypassed altogether and becomes obsolete). Because of this, the Environment is the obvious next area for improvement. I'm presenting a coherent architecture, goals for directly usable features, and lists of highly useful features to implement as Env objects. Also the historical bad reputation of the Environment, for being complex and hard to use, single biggest black mark against Logic... is an excellent reason to improve it. > *It wont make LA easier to use, implementing lot's of this and that, > while e-MAGIC things are already there. The Environment can & should be made easier to use. > *It will make Emagic easier to expand LA with possibilities, while > keep concentrating on there e-MAGIC parts. Not sure what you mean? > Need an example ? Now you have that Track-Mixer (great indeed, > leave it) I like the Track Mixer very much; but it's not *nearly* sufficient for real work. It needs to be a smarter user interface, connecting to back-end information & configuration of what it controls... this config info would be stored in the Instrument/ Multi-Instruments, in the Environment. Each Instrument needs to know/ be configurable as to what controllers (volume, pan, reverb, chorus, cutoff, resonance, etc) should be displayed in the track mixer and what numbers they are on. Each Instrument needs the ability to store bank & patch select, SysEx dump, controller dump or whatever is needed to set it up. Multi-Insts need this for each channel, plus a global setup. With the back-end Instruments and Multi-Insts knowing the *basics* of controlling their devices; and the Track Mixer providing a user interface across all of this; we will be able to control our MIDI devices with a functional user interface. As opposed to the fairly opposite situation, which we currently have. Sending setup info for a song, is an absolutely basic task. We need much better usability here. > Now that MIDI MIXER with MEMORIES. > What can it be used for ? > To setup all Volume, Pan, Reverb, LPF, Resonance and so on > (maximum eight controllers on 16 channels) while mixing. That sounds good. But I expect it can't receive and store SysEx/ controller dumps to send as device setup. Really this is very basic functionality. Logic should offer *strong* support so no-one needs to build their own. It can & should be done better as coer functionality in Logic. Cheers, Thomas