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@email-addr-hidden development-subscribe@email-addr-hidden _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Fri Nov 19 00:15:02 2010
This archive was generated by hypermail 2.1.8 : Fri Nov 19 2010 - 00:15:02 EET