Do you see any visual indication of the parameter change, or do you have to just listen for it?
I was using 2 ADDR to change them and on new step of ADDR I got audible changes in root and scale that seemed consistent, I was also using a divided EOC to trigger regen which may have been when I got changes in scale.
I’m just using AS Triggers MK1to adjust the CV and can see any feedback that that the parameter is changing. Seems like there should be some visual feedback or CV control is blind.
as it stands, there is currently no visual indication of cv controls changing parameters, so “listening for it” is kind of all there is. i can certainly look into trying to find a way to visualize the changes, though.
i’ll be honest, some of this was something i’ve been worried about since starting the module. i have zero prior knowledge about music theory, musical scales, stuff like that, so i’ve been pretty paranoid that the module’s internal quantization isn’t actually correct somehow, and that i wouldn’t even know it because i can’t tell what scale i’m listening to just based on hearing it.
but now i’m even more concerned, realizing that something seems at least partially wrong with cv control of the root note and scale, and it’s making me wonder if i need to get a second opinion on how i’m doing things, so to speak…
Ken, just an idea I got to get some visual feedback.
you could try stoermelders strip module,
maybe this works.
I can’t test it right now, but I think it should work
Actually, this stimulated me to try uMap and it does give a visual indication of the root and scale parameter knob changing with CV control.and I can hover over the knob and see the discrete state. Thanks for the suggestion. I will use this to continue exploring Slips. Looks like it works for each of Slips CV panel parameters. Not all parameters behave the same way. Some show the voltage when hovered over and some show discrete or quantized states.
I’m usually satisfied if upon CV input I can hover over the knob or button and see the value or state in some meaningful way rather than just voltage. Try Stoermelder uMap and Slips and see what I mean.
Now I can see the output changing as I expected.and I can determine the param setting or state. I can work with this Thanks for looking into it.
I have not attempted to verify that the scale and root is working correctly. You may want to use the Impromptu Adaptive Quantizer with the CV going in to REF CV and the clock going into REF GATE and you can watch which notes are played with a setting. I have used this to diagnose elusive quantizer issues.
Have you ever taken a look at adding a “Poly External Scale” format output to Slips? That comes in very handy for seeing what the scale for a setting is and that can be shared with some other modules such as Grande Quantizer to quickly see a graphical view of the quantized values as well as allowing other modules to quantize to your scale via Grande Quantizer. That is basically what I’m doing with Adaptive Quantizer
BTW, your method of CV control is an attenuvertor, I think. using uMap makes into a parameter automation control. All of my modules’s CV controls are geared for parameter automation.
BTW, I really like Slips and enjoyed watching Omri’s YouTube video yesterday. I am going to write a BASICally script that will map PurrSoftware modules (Meander, ModeScaleQuant and ModeScaleProgressions) scale and root outputs to Slips CV inputs so that Slips can track my modules’ scales. I only support the modern modes so a couple of your scales will not map directly, but that is fine. In this use case Meander will create the chord progression and Slips will create a melody in the same “key”. And Squinktronix Harmony will create alternate chords. Or something like that…
thanks! so glad people are enjoying it, and Omri’s video was really fun for me as i’ve never had anything i made get “featured” in that way in some form of public setting. it was exciting and i’ve gotten some great comments since.
by this do you mean something like adding an output that simply always outputs like a poly cable of all included notes in the current root+scale? that’s certainly an interesting idea to take a look at.
interesting. i just opened Rack and tried plugging an LFO into some of Meander’s inputs and immediately saw the knobs changing with the input. i think, pretty early in my Rack dev journey, this was something i wondered about, if it was possible and how to accomplish it, but never figured it out and just moved on. but clearly it’s possible, so i’ll certainly dive back into this as well.
(EDIT: quick note - i just opened slips’s code to double check, and actually none of the params on slips are used as attenuators/attenuverters for their associated cv signals - the cv input simply overrides whatever is set by the param)
and as i mentioned, i’m still pretty paranoid about my entire quantization process, because i basically found one of the simplest examples i was able to understand in order to throw it together, so i’m not entirely sure if it’s all actually working correctly to begin with. i think at some point i do want to ask someone with more knowledge to at least take a look at my Quantizer.hpp and maybe try to give me thoughts on how to improve it to make sure it’s accurate. like i said, i’ve never noticed any issues, but since i’m not particularly musically inclined and couldn’t tell you what note i’m listening to to save my life, i wouldn’t know anyway, so i’m still pretty paranoid about it working or not.
anyway, thanks again for the feedback, suggestions and tips. Omri’s video already made me want to go back in and work on it some more, and now i have even more reason to do so.
Well, to be honest, I took a lot of heat for developing Meander with the equivalent of “motorized knobs” for automation. Some people freak out when the knobs start moving
I got my BASICally scripts working so that my modules can directly control the scale and root in Slips.
Yes, “poly external scale” is simply 12 channels where there is a channel for each semitone in the chromatic scale and a channel has a voltage of 10.0v for the root or tonic, 8.0v for any other scale note and 0.0 for all non scale notes. Meander can send the diatonic heptatonic scales or pentatonic scales.
Nice – in this chilly fall I can warm my hands by the heat of the feedback for HC-One (in beta) that animates the knobs.
When CV controlled, the track around the knob turns orange and in absolute mode, the knob is animated to show the value being sent. In relative mode and something’s plugged in (e.g. Rate), it animates the orange LED on the track at the effective value being sent (via MIDI). In relative mode, the knob isn’t animated and you can twiddle the knob to change the value that the CV is an offset from.
In this picture, everything is set to relative (assumed bipoler) CV mode except Mod Delay Depth, which is in absolute (assumed unipolar) CV mode.
The small buttons with a blue LED toggles absolute/relative CV mode
Very active and nice in a dark room.
so i’ve added polyphony to slips. i’m still tinkering with it to see if i can make it cleaner than it is right now, but it works, at the very least.
i’ve also added a ‘Nightly’ build to my github action, so every time i push to the repo, it builds the plugin and updates the ‘Nightly’ release, so the most up-to-date build will always be available here:
this includes the polyphony in slips, as well as automatically generating a new sequence/mod sequence when the module is first created, and the sequence will no longer reset to the start when generating a new sequence and will just continue along the new sequence from where it was.
… It’s a specific case and nothing I couldn’t fix with a quick comparator, but I was driving SLIPS’ starting step with an accumulator (on EOC, push sequence one step to the right), and when that CV input goes over 10v, it keeps going, trying to play stuff that isn’t there with modulation and sequencer events defaulting to 10v. Gave me a small scare, when suddenly an anvil was falling on my delicate (vst) piano
Oh, edit: Slips is fantastic, of course!
oooh, nice, thanks for the heads up. i have the poly update going into the library as we speak, but I’ll get this taken care of today and hopefully can sneak it in with the poly update. otherwise, I’ll get it submitted soon.
just managed to sneak the update in to the library submission, so it should be coming with the next library update along with polyphony.
until then, the v2.5.54 release here contains the fix. starting step cv input values above 10V will just wrap back around to 0V.
thanks again for catching this (and for the kind words)!
aaaaaand because i’m dumb, i didn’t consider negative values. now i’ll need to try and sneak one more update in when i’m able to fix it. please don’t hate me, maintainers!
updated build that also wraps negative values back around to 64: Release nightly build updated with every push · alefnull/alefsbits · GitHub