Sorry guys, other two (silly?) questions:
1. apart from the process callback, which callbacks need to be
RT-safe? Looking around I found a master thesis [1] that says: Apart
from
the JackProcessCallback callback, which is called in the realtime
audio thread for obvious reasons, all other
On Fri, Feb 21, 2014 at 9:38 AM, Stefano D'Angelo zanga.m...@gmail.comwrote:
Sorry guys, other two (silly?) questions:
1. apart from the process callback, which callbacks need to be
RT-safe? Looking around I found a master thesis [1] that says: Apart
from
the JackProcessCallback callback,
2014-02-21 16:51 GMT+02:00 Paul Davis p...@linuxaudiosystems.com:
On Fri, Feb 21, 2014 at 9:38 AM, Stefano D'Angelo zanga.m...@gmail.com
wrote:
Sorry guys, other two (silly?) questions:
1. apart from the process callback, which callbacks need to be
RT-safe? Looking around I found a
On Fri, Feb 21, 2014 at 10:04 AM, Stefano D'Angelo zanga.m...@gmail.comwrote:
Well, here
http://jackaudio.org/files/docs/html/group__ClientCallbacks.html
I only see that process has to be RT-safe and thread-init needs not,
but regarding others I have no clue. Is that stated somewhere else
2014-02-21 17:21 GMT+02:00 Paul Davis p...@linuxaudiosystems.com:
On Fri, Feb 21, 2014 at 10:04 AM, Stefano D'Angelo zanga.m...@gmail.com
wrote:
Well, here
http://jackaudio.org/files/docs/html/group__ClientCallbacks.html
I only see that process has to be RT-safe and thread-init needs
it was part of the API very early on, then we decided we didn't want to
impose the possibility of change on clients. as time goes on, it becomes
clear (to me at least) that we should have implemented it.
What would be use cases for changing the sample rate dynamically?
lieven
On 02/21/2014 07:52 PM, Lieven Moors wrote:
it was part of the API very early on, then we decided we didn't want to
impose the possibility of change on clients. as time goes on, it becomes
clear (to me at least) that we should have implemented it.
What would be use cases for changing the
On Fri, Feb 21, 2014 at 08:34:16PM +0100, Jörn Nettingsmeier wrote:
having wired up a complex signal graph, which for the most part
depends on the studio, not on the project at hand, and then having
to deal with different projects in different sample rates.
...
as it is now, i have
On Fri, Feb 21, 2014 at 08:34:16PM +0100, Jörn Nettingsmeier wrote:
On 02/21/2014 07:52 PM, Lieven Moors wrote:
it was part of the API very early on, then we decided we didn't want to
impose the possibility of change on clients. as time goes on, it becomes
clear (to me at least) that we should
On 02/20/2014 11:32 PM, Stefano D'Angelo wrote:
Hi Stefano,
You got this right.
Hi all,
Let's say I have a client that introduces an amount of latency that's
variable at runtime and potentially unbounded. From JACK's docs it
seems that you need to recompute the min/max latencies in the
2014-02-21 0:45 GMT+02:00 Paul Davis p...@linuxaudiosystems.com:
On Thu, Feb 20, 2014 at 5:32 PM, Stefano D'Angelo zanga.m...@gmail.com
wrote:
Hi all,
Let's say I have a client that introduces an amount of latency that's
variable at runtime and potentially unbounded. From JACK's docs it
On Thu, Feb 20, 2014 at 6:05 PM, Stefano D'Angelo zanga.m...@gmail.comwrote:
reset your port latencies.
Ok, thanks (to Robin too). Can jack_recompute_total_latenices() be
called from within the process callback too?
you cannot contact the server from with the process callback, so no.
and
2014-02-21 1:08 GMT+02:00 Paul Davis p...@linuxaudiosystems.com:
On Thu, Feb 20, 2014 at 6:05 PM, Stefano D'Angelo zanga.m...@gmail.com
wrote:
reset your port latencies.
Ok, thanks (to Robin too). Can jack_recompute_total_latenices() be
called from within the process callback too?
13 matches
Mail list logo
