| BrianHechinger[m | Does anyone else have issues with the KDE error popup thing complaining about things that never actually crashed? | 11:47 |
|---|---|---|
| bhechinger | Hmm, seems the matrix bridge is broken (only one way) | 11:48 |
| bhechinger | Also my quest for Audacious MIDI control has ended up not finding anything. :( | 11:51 |
| OvenWerks | bhechinger: I have the crash popup sometimes when closing applications. I would guess they do not close in a way that is expected. Either they pass a non-zero exit code or they don't call the correct exit method for the language they are using. I have an appimage that does that for example. | 14:45 |
| bhechinger | Weird that mine happen without the app even closing | 14:47 |
| OvenWerks | the crash popup when clicked, should bring up a dialog with an information drop down or a send bug report button on it. That should at least tell you which application/utility plasma thinks did something wierd | 14:50 |
| OvenWerks | Audacious does not have built in MIDI control of the transport, though it does have a plugin that will take MIDI in and play it through a synth. A MIDI to text converter piped into Audacious' stdin might work though. | 14:54 |
| OvenWerks | The midi to text converter would have to be set up to give text that matches Audacious' hot keys for transport control. The problem with this method would if course be that Audacious would no long see key presses maybe. It depends on how Audacious gets it's key inputs, the lib it uses may, rather than use stdin, take them direct from X/wayland | 14:59 |
| OvenWerks | It is possible to run a utility (as root) that injects midi as keyboard codes into the system as if it was a second keyboard as well. | 15:07 |
| OvenWerks | The problem with this is focus. whatever application has keyboard focus is the one that will get the MIDI events turned keypress. :P | 15:09 |
| OvenWerks | Anyway, if you want to experiment and know c a bit, midikb might be a good place to start. All the right bits are there except a MIDI event type. | 15:11 |
| OvenWerks | I do not know if there is a way to take an input device in Xorg or wayland and force it to remain attached to only one application, focused or not. I expect there is but I am not aware of it. | 15:13 |
| OvenWerks | bhechinger: There is a tool called audtool that takes text commands as commandline parameters and sends them to Audacious. That could be used as a backend to a midi to text setup | 15:27 |
| bhechinger | Ok, I'll give that all a look. I don't want to do the map to kb thing because I already don't like the focus issue. Aud runs on another virt desktop so it's rarely actually in focus. So I want something that's tied to it. | 15:31 |
| OvenWerks | Something like midi2osc might be easy to hack to provide the input audtool | 15:32 |
| bhechinger | I'll definitely give that all a look, thanks!@ | 16:18 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!