The README explains the functionality of my modules. If you have any comments, please reply to this post! I plan to have the FRAME module and it’s expansions done sometime in the next two months.
Yeah I imagine so, although I’ve found that a lot of the features exist already, they are just scattered across modules. For example I believe Entrian developed some pop up windows for editing midi and envelopes, there are also loop recorders that are not polyphonic made by Sonus, and trowaSoft made those modules that respond to OSC messages. The largest task would probably just be integrating all of these things.
There’s a timeline in rack 2.0? Also about that, when Rack can be a vst, a lot of this functionality can be achieved in the DAW, though it will probably be a poorer interface, and less modular. For example I noticed one can’t introduce any feedback in the routing of tracks REAPER, signals can only flow one way.
Getting into it, not so much! I got some basic looping functionality done today with the FRAME module, and the rest is just refining the software and adding more features. The scope of the ‘Sound Interface’ section will be a bit larger, but it’s certainly doable! The longest part will probably be creating an OSC server in a VCV Rack module that reacts to a custom protocol and controls other modules.