Edited to add: For anyone stumbling across this out of the blue it follows on from a previous thread called What if? that explains the context.
viewtopic.php?t=2882
This thread has become a sort of thinking out loud blog on the development of Adroit Custom so might not be of interest to many people especially given some of the minute technical detail.
====
- Reflection.png (352.35 KiB) Viewed 8347 times
This shows a ittle test patch with Adroit Custom doing some reflection.
The focus here is the single Custom Panel module labelled TEST. In a practical application the other modules would be off-screen and not visible.
It took ten mouse clicks to add the two knobs, two scopes and the LED.
A few seconds later the top knob was labelled KNOB 1 and had a CV mapping to output 1 of the Custom IO module. Similarly for the knob below. The two scopes took a few more clicks to configure. Finally another two clicks were required to make the LED monitor Input A3.
The controls on the Custom Panel (in this case just the two knobs) have up to four simultaneously available mappings that can perform remote control on other module's controls, send CV to a Custom IO's CV outputs or send MIDI messages such as CC to a Custom IO module. Here they are just outputting CVs for test purposes.
The Custom IO module defaults to Bank A but one could add three more modules and switch them to Banks B, C and D so in total Custom Panels can access 32 CV or audio inputs, 32 CV outputs and four MIDI outputs.
Each MIDI output supports 16 channels and 128 different CC's as you'd expect so that's 64 channels of MIDI and 8,192 CC destinations for anyone who has a warehouse full of outboard. In a more practical realm it means you can simplify MIDI configuratiion - say always sending MIDI CCs on channel 1 while still controlling four different hardware or VST synths. Or it may be that you don't need MIDI at all.
In this patch Output A1 is connected to Input A1, Output A2 is wired to Input A2 and Input A3 receives the triangular output from the second Mini LFO. So we can see the CV mapped outputs from KNOB 1 and KNOB 2 on the scopes while the LED at the bottom of the TEST module throbs away in time with the LFO.
The Custom Control module looks after control automation. The keypad with 16 buttons enables you to switch between 16 different scenes. Each control on every Custom Panel has 16 memories of its settings so a single button press on the keypad can change every single control in a large interface if required. A mini Scene Selection keypad is also one of the items that you can add to a Custom Panel.
The MORPH SPEED control enables you to set how quickly the scenes change (anything from 0 to 25 seconds). So when selecting a new scene the knobs and sliders can move smoothly from one setting to another.
As mentioned the two scopes show the mapped CV outputs from KNOB 1 and KNOB 2 varying over time. If MORPH SPEED was set full CCW then these graphs would be stepped.
Here scenes are being changed by the upper Mini LFO sending a regular pulse to the NEXT input of the Custom Control module.
The GATE OUTPUTS beneath the keypad reflect which of the 16 scenes is currently selected. In this instance the 9th output is wired to the RESET input so that the sequencing automatically resets on completion of the 8th scene but you can use these gate outputs to control things like switch modules so that each scene can have different inter-module wiring.
In the screen grab we are transitioning from Scene 2 to Scene 3 . The Custom Panel knobs show their Scene 3 settings and the yellow arcs show the difference at this point in time between these settings and the morphing settings. As the transition progresses these arcs shrink and eventually disappear when the morphing catches up to the knob settings. However you can still adjust the knob settings mid transition and the interpolation is recalculated. This is particularly useful when the morphing is slow.
Finally we have the Custom Look module. This configures the visual appearance of itself and the other Custom modules but its main purpose is to allow you to skin the Custom Panel modules so that they look unique. Here no background image is loaded so the Custom Panel module uses the same three-color gradient fill as the other modules.
This was supposed to be a brief post! Still it will fold into the documentation. Hopefully my ramblings have been of interest to some of you.
Things may change quite a bit from what's shown here and the ETA is difficult to judge as there are several other aspects of Custom that I've not revealed yet and they need considerable work. But I'm hoping to launch before the end of June.
