New version just pushed to the library which includes a new module Purfenator @purf hi there
I created a feedback thread for the new module DanT: Purfenator
New version just pushed to the library which includes a new module Purfenator @purf hi there
I created a feedback thread for the new module DanT: Purfenator
(a shame that .gifs don’t work)
v2.4.35
has just been pushed to the library, this update is just for the Purfenator module, please see the dedicated feedback thread for more info.
v2.4.36
has just been pushed to the library with more updates to Purfenator:
Shameless Self-Promo Warning
This year I want to try to stay fully engaged with my plugin development.
The success of my recent MOAR COWBELL!
and Purfenator
modules and the community feedback was great and it gave me high motivation to continue and to do more.
In an effort to sustain this feeling, I have created a more formal way for users to give feedback. Yes, it does involve money, but it is the minimum required to make this work, I think.
I will treat this as an experiment initially and see what the engagement is like, maybe it will work out, maybe it won’t. One thing is for sure, the low bar to beat is zero in donations since the inception of my plugin
Please take a look if you feel so inclined
Edit: I made a post to explain how the membership works
Edit again: This is the milestone for what I am working on in January (so far) 2.4.37.beta.01 Milestone · GitHub
My VCV is downloading v2.4.37 from the library, but I get the following error in my log file when it tries to extract the new plugin version:
[4.117 warn src/plugin.cpp:230 loadPlugin] Could not load plugin D:/Users/david/Documents/Rack2/plugins-win-x64/DanTModules: Plugin defines module SeizureTrigger but it is not defined in manifest
Good pitch!
Does anyone else have this issue?
I cannot reproduce nor see any reason why this would happen either in my local code or the GitHub repo.
My only guess is something out of sync with the library, maybe try removing and reinstalling my plugin?
Edit: the manifest is the json file right? Could you take a look in the file and see if it is corrupted or is obviously broken in some way?
2nd edit: I just deleted the plugin and let it redownload locally and that was fine, I think this supports the “something got corrupted during download” theory, so hopefully deleting and redownloading will fix the issue
Thanks Dan. The problem is on my end. My hard drive is going bad, and occasionally corrupts portions of the file system. Your plugin was corrupted in a way that prevented the normal deletion of the old version. I manually fixed things and all is well (except for my damn hard drive!)
OK, as you may have guessed, a new version of the plugin has been pushed to the library. This update is the result of Januarys milestone. I would have made an announcement earlier but it took me quite a while to create this video
v2.4.37
Sadly my Beta Test Team experiment hasn’t even got off the ground yet, I suppose it is not really that surprising since I only have 130
subscribers on YouTube, 246
followers on Instagram, and those are the only two socials I can stand to interact with…
I guess I’ll keep plugging it for a bit longer, maybe persistence will pay off at some point
Since I haven’t got a Beta Test Team yet, lets have a vote for February, what should I work on for my plugin? Please leave me a comment if you have any other ideas too
I always liked your Wavulike module for its versatility and ease of use, and I would appreciate having more VCOs with easy timbre morphing.
If I worked on a Wavuluv
module, would you prefer:
or
I don’t think it would be feasible to have both because I would be oversampling to combat aliasing which would likely make the cpu usage too high
Thank you for giving the Wavuluv
option some consideration!
My personal impression is that more edit points would likely make the wave look nicer, but the effect(s) on sound would not be overly dramatic, especially since you already have control over the Q parameters to bend the wave.
In contrast, at least to me, polyphony would be a real step up.
And perhaps some kind of unison, if CPU allows. I could envision Wavuluv
for lush pads with a slowly morphing waveform.
Hey dan! +1 for goniometer, also i have a random sequencer module idea!
The idea takes two possible avenues but the idea is the same, turings are cool, but lack some control, slips is awesome also but its all or nothing if you dont like a sequence.
Avenue one, 16 step sequencer where each step has a turing knob, and the values of the turing when random are updated when that step happens allowing time to judge if that new random note is what you want.
Avenue two, 16 step sequencer where you can again dial percent randomness or “slip” on a per step basis. (So you might need a knob for setting cv and then a knob for % of random, and then global settings for ranges of random.
Bonus points for turning steps off and built in quantizers.
Im also available to help design some panels if you wanted
Feel free to feel these are dumb.
Cheers.
If you are accepting random module concept ideas, my heart wants a guiro that’s easy to play around with. Your cowbell is so good, I know this would rock!
Hmm, not sure I’ve ever heard a synthesised guiro, interesting. I’ll have to do some research and see if there is a good physical modelling technique for it, but I’ll put it on my backlog for sure, thanks for the suggestion.
its a classic drum machine sound, Roland CR-78 and Minipops MP7 for sure
I think a little hand drum orchestra, featuring the Cowbell, guiro, tambourine, cabasa, vibraslap and flex-a-tone would just be too much.
cuica would just melt my brain