The Orthogonal Devices ER-101 is something I dearly want and will likely never have, and so I’m beginning to develop a VCV sequencer along the lines of that or the Buchla 251e, something designed to be controlled over MIDI via physical encoders & buttons/pads.
The basic unit will be a note, which will contain 2 CV channels and 1 gate/trigger channel. Notes and gates can be arbitrary lengths as counted by pulses of the master clock. Slew can be applied to individual CV channels of each note. Groups of consecutive notes will be able to be deleted, copied, or operated upon via some basic operations, and can be arbitrarily inserted or rearranged. More advanced, sequence-level arrangement is also something I’d like to figure out as well.
As I’m putting down my conceptual groundwork, I‘d like to ask if you have things you want to see that you feel are currently missing in your creative workflow and from the other sequencer options which exist on the library.
I have no promises as for how long this will take me or if I will ever complete it, so please don’t ask. I do, however, hope to get it working for my own selfish, creative purposes and if so, I will make it available either for free or cheap depending on the amount of development effort.
As I’m very early in development and currently working out data structures and figuring out the workflow, now is the best time for feature requests.
To clarify: I don’t plan to write specific MIDI functionality. Rather, I want to expose the functionality such that you can use Stoermelder MIDI-CAT or the like to map your MIDI controller to the module effectively and have it make sense to your hands.
I just tried planning a useable OSCilot / Open Stage Control configuration to interact with “Foundry” - I can’t map the piano keys, and I don’t know how to get feedback indicating the state of CV2/p/r for example.
If it was written with OSC in it’s inner workings, I guess I could have blinking LED’s on my tablet, use multitouch to enter chords, etc.
Possibly one of the biggest technical hurdles is the one specifically relating to the user interface.
In the interest of making this module accessible to OSC/Stoermelder’s MIDI-CAT, I need to allow the knobs (and possibly the buttons but we’ll see) to be multifunction – one knob needs to be able to control the value of different internal variables, some alike and some different.
The one instance I can think of in VCV Rack is the blend/spread/feedback/reverb knob on Clouds – but in that case there are actually four knobs. I would need hundreds of knobs if I followed that strategy, which also makes it much less useful when exposed to MIDI, since MIDI-CAT can only see the individual knobs.
Being a novice at the alien world of C++, I’m trying to work out how to pull and place the value at will. If anyone more experienced can give me a tip on how to resolve the issue that getValue() then setValue() leads to infinite accumulation, I would love to hear it.
(I’m moderately sure the problem stems from the engine smoothing param values, which means I need a different approach to getting and/or resetting the value.)
@Jens.Peter.Nielsen if you had a choice between a pure-CV interface or an interface with plain old knobs and buttons, which would you be most interested in?
I’ve discovered why OSC/MIDI can’t access the endless encoders on e.g. Impromptu Foundry. From what I understand, it’s an engine-deep issue where none of the OSC/MIDI map utilities have the ability to relatively increment or decrement parameters. Since they can’t map a finite set of data to the infinite range of the endless knobs, they instead fail to 0. @TheModularMind you may be interested in this.
For MIDI, you could use Stoermelder’s MIDI-CAT with a pure CV interface to increment and decrement values for the various parameters. I do not know if the expander for OSCelot allows for increment/decrement CV controls but that could be an alternative.
For what it’s worth, I’m more interested in a pure CV interface simply because it allows for simpler and easier data entry and can be directly controlled through the relative MIDI encoders on my device.
Ah, I don’t know. I think i would prefer the third option - a sample accurate sequencing engine in VCV, that comes with only remote OSC control - and a great interface in OpenStageControl
You can connect midi controllers, knobs and dials to Open Stage Control - pre-process and send via udp/tcp OSC to the sequencer.
There’s allready so many ways to do sequencing.
Some support control via OSC from a tablet - some do not.
So, Instead of doing a great deal of thinking about developing one, I think I pretty much have what I need allready in the modules available for VCVrack, but thank you for asking