Skylights and SkJack modules are free but developing, debugging, and keeping up with Rack updates is not. 3$ is an hour that can be spent with Rack instead of doing menial typing labor on job markets.
This plugin aims to bring first class support for the JACK Audio Connection Kit to VCV Rack.
- There are four input and four output ports.
- Output ports are marked with an off-color accent.
- Each port may be named.
Four ports is not enough for me!
You have some options:
- Just add another
JACK Audio. Seriously.
- Add one of the special 8 inbound or outbound modules.
JACK modules are designed to cooperate with one another. They will feed audio to JACK or to Rack and only one of them will block Rack while waiting for audio to be processed. You can consult the power meter for proof.
This is the same as a
JACK Audio excepting all ports output to JACK.
This is the same as a
JACK Audio excepting all ports output to Rack.
Port names have
-out suffixes added in the background. This
matches how applications usually work in the JACK ecosystem. It also
makes it possible to run Rack effects where both input and output
channels are named “reverb.”
Input ports must have unique names across all inputs in a Rack instance. All output ports must have unique names across all outputs in a Rack instance.
This is a compatibility breaking change.
All port names had to be unique across an entire Rack instance. Names appeared exactly in JACK as they appeared in Rack.
We do not currently calculate and report processing delay between a signal entering Rack and exiting it. This means none of the delay compensation logic works and you may end up with desyncs if running more than one Rack instance or certain DAWs.
The issue is known and some attempt to fix this issue is scheduled.
Patched Rack’s with JACK in RtAudio
Some users are running versions of Rack which contain patched RtAudio
libraries. These patches allow you to use JACK with the native
Experience has shown that while this works enough to get audio to and from Rack, it does not integrate well with the JACK ecosystem. I do not support these special builds.
Audio and rcm’s Audio 16
ALSA, JACK and Pulse Audio tend to compete for exclusive access to the
sound card. Having an
Audio module from
Core, or an
rcm will result in issues.
These issues have mostly been reported as:
- A crash when exiting Rack,
- Rack crashing when trying to delete the
Some workarounds are known:
- Delete the offending models from patches,
- Leave them be (leave the
Audiomodules blank so they read “ALSA” but do not show a device such as
Systems without a JACK server
Special support has been added to address:
- Running on machines with JACK, but the server is turned off.
- Running on machines where no JACK server is even installed.
In both cases the modules will simply do nothing. You may still name ports and hook them up, and those will work if loaded in to a Rack instance with a functioning JACK server.
Licenses and Credits
The module graphics template was designed by github user @infamedavid (David Rodriguez), and are available via CC-BY.
The 3270 terminal font is used under the BSD-3 license.
This plugin is made available under BSD-3.
A copy of the JACK client headers are included under
are made available to us under the LGPL license.
We have included them because it primarily simplifies compiling the plugin on Windows (MinGW2) targets.