Hi,
I have two questions concerning the jack callback,
1. what is the preferred way of feeding data from disk to the callback?
Is there a general design pattern agreed upon? Best Practices?
2. What is the preferred way to notify the non-realtime thread that
something happened in the jack-callback?
A condition variable? How to avoid blocking? How do you do it?
I read the tutorial at http://userpages.umbc.edu/~berman3/ , it uses
mutex+condition, is it okay to do this? Are there better ways?
thx
-Richard
Hi all,
some weeks ago I sent some mails ranting about problems getting my
tascam us-122 to run on a turion64 running gentoo.
As time has gone and new kernels arrived I have reached a state where
I can play (synths, effects, ardour, etc) and "record" ie. sent the
incoming audio to effects and back out.
But: If I want to record to disk I get the same old error (should not
be here with counts=0) again and sound stops completely. The computer
freezes if I try to restart jackd...
Some tests showed that this doesn't happen if I record into ram (using
/dev/shm to save the recordings).
I modified the driver to give some more debug and to not stop at the
first error (see the attached usbusx2yaudio.c for details) but still
after some more function-calls the driver stops working. Sadly there
isn't much documentation in the source so I am a bit lost there.
Can someone give my some hints?
Thanks in advance,
Arnold
--
visit http://dillenburg.dyndns.org/~arnold/
---
Wenn man mit Raubkopien Bands wie Brosis oder Britney Spears wirklich
verhindern könnte, würde ich mir noch heute einen Stapel Brenner und
einen Sack Rohlinge kaufen.
On Dec 1, 2005, at 9:05 AM, linux-audio-dev-
request(a)music.columbia.edu wrote:
>
> it seems that gmail has an unfortunate default setting that some
> people
> are not aware of... gmail users, please fix your settings!
To be specific, in Settings, choose the "use UTF-8" option for
"Outgoing message encoding" on the General page.
---
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
lazzaro [at] cs [dot] berkeley [dot] edu
---