Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Utterly amazing, but why did you not develop this as a VST? It's of little use to musicians otherwise. If you are planning on a VST in the near future, count me as extremely excited!


As an answer to "why", if you are curious:

Technical limitations of being a VST/AU plugin: Sparse support of window resizing, lack of multiple simultaneous DAW integration, ability to only exist on multiple channels, ability to output/input its own audio/MIDI, limited number of automation parameters, ability to remain playing without hiccups after a DAW has been closed, future ability to exist on a completely different computer. Compare Rack to something like Reason instead of a single synthesizer, which has no plugin version.

Philosophy of a standalone application: VCV Rack attempts to emulate not only the technicalities of modular synthesizers but the entire mindset and workflow. Most modular artists consider their instrument to be a composition tool rather than an element of a song, which more aligns with the title of a DAW. Eventually the need to use Rack in a DAW will nearly disappear, as more modules are added to compose and record a song from scratch to finish. However, many DAWs have ways of communicating with other DAWs, and Rack is no exception after the release of "VCV Bridge", scheduled to be included in Rack v1.0. More information:

https://vcvrack.com/manual/Core.html https://github.com/VCVRack/Rack/issues/31


Kudos for going the route of a VST bridge on this. I can see this becoming a necessity as this project grows. This is the route the Hauptwerk took for their pipe-organ software. They used to have a VST-version of their platform, but it was just too unwieldy, particularly if the DAW ever crashed, taking Hauptwerk down with it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: