When will Rack v1.0 be ready?
Rack is currently in Beta (thus the version v0.x), so by using it, you are an “early tester”. Don’t worry, Rack v1.0 will also be free open-source software.
In order for Rack to earn its “v1.0” designation, it must improve in the following three fronts.
Since I am an “indie developer”, I cannot yet afford to test Rack on every combination of hardware on the market. With the introduction of commercial VCV plugin sales, I will soon be able to invest in hardware that is known to have compatibility problems with Rack. If you are willing to lend me hardware to test, email firstname.lastname@example.org for details.
Rack is not ready to be trusted for live use, although some musicians have used it successfully in live performances. In order for Rack to be considered “stable”, it must produce audio with no clicks or pops on modern hardware for several minutes and must crash less than once per several days of continuous use. Currently, stability in Rack is the most developed among these three fronts.
Depending on your CPU and graphics card, Rack may consume high CPU/GPU resources and therefore increase your laptop’s fan speed. I am aware of this, so there is no need to inform me. There are currently two low-hanging fruits: optimizing the graphics renderer on the main thread and replacing the sample rate converter on the audio thread. If you are dying to improve performance now and are a software developer, you may research one of these two issues.
To answer the actual question, there is currently no time estimate for v1.0.
When will VST/AU support be added?
VST/AU support will be added with the “VCV Bridge” module in Rack v0.6.0, scheduled for release in late January 2018.
Rack itself won’t be a VST/AU plugin because of the major limitations of these formats, but instead you’ll be able to connect Rack to your main DAW by adding the lightweight VST/AU Bridge plugin to as many DAW channels/tracks as you like, which will each connect an equal number of Bridge modules in Rack. This cross-application method allows you to break the mindset of mixing linearly in your DAW and instead use nonlinear methods like cross-modulation between tracks, enveloping audio to control filters and sidechain compressors, etc. The Bridge protocol will be fault tolerant and will not matter which order you open the DAWs.
My audio interface / MIDI device doesn’t work.
Make sure the device drivers are up to date for your operating system. If this does not solve it, please refrain from notifying me unless you
- are willing to lend me your audio interface (email email@example.com for more details), or
- you are a developer and have discovered a fix to the source code of Rack, RtAudio (use rtaudio_test to determine whether the issue is with Rack or RtAudio), or RtMidi.
See Compatibility above.
The graphics are rendered incorrectly, not at all, or Rack doesn’t launch because of an “OpenGL error”.
Rack requires at least OpenGL 2.0 with the
Make sure you’ve installed the latest drivers for your graphics card, and restart Rack.
If this does not fix it, see below for instructions on submitting a bug to Rack’s issue tracker.
See Compatibility above.
The CPU usage is high.
See Performance above.
I found a bug.
Search Rack’s issue tracker to check whether someone else has posted a similar issue. If you think your problem is unique (unlikely but possible), you may open an issue or email firstname.lastname@example.org with a detailed report containing the following information.
- Your operating system and version
- The Rack version
- The actions that trigger the problem
- Any error messages that appear. Screenshots are helpful.
- The hardware (e.g. audio interface, MIDI device, graphics card) related to your problem
I have a feature request.
- Your proposal, with consideration for how it fits into Rack’s existing features
- A possible workflow or diagram (if your request involves multiple steps or UI states, e.g. dragging multiple modules simultaneously).
Depending on the usefulness of your request, it may take 15 minutes or 24 months for your feature to be added, or the issue may be closed if there is little total benefit compared to the cost of implementation (time saved or spent using the feature, divided by the time to develop the feature).