Kosmo Modules Wiki

KOSMO MODULES
1

I created a wiki for Kosmo modules! I have put in a lot of work to bootstrap it with a lot of information I went to hunt down all over the place last two weeks, and now it’s ready to hand it over to the community:

Visit the Kosmo Modules Wiki »

The wiki is intended to supplement our community, not to replace it: it’s mostly an index of off-site resources. And hopefully, it will revitalize the pace of new Kosmo releases.

I encourage you to help out with editing: I have done my best to make editing as easy as possible. And learned 10 times more than any reasonable person ought to know about cursed MediaWiki internals in the process.
You will find that the syntax to add modules is simple and self-explanatory. Here’s a little guide how to add modules.

However, you can also use this thread to discuss the wiki and suggest changes, so if you don’t feel like learning MediaWiki, simply use this thread. Having good info to contribute is a lot more valuable than knowing how to format it.

I hope we can use this wiki not simply as a shopping mall, but also as a showcase: don’t hesitate to create wiki pages for one-off modules, and please also create pages for your rack!

However, the wiki is limited to the Kosmo format: if it’s not 20 centimeters tall, it doesn’t belong on it.

Don’t we already have Kosmodulargrid? Yes, we do, but it’s difficult to update. And it’s also barebones: a wiki allows us to add any useful information we want to pages. Additionally, it depends on a single person who is no longer very active in the community.
By contrast, this wiki belongs to the community: if I stop being active, you can ask the wiki host, Miraheze, to transfer the admin rights to someone else.

Miraheze is a non-profit independent wiki farm: unlike Fandom, they won’t plaster our wiki in ads on every corner. (They’ll just show the occasional fundraiser reminder: toss a few coins their way if you find our wiki useful).

For now, the wiki has almost no restrictions on editing. We’ll see if vandalism is a problem: Miraheze runs a lot of safety checks in the background to make it something we rarely have to deal with. We’ll add more restrictions if they prove necessary.

7 Likes
1113 Performance Filter
2

First wiki to forum liaison post!

If you are a module creator, can you please review the pages I’ve made for you? I’ve already wikified the work of @lookmumnocomputer, @analogoutput, @Dave, @jkb, @Sonosus, @sebastian, @tamasgal, and @TimMJN

  • Anything you’d like changed?
  • Any missing information?
  • Any incorrect information?
  • Got more data to suggest? In particular, current draw, and depth of the module.

I plan to add pages for @Dud and @EddyBergman next, then hunt down for more stuff to add - you can see details on the Wiki projects page: Wiki projects - Kosmo Modules Wiki

8 Likes
3

I edited the Kosmic Superspreader page to add the actual depth of the module.
One I think should be added is my 3340 breakout board. GitHub - Sonosus/3340Breakout, 3340 VCO Breakout - Sonosus's Synth DIY documentation Happy to try adding it myself.

I have a bunch more random PCBs and badly documented modules on Github that I’d like to add at some point in the future once I document them more.

One notable omission: @CTorp has an excellent series of 2.5cm modules that were popular when he first released them.

5 Likes
4

Analogoutput already added a few of those! Glad to see third-party edits are starting to come in. (Don’t sweat the formatting, I clean up everything as needed after I see new edits.)

I’ve been focusing on reproducing the Kosmodular index, but there’s a lot of stuff that never ended up on that site.

3 Likes
5

Yeah, I wanted to add my builds of several @CTorp and @BenRufenacht modules, so I put up pages for those. Just the ones I’ve built, there are others.

There were a number of modules of mine not on KMG, either because they were recent and I’d not gotten around to it or because they were older one-off “showcase only” modules I didn’t want to bother with before — today I did.

Thanks @AriaSalvatrice for doing this! A fine resource.

2 Likes
6

Great to see a bunch of third-party edits right from the start! I’m glad I didn’t open the gates of the wiki too early, now it should have some momentum.

One thing that’s important for the wiki is that we should keep it to stuff that has been turned into Kosmo modules successfully, because there’s a huge wealth of potentially Kosmo compatible projects out there, such as those breakout boards that just need a panel and I/O. If we listed them all, it’d outnumber the modules. Better to keep it to stuff we know for sure someone built successfully.

Of course, while I don’t know if you ever turned it into a Kosmo module… I certainly did turn one of those boards into a Kosmo module myself.

