Clocked now keeps its outputs high when resetting a stopped clock, such that when starting again, it will not miss the first step in sequential switches or sequencers that don’t have run inputs (see picture below). It is my belief that a clock should correctly drive a sequential switch and not make it miss its first step when we turn the clock on, since a sequential switch is actually the simplest sequencer and should always be able to be used as such in a patch. In the picture below, if we press run, the first step will play.
Clocked and all sequencers are now running by default. This probably should have been done a long time ago, and if DeadMau5 ever touches one of my sequencers again, the outcome might be better!
GateSeq64: we can now right-click steps to turn them off (instead of two left-clicks needed when the cursor is not on the step we want to clear. This might change in Rack 1.0. I will also try to implement mouse painting of steps, as suggested by Skrylar (and cf a long time ago!)
PhraseSeqs and Foundry: rotate offsets are now persistent and stored in the sequencer. Also, ctrl-right-clicking of notes can now be used to automatically copy the note or gate-type over to the next step (not just moving to the next step as is done by normal right-clicking)
Foundry: added bipolar option for CV2 outputs, available in the right-click menu (outputs will be -5V to 5V when active, instead of 0V to 10V by default). Reworked how CV IN and CV2 IN input writing behaves (thanks to fbeecher for the discussion): writing is now only performed for the active track (unless ALL is selected, then all tracks are written). Unconnected tracks are never written into the sequencer. When the expansion panel is active, a new button now allows selecting only CV IN, or CV2 IN, or both, for writing. (The quad LEDs near the CV IN and CV2 IN are now red, instead of the green seen in Omri’s tutorial and live stream)
So does this mean it sets it to high, or it will leave the gate at its current strength? Ambiguous
Andrew’s argument to removing right click init is because resetting controls in the general sense are not done enough to warrant stealing the button (in his opinion.) The supposed replacement is that right clicking on the controls will allow you to do MIDI controller mappings out of band (are you going to have individual step buttons mapped out of band?) I would argue that un-setting a beat in a step sequencer though, probably is done very frequently (although I do right click init quite often ) . Oh the things one might wish they had telemetry data for
Not sure I follow 100% your question. The clock outputs are either 0V or 10V; there is no notion of gate strength in Clocked. So in that sentence, “high” can be understood to mean 10V. It thus sets the outputs to 10V, and they will implicitly stay like this until we hit run and start Clocked, whereby they will oscillate between 0 and 10V according to the clock signal they are intended to produce.
Usage statistics would indeed be quite interesting to have!
If the clock is low when we turn off run, it will indeed stay low. But after a while if we hit reset, bringing the clock outputs high should not be a problem because the othe sequential elements in the patch typically get reset also, and so they will not be affected by the clock going high.
Marc I would like to thank you for update 14B, the right click option for Clocked to disable the high gate was what I was hoping for.
After update 14 some of my patches did not sync any more but now with 14B we are cooking again.
Thanks again for all your great modules.
BTW it reports version 13 to the Manager not 14 ! so it still wants to update, thought you want to know.
Thanks Peter, I just updated the github build now, I had forgotten to do a clean build and the version number had not taken effect. Nice catch
Glad you like the modules!
It looks like I will have to do an official update rather soon, since your side effect above will likely happen to others too!
https://github.com/MarcBoule/ImpromptuModular/releases/tag/0.6.14b
Hi Omar, if you are on windows, you can grab the windows build in the github release link above (if not I’ll try and make a mac build later today) until the next update goes through. Thanks.
I completed the first draft in my user manual regarding timing issues and missing first steps, and how to setup clocks and sequencers for best results. For interested developers, I also show some code excerpts of how resets, run states, and clocks are handled in Impromptu sequencers. Any comments are as always greatly appreciated.
CLOCKED: fixed P2 mode which was erroneously loaded as P4 when patches reopened.
WRITE-SEQs: added 2nd gate mode (held gates), added right click to turn gate off.
GATE-SEQ64: added step visualization in song mode (white lights), and added right-click initialization on main knob. Increased the number of sequences to 32 (up from 16).
PHRASE-SEQs, SMS16, FOUNDRY: added gate visualization in step lights.
FOUNDRY: fixed write bug when writing all tracks via CV IN.
Randomize in the right click menu now only randomizes the active sequence (notes, gates, etc), as opposed to the entire state of the sequencer (which was pretty useless). For sequencers with a SEQ/SONG switch, nothing is randomized in song mode. (This change will also be done to the Geodesics sequencers in their next update)
For users of Foundry, I also want to mention that if everything goes as planned, there will be a non-trivial change in the next update. After many discussions, it seems best to make the SEQ/SONG switch have the same behavior as in the Phrase Sequencers, namely that when in SEQ mode, the sequencer plays the currently selected sequence. Currently, the sequencer always plays the song irrespective of the SEQ/SONG switch position. Since there are 4 tracks in Foundry, there will be 4 separate sequence numbers in the sequencer, but with the ALL button we can manage them together if wanted. There’s so much more I could write here, so feel free to followup with any questions you may have.
Interesting idea Omar! Xavier Belmont is the concept designer of this module, and he’s actually under the knife these days, but when he is back from the hospital, I’ll mention it to him!
Glad to hear about the RAND function changes… Makes complete sense tp me to limit the values randomized Also, Im on board with the changes to the Song / Seq switch in Foundry. While I have become accustomed to the new system… (it’s taken a while though I will admit!) making it work the same as the rest of thew Impromptu Seq range makes a great deal of sense… and probably will reduce the learning curve for such an excellent Sequencer Btw Marc… I cannot post on FB (Some messed up account issue the FB are taking their sweet time to fix…) so please email or contact me here if needed… Cheers my friend!
I do have one suggestion… When changing sequences using pitch/V Oct to do so… (rather than song mode) would it be possible to do so sync’d to the end of the last sequence? In other words… you would select a new sequence via the Twelve key for example and it would only change to the selected sequence at the end of previously selected sequence so you don’t get glitches if your timing isnt perfect…(as mine often isn’t )
) . Oh the things one might wish they had telemetry data for 
Glad you like the modules!
It looks like I will have to do an official update rather soon, since your side effect above will likely happen to others too!