asked Mar 13 '19 at 01:13 by xiso (76)

edited Mar 17 '19 at 14:47

Bitwig's touch-enabled virtual keyboard is a really great tool, but there's still room for improvement.

  1. First of all, it should detect Transposition modules or Note filter modules and show keys layout according to final output skipping unused notes (or simply ones that will be blocked and won't come through). This is needed for simplification and ease of performance and also for avoiding pitch-sliding to notes that are supposed to be blocked. This should be top priority for touch keyboard improvement.

  2. Going further with idea of touch keyboard adapting to Note FX modules used in track to match expectations from it with actual result. Would be nice to have some visualisation of what Arpeggiator doing, like phantom touch points, but with blue color. Currently only played clips represent what keys are hit on the virtual keyboard, should work with overall output from the track and apply overall principle of blue/green phantom touches whenever something beyond actual touch is happening (just like modulations are represented with blue or green depending on poly or mono modulations).

  3. More options like how many rows and columns of keys keyboard should fit, it should be scalable. Also optional vertical touchpad on the side for holding initial velocity value for incoming notes, since it's impossible to do otherwise with matrix-style keyboard. And maybe additional touchpad for global pitchbend?

Hi @xiso,

This is a user's forum, feature requests should be submitted directly to tech support here:


answered Mar 13 '19 at 10:08 by sticklebrick (480)

Thanks, didn't realize that.

  — (Mar 13 '19 at 10:46) xiso

No problem, you're not the first, won't be the last :) Alternatively there's a Bitwig forum set up by the developers on KVR, I think you can submit feature requests there and also have more open discussions rather than the Q&A format here.

  — (Mar 13 '19 at 10:49) sticklebrick

No one knows this because Bitwig has not created a sticky for it.
Please create a sticky and people will start sending feature requests to the tech-support team instead of posting here.


answered Mar 17 '19 at 13:09 by Jeremysfx (132)

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: Mar 13 '19 at 01:13

Seen: 400 times

Last updated: Mar 17 '19 at 14:47