There’s not really logic involved since it’s not using the state of input gates to generate output gates. From MG’s function list I think “Random” would best apply, but I do think “Gate Generator” should be added to that list. You can use both.
On MG, Barton’s BMC3 is listed as Clock Generator, Clock Modulator, CV Modulation, and Sequencer.
That’s ugly, “Modulator” for Clock vs. “Modulation” for CV. I’d advocate “CV Modulator” instead.
Indeed, some thought ought to go into standardizing function names instead of just blindly adopting MG’s or whatever anyone types in. One way to think about it is: What kinds of inputs does the module take, what kinds of outputs does it create? CVs, triggers, clocks, gates, audio? Are signals created from “nothing” (under control of inputs) or are they more direct modifications of inputs? (E.g. a sequencer generates CVs, a quantizer modifies CVs.) Questions like those should guide choices of function names.
Notice this is a graph, not a tree. For instance, “Audio mixer” appears both under “Audio processor” (along with “Filter”, “Wave shaper”, etc.) and “Mixer” (along with “CV mixer”, which also appears under “CV processor” along with “Quantizer” and “Slew”).
Signal generator
CV generator
LFO
Envelope generator
Sequencer
MIDI to CV
Envelope follower
Audio generator
Audio oscillator
VCO
Percussion
Drum
Bell
Cymbal
Oscillator
Audio oscillator
VCO
LFO
Noise source
Signal processor
Audio processor
Audio mixer
Filter
VCF
Wave shaper
Wave folder
Sub oscillator
Output
Effect
Delay
Distortion
CV processor
CV mixer
Quantizer
Slew
Amplifier
VCA
Mixer
CV mixer
Audio mixer
Attenuator
Multiple
Passive multiple
Buffered multiple
Sample and hold
Control generator
Gate generator
MIDI to gate
Clock generator
Trigger generator
Control processor
Gate processor
Logic
Clock processor
Clock divider
Trigger processor
Interface
Stomp box adapter
Obviously there’s going to be disagreement here. (I’ve already debated drum vs. percussion here, and whether triggers belong with CVs or gates.)
“Signal” here means audio or CV. “Control” means gate, clock, trigger, or MIDI etc. Continuous vs. binary, basically.
I just pushed an edit to kmg.py: Previously it ignored lines with nonempty ‘id’ field. Now it doesn’t generate output from them, but it does handle the ‘makerId’ field so if it’s nonempty (and if its value isn’t ‘makerId’) it becomes the new default ‘makerId’. This just makes handling the makerId easier (I think).
Yo @jackb any more progress on this? I have at least 3 modules almost ready to be officially ‘published’ and am happy to test out any new method of adding modules.
Cheers
Hey @Sonosus, unfortunately nothing to report yet. November/December was pretty busy at work and spending my free time writing more code wasn’t all that appealing
Things are calming down now so hopefully I can carve out some time.
Sorry for my ignorance, but what is the current workflow to contribute to the grid? I’d like to publish a simple 4x3 buffered multiple stripboard + panel
Btw. if you need any help in the maintenance, just let me know. I am also planning to publish a few more modules in the next months (hopefully much more interesting ones )
maybe some day a growing number of people using Kosmo . there is also growing number of modules that have been offered , but no actual manufactures which is probably a issue when it comes to Modular Grid .
Getting a manufacturer on Modular Grid is like getting a Twitter bluecheck. They’re like, “You got $$$?” I saw that AE Modular decided to make their own clone of Modular Grid and it makes sense Kosmo followed suit.
Modular Grid specifies a manufacturer of Eurorack to get their page must be bringing three modules in a store or have one “everybody is talking about” which is not a trivial thing that happens to every hobbyist. A manufacturer would be putting capital elsewhere to get Modular Grid’s attention. One would have to spend capital just not to Modular Grid. It’s not “free as in free beer.” But yepyup they aren’t listening to requests to add new formats.
