I was thinking it would be helpful to have a way to see all the modules available on the MM in a particular category, and I wanted to try using A.I. to help me make a website, so I made a website:
You can select multiple tags. You can favorite modules you like and then filter by favorites. You can filter out particular plugins if you don’t want to see them.
Important caveat: I knocked this up in a couple hours and I don’t really know what I’m doing and I’m sure there are issues. Here’s some that I already know about:
I got the module names from Dan’s great CPU load database, and I think those are pulled from the library URLs, and the library URLs are sometimes funny, like the Mutable clones are called Plaits and Clouds instead of “Macro Oscillator 2” and “Texture Synthesizer.”
I got the tags from the VCV Rack library, but Airwindows isn’t tagged there. So I got tags for the Airwindows modules from the Airwindows documentation, but the categories are different – there’s a lot of tags that now only apply to Airwindows modules.
I got the descriptions (again, apart from Airwindows) from the VCV library too, and some modules don’t have good descriptions there. (Cough cough 4ms I’m looking at you.)
You can’t log in so favorites are only saved on the specific device you’re on.
If people find this useful I can try to keep the data up-to-date, but no guarantees! (Especially with @etcetc porting new modules all the dang time.) Happy to have volunteers to help out there — it’s just a JSON file.
Magnificent. I knew, this would come along. I have been maintaining a spreadsheet. Is a Google Sheet any value you to you with the following: Image link, Module Manual Link, ModularGrid Link (where aplicable) Description Field, Notes Field. AV CPU if so, here Extract for Module finder - Google Sheets.
Also happy to help maintain
Hey, awesome. A CPU load metric is a good idea. I thought about manuals and that’s probably a good idea too. I can’t really see how images would work, I guess you could do a big JavaScript overlay, that might be fun …
Yeah, the percentage would need to have lots of caveats, I averaged the load numbers, it was just meant to be indicative. Dan noted. CPU load number database - #42 by danngreen
CPU is maybe the hardest to keep up to date — it would potentially need to be updated with every new version, which is a pain … on the other hand, “I need a filter but I’m very close to the CPU limit” is a pretty obvious use case.
Thanks for sponsoring this to MM users. Personally, I find it easier to include rather than exclude when I click on a brand name of modules. The current behaviour is to exclude. I was hoping it worked the other way. Add (include) company A, and upon another click, Add company B before “clearing all” to see the universe again.
Wow this is cool! @audiobird and I were just talking about making a website like this that also has the CPU load database tied in
Yes, it’s not trivial. I think we can help here – the CSV format can be imported and parsed by a script. We had talked about having it part of the 4ms metamodule site, which already parses various text files to generate the site. So updating to new modules or new load tests would just be a matter of uploading the latest CSV file, then either restarting the server or sending a “reload” command via a web address (endpoint).
I agree this is an important use case. Also “I want 8 LFOs, which one has the lowest CPU usage?”
We also talked about having a button for block size. So you can select your preferred block size (if you care to) and it’ll highlight that column of the CPU loads. Also it would probably be best to just display a range of numbers for a module of each and every test result.
Eep! Will do!
Anyways, we (4ms) want to help with this! I’ll follow up later when I have time with ideas
Hey, thanks Dan! I agree it would be better for something like this to live on the main MM site. Let me know what makes the most sense. And feel free to make use of the existing code if it’s helpful.
I might keep noodling on it for fun until you get yours working, but it’s nice to know someone better qualified could maintain it for the long run!
Yes, and if not too painful, could we add a simple ratings system to separate the wheat from the chaff. I say that because we have like over 1,000 modules now? For example, a user is trying to quickly find a flexible clock module that just works, etc. Bit rate to use, cautionary use of RAM in order not to overload (ties in with CPU meter rating) for this module and other bits of ancillary information could also be considered.
