Re: [Jack-Devel] zombification behaviour...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Torben, a few questions.

1. Is the uncertainty over knowing which client is the offender a
result of the client's jack code being less than optimal? (no offence
to coders)

2.) Can jack, if advisable, take a bit of extra code to more clearly
define which client is the offender?

3.) Would a more robust client ID system solve the challenge of jack
knowing 100% which client is the offender? i.e. Ardour is 001,
jconvolver is 002, etc...... (I imply with this a central list at
jackaudio. org, where jack capable clients are listed, and any coder
that builds a jack app "officially" registers their app, and gets an
app specific ID.)

These questions are based on jack1, which i use.

Alex.



-- 
www.openoctave.org

midi-subscribe@xxxxxxxxxxxxxx
development-subscribe@xxxxxxxxxxxxxx
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user


[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux