Re: [Jack-Devel] behavior of jack_port_register on activated client?

PrevNext  Index
DateTue, 15 Feb 2011 10:12:37 -0500
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToEdward Amsden <[hidden] at cs dot rit dot edu>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToEdward Amsden Re: [Jack-Devel] behavior of jack_port_register on activated client? 
On Tue, Feb 15, 2011 at 9:50 AM, Edward Amsden <[hidden]> wrote:

>> you need to call it from another thread, and thats safe then.
> OK. So then if I call it while a client is activated, when do I know
> that I can start getting and reading from/writing to the port buffer
> inside the processing callback?

you won't get the jack_port_t till it returns. you can't use the
jack_port_t except in either

   * process callback
   * port connections

the process callback and port registration are interlocked, so there's
no problem using it there. the port is valid for connections as soon
as you have the handle.

basically: don't think so hard about this :)
PrevNext  Index

1297782797.6067_0.ltw:2,a <AANLkTi=7bwUnk+MyT7htAcq_vSaOVu2UAUbCOptc_U4C at mail dot gmail dot com>