Flanger had the same issue as Chorus, but claude has found another bug, that fixed even in the chorus too.So this is the right newest version of Chorus:
h90-chorus-fixed.mk (18.3 KB)
And here is Flanger:
h90-flanger-fixed.mk (18.5 KB)
Flanger had the same issue as Chorus, but claude has found another bug, that fixed even in the chorus too.So this is the right newest version of Chorus:
h90-chorus-fixed.mk (18.3 KB)
And here is Flanger:
h90-flanger-fixed.mk (18.5 KB)
flanger sounds perfect, chorus is a bit clicky at times and doesn’t seem to have the quality of the flanger not sure why yet . I will try chucking through gemini to see if that helps.
H90 Flanger definitely finished I think
h90-chorus.mk (19.7 KB)
post gemini , not too bad maybe still a bit subtle, see what you think
h90-modfilter.mk (18.8 KB) modfilter pretty much there but still might need a tweak for stereo width
Modfilter had the same kind of issue as chorus and flanger.I fixed it.I tried with the stereo width parameter, but I don’t feel much difference.
h90-modfilter-fixed.mk (18.8 KB)
Pitchfuzz had a wrong calibrated delay level parameter, now it’s good.
h90-pitchfuzz-fixed.mk (19.2 KB)
haha yes…I can tell you what I was wondering…a pretty simple thing that I use to do with MaxMSP and I was getting pretty nice sounds: a delay (nice if it’s already a good sounding delay) with an FX loop inside the feedback loop. So when it get’s in the feedback part of the delay you can send that audio out, input some other effect and return it before the feedback out…This is pretty simple, but with stuff like filters, pitch shifters and even multiple effects can sound pretty cool. I have a Memory Man 1100TT, that has an effects loop, but I believe that is after the feedback. Someone can correct me if I’m wrong ![]()
I must say that I thought exactly about this the other day. Remove them I don’t think is a good idea. What came to my mind for a possible solution would be create a new section or filter for “legacy plugins”, but I must say that I didn’t put much thought on that, nor even discuss it with anyone else. Anyway…wrong thread and bad timing to talk about that
let’s for now focus on the beta store and then eventually moving some of the new creations to the “system”
I was actually just thinking about another idea that you might be able to help with. As you can see from this thread the creations are all over the place especially from me - with Lipi helping out, its almost like we need a separate thread with say the H90 plugins pinned to the top (and other creations) so that people can find the finally working versions of each of our many creations a bit like you do for some of the other plugins that aren’t mod cookbook creations. That way we can update them as required and they stay in the same place. Not sure how feasible that is, and its just an idea. Otherwise its hard to find the beetronics stuff etc
That is super feasible and actually not far from something that I thought before while reading your iterations.
I would suggest you to keep the iterations in a DM system. There you can even add other people in case you need it. Once you have an MVP version of something that you would like to invite the community to test, you can create a new thread and share it there.
On top, I can maybe create a sub-category on the Plugins category called “Plugins - MOD Plugin Cookbook” or something along those lines. How does that sound?
Yes that’s a really good idea, if Lipi and others are onboard with the DM it makes perfect sense. It might even be worth while if one of us is sort of the admin for it and when the plugins are a bit more polished we could release to the plugin store under cookbook. That way it’s not inundated with inferior or part finished stuff
This is highly interesting. I just created my first plugin with the help of AI to understand the codebase of existing plugins. I’m waiting for approval to post it here.
Welcome aboard mate, what did you create? And what did you use?
That’s a bit on your side and how you define “roles in your team” ![]()
I didn’t mean to release it to the Plugin Store, but to share it here in the forum (let’s say as an Alpha plugin). I’m not sure if that was what you meant, or if you thought that it would get directly into the device Plugin Store.
Exactly. Not before an alpha, meaning with parameters not working or without any test sound.
I have just created the subcategory Plugins - MOD Plugin Cookbook - MOD Audio Forum and pinned this very same topic to the top. Now you can create topics/threads there with your plugins (the most polished version preferably) or if you need to openly discuss something, go ahead ![]()
Let me know if that works and/or if you need something else.
Welcome on board @valentingregoire ![]()
Do you mean that your permission levels here in the forum should be raised for you to be able to share the file? I checked and you are already a “Basic user”, I believe that should allow you to share files. Let me know in case I’m wrong and I will manually take care of that.
Hi Jon,
I know it might be a silly question, but what “DM system” means?MVP would mean that a plugin is ready for a beta test?I have a lot of plugins that are ready for test and use, i didn’t even share them, just a part of it.Now I will focus to finish some, that are not 100% yet, and help to finish austin’s plugins, as he has also a lot.
Direct message I’m guessing Lipi, yeah I think I’ve finished the H90 drive and modulations now but need to run them through a couple of more times to get the sparkling and correct controls, before I embark on the delays and reverbs.
Sent you a DM
Thanks for getting back Jon, I have messaged Lipi regarding dual Admin role for the cookbook stuff so hopefully he will be onboard with me. We will keep the mk files to DM till we are both happy then release to new thread or would you like the final say?
Have you tried any of our creations out yet? I know you are deep in the Beta sorting but maybe have 5mins out, I’m sure you will be impressed and your feedback would be gratefully received.
I made a thread here: https://forum.mod.audio/t/switchbox-1-4/13375
Hey @Lipi, there are no silly questions here…otherwise I would be the first one full of them ![]()
In the forum, when you click on top of my username on this post (for example), a pop-up window shows up and on the right of it, you have buttons to message me or create a chat with me… essentially, that’s the DM I meant. I suggest using the message, as it works better with the format of any other thread, and it’s just private.
I would say an alpha test first. Meaning, share a build with other users so they can try it on their devices and return you feedback. Without being listed in any Plugin Store.
Part of this is realated with getting the plugin circulating faster so you can get outside feedback and iterate. Another part is to help with another odyssey that we are starting, which is the clean -up on the Beta section of the plugin store. I hope that’s fine with you.
I would say, share them (publicly) once you are happy with them and ready to get outside feedback. That’s a lot up to you when this moment exactly is, but personally, I would say when you made sure that the plugin in general, all parameters, etc. are working as supposed and you didn’t find any major issue on your own testing.
That sounds really promising…and it’s exactly what I meant…share them publicly (if you feel like doing it) after those runs to “get the sparkling and correct controls”
No no…I have no “say” on this. Once you feel that you want to share it with the world, I would just give you my blessing and try to be one of the first to test it, so I can give you my feedback ![]()
I must be honest and admit that no
Which one would you say that I should start with? I will try to do it early next week.
Great @valentingregoire! That’s exactly the forum structure that I meant to this, so we can keep the discussion about the specific plugin in one place and with the builds easy to find.
I mean hat I didn’t have enough permissions to create a post. I had to wait for a day.