I should say that while aconnect works fine mostly, there are a lot of issues with running it. The main one is that it doesn’t seem to show current connections, just available devices, also, often it will stop working (with no apparent reason) and the device needs to be unplugged and plugged in again. I don’t know if connecting from Pd would solve these issues, but that would be a reason to bother. I however, don’t know either if this is an issue for anybody else… best, J
On Apr 21, 2016, at 11:09 AM, Miller Puckette msp@ucsd.edu wrote:
I don't know of any reason this can't be done. The main alsa api limitation that has stopped me is: Not Worth the Hassle. That, however, is subjective - if you indeed want to attack it I'll be glad to see it (and perhaps even borrow it into vanilla if you're game).
cheers Miller On Thu, Apr 21, 2016 at 02:25:26PM +0000, Jonathan Wilkes via Pd-list wrote:
On Thursday, April 21, 2016 3:39 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2016-04-21 06:38, Jonathan Wilkes via Pd-list wrote:
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
because nobody has implemeted it.
I'm mainly fishing for any potential alsa api limitations that would make doing what I want very difficult or impossible. Like "it garbles the device names", or "crashes every Tuesday", etc. -Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list