You’re my hero!
Last few days, I’ve been working on the documentation for my modules, to replace the github README.
I’m particularly happy how I’m simulating patchcables in the browser, showing you exactly what the jacks do as you scroll:
I’ll be honest with ya, my effort was 1000% overkill compared to what’s necessary, my module docs were more of a use case for me to learn more about the vue.js ecosystem (it’s nuxt.js under the hood). I got most of the basics in place, needs a bit of polish.
If you wanna give it a spin, lemme know what you think, but please note, only the pages for Arcane and Darius exist for now, every other page will just give you an error. And for now, it only works on a big screen, it will break on phones or if the window isn’t maximized, and it consumes more CPU than it ought to.
And the source:
Unsurprisingly, I’m finding out that Modulus Salomonis Regis works much better with self-patching patterns simple enough you can follow how they change.
A few interesting techniques I discovered:
- Because a gate to a + and its corresponding - cancel out each other, you can use that to slow down the rate of change
- By sending gates to “Queue” twice as fast as “Forward”, you can create interesting rhythmic patterns. By setting a single output to trigger many queues, and staying in Keep mode, you can make the pattern accelerate for a few steps.
Test beat, with also some QQQQ tricks in SD transpose mode
First quirky interesting excellent modules and now equally excellent docs? NICE! Great job on a very unique doc site!
Modulus Salomonis Regis is close to finished.
Only a few features are missing:
- No documentation yet… Embrace the mystery! (look at the previous posts for some explanations)
- No portable sequence I/O yet
LCD not fully implemented yet, it’s a bit wonky but you can set the key and scale.
I encourage everyone to please start testing it heavily, and report. Lemme know if it works for you (I need a report from an OS X user!), and what you think about it.
Be sure to report any weird behavior, just be prepared for me to tell you they’re intended. For example, if you change the scale, it doesn’t re-quantize the nodes until they’re changed. That’s by design.
Automatic builds from the usual place: https://github.com/AriaSalvatrice/AriaVCVModules/releases/tag/AzureCI
This version also includes a fix for the QQQQ crash when importing long chord progressions.
I ran into a bug that surprised me so much I decided to canonize it. When sending both a Walk and another type of input, there was a chance to repeat the note! This was not intended, because you can already set up this kind of behavior through self-patching, so I fixed it, but I thought it’d still be useful to expose that possibility:
In Teleport mode, it has
1 / Total nodes enabled chances to repeat. In Walk mode,
1 / 3 chance (then the direction is
1 / 2 ). The New/Any has no effect on other modes.
Once I release this module, I will NOT consider feature requests. It is intentionally challenging and surprising to use, to the point I feel I’ve barely started to discover myself all the fun tricks it makes possible. I want us to explore its potential before exposing more options.
So if you want to argue for changes in its behavior, do it now.
And reminder: I need confirmation it works from a Mac user.
Also, since I am writing the credits for the docs right now, I’m reminded of this, for the segment display, I’m using the DSEG font - and take a look at the author’s page, they also created a lot of cute DIY synth hardware
Hi, Aria. There’s a flicker in the display of the active step:
if you want to argue for changes in its behavior, do it now.
Okay, I was kinda hoping that triggering the reset, would reset to the first step. (Instead of doing a pitch reset) And that maybe we could have that “pitch reset” as separate inputs for each step (I know that one might be too much changes with the ui). Whatever you think is best. I love it no matter what! Amazing work. Keep it up.
Log file? log.txt (100.2 KB)
The behavior in the video is intentional. The play button isn’t eye-catching enough to visualize the current step once the module is heavily self-patched.
I figure that one is best left for queues.
In general my thinking for this module is to provide well curated defaults that produce musically surprising results instead of a lot of toggles. Things are already sufficiently intimidating as they are. The more options I add, the more I restrict how many people will dare learn how to use it.
I figure that one is best left for queues.
How did I not think of that! Thank you!
This was intended, it not happening was a bug, fixed, thanks. As of the last build, the LCD is also fully implemented.
I have added the following right-click options:
With that, I consider Modulus Salomonis Regis complete. Work on the documentation will start now.
Please test it and let me know what you think.
Reminder, I need someone to test it on the Mac
Sanity testing on my MacBook running MacOS 10.15.5 looks good!
Thanks for testing on the mac!
The first part of the documentation is ready, it’s not complete but it should help if people had trouble figuring out how to get started: https://aria.dog/modules/modulus
Whoa - I don’t really know what I’m doing, just patching stuff but I’m getting very cool evolving melodies. Seems very powerful and unique! I’m going to investigate more…
Played with it some more. It’s not as intimidating as it first appears with all those patch points - the design is super smart and very unique, I don’t think I’ve ever used a sequencer quite like it. If I had to describe it, it’s like a sequencer with a brain that you can program. So cool!
As an aside, it looks really great in lights off mode.
And the manual is now finished! https://aria.dog/modules/modulus
We still haven’t figured out how to get my stuff to build again in the library, but I’ll be doing a manual release soon. If you got feedback, don’t delay!
I have added one more feature: right-click option to quantize upon reset input.
The module is now soft-released, beta-testers just can’t keep up with my pace lol.
I’ll just do a 1.6.1 if stuff breaks.
Stable downloads: https://github.com/AriaSalvatrice/AriaVCVModules/releases/tag/1.6.0
I submitted it to the library, but we haven’t solved the build issue yet, so for now it’s a manual install.
Still gotta finish up the doc site & collection video intro, then I’ll make an announcement thread.
Fun trick you must try at home:
- Save a sequence in Modulus Salomonis Regis.
- Use Modulellus Salomonis Regis to generate a new chord each bar.
- Turn the chord into a Poly External Scale using a merger then Quale
- Send that Poly External Scale to Modulus Salomonis Regis (on this pic, going thru QQQQ)
- Set Modulus Salomonis Regis to re-load and re-quantize the pattern on reset
- Reset each bar
It’s nice to see all the pieces of the system I have in mind starting to combine together the way I wanted
Looks like we might have a solution for library automatic builds, so I’ll hold off on making a 1.6.0 announcement with a manual download link and get a few bugs fixed first.
Coming in 1.6.1:
Additionally, I implement the changes from Revision 2 of Poly External Scales (behavior subject to change pending reactions from other developers):
I kinda wanna provide an option for saving knob positions with scenes, but:
- It’s hard to expose to the user in a way that makes sense
- It’s full of edge cases
- 8FACE already does the job just fine in a way that matches users’ intuitions
Hands down the most playfully done and cool manuals around. Well done !