Hello! Enjoying the modules. Pul5es is a great utility module.
However, there’s one issue with Pul5es that could be improved in a future update. The “LOOP” button is not stateful. It doesn’t save the state in a preset, nor does it save upon closing a patch and re-opening.
I just banged my head against the wall for 30 seconds searching for what error I had made when a thing wasn’t modulating…ah, Pul5es wasn’t on loop!
Possible fixes/improvements:
save state on exit
state saves in preset
CV gate input for on/off
[edit] As long as it’s a wish list, CV input for the “Out On” setting would expand the possibilities quite a bit!
Sorry for the problem not saving state with Pul5es It was a silly error on my part and has already been fixed! The next update will resolve that.
I considered the CV input for the timing, and will definitely give it more consideration now
I am very curious about the gate input for on/off… Do you mean that instead of triggers in, that it counts input pulses from gates? And if so, would it could them differently (e.g.: both on and off as two pulses)? Do tell!
Got it! I should be able to get both of those suggestions in before the next update is pushed (though it might be at the expense of a little more width to the module). Thanks for the input (pun intended).
I’ll add that I also keep track of my stupid mistakes on the GitHub repo for the modules, and am happy to take bug reports and suggestions there (as well as here).
Just wanted to follow up and say that 2.0.5 just made it into the library and has the fix for saving loop state AND three new features based on this thread:
Change the “out on” count based on CV input (0-10V)
Toggle loop state using a trigger input
Switch to using a gate instead of a trigger, meaning it will only loop while a gate is open. You can also choose to output triggers only while a gate is open (the first trigger would normally still play as this only controls the loop functionality)
New Module: CFor2N2ForC - will send configurable CV and/or trigger outs based on one octave of note CV coming in. E.g.: on C# output 4.23V, but on D output -3.9V.
Pul5es: fixed not saving loop state
Pul5es: Added CV control of “out on” count and loop state
Chord4Roy: Wrapped negative voltage to positive range for extended V/Oct root note knob selection
Merc8or: visual tweak (0V center line wasn’t centered! D’oh!)
A cursory test of sending my Meander chord progression chord root to Chord4Roy as v/oct results in the correct interpretation now. Thank you very much for changing this. I will resume exploring the modules. Actually, PICK6 is working very well with this setup. Meander is playing the progression chords and chord bass as well as a scaler melody and arpegiattion. Everything sounds very good playing together in Cmaj.
There seems to be an occasional issue with negative v/oct in Windows. No errors are shown in the log file however. This seems to be a crash on exit or perhaps upon the next launch. I’ve stripped the patch down to mostly just have Chord4Roy in it.
If I can get a log file indication, I will let you know.
It appears this crash is occurring as a result of sending the Chord4Roy poly CV out to Impromptu FOUR-VIEW. Perhaps that very high 10V output from some channels is causing some problem in FOUR-VIEW. It is very reproducible, so I think this is it. This is compatible with the log as on a crash there is no error in the log file but FOUR-VIEW is the last line in the log. That is usually when the crash is on load.
So, I will keep messing with it.
I’ve convinced myself this is the problem and I can get rid of the crash by not sending the poly CV out to FOUR-VIEW. Could be just that fact that I am sending 13 channels to Four-VIew and there is an array overrun issue.
I added Four-View on my Mac (Intel), Windows 10, and Ubuntu machines. I put C4Roy into VOct mode and hooked a LFO up to root note and chord and pushed it slow and fast and at both ±5V and 0-10V, and Four-View in both Notes and Chord mode. Through all that I could not reproduce the crash. I also split C4Roy out into individual channels and sent the 10V mutes to F-V and it just reported “C” (as it should).
What platform are you running on? What audio interface sample rate are you running at? Are you running C4Roy through anything before F-V? (e.g.: octave or something). I’m just trying to think of things that might have some impact.
I am running Windows on an Alienware gaming tower, 48 kHz, 1024 buffer, 2 threads.
But, I suggest that it may not make sense to dig into this more as in my experience, buffer overruns are notoriously difficult to track down. Often the log will show various modules causing the fatal error, even when the root problem has nothing to do with those modules.
For my purposes, the problem totally went away by not feeding the Chord4Roy poly CV out into F-V. It did not make sense to be doing that, but I use F-V as my default poly channel display and I use Chinenual NoteMeter for up to 12 channel viewing. Sending 13 channels into NoteMeter has not caused any problems.
That’s a weird one, and I’m always willing to try to figure out problems (especially if it could be my fault). I’ll keep an eye on things and see if it pops up again. Thanks for letting me know that you do have it all working.
MOREc8or: A new (expander) module! Add input options to Merc8or output params. Wild stuff!
C|RB Vi: Another new module! A 2D performance instrument/playable VCA (XY pad with bells and whistles). A virtual port of the C|RB ribbon controller from Wygonium.
Merc8or: Output snapping to octaves or semitones (this is like chromatic scale quantization)
Merc8or: When snapping, option to add half-semitone to output (added stability with some modules)
Pul5es: Added visual display for “Out On…” param because it was suggested and is the right thing to do!
Thanks! I went with just three octaves for two reasons: it matches the hardware ribbon controller functionality it’s based on, and I didn’t want to make it too wide for on-screen/trackpad use (I actually considered making it 3x the current width, but reeled myself back )
But this is exactly why I put the raw X and Y outputs in the “RAW OUT” polyphonic output; channels 4 and 5 are the X and Y, respectively, each at 0-10V, so you could run those through a quantizer (and shift it down -5V) and have 9 octaves. (The info on the github site is still in progress, so you might be understandably not aware)
I had also considered making it resizable like some of the blank panels, but maybe I’ll work on an expander that can connect and bridge the gap between the sides. Next week’s project
For a horizontal touch strip, you want to be able put one above the other like an organ, which you can’t do using the Rack extender mechanism because it only works horizontally for adjacent modules.
There are other ways to get module instances to cooperate.
I had made a triple-stacked horizontal touch strip for my Sensel Morph in place of my hardware ribbon controller, and didn’t find it to be a good experience. I prefer to be able to slide between notes across octaves at times (most of the time), and vertical stacks of horizontal strips aren’t good for that.
It was a silly error on my part and has already been fixed! The next update will resolve that.
I also split C4Roy out into individual channels and sent the 10V mutes to F-V and it just reported “C” (as it should).
