Looking at the acconnect code as well as the Pd diff that got rid of the autoconnect code, it looks like it's 

pretty easy to list i/o port info.

> I however, don’t know either if this is an issue for anybody else…

It'd be helpful to know whether it's a general issue or not. 

If it is a general issue then Pd will almost

certainly inherit those problems if I add the functionality I want.  aconnect is about as simple a wrapper

around alsa's API as you can get.

(> and !>) 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