I will also look into this. It does seem that the source/sink name
seems good enough. Does anyone know for sure?
On 15 June 2010 04:19:28 UTC+10, Tanu Kaskinen wrote:
> the alsa devices seem to use udev variables that contain the
> serial number, if a serial number is available. bluetooth-discov
Thanks for the responses. I will take a look at PA_PROP_DEVICE_SERIAL.
I am implementing a Linux port for an existing API. The API has
existing expected behaviour that comes from these other platforms and
is expected to behave similar on Linux also, thus the need to
implement it like this. As a re
On Thu, 2010-06-10 at 11:47 +0200, Lennart Poettering wrote:
> On Thu, 10.06.10 15:06, Brendon Costa (brendon.j.co...@gmail.com) wrote:
>
> heya,
>
> > I am integrating Pulse Audio into a cross platform VoIP API at work.
> > We currently allow a user of our API to use a "GUID" that is simply a
>
On Thu, 10.06.10 15:06, Brendon Costa (brendon.j.co...@gmail.com) wrote:
heya,
> I am integrating Pulse Audio into a cross platform VoIP API at work.
> We currently allow a user of our API to use a "GUID" that is simply a
> unique identifier for a audio device to identify a device. Thus they
> ca
'Twas brillig, and Brendon Costa at 10/06/10 06:06 did gyre and gimble:
> Hi all,
>
> I am integrating Pulse Audio into a cross platform VoIP API at work.
> We currently allow a user of our API to use a "GUID" that is simply a
> unique identifier for a audio device to identify a device. Thus they
