info about 4k resolution

you have been clickbaited! :squinting_face_with_tongue:

thanks everybody :heart:

7 Likes

GG about.. 4k! :+1:

1 Like

We may have reached the runaway positive feedback loop where it is quicker to create a new module than to find an existing one that does what I want.

14 Likes

Yep, I noticed this the other day. I hate to mention AI (someone else probably would anyway!), but this could accelerate the number of new modules coming into the library too. I’ve seen a few collections already where the author says they are using AI to develop code.

1 Like

Correction - has accelerated!

Some developers have made the most of the technology - using it to quickly produce quality modules. Not surprisingly, some have used it as a shortcut only to end up with modules of marginal quality.

I am an old dog, and have resisted any urge to use AI as a coding or documentation aid. I’m probably missing out on opportunities, but I want to keep my brain cells engaged as much as possible.

7 Likes

amen to that!

2 Likes

Ohh! :joy::rofl:

1 Like

modules vs date
( VCV Rack 2.0 was officially released on November 30, 2021 )
Data from wayback machine.

9 Likes

Well I stand corrected! That rate is amazingly consistant.

Thank you for some actual data! I am also surprised at how linear the growth is.

I’ve found the search engine AIs (google) OK at the question ā€œvcv rack module to ā€¦ā€ but do they really know the library? The inbuilt search is quite good too. I’d improve it with an option to order by HP. Generally thin for common, wide for full featured specialist modules.

I like this idea! I hadn’t really thought about it before, but HP width probably does correlate strongly with how complex or ā€œopinionatedā€ the module is.

About implementation, I’m not sure how you know the HP width of a module until its widget gets created by the plugin.

From the VCV library maintainer’s point of view, they are already creating screenshots of each module, which means they have to load each plugin, scan the manifest, create a widget using each module slug they find, and capture the image. At the time they create the widget, it’s easy to determine the HP width. I guess just add another database column and store the HP width there.

Just me thinking out loud…

[EDIT] An afterthought: some modules can change their panel width. I know there are some blanks whose panel width can be adjusted by mouse. Whatever HP width you sort by will be based on whatever you see in the screenshot.

1 Like

Good conceptually until DocB. The doc can really cram.

2 Likes

Oh yes, I forgot about The Grid! It does have an HP sort already! LOL.

And yes, docB modules are very dense, like concentrated laundry detergent. They get the job done with very little HP!

2 Likes

I like the hp sorting, you can go exact HP or up to a certain HP. Sometimes I like to use it looking for small modules. Unrelated, but we need a bytebeat Tag at the library, there are several and I expect even more.