asked Jan 18 '19 at 07:48 by manueldelatorre (11)

Using previous versions of Bitwig, I've prepared more than 40 backing track projects that, in addition to typical audio clips, also control 2 external vocal processing units via MIDI automation lanes on channels 13 and 14 respectively.

In older versions of Bitwig (e.g., 2.3.5), there was no option to assign a MIDI channel to an automation lane; it would simply follow the channel assigned to the HW Instrument. In newer versions of Bitwig (currently using 2.4.3), this option has been added.

The issue I'm running into is: when I open a project created in a previous version of Bitwig, the new 2.4.3 assigns MIDI channel #1 to the existing MIDI automation lanes, instead of the MIDI channel set in the HW Instrument, therefore not sending the control changes to the vocal processing units. I really hope there is a way to fix this that does not involve manually modifying every single MIDI automation lane of every single project. Any help will be greatly appreciated.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Jan 18 '19 at 07:48

Seen: 383 times

Last updated: Jan 18 '19 at 07:48