AI Made modules and proper tagging

Plugin Development
1

Please don’t take this as a rant but as a polite request.

I am concerned about AI-only made modules showing up in MM development. The VCV team has explicit guidelines that any module be reviewed and tested by a human, but so many people are doing it without the ability to evaluate the code.

Here is a concrete example of what can happen:
As a C/Python&JS coder myself, AI generated code is rigid, and makes assumptions about what a function does without knowing side effects of proper usage. My working example is PDFlib in JS and how AI totally misuses (over 2 years now and no improvement) the functions and how they interact (trying to load a file into an object that hasn’t been allocated since the lib doesn’t create an object automatically on load). This occurs even if I feed the tool the PDFlib prior to asking it to code.

If there are AI generated MModules, can they be tagged with #ai, #developertested & #notadeveloper or something similar? That way I can play with them but not use them until tested. Without this labelling, I may go after a module made by AI and find myself totally glitched in a performance.

My apologies if there are guidelines for MM development similar to VCV and I missed them.

.maury

2

afaik the madzine ones are the first/only so far made for mm soley with ai. you can read all about it here:

there’s some great discussion and links in there pertaining to this ai topic.

and it seems dan will be doing a ‘test’ of sorts with any/all modules (ai made or not) - and they must pass before being added to the plugins page:

3

Oh, sorry for not seeing that thread. But I guess it’s good to have it as a topic heading.
Thx
.m

4

mistakenly deleted the old version (again)
Sorry but if you’re interested, the updated version is here.