AW: Matrix board!

[jorgen.bergfors at idg.se]

>> How much of  a problem is this in reality? I'm thinking of using the
>> matrix board for modulation and not for signal routing. > My humble >opinion: Don't even *think* of making a distinction between
><"modulation" and "signal"
>connections.
>Well, I sort of make that distiction as well, generally using red pins for
>slow signals and green
>pins for audio rate signals, but it's hard to imagine how to restrict either
>of them to a certain
>area of the matrix.
>Not being stuck with a fixed architecture is what most of the fun with a
>matrix is all about.

The problem is that if I include all signals, there simply will be too many for a single patch matrix. I made a quick list of the modulation routings and came up with 28 sources and 39 destinations. That includes the VCOs and noise as sources. And I haven't even counted exotic modules that I might build in the future.
 It is clear that I have to prioritize even if I only include modulations.
All my signal prcessing modules will have two mixable inputs, with a thumbwheel for selecting among the ten most used signal sources. So this makes it less important to have them on the patch matrix.
In addition to this, I have jacks for all inputs and outputs on each module. So if the connection is not possible on the patch matrix or the thumbwheels, I can always use a patchcord.

/Jorgen