k.s.matheussen(a)notam02.no writes:
>
> (I'm crossposting this to linux-audio-user since there so few
> reading laa, for some strange reason, and that people often seems to
> be surprised this program exist, even though it has existed for nearly
> a year.)
I'm not surprised that noone reads laa.; Lots of people are
crossposting their announcements to lau, and some even add lad to the
list. If people would stop doing this, there would be incentive to
read laa.
--
Han-Wen Nienhuys | hanwen(a)cs.uu.nl | http://www.xs4all.nl/~hanwen
Greetings all! I am attempting to initiate a long unattended 2-channel
audio recording - perhaps lasting for an hour or two - but I am prevented
from doing so by periodic overruns which occur at regular intervals. This
interval changes according to my system configuration. Currently, I
consistently get an overrun about 20 minutes after I start recording.
My system is an AMD Athlon XP 1700+ with 256mb DDR266 memory. Video card is
an ATI Radeon 7500/64mb. Sound card is an M-Audio Audiophile 2496. I'm
running Slackware 9.0. My kernel version is 2.6.test5. Prior to this
kernel I was using 2.4.21 with low-latency and preemptible kernel patches -
with exactly the same overrun issue. I'm using jackd version 0.79.2,
Ardour/GTK 0.378.0, and libardour 0.686.0 (all built from CVS source a few
weeks ago.) I'm starting jackd with the command:
jackd -v -a -R -d alsa -d ice1712 -r 44100 -p 2048
I don't want to clog everyone's mailbox with an even bigger message, so I've
posted a bit of additional info online.
Results from running latancytest0.42-png:
http://www.comevisit.com/NorthernSunrise/latency/3x256.htmlhttp://www.comevisit.com/NorthernSunrise/latency/test2/3x256.html
My .config file from my most recent 2.6.test5 kernel build:
http://www.comevisit.com/NorthernSunrise/latency/.config
My jack, and ardour version numbers, and hdparm info for hda and hdb:
http://www.comevisit.com/NorthernSunrise/latency/configuration
I can see from the latency tests that *something* is causing spikes,
particularly during disk write, but I'm not sure how to determine precisely
what it is. Is there any way to obtain a snapshot of processor usage at the
exact moment of an overrun? Any help or advice (or reminders about what
info I've neglected to give) would be very much appreciated!
|)
|)enji
Benjamin Flaming
--------------------
"The trouble with computers, of course, is that they're very sophisticated
idiots."
Hi,
A few months ago someone on this list managed to compile shaketracker
with gcc-3.x. He offered to make a patch if anyone was interested. Is
that offer still valid? I am on redhat 9 (planet), and i have no
skills to get there myself.
I also would like to try ttrk, but this one also fails to compile on
my box.
Any help would be greatly appreciated!
--
Gerrit
I'm having a hard time bringing my new RME pci interface and Multiface
to run... and would appreciate some help ;-)
I'm working on Debian/unstable, have compiled the kernel with lowlat and
preempt, installed ALSA, inserted the hdsp modul, made a basic ~/.asoundrc,
compiled hdsploader from alsa-tools and with the friendly help of Thomas
Charbonnel also hdspmixer.
hdsploader loads the firmware (well it does the *second* time I run it,
which is a known problem, as Thomas told me). The error LED on the
Multiface is off. Input (on analog input1) *does* show in hdspmixer
(only in the *input* channel, nowhere else), but I can't get any sound.
Hmm, here I have the first question: Do I have to run alsamixer or
hdspmixer or both to unmute the channels? (I have tried all of this).
I have tried to feed a signal to analog input 1 and get it out from
analog output 1. I have also tried to set the internal routing with
amixer, but don't know if I have done that right... Well, the doc
says hdsp defaults to route inputx to outputx anyway. But I can't
hear anything...
I have tried 'cat some.wav > /dev/dsp' no sound, no errors.
(where would the error message show up?)
I do hear a high pitched hiss on line out, nothing else.
Please tell me: What would be the most basic procedure that should
produce sound output on the Multiface?
What diagnostic information can I give you to find out why it is
not running yet?
Thanks a lot for any hints!
Robert Epprecht
Hi!
Finaly I can run jackd and compile Adour.
But I can't run Ardour. I can see the splash screen, but Ardour killing
itself.
So:
# ardour
Ardour/GTK 0.380.1 running with libardour 0.686.3
Loading UI configuration file /usr/local/ardour/ardour_ui.rc
Loading system configuration file /usr/local/etc/ardour/ardour_system.rc
Loading user configuration file /usr/local/etc/ardour/ardour.rc
ardour: [WARNING]: MMC MIDI port "trident" not available: no MMC control
possible
343: received signal 4
ardour is killing itself for a clean exit
Killed
I don't get Ardour using CVS because I can't connect the cvsroot.
So, I get the file ardour_current-cvs.tar in the website of Ardour.
What is MIDI port "trident"? I haven't hardware trident, any, in my computer.
The TODO file say: "don't initiate MIDI binding if there is no MMC control".
Is it my answer?
But where I disable "MIDI binding"?
I don't make any change in the files *.rc
But after this error I remove any line about MMC or MIDI and I get the same
error.
Somebody can help me?
Thanks!
Alexander
snd-mpu401-uart is the driver for the external MIDI port (you'd need a
gameport/MIDI adapter for this). snd-rawmidi is an ALSA module
handling device file management and buffering for MIDI ports.
snd-opl3-lib is the driver for the OPL3 FM synth.
Thanks, got it. So if I wanted to deal with the FM sound quality I could use the legacy synth?
I guess Muse uses the ALSA sequencer. Run "aconnect -o" to see a list
of output ports.
This is the output of aconnect -o when both TiMidity and MusE are running:
[barton@localhost barton]$ aconnect -o
client 128: 'Client-128' [type=user]
0 'TiMidity port 0 '
1 'TiMidity port 1 '
client 129: 'MusE Sequencer' [type=user]
0 'MusE Port 0 '
>Checking /proc/asound/devices does not list any midi devices,
Did you specifiy the parameters for snd-ymfpci in modules.conf?
(e.g. mpu_port=0x330 fm_port=0x388)
No I didn't. So to use alsa with the midi port that is on the motherboard I would need to configure the memory address mpu_port=0x330 in /etcmodules.conf? Does the line need to go in a specific place, and is that the exact syntax? Is this documented somewhere? I have installed alsa manually on this machine before (this time I used the Planet RPMs and alsaconf) and I don't remember seeing anything that referrred to memory addresses for the midi ports.
Thanks,
Barton
Hi,
I can higly recommend the services and documentation provided by
Planet CCRMA:
http://ccrma-www.stanford.edu/planetccrma/software/
I just did a fresh install as described there and was in business in
no time.
--
Gerrit
might be of use.....
m~
-------- Original Message --------
Subject: FreeSamples now online
Date: Tue, 9 Sep 2003 20:33:05 -0400 (EDT)
From: Dennis Miller <dennismi(a)lynx.dac.neu.edu>
Reply-To: cecdiscuss(a)concordia.ca
To: cecdiscuss(a)concordia.ca
Northeastern University is pleased to announce the release of FreeSamples,
a Web site that features new and unusual sounds created by Northeastern
faculty and staff that are available free of charge. The sounds were
created using the various hardware and software resources found in the
labs at Northeastern and incorporate techniques such as convolution, cross
synthesis, LPC, phase vocoding, and a variety of granular techniques.
FreeSamples is a co-production of Northeastern and House of Samples and is
found at http://www.mtlc.net/freesamples/.
Hi there. Does anybody have a step by step on how to get a little Steinberg USB MIDI 2 (2 ins 2 outs, little blueish box) running with red hat 9? I have installed the planet ccrma alsa stuff, along with the audio stuff. things are working to some degree (except I haven't been able to record yet - but I'll wait to ask about that, when my real sound card comes :) )
I haven't got a clue, basically. I'm pretty new. When I wanted a midi interface to work in Cakewalk for DOS (that's right, that's what I was using last) I just downloaded the driver, and copied the driver into a file called driver.something - this apparently is not quite that simple? (I have read the planet ccrma how to on usb interfaces - so far nothing, and I was afraid the apt-get hotplug thing would flash firmware onto my steinberg that wouldn't be right, considering the steinberg isn't listed on their hardware list...
am I even remotely understandable???
thanks in advance! *laugh*
---------------------------------------------------------------
Houston Poetry Slam Team
www.houstonpoetryslam.com
NQuit Records
www.nquit.com
---------------------------------------------------------------
Hi!
What a way would you suggest me to go, if I decided to emulate a sound of
an explosion?
--
Alexandre Prokoudine
ALT Linux Documentation Team
JabberID: avp(a)altlinux.org