Console 1 Known Issues/Work In Progress

For the latest release of Console 1 we have the following known issues or work in progress.

General:

  • Some users have experienced problems when connecting Console 1 to a USB hub. The solution in most cases is to connect Console 1 directly to a USB port on the computer.
  • Solo doesn't work when running a 32-bit plug-in using a wrapper in a 64-bit host. It also doesn't work if you use both VST2 and VST3 plug-ins in the same sessions.
  • Switching strips in Console 1 on multiple channels can in some cases take a long time.

UAD:

  • UAD Precision Limiter does not correctly report errors back to the On-Screen Display in 176 and 192 kHz sample rates.

Ableton Live:

  • When the AU version of Console 1 is used in Ableton Live and the buffer size is changed, track names are reset in the Console 1 On-Screen Display. Workaround: use Console 1 in the VST2 format, or don't change buffer size.

Logic Pro:

  • For now, always connect Console 1 hardware before starting Logic, to avoid MIDI related issues. We're working with Apple to fix the issues.
  • Some Logic users have experienced that following the Bounce of a song, adjustments made to Console 1 do not take effect until another track is selected using the track selectors.
  • Users are reporting that track numbers get messed up when making several takes on a track in Logic. The reason is that Logic wants to give each new take a new track number, even if it's not possible to insert Console 1 or any other plug-in on one of those tracks. Workaround: If the 'takes stack' is folded in, the numbering will be correct. If the takes stack is folded out, each take will get their own track number.

Nuendo 6.5:

  • Automation should be switched to Auto-Latch mode to work correctly with Console 1.

Sonar:

  • Using several Pro Channel plug-ins and Console 1 in a session can cause Sonar to hang.

Studio One:

  • Track conflicts, causing flickering LEDs on th Console 1, occur within Console 1 when using Native Low Latency Monitoring. Workaround for now: do not use low-latency monitoring.

REAPER:

  • When using the Console 1 pan pot, parameter data in Reaper suggests that panning left can continue past the 100% mark to infinity.
  • The Console 1 plug-in user interface (not to be confused with the On-Screen Display) needs to be open for automation data to be written.