pax-eterna wrote: ↑Wed Sep 15, 2021 6:53 pm
Drumfix wrote: ↑Wed Sep 15, 2021 6:37 pm
EOS is based on Ubuntu which is based on Debian. Why do you refuse to follow the advice given to you ?
I did follow the advice and I did report back!
The link for Ubuntu you gave was for a version four release old, but I DID try it anyway!
I also reported back that ldd bluetoothd did not run at all.
I reported back that I removed the existing version of Bluez and re-installed it as best I could following the instructions.
I found that a command --enable midi was apparently needed, but found no actual instruction on how to run it.
I tried running this sudo modprobe snd_virmidi - it just created 64 virtual midi slots in the DAW, none of which worked.
Tried this
https://tttapa.github.io/Pages/Ubuntu/S ... BlueZ.html ( which I think is the same as you provided earlier in the thread???) It didn't work.
I think I've boiled it down to the problem of actually turning it ON in bluez and it is this, I think, where it is at. Bluetooth and Bluez are all working fine as I have said time and again, it is the MIDI component that is not turned on, and I have found no instruction other than some cryptic --enable midi command!
[edit: missed all the replies on page 2 of this topic. Oops!
]
I had a look at the
link @Drumfix pointed to in the
topic we're talking about. I have Ubuntu 20.04 and I was able to successfully compile it from source code. I did not install this newly built version of bluez yet because I still have the old version on my PC and the instructions in the link on removing and reinstalling bluez are a bit confusing to me (long story). And I do not have a Midi BT dongle to test it all with.
So, I'm afraid its a semantic case.
You keep on talking about "the problem of actually turning it on in bluez". I do not know what you mean exactly by this and I think we all have different ideas about what we mean in this case. We Linuxers do not talk about "turning Midi on in Blues". We talk about a bluez version that supports Midi because it is built in or we don't have Midi over Bluetooth at all. Remember: for some reason no Linux distribution comes with a version of bluez (yet) that has Midi support built in.
If we have a bluez version with Midi support
then we can pair and connect bluetooth devices by running the following command, which is part of bluez:
A prompt now opens. Then one issues the command "scan on" to scan for new bluetooth devices like the WIDI-Master midi-to-bluetooth dongle/device (dunno how to call it exactly). This dongle needs to be in pairing mode (read manual of the WIDI-Master). Then it will show up with a MAC address in the form of "11:22:33:AA:BB:CC". Then type the command "pair 11:22:33:AA:BB:CC", then "trust 11:22:33:AA:BB:CC" and finally "connect 11:22:33:AA:BB:CC". At least, that's how I do it. In some form or another that's what you need to do in Windows and Mac too (
scan, pair, trust & connect).
Then and
only then you can look in the 'Connections' window from
qjackctl (Jack) to see if it worked and if the WIDI-Master is in the tab "Alsa" (which is Jack speak for "Alsa Midi"). If I recall correctly you posted a screenshot of said window and the WIDI-Master was not there. Hence, it is
not (properly) connected, activated, installed or whatever we want to call it. The proper way to say it is that your WIDI-Master device is
not paired via bluetooth. That means that the
bluetoothctl procedure failed or that you din't execute it right. You keep on saying the the WIDI Master device is connected via bluez but I have strong doubts about that.
Additionally the
bluetoothctl procedure might go wrong because you have a version of bluez that has no Midi-over-bluetooth support. You have to compile (and properly install) blues from source code for that. I tried to explain to you what source code and compiling is. I don't think you fully grasp that (yet). I highly doubt the compile and install procedure went well.
To make a long story short: I'm afraid you don't have enough experience with Linux yet to fully grasp what needs to be done in the abstract sense. Am I right?
pax-eterna wrote: ↑Wed Sep 15, 2021 7:33 pm
[...]trouble is I am sure this last issue with the bt midi, is a simple one, but it is eluding me! But it is important enough to have me considering just dealing with MS bs!
I'm afraid it is not. Compiling stuff from source code is never simple. Nobody does that fot starters if one tries to learn a new operating system, be it Windows, Android, MacOS or Linux. You have the misfortune that you need to to this for starters and cannot get familiar with your new OS in a user friendly way.
Anyway, I like you (don't even know you) and wish you al the best. There's no shame in using Windows. I'd like to thank you for the tip on the WIDI Master device: I didn't even know such a thing existed. And thanks for the topic you opened on it: it learned me, via
@Drumfix's link how to compile a version of bluez that does support it. I might buy the the WIDI Master myself.
All the best and good luck!