Baconpaul (Surge Rack, Bacon Plugs and the Rack port of the Airwindows plugins) and I have completed the initial work necessary to update the mscHack plugin for VCV Rack 2. It was last released for VCV Rack version 1.
The original developer has been notified and has gotten back to us that he is fine with the creation of a fork to enable it to run in VCV Rack 2. Given that this is a fork and not initiated by the original developer, it would be appreciated if all issues are raised on Github here: Issues Ā· baconpaul/mschack-VCV-Rack-Plugins Ā· GitHub or added below in this thread.
Right now, we have gotten the plugin to the point where it seems to work and have re-engineered the parts that made them tricky to port over to VCV Rack 2. Weāve done basic smoke tests but they are not extensively tested. We would love open issues at the repo above or feedback in the thread below.
So nice to have these back again. Iāve built the plugin for Mac OS x64 and arm64, clean builds with no warnings or errors. Will test some favorites later today.
Yeah I finally got the docker tool chain running in my arm mac (thanks @cschol ) which helped me find the warnings on all platforms. Highly recommended and I wish I had done it earlier
Paul. Maybe it is the nature of āPing pongā delay. however I am seeing a high peak of -700 cv on that module when I turn up the RR, RL, LL, LR dials, it then freaks out even worse when the delays are set to full amount. This causes the Mindmeld mixer to jump into the red.
Iāll take a look sure! Sounds like a normalization problem. Our port should have left that unchanged but doesnāt mean it is correct
(In the surge delay we end up putting a variety of optional clippers in the feedback path to avoid runaway at the cost of distortion. Maybe the same trick here optionally would make sense)
OK I pushed a fix for the falk issue (and opened an issue to scan other code for similar bugs); and a fix for the lorenz draw (when i lifted the waveform into the room brightness layer I didnāt also lift the crop rectangle)
The feedback one is easy to reproduce but Iām not quite sure what the solution is. The module itself has unfettered feedback.
I might choose to add a switchable soft clip at +/- 7v or +/- 12v or so (and also have no clip). Still need to peer at the code. But āits not a bug its a featureā is sort of one assessment of the bug. Turn down your feedback levels and it should subside.
Oh and @pgatt and I were chatting. We have crossed the Ts and dotted the Is to push this to rack 2 library, and think we will do it in mid-late sept. So testing and bug reports in the next 3 weeks particularly welcome.
Hello there! I donāt know if Lorenz module is supposed to work as I described in the issue I opened in github but here it is ā> ISSUE
(Quote from github):
when all the parameter are DEFAULT, if I turn parameter P1 = 0 it seems that the whole module stop to work. I can twist any other knobs but I got no changes at all, both visually and audio. I have to CTRL+R the module to make it work again. I donāt know if it is intended or if it is a bug.
If I turn
P1 = 1
P2 = 0.946
P3 = 0.095
All the T as DEFAULT, all the Filters as DEFAULT and all the Levels to the max (X = Y = Z = 10) it happens what you can see in the picture (THE PICTURE IS ON GITHUB) and consider that the cyan curve is static, not moving and there is no output sound I can hear.
All in all it seems (but I might be wrong, not knowing how the algorithm work) that the P1 knob/parameter work a little bit weird.
Also, sorry if I have answered so late to your question, @baconpaul on my previous issueā¦ I put a description in my new issue. I hope it helps.