1703717665281
17037176652811125×2000 263 KB

2 Likes
7

I did though probably didn’t get round to posting it anywhere here. It’s on my slightly bare docs site: 3340 VCO Breakout - Sonosus's Synth DIY documentation
It’s clear you’ve put a fair bit of work into this - it will indeed be an excellent asset to this community.

8

@telec16 did some Kosmo modules too back in the day.

The definition of ‘Kosmo Conversion’ seems a bit gooey. There are modules that are built around Eurorack-(or other-)intended PCBs, ones built around Kosmo-intended PCBs with the identical circuit, ones where the circuit has a few minor tweaks, ones where there are larger modifications to the circuit, ones with really substantial changes… not clear where to draw that line. I’ve been using the tag only for modules that use the original PCB, especially since once I start laying out a PCB I almost always end up making some changes, but it looks like that’s not the universal interpretation. (And then just to make things worse, one of my dual VCAs uses the MFOS PCB and the other, electrically identical with identical front panel, uses my own Kosmo PCB layout.)

1 Like
9

I think the test for this one is “whose name is/belongs on the faceplate”

Either way, i think the wiki should reflect the creator’s naming scheme rather rather than prescribe its own taxonomy

1 Like
10

Hm, well, that’d violate my line-drawing (or vice versa), I put others’ names on my front panels even if I’ve made some fairly significant changes. Except of course in cases like Music Thing Modular where they seem to prefer not having their name displayed on derivative works.

It’s easy enough to add or subtract the tag if need be, but it seems the page naming convention for Kosmo Conversions is different than for non, and changing that is a little more bothersome.

Some of the modules I posted are not labeled as Conversions (because the PCB is new) but have the original designer’s name attached as a co-creator.

11

In any case, changing the name of a module is not too complicated, wiki redirects avoid breakage. Though in addition to a page move, the name needs to be changed in the article metadata:

Every module page has a “pagename” field filled automatically at page creation, but it isn’t updated on move… Slightly inelegant, but that’s the reason we can use transclusion to build module galleries that stay in sync without duplicating info.

(Do not dare to peer into the main template that powers the site. It’s unsightly)

12

We now have Light Mode support, if you enjoy burning your eyes. I figured out why it wouldn’t work.

And we now have all the modules by @BenRufenacht !

Please let us know if you’re happy how we’ve wikified your work.

(Also - any picture you’d like us to use as a logo? I couldn’t find anything suitable)

1 Like
13

And we now have all the modules by @BenRufenacht !

Which makes this objectively better than KMG.

14

By the way — René Schmitz’s name isn’t on the faceplate of the 1113 but he’s credited in the documentation and the circuit is basically the same as his as far as I know.

15

It’s not?

1425×1425 252 KB

-Fumu / Esopus

1 Like
16

Duh. :grimacing:tiny

1 Like
17

Looking through Sound Bender’s stuff, I see he made the same sub-oscillator as @AnalogOutput - Not sure how best to handle a situation where there are multiple implementations of a circuit but no “canonical” one. For now I will probably just list it as a “user build” of yours since it’s the same circuit but it’s a bit inelegant…

We need to figure out an organization where nobody feels cheated out of a credit but nobody providing generic circuits feels expected to “officially” support Kosmo versions

Speaking of that circuit, would Carmelo Azzarello be better credited as Analog Lab Swiss? I’m not sure what name they use the most for synths stuff since they seem mostly active on Facebook and you can’t see it without an account.

18

I feel like it could be listed as its own module, with cross references added between his and mine.

19

Maybe the logic for quasi-identical modules could be:

  • If someone provides PCB gerbers, sold PCBs, anything easy to acquire: they get their page even if there are other implementations.
    • If someone builds the same circuit in a way that is less easy to acquire (e.g., stripboard layout), they are listed as a User build
  • If a single person has built it, credit in whatever way makes sense
  • If multiple people have made builds of equivalent availability, credit the circuit author, and use the best photo as showcase. Mention everywhere that the circuit author is not involved in the Kosmo community but simply provided thee circuit, to limit expectations of support.
1 Like
20

Why is there no “Edit this list” here?

image
image762×251 93 KB

(Kosmo Modules (by Function) - Kosmo Modules Wiki)

(Also this is at the bottom of that page:)

image