Yeah you need to create a DistrhoPluginInfo.h for each new plugin, so the framework knows how set up the extra details that are not defined on the max-gen side.
You also pushed the binaries directly in the pull request, which is not good.
Basically following the same as https://github.com/moddevices/max-gen-plugins/blob/main/plugins/zwabo-mirrorz/DistrhoPluginInfo.h
Should I handle this part perhaps?
Ok, I did the DisthroPluginfo files, put the .ttl files in the custom.ttl folder and added a folder with the modgui’s…but without success, I’m afraid I need help.
Everything you listed is greek to me, except for the Legos… so, uh… yeah man, right on, keep it up!
wow, this all sounds amazing 
reading about the CV utility plugin, may i hint you to an idea for a MIDI plugin generating programm change messages i had in another thread? the thread is about improving control over snapshots, by adding a way to group snapshots by songs. snapshots can be loaded by MIDI PC messages (so you should be able to jump to each snapshot that is the first in a song), but as far as i am aware there currently is no plugin to do it within the dwarf (only via external MIDI devices). perhaps this sounds interesting enough for you to consider it for a future project 
Hi m.useon
That could be great, but unfortunatly out of my skills…
All these custom utility plugins have to do with signal processing (routing, mixing) they are all produced thanks to the Gen ~ objects of Max/Msp which remain in the signal domain, Gen~ does not process MIDI signals. It is only after having been compiled in the Mod Cloud Builder that parameters become accessible via CV or MIDI.
Hello @zwabo,
I hope that you are still around.
I think you have reasons to be proud, from all the plugins on the beta store, yours was the first that we can call an audio effect, which the majority of users want to move into the stable store.
For that to happen, it would be great to collect a little bit more info and materials about the plugin.
Here are my notes on what we need to get to make the move:
On device testing:
Anyone that uses it either on the MOD Dwarf, on the MOD Duo X or on the MOD Duo is welcome to share their experience with the plugin. Does everything work as expected? Is there any interaction that crashes the plugin, the device, or the WebGUI? Idealy we should collect this feedback for the three devices.
Audio levels:
is the plugin level with other plugins in the MOD platform or when you add it, it boosts or reduces the audio level of your effects chain?
Documentation:
above in this thread, there’s an explanation from @zwabo that can be used as a good starting point for the documentation. It also has a great demo video that demonstrates a lot of sounds one could get from the plugin.
It would be great to create a pdf with everything explained and eventually with guidelines to recreate all those sounds.
Would any of its users take this challenge?
Presets:
There are no presets for this plugin. Creating presets from those sounds on the demo video is a great starting point. More presets that any user could share would be even better. Users of the plugin, what magic sounds do you get from it worth making as a plugin preset? Would you be so kind and share it?
Hi Jon, yes still on board.
On device testing:
Can’t say anything about the Mod Duo and Mod Duo X, I’m just a Dwarf owner. On my side so far no problem since february 2023 with extensive use. I’ll be happy to hear other users about that.
Audio levels:
No boost or reduction, dry signal 1=1 wet signal = 1 reverse
Documentation:
I did send you a PM with the pdf
Presets:
Pretty useless, the Beta version has now a speed selector which cover all the aspects of the demo.
Best
I use it all the time on MDX but in a very simple way at the front of my chain, feeding through everything my normal signal would. It’s a little hot, especially at 2x as expected, so I always put it through a volume pedal… haven’t actually looked at the interface for a while but could maybe use an output level parameter. Doesn’t cause any freezes or hangs for me, whatever that’s worth, seems pretty stable. Heck of a plugin.
It’s great to hear from you 
Pretty cool! I think that that means a sure check for the MOD Dwarf testing.
Awesome! That’s also my (quick) experience with the plugin. I must say that I didn’t give it so much the love as it deserves, especially from a guy with my “sound interests”.
Perfect! I will take a look at it.
I didn’t fully get this one. Don’t you think that the preset function is useful? (I believe that’s not the case). If not, I think 4 or 5 presets with different envelope levels, filter, speed settings, etc. would be a great starting point. Even if the presets are something like “fast guitar”, “slow guitar”, “synth pad”, etc. (just throwing some fast examples of preset names that could be a fast “go to” for users using the plugin in different scenarios).
I will ping you asap on the DMs regarding the manual.
Cheers!
EDIT: where did you sent the PM? I thought that over here, but maybe you did it directly in Github, no?
Thanks for your really useful feedback @oeSmash!
Do you mean the plugin doubles your gain?
There’s only a Dry/Wet parameter, so I would say that you should always expect the level that you put in to be similar with the one that gets out. There’s no possibility that some “output level” or “level” parameter could be at fault to increase your levels.
Is there any other user reading this having a similar experience? and if yes, in what device you use it?
That’s pretty useful feedback, especially since you use it on the MOD Duo X. I believe that it allows us to check the box for MOD Duo X testing as well.
It would be great getting someone for the MOD Duo
Oh good, glad it’s somewhat useful. I wouldn’t say “doubles” the gain, but definitely boosts it at 2x rate. By “could use an output level parameter” I just mean that if it had that I could lower the output rather than put an attenuator volume plugin afterwards. I always run it 100 wet. I’m hoping to do some pedalboard maintenance/tweaks in the next day or two, I’ll pop a level meter before/after and see if I can get more specific.
That actually would be great. So we are not in the “supposing world”, but can get pretty certain of what’s going on.
Thanks a lot for your help on this
I did a test on the Mod Dwarf thanks to AndreaDelSignore’s Alabs v.14 and his Audio level monitor feature. No level jump regardless of speed. However, one factor must be taken into account :
" Playing a sound file at 2x speed does not inherently increase its volume, but audio may perceive as louder or more intense .
Frequency Distribution: Higher frequencies are often perceived by the human ear as louder than lower frequencies at the same decibel level, and doubling the speed shifts the entire frequency spectrum upward. "
And of course the opposite for half-speed.
Just did some brief testing with level meters, @zwabo’s note is dead on, the levels are matched fine, it’s all my perception. Seems to work perfectly. The only (very mild) complaint is that the dial on the front of the gui gives the impression that there is a sliding scale for speed, rather than the three options it actually has. Of course when you try to map it to the device that becomes clear, as it doesn’t map to any of the potentiometer knobs, just buttons/endless knobs… but I feel like that’s an inherent limitation of the MDX and the overall GUI, and really not a problem. Again, thank you Zwabo for such a great plugin.
This is actually a great thing to add on the manual. I still need to read it, but have you added this info over there?
So this gives it a check on the “Balanced audio” criteria.
That’s actually really well spotted and I totally agree with you @oeSmash, it’s quite misleading. @zwabo do you think that we could fix this? Eventually replace it with a stepped dial? Something for example like the wave or octave selector from the AMS VCO 3 (I picked up literally the first plugin that I found with this type of interface).
The problem is that I designed the GUI using the old Mod SDK and couldn’t find a way to implement a selector.
Actually, in the version of Mirrorz I’m using, I reverted the speed parameter to a rotary control for speed selection, simply because it can be CV-controlled (unlike the selector). This allows me, for instance, to modulate it randomly and create some cool effects!
I should probably send you this version and add that tip to the PDF ?
That would be a fantastic feature and I would definitely use it.
OK. Here is a new version:
RANDSPDON: (Random Speed On) Activates random speed; overrides the speed selector to apply a random speed.
RANDSPEED: Sets the rate at which the random speed changes.
This offers two options:
- Speed selection via the device
- or random selection.
It sounds cool! Personally, I like the idea of having the speed control more “free”.
Maybe worth doing an update with that? Like that, you sort of solve two “problems” at once
Sure, aren’t you able to release the update with all of it directly yourself? If you are, go ahead.
Love it!