Hi Eric, It changes from time to time, but here is mine: Audio ins: A: main 261e B: mod 261e C: main 259e D: mod 259e E: 266e noise (flat) F,G,H: variable Audio outs: 1: to 291e input A 2: to 291e input B 3: to 291e input C 4: to 292e channel 4 5: to 291e Mod input A or B or C Channel A,B,C from the 291e go to the first 3 channels of the 292e, then to the 227e. Channel 4 of the 292e goes straight to channel 4 on the 227e. CV ins: A: 249e CV 1 B: 249e CV 2 C: 249e pls out. D: 281e(1) env out. E: 266e Qantized Random Voltages output C. F: 222e ch 6 CV1 out G: 222e ch 7 CV1 out H: 222e ch 6 Loc out CV outs: 1: 261e CV in 2: 259e CV in 3: 227e ch 1 spatial control in 4: 227e ch 2 spatial control in 5: varies. this is a rough idea of what i do at the moment : i recently upgraded from a 12 space case to an 18 with a 222e, so i am far from an ideal routing standard....what you see here is a natural evolution of the old routing. There is also a lot of direct patching involved, most of the time, which i am forced to write down in order to recreate later on, if needed. I am also uploading a copy of a patch sheet i used early this year for a concert i did at Berklee College of Music in Boston: the whole concert was based on that routing and i developed the composition over a series of different presets. hope this helps, A. --- In 200e@yahoogroups.com, alt-mode <yahoo@...> wrote: > > Hi, > > I just rearranged my system into an 18 WLS from a bunch of 4 boat racks and > I would like to develop a basic set of routings through the 210e as patch > templates and for performance. The question is, what do you route through > the 210e to gain the maximum flexibility/functionality? I don¹t mind > overriding or adding additional patch cords for a particular setup but I¹d > like to have some basic routings stored. > > What do you run through your 210e? > > Eric > > > > [Non-text portions of this message have been removed] >
Message
Re: What to connect to the 210e?
2008-11-08 by Alessandro Cortini
Attachments
- No local attachments were found for this message.