Re: [Jack-Devel] port callbacks, jack_port_id_t

PrevNext  Index
DateFri, 29 Apr 2011 21:32:01 +0300
From Dan Muresan <[hidden] at gmail dot com>
ToDan Muresan <[hidden] at gmail dot com>, [hidden] at jackaudio dot org
In-Reply-Totorbenh Re: [Jack-Devel] port callbacks, jack_port_id_t
Follow-Uphermann Re: [Jack-Devel] port callbacks, jack_port_id_t
> jack_port_get_buffer() is valid, even when the port is not connected.
> however, it might not be valid, when the client is not active yet.

Hm... I only use port_get_buffer() from the process routine.

From my experiments and looking at the source, even in the async
model, the user-specified process_thread is only called once
activation is finished (perhaps this should be documented BTW).

So what you describe should not be possible. Yet I did have some
segfaults right in port_get_buffer(), which went away when I
synchronized on port connection. I can't reproduce them anymore. I
will try some more experiments...

-- Dan
PrevNext  Index

1304101946.8312_0.ltw:2,a <BANLkTi=jGXmWF7ARQtXVRVYB5=khxg=sRw at mail dot gmail dot com>