With the release of 2.1.7 coming, its about time to create an announcement thread for my collection of modules
Questionable Modules is a collection of my weird module ideas, I have currently made a sequencer, oscillator, and some randomization utilities. Their description and usage are linked below.
You can toggle the labels for the modules by selecting âToggle Descriptorsâ in the context menu. This feature will be available when 2.1.7 gets pushed to the library. You can manually download 2.1.7 here in the meantime
Very cool looking, and I love the demo! The circular oscilloscope looking display on the Slurp oscillator is really fun. Sounds great! Love it.
From a marketing point of view, if someone posts a video using your modules (like you did above), and a viewer got interested in them and tried to find your plugin, they might be a thrown off by seeing âISIâ at the bottom, while the brand name is really âQuestionable Modulesâ.
Here I am on the VCV Rack Library, looking for âISIâ brand name. Where is it? I canât find it!
This is the kind of confusion that can reduce the download rate of a plugin, even if it is functionally wonderful. Ideally you would put âQuestionable Modulesâ somewhere on the panel, but of course thatâs rather large to fit. You might want to consider something like âQMâ or â?Mâ or something at least tangentially indicative of your brand name.
Obviously SLURP is pretty cryptic. It sounds good, but the lack of labels, and the weird nature of the beast make if difficult to figure out. Are the three V/OCT inputs really independent? If they were normalled so you could use it as a regular VCO is would help.
The panel layout does not make it clear at all which inputs go with which knobs. That and not having labels makes it really difficult to figure out. The controls and knobs are much more dense than you commonly see in a VCV module. Maybe the module wants to be wider, or the cool display could be sacrificed?
Also it is monophonic, which is getting less and less common in VCV oscillators.
It is also very heavy on the CPU - its it possible to make it more efficient?
The inclusion of presets is a good idea.
Anyway, an interesting sounding module, but it probably wonât be very popular in the present form.
Also, I was unable to build the module, and I donât think there are any instructions in the README. I figure you probably need to do the deps thing like you do with VCV, but I get a semi scary error when I try that:
$ git submodule update --init --recursive
Cloning into '/d/Rack/plugins/questionablemodules/src/gmtl'...
The authenticity of host 'github.com (192.30.255.113)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
cool. Itâs very, very unusual for VCV modules to use SSH. I understand itâs your workflow but itâs not the workflow of 99.99 percent of your âcustomersâ.
If it helps I do a bunch of submodule stuff. I use the https in the git modules so folks donât need ssh to update but that sucks for dev. I fix that by just adding an extra remote in my dev area after I update. So first time I clone I go to libs/foo and git remote add upstream-write or origin-write with ssh.
This may not help in your case since I donât know your workflow
oh yeah that works great if you are all in GitHub! Should have thought of that. Glad it works for you! That syntax can cause problems if people fork your plugin and not your submodules though, just FYI.
$ git status
On branch master
Your branch and 'origin/master' have diverged,
and have 1 and 6 different commits each, respectively.
(use "git pull" to merge the remote branch into yours)
nothing to commit, working tree clean
did rm -rf on the whole folder, re-cloned, stll get that same ssh error:
$ git submodule update --init --recursive
Cloning into '/d/Rack/plugins/questionablemodules/src/gmtl'...
The authenticity of host 'github.com (192.30.255.113)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
Anyway, the new version in the library does indeed have labels I think they are off by default? Which is kind of weird. In any case, once you turn them on the font size is super small. Totally out of scale with other VCV modules. I canât read them. (notice that the huge majority of VCV modules have the labels on all the time.)
SLURP also has a new polyphonic mode called spread. (CPU Intensive, hopefully less in future updates)
Can now disable the octave knobs quantization for more fine tune offsets (for SLURP). (broken in Rack 2.4.0 )
Rack 2.4.0 prefer dark panel is taken into account for newly created modules. Modules can still be changed to different themes regardless of this. Rack 2.4.0 is now required to run
Deleting Night-bin and then quitting Rack causes a crash. Looks like some structures are left allocated that eventually cause a double free on Rack exit:
MacOS 13.5.2, M1, Rack 2.4.1 arm64, latest build, just downloaded. Also still doesnât sort plugins alphabetically btw.
Edit: Seems to leave some permanent structures in Rack as it crashes still on exit with same stack on exit, even though no Night-bin had been used since initial test and several new patches were played with (with no Night-bin ever added).
And Slurp is one of my favorite VCO!! Great sounds! I am currently studying what quaternions are to better understand that module. As always, Math rules!
)
