On 2018-06-15 08:31:41 (-0700), Jimi Bove wrote: > Yeah, what Albert said. a2jmidid is actually still pretty vital as most > MIDI programs still *only* support either ALSA MIDI or Jack MIDI, and I use > some of both. But if all I'd have to do was install it from the AUR instead > of the repo (rather than deal with some sort of dependency nightmare), > that's fine. Please don't get me wrong here: I'm using a2jmidid myself from time to time. I wrote "in the not too distant future". I mainly have falktx' statement regarding jack1/jack2 feature parity in mind here [1]. Those are my hopes for the future of jack! Given Filipe's new employer, I'm not so sure he will have a lot of time to invest in jack2 any time soon though. So, if you're able to help, get in touch with him! Lash, the same as a2jmidid was developed by Nedko Arnaudov, who didn't respond to my requests at all and seemingly abandoned development. The a2jmidid upstream is basically just around, because someone most likely forgot to delete it (or the server just luckily has never been shut down). It's a very unfortunate situation for a piece of software, that everyone needs, when using jack2 and MIDI! I'm just as unhappy about this as anyone else I guess. Probably thirdparty tools such as this should be picked up by the jackaudio association on github, so they'll at least be around for a little longer. > When you say those other packages have been rebuilt without lash support, > do you mean that by the time lash is gone, versions of them that don't > depend on lash will have left testing and will be ready for me to update > to? If so, great! hydrogen, zynaddsubfx and fluidsynth were the only packages in Arch still "using" lash. I rebuilt them without their lash feature. Those are the current versions in [community]. Lash is in the AUR now and needs fixing to even be able be build. [1] http://kxstudio.linuxaudio.org/News/?action=view&url=jack2-1912-release-and-future-plans -- https://sleepmap.de
Attachment:
signature.asc
Description: PGP signature
