hello all - got a question - I've only recently been stopping and taking a
look at my studio computer's performance and in the almost year since I
change from Red Hat 9 to gentoo, it's been more solid on some things, but I
notice a huge latency difference - ie: I have to run Jack at -p 8192 to get
anything done in Ardour
Anybody have any tips on what to look at to tweak it? Seems like it should
do better than that... I didn't see it as a problem until in the last few
days I started playing with playing softsynths live directly into Ardour -
you've gotta be running at -p 1024 or there's a latency that screws up your
playing - at 8192 it's a downright 8th note delay...
Here's some vitals that I can think of:
OS: gentoo 2.6.6-rc1 kernel (alsa built in)
jack: 0.99.0
ardour: beta28
jack command line:
jackd -R -d alsa -d hw:0 -r 48000 -p 8192 <------- (or whatever)
harddrive:
multicount on
io support: 32 bit
unmaskirq on
use dma on
keepsettings off
readonly off
readahead on
chip: 2ghz amd (I THINK - not at computer now)
ram: 512MB
thanks for any ideas! :)
---------------------
Aaron Trumm
www.nquit.com
-----------------------
Hi Folks,
So, I have spouted off about a distro before (I know some of you checked
it out) and it was not as good as I hoped it would be! :(
Trust me...THIS is not the case this time!!!
Announcing PClinuxOS (PCLOS for short)
http://www.pclinuxonline.com/pclos/
This is based on Mandrake but minus the bloat! One ISO built as a
LiveCD! You can boot it and not install...no commitment unless you want
to. The install is simple as can be and fast. KDE 3.4, Fluxbox, Gnome,
etc. The distro was started by Texstar who used to build packages for
Mandrake a few years ago.
So, whats that got to do with Music?? Just this; Thac has decided to
start packaging for PCLOS just as he has with Mandrake. For those not
familiar with his work...
http://rpm.nyvalls.se/sound10.1.html
I have relied on Thac's RPMS for audio since I started Linux audio work.
He keeps his packages updated and has about everything worth having in
his repositories. They have been invaluable to me.
As recently as yesterday, Thac has started his own 3rd party Apt
repository for PCLOS and as I write I am downloading the first of his
packages and new mm kernel, etc. We are chatting on the Pclinuxos IRC
chat room and ironing out a few minor bugs. It will be a few days before
he has all of his packages done.
Texstar suggested that we might make a liveCD with the key audio apps
and a R/T kernel for easy usage and evaluation. Obviously some time is
needed to work the bugs out but this is very likely in the not too
distant future! I should think those of you working with MDK right now
would see this as an easy step....others...well, the proof will be in
the pudding.
More soon....
R~
I don't think I understand this jackplug concept.
I'm trying to get an alsa client, such as aplay to play through jackd.
I've setup jackplug in /etc/asound.conf
pcm.jackplug
{
type plug
slave
{
pcm "jack"
}
}
pcm.jack
{
type jack
playback_ports
{
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
}
capture_ports
{
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
I then tell aplay to use:
#aplay -d jackplug foobar.wav
But aplay plays the file even if jackd is not started; why?. Isn't
jackplug supposed to show up in my jack connections when aplay is
playing?
I seem to be missing something vital.
Is there some way to make a "fake audio device", like hw:3,0 that alsa
applications can connect to so that I can get the audio out and then
send it through jack, process it and then send it to the real audio
device?
--
Esben Stien is b0ef(a)esben-stien.name
http://www.esben-stien.name
irc://irc.esben-stien.name/%23contact
[sip|iax]:b0ef@esben-stien.name
I have just upgraded to alsa 1.0.9 and the midi controllers on my
evolution mk-249C no longer work.. Has something changed with the alsa
config files? Anyone else see this problem? I can't find anything of help
by googling..
Any help would be appreciated!
All the best,
James
Hello,
I'd like a simple keyboard for plonking out notes to help me learn my
choral music. First, I'd like a piece of software that accomplishes
this by using my usual PC keyboard. Second, I'd like actual keyboard
hardware that can operate by itself, or connected to a computer
through either USB or MIDI (preferably both). I don't want any
extraneous features on the keyboard, although I'd be interested in
hearing what features people find particularly useful. Velocity
sensitive keys that feel like a piano to some degree would be a major
plus, but that mostly depends on the difference in price. Any
suggestions?
Cheers!
Shaun
Someone brought this device to my attention:
http://www.emu.com/products/product.asp?product=2209&category=754&maincateg…
Creative may donate a device to an ALSA developer to develop the
necessary support, if they think Linux users would be interested. There
is already a volunteer to develop the driver support. If you would
consider buying this device were it supported (I certainly would) please
contact Creative and politely ask them.
I think if just a few people write them along the lines of "I really
like looks of the 1212m, and I'd like to buy one, if I could use it with
Linux. Can you provide one to the ALSA developers?", they will do it.
Every person who takes the time to contact them, they will assume
represents N users.
Lee
Quoting Christoph Eckert <mchristoph.eckert(a)t-online.de>:
> We all would be glad if we didn't need to patch and recompile
> the kernel. BUt there's hope that we get realtime
> capabilities in the vanilla kernel soon. Let's stay tuned.
You are a bit late actually. :)
>From 2.6.12 changelog:
"commit e43379f10b42194b8a6e1de342cfb44463c0f6da
Author: Matt Mackall <mpm(a)selenic.com>
Date: Sun May 1 08:59:00 2005 -0700
[PATCH] nice and rt-prio rlimits
Add a pair of rlimits for allowing non-root tasks to raise nice and rt
priorities. Defaults to traditional behavior. Originally written by
Chris Wright.
The patch implements a simple rlimit ceiling for the RT (and nice)
priorities
a task can set. The rlimit defaults to 0, meaning no change in behavior by
default. A value of 50 means RT priority levels 1-50 are allowed. A
value of
100 means all 99 privilege levels from 1 to 99 are allowed. CAP_SYS_NICE is
blanket permission.
(akpm: see
http://www.uwsg.iu.edu/hypermail/linux/kernel/0503.1/1921.html for
tips on integrating this with PAM).
Signed-off-by: Matt Mackall <mpm(a)selenic.com>
Acked-by: Ingo Molnar <mingo(a)elte.hu>
Signed-off-by: Andrew Morton <akpm(a)osdl.org>
Signed-off-by: Linus Torvalds <torvalds(a)osdl.org>"
Sampo Savolainen
Hi,
my terratec card provides very high latencies (more than
40msecs), so I wonder if there are cards out there which are
USB 2.0 compliant but can be used on my USB 1.1 machine
(until I get a new one) at low latencies.
Anyone can tell about such a card? I do not need MIDI ports,
but full duplex 2 in 2 out with a mic in and a headphone out
would be great. More ins and outs are welcome.
Because I'm a hobbyist, the cheaper the better ;-) .
Thanks & best regards
ce
[after writing this I found
http://lists.agnula.org/pipermail/users/2005-June/006358.html in the
agnula-users archive. many of the same points are raised, but it appears
not yet corrected in the wiki.]
[and now I've found and have begun reading the more recent thread:
http://lists.agnula.org/pipermail/users/2005-June/006417.html
still I'm wondering which of the deb lines below is correct]
There seems to be some inconsistency on the agnula pages on the correct
apt sources line. I want to try adding demudi to a fresh debian sarge
install.
Here: http://demudi.agnula.org/wiki/InstallApt
it says use this:
deb http://demudi.agnula.org/packages/demudi testing main
and in the FAQ:
http://demudi.agnula.org/wiki/DocumentsFaq#Upgradingexistinginstallations
it says use this:
deb http://apt.agnula.org/demudi testing main local extra
Are those 2 apt sources the same? if not which is correct?
These instructions from the FAQ are somewhat confusing:
"* from the command line issue:
# apt-get install demudi
* install the tasks you are interested in. To have a look at them run:
# apt-cache search demudi
The task demudi installs them all."
It should probably tell the user to apt-get update after editing
sources.list. Also, the two statements above appear to be contradictory,
or at least out of order.
Installing package demudi appears to only install some pixmaps and pngs.
Attempting to install any of the demudi-<foo-task> packages returns
saying that it's not available and is replaced by demudi. Maybe these
only work if you use taskselect?
I must be missing something pretty basic here.
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network(a)rfa.org.