Hoi Paul,
Check out the "Modular2 manual.pdf", page 16 on signal types. That explains as you did above, but in more detail. However, don't feel limited to that - for example: You cannot connect certain outputs to certain inputs directly. Some signals are sync, some are async. Some connections contain convertors, for example the modulation level input of an ADSR accepts LFO output as velocity from an MVC. A built-in sync/async convertor will make the ADSR accept both, although sometimes once the convertor is switched to a certain state, it cannot switch back. Right-clicking the module and "Disconnect" resets the convertors. Then make your connections again... Another typical sync output is a 4x1switch, which will refuse to connect to certain async inputs. A workaround is to insert a Volume Attenuator or so, which output seems a bit more flexible for some reason.
Now with Flexor that becomes a bit twisted, since it uses just one signal type: sync, at audio rate. Even the Gate input of Flexor's envelopes can accept sync signals, from a ramp or any logic's condition made by math...
But really, let your imagination be the limit, if you think it's functional and you find a way to connect things, then please do so
One of the most weird (and clumsy) patches I made was by connecting an LFO's output to an Osc's freq input. I also remember there was a filter in it, and a feedback circuit of the output to LFO modulation. It was about my first patch, with connections that nowadays wouldn't seem to make any sense. But it did bass when the filter/osc freq was modulated low, and a hihat when it was up high. LFO speed made BPM, and these 4-5 modules made the tune :>
There's different signal types, made for DSP efficiency and practical reasons etc., but don't let that stop you to find workarounds and try to connect whatever you consider usefull. Not sure if that's really what you're after, but there's no such thing as rules in modular.
Greetings,
at0m.
