khz wrote:I haven't found any MIDI inputs/outputs function in Bitwig nor do I see any Bitwig MIDI I/O in qjackctl (a2jmidid - neither in jack nor alsa). At the first start I thought I saw a MIDI I/O from Bitwig in qjackctl. Without the Bitwig MIDI entries in qjackctl I wouldn't know how to route MIDI to external software or hardware programs/devices.
On Xubuntu and Linux Mint, Bitwig integrates right away from boot of the machine and it's rather Ardour/Mixbus that needs some special care.
And still about Xubuntu and LM, for Mixbus the following has to be run in order to use a MIDI controller:
a2j_control ehw start
And when that has been run, going back to Bitwig means doing:
And in terms of practical regular use, one approach is:
alias A2J='a2j_control ehw start'
alias KA2J='killall /usr/bin/a2jmidid'
This is from a regular install of both of these distro, without having modified anything to the audio subsystem. If the audio is modified at installation then behaviour can be different.
In my case, since I create using Bitwig I prefer to have Bitwig flying off right away from the start and I don't mind having to execute an alias or two for Mixbus32C since mixing happens much less frequently than creation. And this is Bitwig 2.4.3 although I doubt very much that this has changed in 3.0.
You do not have the required permissions to view the files attached to this post.