i too had my own 2.6.26-rt1 hard lock; for me 2.6.25.4-rt5 is most solid.
would recomend to others. rt-6, and .8-rt7 hard lock for me also. the radix
tree entry in general has to be off otherwise i get lockups btw, and group
scheduling off entirely.
hth
best,
g.
Hi there!,
I want to optimize JACK capabilities in running Linux PCs.
What JACK configuration parameters do I have to vary (and in what way) to
achieve that?
(by "that" I mean: minimum latency, zero noise and zero xruns).
I'm looking for something like a "standard procedure"...
...not just trying all the possible configurations of JACK and picking up
the most convenient.
(... maybe an "autoJACKtuning" program can be done for this purpose, but
there MUST be a procedure to follow)
Maybe you just can't tune the best of every system by following the same
pattern, but making the average best is what i'm looking for.
I'm working in a program that's a metronome that reacts to human
synchronization errors (to the very same metronome).
That errors are just some milliseconds, and a further advance in the program
would need reacting as quickly as that - Fast!.
In some ways, the program is similar to a tap-tempo thing, but it's meant
for synchronization experiments.
That experiments are aimed at researching how do people sync themselves to
outer stimuli, like... the beat of a song.
Results of that can end up in cool stuff - e.g., the possibility of making
the sync of drum-machines REALLY human-like.
Well...
This program should be as "portable" as it can be.... but I'm having trouble
with some audio cards.
I don't think powerful sound cards are needed for this task... the
bottleneck seems much more of a OS scheduling thing.
I turned to JACK because of the promised low latencies and throughput (and
an easy API)...
... but sometimes the audio crackles, has xruns, can't get it to work even
with high latency, etc... and I don't have a clue about what to vary to fix
that.
Besides that, I'm kind of a musician too and it seems everybody who uses
JACK wants low low low latency and good sound, so a "guide" to tune up that
would be a step forward to the self promotion of JACK-based software.
Sorry for my Neanderthal-ish English
and cheers from Argentina,
Trece.
> > I got rid of rtirq and das-watchdog entirely. after that, the machine
> didn't
> > lock up for at least as long as Robins session, ~45 mins, but the in the
> > middle of some session I would have liked to keep the recording of,
> dang..
>
> sorry, but without rtirq the whole thing is useless.
>
really? how so? I mean I can understand what it doesn, but I personally
havn't seen it doing anything significant for i/o performance. that said, I
don't really do latencies lower than 128 samples... let me know your
view/experiences/hints.
thanks
karsten
Hello.
My name is Gilberto Andre Borges and I am from Brazil. I am happy to subscribe this list and I stay here because I am Musix Project's co-ordinator. I am postgraduate in Music, in the area of concentration Music Education, for the University of the Santa Catarina State.
At present, I work with teachers' formation in the Public Net of Schools of the city of Florianópolis, in the Santa Catarina State, Brazil. I am an investigator in the area of Music, where I am developing one dissertation about Music Education and Free Software.
In Brazil, the adoption of free software in the public schools is stimulated by the federal government and, recently, a federal legislation made the teaching of music compulsory in the basic education (first nine years of school education).
I believe that adding efforts up the whole community of musicians who use free software will leave winning. Forgive for me some mistake of orthography or grammar, since I have practice little with the English language, but I speak very quite Portuguese and Spanish, so that I can help with these languages.
MUSICALLY.
Gilberto André Borges
http://musix.codigolivre.org.brhttp://www.musicaeeducacao.mus.brhttp://palcomp3.cifraclub.terra.com.br/gilblack/
Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com.
http://br.new.mail.yahoo.com/addresses
Hi LAT!
Thanks for setting this list :)
Quick intro for those who do not know about pure:dyne.
pure:dyne is a live distribution for artists and musicians. With artists
and musicians we mean persons working in the field of
media-art/software-art/net-art/... using GNU/Linux as a platform to
create installations, make performances, give workshops, teach GNU/Linux
in art schools, and also use pure:dyne as an OS for small media/artlab.
The project has been initially started by GOTO10, a distributed
collective of artists, and it is now growing to a group of 8 persons.
We provide "studio" applications from Gimp to Ardour, but our focus and
packaging is around software such as Pure Data, Supercollider, Csound,
fluxus, Processing, Arduino and more exotic things :)
We recently switched to Debian as our core system to build the liveCD, and
we aim to stick to it as much as possible, which means that we intend to
move our packages from our repos to Debian eventually, this will be done
with help of Free and I believe part of the Debian Multimedia group effort.
Right now, we use a mix of 3 repos for our system, lenny, multimedia
(debian-multimedia.org repos) and ours. So far so good :)
We have been contacted by Daniel after we announced the project was
switching to Debian and started to talk with Free to see what kind of
technical overlap the 2 projects had so we could try to limit dupe works
in the long-term. Part of this discussion we met Daniel during one of
our code sprints and moved the discussion forward with concrete
initiatives, like the idea to have such a list for distribution
maintainers and advanced users to exchange tips and tricks on linux
audio tuning. We also talked about the idea of a set of common kernel
config that could be reused by different audio/video distros.
Part of pure:dyne we have always put our config on SVN,
http://code.goto10.org/projects/puredyne/browser/live/kernel
(this is the one currently on the liveCD btw)
and we have started to make some kernel benchmarks and audio
optimizations page:
http://code.goto10.org/projects/puredyne/wiki/KernelAndSystemOptimization
I think it would be very useful if the 1st projects of this list were:
- a common place for all the distro maintainers to write a common tuning
doc (wiki.linuxaudio.org?)
- the creation of a repository with a couple of kernel config and patches
that would be common to our distros
- a benchmark protocol for testing audio settings and kernel
config/versions
Let me know what you think!
a.