Frequently Asked Questions

From Patchblocks
Jump to: navigation, search

Don't see an answer to your question? Head over to the Patchblocks Community for more help!

Are Patchblocks Compatible with MIDI?[edit]

Not at the moment, although this is currently in the works. For now, one of our users has created a MIDI wiring schematic that is being discussed here. Also see the MIDI page in this wiki.

Are Patchblocks Compatible with Control Voltage (CV)?[edit]

Not out of the box, but there are ways to make your Patchblock compatible with your modular rig or other CV device. Since the analogue input and output are DC coupled, you can send and receive a constant voltage signal with the Patchblocks. Because the voltage range of the analogue input and output is -1/+1V, a level shifting and amplifying circuit will likely be required to map that to the voltage range of your CV rig. Another option would be to send a constant -1V on one output channel connected to ground on the CV device, while the other channel provides a 0-2V range. A third option is to take a look at the user-created patch that works as a CV LFO. The patch can be downloaded here.

What are Those Big Chunks of Text on the Wiki and on the Forums?[edit]

The Patchblocks software makes it super easy to share bits of patch code without saving files. If you see a block of text like the one below, just select it and copy it to your clipboard (cmd+c, ctrl+c). Then go to any patch window and paste it in (cmd+v, cntl+v). Patchblocks will perform a little magic and a chunk of code gets inserted right into the patch window. Give it a try on this code below:


Why Do I Hear High Pitched Noise/Static When Moving the Knobs?[edit]

This is not uncommon, and is most likely due to cross-talk between the knobs. A possible fix to the firmware is in the works. Another cause of this low-level noise may be due to low signal strength within a particular patch. The Patchblocks are designed to operate at high volume levels, so if your patch uses an audio input signal that's too quiet you may end up with a low signal to noise ratio.

Why Does Movement of One Knob Affect Controls Related to the Other Knob?[edit]

This is not uncommon and is most likely due to cross-talk between the knobs. A possible fix to the firmware is in the works. In the meantime, the user-created [1] block has helped resolve this issue for some users.

Why Does a Patch Work in the Emulator, but Not on a Patchblock?[edit]

There are a few possible causes of this, and the first place to look for help troubleshoot is within the Console view window. It is highly recommended to keep the Console panel open when starting an emulation or uploading to a Patchblock.

If a patch does not compile properly in the emulator the following events will occur:

  1. One or more error messages will post to the Console window.
  2. The emulator will revert to the last successfully compiled patch and play it.

If a patch does not compile properly when uploaded to a Patchblock the following events will occur:

  1. One or more error messages will post to the Console window.
  2. The failed patch is uploaded to the Patchblock and nothing happens when it is turned on.

Furthermore, a patch can work perfectly in the emulator but fail to be copied to the Patchblock hardware because it doesn't fit into the Ram or Flash of the hardware. This is often because there are too many blocks and connections, or because there are too many Ram-hungry blocks such as Delays. One way to tell if this is happening is if the patch works in the emulator, but when the Patchblock is turned on the main green light appears dim. The only solution to a patch that is too large for the Patchblocks Ram is to slim down the patch. Often the simplest solution is to break the patch into multiple patches and load them across more than one Patchblock.

As of Patchblocks version 0.2, the software emulator does not check if a patch is too complex for the hardware.