Trying to get a better handle on how the Network page works. I’m just going to state a whole bunch of assumptions based on my understanding with the hope that you’ll correct me where I am wrong. There are a lot of questions in this post, and I apologize for not isolating them. However, I have refrained from making any bug reports or feature requests in this post, so I assume that tracking these questions won’t really be necessary.
The left column of parameters, scrolled using encoder #3, are inputs? And the right column of parameters, scrolled using encoder #4, are outputs?
In the “4voices_” preset, if I highlight the WTO module in the first voice, I can see that the following parameters are mapped, because of the  to the right of the parameter name:
- WT Osc: Pitch
- WT Osc: X
- WT Osc: Y
- WT Osc: Z
- WT Osc: Amp
I think the  to the right of the other parameters means they are not mapped.
I don’t think there is any indication at this point of what those parameters above are mapped to. I guess this information is only available in the rightmost column (outputs), scrolled using encoder #4, shows this information. So, if I scroll over to the INP module, I can see in the output (rightmost column) that the following parameters are mapped:
- 1:WT Osc: Pitch
- 2:WT Osc: Y
I believe that none of the other parameters listed in the rightmost column are mapped, because the orange highlight is the indicator of an existing mapping.
If I scroll to the MIDI module, I see these output (rightmost column) parameters are mapped:
- Pitch:WT Osc: Pitch
- VelOn: Env: Amp
- Gate: Env: Gate
- CC1: WT Osc: Amp
“Gate”, while a familiar term in CV parlance, is not familiar to me as a MIDI term. I presume this is a derived value that is the difference in timing between note on and note off? I’m curious to understand how pitch bend is being used. I assume “Pitch” here is another derived value that is the sum of the note on pitch value and the stream of pitch bend messages as they arrive? Aftertouch doesn’t appear to be in use in the “4voices_” preset, but I assume this is actual aftertouch, and not channel pressure?
If I scroll to the ENV module, I can see these input parameters (left column) are mapped (but I can’t tell where from in this view):
I believe the Gate parameter controls the duration of the sustain stage of the envelope (but this association is not visible). I believe the Amp parameter controls the amplitude of the attack stage of the envelope.
I can see that this output parameter (right column) is mapped):
I still don’t really understand “How can I quickly see if a valid patch connection exists between 2 modules?” I guess at first I assumed this question was about how a user could determine what output parameters were possible to validly match to input parameters of another module, prior to actually making the connection, but now I think maybe this information isn’t available, and the manual question is just getting at “how can i see what connections have already been made?”
- If I click the “In/Out” button, I can see that the arrows on the network grid change.
- clicking “Togg l” or “Togg” appears to do the same thing as an encoder push on encoder #3 or encoder #4.
- clicking “Clear” appears to remove all connections from the selected module. Except that I still see a cyan arrow from ENV (the module that was selected when I clicked “Clear”) to WTO. Oh, but that vanished as soon as I turned one of the parameter list encoders.
I’m not entirely clear on the behavior of toggling a connection in the input list. If I have ENV selected, and then toggle the “Gate: Env: Gate” input off and then back on, then scroll over to MIDI, I can see that the previous connection has been maintained. This is a good thing, but I didn’t know what to expect from toggling that input off and then on again, since I can’t see what output is attached to this input. It’s even more ambiguous what to expect if doing this while patching modules that have never had a connection previously.
I’m gathering that the expected operation when intending to adjust patching between two modules, is to think of one of the pair as the output module for the parameter you want to map, and focus on the rightmost column, which contains the combinatorial of the currently selected module’s outputs with the destination’s inputs. I assume you typically won’t be toggling things in the input column, since there is less visual feedback for what type of connection this toggle is enabling/disabling. I’m also realizing that there’s nothing indicating that a particular output “should” be patched to a particular input. Understanding what connections make sense is left to the user.
I may have some suggestions for usability improvements in this area, but I want to be sure I am understanding the current intended behavior clearly before I start suggesting changes.