grep '"model":' * | cut -d ':' -f3 | tr -d " " | tr -d '"' | tr -d ',' | sort | uniq -c | sort -n
worked for me on MacOS after replacing all the fancy quotes that the forum software “helpfully” interjected into this clever command. (formatting it as a code snippet fortunately seems to avoid this problem)
Glad it worked. I was gonna fix that, but I figured people could figure it out. Thanks.
I was amused to learn (thanks to your script) that my #1 module, by a sizable margin, is the Submarine TD-202 Vertical Text Display. This might say something about my patching personality (in addition to the fact that it was formed before Stoermelder’s Glue was available).
sry, my script doesn’t handle having different files (like .html) in your patches folder.
Oddly enough, there are no html files in the folder. I went ahead and removed a few audio files and a video from there, leaving only .vcv files, .vcvm files, and .vcvss files. Still the same error. Removed vcvm files and vcvss files too, but no dice.
I guess one of my patch files has html inside…?
I updated it to skip those files and to provide a bit more silly stats, like how many meters of cables you’ve used in your patches (just an approximation ofc).
I get you are asking anyone other than me 
but I think seeing you own data summarized is generally an interesting thing to people.
Of course if you use MB long enough, you’ll gonna get a meaningful “most used” list, but this would make it so from the beginning. And once you scan the patches, you could extract some more statistic.
I’d propose this as a separate module idea, but at the same time I feel like a Stats page would be a good fit to put inside the module browser as well.
my 2 cents: stats can be really interesting (at least for some of us) but need to be flexible in their implementation, which may require some research among users. In other words “the usage of a module” means different things to different users:
Flexibility about paths may be required too - some users organize their patches out of the default /patches/ directory.
1 more cent: I’d welcome any stats that would help establishing a correlation between the number of available modulation sources and the number of available inputs (or other interesting “ratios”). Example: “oh look, according to stats my average patch has 10 available inputs, but only 3 modulation sources…I should try using more LFOs/envelopes/random generators/etc”).
A different “ratio”: how many times I’m choosing a kind of module vs. how many modules of the same kind are available. Example: given the number of alternatives, including VCV LFO-1 in all your patches is a bolder choice than always including VCV MIDI-CC.
I’d propose this as a separate module idea, but at the same time I feel like a Stats page would be a good fit to put inside the module browser as well.
I also don’t know about this - moderators please feel free to move my reply to a new “Stats” thread if you create one.
(EDIT: this is now a Wiki-style collaboratively-editable list of “smart combinations” of Stoermelder modules with basic written instructions**
Controllers: MIDI-STEP + PILE
Handling a list of presets for a given module: STRIP + 8FACE
(in my original post I was saying that I’m relatively new to Stoermelder modules and I was looking for a comprehensive, written list of “smart combinations” of Stoermelder modules. I also included the Strip + 8 Face combination, which was probably already known. Reminder: you can check history/edits of posts and comments).
There might be a more comprehensive list around but @VCVRackIdeas youtube channel has some really good videos about using them in combination.
Hey thanks, but no. Another user recently expressed very well why video don’t work for everybody. I know there’s a million of Youtube channels about everything.
I’m looking for a written list. If it doesn’t exist, that’s fine.
No, there is no written list I know of. But I think it is a good idea to start something like this 
Amazing how something as simple as scaling the modules in the browser, a functionality which certainly should be in the software by default, becomes such a source of excitement for so many people…The developer certainly has his own ‘vision’ of such a things though…this and some more, like that crazy load of GPU the rack does…
The developer certainly has his own ‘vision’ of such a things though
I think he’s just got an absolutely insane to-do list of things necessary for V2 and is having to ruthlessly prioritize. I strongly suspect that we’ll get a revised official module browser by (or before) V3. In the meantime, it’s great that the Rack API is wide open to modules so that @stoermelder’s work is possible!
Agree that the MB module is pure gold 
It does not do “a crazy load of gpu”. It uses more than is strictly necessary, but I don’t think the term “crazy” is a all justified.
In STRIP, would it be possible to select a group of parameters for randomization on a module?
I was playing out with Curve Sequencer and wanted to randomize all the Durations and all the Levels, but had to pick them to the list one by one. Just popped into my mind that with larger Curve Sequencers that functionality would be a godsend.
Yes it does, at least in my case(macbook pro 16). It eats through the battery in no time, like literary in 15-30minutes all the juice is gone, and it mostly the gpu…And there’s no way to justify that, all the modules graphics are mostly static…There’s an alternative which we’re not supposed to name 
which uses MUCH less cpu and gpu while sounding the same to my ear, so i suspect things could be done to improve the situation, but from the reactions of the developer to any criticism i doubt this aspect of VCV will change…its a pity, i’d love to use my laptop to work on patched while unplugged, but i just can’t afford it…
I think it will change
Hi i have an quality of life feature request for MB. is it possible to sample and hold the mouse position on initial browser open and create the module at the sampled position instead of the position the mouse is at when clicked in the browser? (not any kind of coder 
)
You know that when you click and hold a module in the MB you can just drag it to where you want it.