Minor bug fixes since last release.
Notable changes:
* Attempt to let client timeout option work again on realtime mode
* Let jackd quit gracefully when USB soundcard or power cable is
unplugged
* Better support for US428 USB soundcard
* SSE/E3DNow mixing support. Disabled by default. Enable with --
enable-dynsimd
JACK is available at http://jackit.sf.net and our new website http://
jackaudio.org.
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
---
hi everyone!
lately there are a number of gmail users filling up the moderation
queues with "message has a suspicious header" bounces.
this is almost always due to people trying to send non-text/plain
content, which for a number of very good reasons is banned on linux-audio-*.
it seems that gmail has an unfortunate default setting that some people
are not aware of... gmail users, please fix your settings!
best,
jörn
Hi Lee
> I just noticed that the sys_get_priority_max and _min syscalls do not
> take the RT priority rlimit into account. Since the watchdog thread
> runs at the -P setting + 10 then if the rlimit is 50 and the user
> specifies -P50 the watchdog thread will fail.
>
> I believe sched_get_priority_max(SCHED_FIFO) needs to take the rlimit
> into account - there's no other way to get the upper limit AFAICT.
I'm not sure what the "set_rtlimit problem" is here - I'm a little confused.
In terms of what set_rtlimits does, it seems to me that the watchdog thread
issue can be easily dealt with: define the max rtpriority value in
/etc/set_rtlimits to be X, knowing that the maximum jackd "-P" option value
one can use is X-10.
Certainly getrlimit()/setrlimit() (which set_rtlimit uses to do its thing)
seem to take the current rtpriority rlimit into account. The former
also returns the rlimit hard limit for the process, which I interpret
to be the "upper limit" mentioned in the original email.
In testing I've done during development, set_rtlimits seems to do the right
thing, based on my understanding of what the right thing is. If I've
misunderstood something though I'm happy to be corrected.
Regards
jonathan
Hi,
Just to let you know about this small-fix release on QjackCtl, that only
affects the MIDI connections (re)nomenclature:
- ALSA sequencer client/port name aliases are functional again; all
actual MIDI sequencer client/port numerical identifier prefixes are also
back in business.
Apparentely, this has been missed for quite a while, almost since
0.2.16. Only noticed this late week, thanks to Domenico Culturato.
You can pick it out from the usual place:
http://qjackctl.sourceforge.net
Enjoy,
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Regret to report I am having problems loading firmware for my multiface
again. This time I have the pci card in a 32-bit system running FC4 with
a recent 2.6.12 kernel and alsa from 1.0.10rc1, including
alsa-tools-1.0.10rc1. The error is:
Hammerfall-DSP: wait for FIFO status <= 0 failed after 30 iterations
Hwdep ioctl error on card hw:1 : Input/output error.
--
Janina Sajka Phone: +1.202.494.7040
Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
Chair, Accessibility Workgroup Free Standards Group (FSG)
janina(a)freestandards.org http://a11y.org
If Linux can't solve your computing problem, you need a different problem.
Hey,
I just noticed that the sys_get_priority_max and _min syscalls do not
take the RT priority rlimit into account. Since the watchdog thread
runs at the -P setting + 10 then if the rlimit is 50 and the user
specifies -P50 the watchdog thread will fail.
I believe sched_get_priority_max(SCHED_FIFO) needs to take the rlimit
into account - there's no other way to get the upper limit AFAICT.
Lee