This returns a pointer to the memory area associated with the
specified port. For an output port, it will be a memory area
that can be written to; for an input port, it will be an area
containing the data from the port's connection(s), or
zero-filled. if there are multiple inbound connections, the data
will be mixed appropriately.
FOR OUTPUT PORTS ONLY : DEPRECATED in Jack 2.0 !!
your "blocksize" callback. For this reason alone, you should
either never cache the return value or ensure you have
a "blocksize" callback and be sure to invalidate the cached
address from there.
Caching output ports is DEPRECATED in Jack 2.0, due to some new optimization (like "pipelining").
Port buffers have to be retrieved in each callback for proper functionning.
This returns a pointer to the memory area associated with the specified port. For an output port, it will be a memory area that can be written to; for an input port, it will be an area containing the data from the port's connection(s), or zero-filled. if there are multiple inbound connections, the data will be mixed appropriately.
FOR OUTPUT PORTS ONLY : DEPRECATED in Jack 2.0 !!
your "blocksize" callback. For this reason alone, you should either never cache the return value or ensure you have a "blocksize" callback and be sure to invalidate the cached address from there.
Caching output ports is DEPRECATED in Jack 2.0, due to some new optimization (like "pipelining"). Port buffers have to be retrieved in each callback for proper functionning.