reposting to the list, my email client had some hick-ups..
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
> if you mean at JACK's level, then it prints out information about
> xruns. i think you mean something else, but i'm not sure what.
OK, but jackd is accessing a DMA buffer - where would that be located for USB devices which doesn't do any real DMA? (OK, maybe that's something for ALSA to figure out)
The debugging I was thinking about would be something more fine-grained than just xruns (as I'm not getting any xruns (well, if I choose a period size of 64 I'm getting lots of them).
I'm not really sure what to monitor either, just thinking out loud here - it might be interesting to find out where the actual playback and recording pointers are pointing when accessing the buffer to find out whether something is out of sync (it kind of sounds like that, that the beginning of the buffer gets overwritten with new data, or that the end of the buffer somehow isn't completely written when jackd grabs it). Not sure whether jackd can actually see that though (?). The two parts of the buffer (when using two periods) is laid out consecutively in memory, right? One possible explanation might be that jackd gets called a bit to early/late when the audio device/driver is switching buffers, but that would be kind of hard to actually see for jackd as a client to ALSA?
(I recognize the audio artifacts from the good old days of DOS demo coding of SoundBlaster DMA, at one point where I had screwed up the logic, writing in the "live" buffer, then the beginning of every period was anything but clean...)
This isn't CPU related, there's plenty of CPU time left, and it's occuring all the time, just curious where to start debugging (it seems like it's a jackd problem because aplay works fine, but then again, I guess that aplay doesn't mmap the buffer)..
/WernerJ
Hi LADers!
I released a realtime Music-visualization-program (my master's thesis)
on http://sonasound.sf.net.
It's probably more of academic use at the moment. Licensed under GPL.
Maybe there is some interest.
Features are:
- Waveform-Display
- short-time-spectrum
- sonogram
- spectrum-generation switchable between lpc and fft
- Major kinds of windowing functions choosable
- Different kinds of windowing functions are directly comparable via
live-switching
- Overlap of 50% can be switched on and off without stopping
- Buffer-Size and FFT-Size freely adjustable
- All Displays work from soundfile while playing or direct live-input
from soundcard
- Comparison of different spectrum-generation-methods via multiple
instances fo SonaSound possible
Libraries needed:
- fftw (www.fftw.org)
- glib >= 1.2
- gtk >= 1.2
- gtkglarea
- GL
- GLU
- portaudio (www.portaudio.com) (Yes, I know, switching to JACK might help)
- sndfile >= 1.0
There are many features I would like to add and a few
not-so-good-features I'd like to clean up.
Have fun*
Niklas
Hi.
I relased ZynAddSubFX 1.0.9 (a very poerfull software
synthesizer for Linux).
News:
- added keylimit to Part
- you can use multiple filter stges in order to make
very steep filter rolloffs (eg. 48 dB/octave)
- ADsynth - added noise mode and you can make fixed
frequencies; added the "Punch" parameter
- added an external program "Controller" which enables
you to use the mouse for MIDI controllers
- other improvements and bugfixes
See more at http://zynaddsubfx.sourceforge.net
Paul.
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
Here's another take on that paste-it-together-out-of-C-code "blockless
processing" idea that was discussed a few months back.
Its incomplete and experimental, and I'm not sure how much further its
worth pursuing it (I'll keep it going for a while longer I think) but its
pretty interesting if you like this sort of thing:
http://www.sbibble.pwp.blueyonder.co.uk/amble/amble-0.1.1.tar.gz
Some (not all) of the demos require libsndfile and its headers.
Simon Jenkins
(Bristol, UK)
Hello LADies and LADdies!
What is new on the SuperCollider front?
I've seen there are some new files up on the page and will try to
compile them later today.
Take care,
Miha...
I'm trying to run a low latency kernel and audio applications on a
crusoe processor laptop.
Yes, I'm crazy.
I have patched a 2.4.20 kernel with the low latency, preemption, and
variable hz patches, as well as a modification to the alim15x3 DMA code
and an extra entry in the "unusual USB devices" list. I'm running recent
CVS checkouts of ALSA from Planet CCRMA.
The kernel works well, and the low latency patches really make the
system more responsive even under load. However, when I run
latencytest0.42/do_test blah blah, the system hangs while playing the
sound. It does not even display the xperf window. After a very long
time, Control-C stops the process.
When I run jack -R (jack 0.55) and freqtweak, freqtweak claims it gets
"shut down" by jack the first time I try to start it. The second time I
try to start it, it connects to jack and plays for a few seconds, but
then audio stops and the system hangs. I need to use sysrq or a power
cycle to restart.
I can send pretty good beer, the alim15x3 patch, and any other clues to
anyone who can help me with this.
--
(jfm3 2838 BCBA 93BA 3058 ED95 A42C 37DB 66D1 B43C 9FD0)
I have already got the sound data from sound card into
the buffer, and I've also finished it to encode the
data to gsm and send to another server. Right now I
need to store the sound data to some .wav file in the
server. How can I do it, ether from memory buffer or
gsm? Are there any API to do it?
Thanks.
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
After trying to track down the cause of xruns, I was just wondering if there
is a way to run... I dunno, kinda like a meta test for jack and see just why
you are xrun'ing?
I know people have probably asked this umpteen times, but I was wondering if
there was a way to say, automate various tests and keep a load on jack and
watch to see if it xruns during any of the tests...
Then, after it's done, it gives you a report of what you need to do to tweek
your system.
Just thinking outloud.
Jonathan
Hi all,
Some fixes and extra bits for the midi stuff; makes things much more
responsive.
* icon and .desktop get installed properly
* much more graceful handling of jackd shutdowns
* midi thread will now try and use SCHED_FIFO. If you run jackd with
jackstart (or as root, but you don't want to do that :) then you
don't need to do anything to enable this as jackd will give the
appropriate rights to jack rack.
Bob
--
Bob Ham <rah(a)bash.sh>