Latest News: Bitwig Updates Bitwig Studio to 5.2
Nektar Impact 25LX+ Not Working Bitwig 2.1 Linux
-
- KVRist
- Topic Starter
- 57 posts since 2 Mar, 2015
My Nektar Impact 25LX+ is auto detected by Bitwig 2.1 on Linux Lite 3.4, but it doesn't work. The Impact 25LX+ does work on the same PC when it boots into Windows 10 and Bitwig 2.1. I am new to Linux so perhaps I have to setup something with JACK for midi. Also the Impact 25LX+ worked great on Linux when I was using Bitwig 1.3.16.
-
ElectronicBattle ElectronicBattle https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=398673 - KVRer
- 25 posts since 19 May, 2017
I'm having loosely similar problems getting MIDI data into BWS 2.1 from my USB audio interface (Alesis io2) which has in and out MIDI DIN sockets. I too am no linux expert.
I *know* the data is reaching my linux OS because I have used a couple of tools to see the data - maybe you could do the same?
Midisnoop is one tool which might be easy for you to install, the other is Gmidimonitor:
https://github.com/surfacepatterns/midisnoop
http://home.gna.org/gmidimonitor/
If I get anywhere (I have a support ticket raised - I have been working at this problem for a week now) I will report here.
I *know* the data is reaching my linux OS because I have used a couple of tools to see the data - maybe you could do the same?
Midisnoop is one tool which might be easy for you to install, the other is Gmidimonitor:
https://github.com/surfacepatterns/midisnoop
http://home.gna.org/gmidimonitor/
If I get anywhere (I have a support ticket raised - I have been working at this problem for a week now) I will report here.
-
ElectronicBattle ElectronicBattle https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=398673
- KVRer
- 25 posts since 19 May, 2017
Another couple of bits of info for you: this guide
http://tedfelix.com/linux/linux-midi.html
seems particularly useful (and off topic, he's got some pretty good linux info too, for example http://tedfelix.com/linux/debian-command-reference.txt)
Terminology as far as I have ascertained so far, which I hope is helpful to you:
# Alsa = audio "driver" analogous to the sort of driver you'd get in e.g. Windows, alsa also handles MIDI interfacing
# jack = jackd = jackdmp = jack2 = a comms layer or software service or "daemon" which serves audio data to different interfaces/programs in a timely fashion ... low & constant latency and enables timing of audio track starts and events and MIDI data to all be synchronously tied together.
#a2jmidid = alsa to jack midi daemon which takes MIDI data from alsa and distributes it via jack
http://tedfelix.com/linux/linux-midi.html
seems particularly useful (and off topic, he's got some pretty good linux info too, for example http://tedfelix.com/linux/debian-command-reference.txt)
Terminology as far as I have ascertained so far, which I hope is helpful to you:
# Alsa = audio "driver" analogous to the sort of driver you'd get in e.g. Windows, alsa also handles MIDI interfacing
# jack = jackd = jackdmp = jack2 = a comms layer or software service or "daemon" which serves audio data to different interfaces/programs in a timely fashion ... low & constant latency and enables timing of audio track starts and events and MIDI data to all be synchronously tied together.
#a2jmidid = alsa to jack midi daemon which takes MIDI data from alsa and distributes it via jack
-
ElectronicBattle ElectronicBattle https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=398673
- KVRer
- 25 posts since 19 May, 2017
BWS 2.1.1 was released yesterday. My problems are better than they were - perhaps you would also benefit from an upgrade?
This sort of approach *might* shed some extra light on things:
1 - Try booting your box *without* the 25LX+ connected.
2 - Start BWS and autodectect (obviously it will fail because the Nektar isn't connected!)
3 - connect the Nektar and see if BWS autodetects and then see if it actually works!
4 - If not, repeat step1 and, once logged in, connect the Nektar and THEN start BWS. See if there are differences between these two test approaches.
In my case, having my audio interface not connected when I boot seems to alter how BWS sees it.
This sort of approach *might* shed some extra light on things:
1 - Try booting your box *without* the 25LX+ connected.
2 - Start BWS and autodectect (obviously it will fail because the Nektar isn't connected!)
3 - connect the Nektar and see if BWS autodetects and then see if it actually works!
4 - If not, repeat step1 and, once logged in, connect the Nektar and THEN start BWS. See if there are differences between these two test approaches.
In my case, having my audio interface not connected when I boot seems to alter how BWS sees it.
