>Hi all, I am having an odd problem with the ALSA cvs compile on SUSE
>8.0. I am trying to do this in order to get the hdsp driver. However,
>whenever I compile the driver it stores all the modules in the
>/lib/modules/2.4.18-4GB/ folder assuming that my kernel is 2.4.18-4GB.
>However, when I open
>Please someone correct me if I am mistaken. Can the pcm.tee option in alsa.co
>n
>(/usr/share/alsa/alsa.conf) be setup so that the output of a program that uses
>alsa natively be monitored by connecting to this "tee" ??
well, the "tee" type allows redirection but its only sane to do it to
a fil
>Also, what is the current status of gstreamer in this department and
>jack? (I tried artsd and that one simply doesn't cut it)
jack allows any number of applications to use a single audio
interface, up to a run-time configurable limit imposed by the total
maximum number of "ports" in the JACK sy
I meant to add:
>Also, what is the current status of gstreamer in this department and
gstreamer has nothing to do with this. gstreamer is an internal
architecture/framework for a single application and has nothing to do
with sharing audio interfaces or audio data with other processes.
--p
>Thanx, I did run the alsactl reload and I glad you know what the problem
>is. I'd love the patch and an explanation. If not for me then for the
>record, for others who may experience this as well.
oh drat. i just looked at the code again, and now its no so obvious
any more. do me a favor will yo
>When i first ran this script it complained alsactl cound not find device
>"9652". I changed the 'Card_ID="9652"' to 'Card_Id = "card0'" and it
>seemed to run just fine. I popped in a CD and ran XMMS and still no
>sound. Ok, I opened up my /stc/asound.state file (which looked as I sent
>it to you
>Whoops! I re-read that an realized my spelling checker screwed up. I
>meant that "Paul Davis thought that you could NOT connect this to a
>cdrom drive output, but i have called a few vendors and the believe this
>is not the case "
>
>There is defiantly confusion
>
>Ok,
>
>I have a dvd-rom drive that i have connected the digital out (2-pin) to
>the cd-in connection on the RME9636. I am sure that the hardware is
>corrected properly.
>
>However I get no sound when playing cds in XMMS or DVDs in Xine. Paul
>Davis thought that you
>I do not mean to be hammering this issue into the ground, but Linux OS
>as an audio workstation solution has been around for 3 years now, yet
>the only soundcard I am aware of that is capable of doing hardware
>mixing is SBLive!, and even that one is due to fact that Creative had
>their hands in
>> the hammerfall cannot do this. the hammerfall-DSP can do matrix
>> routing of signals between channels, but it does not mix software
>> streams down to a channel.
>
>Crap! :-) So does this mean that RME card cannot be accessed from
>multiple applications at the same time? This is one of the mos
>Well, I tried restarting the alsasound and that did not fix it at all.
>Granted, I was also trying to use cmixplay command which most likely
>invokes rme card via oss emulation, and I've heard that oss emulation is
>a bit flaky. So, I did end up having to restart the machine to get the
>sound bac
>> i have had this problem from time to time as well. i am still, after 2
>> years of working with the hammerfall, unsure of what causes it.
>
>Could it be a PCI problem? Latency timer issue? Busmastering problem?
it seems to be related to the condition of the h/w when it was stopped
and/or resta
>It seems I have been celebrating too early.
>
>Here's the scoop on my current issues:
>
>I have finally managed to produce sound with the darn thing, but every
>so often now I get sporadic "crackle" out of the output, as well as
>complete distortion of the sound, almost as if the pitch is constan
>I noticed your post regarding the IRQ issue. How did this issue manifest
>itself when you tried to use the Hammerfall card? Could you still
>install (modprobe) the driver without any problems, or was it preventing
>you from doing even that? Could you please give me more info so that I
>can see if
>Also, could someone please be so kind to send me their asoundrc file
>that they are using for the hammerfall, so that I can learn from it as
>to how to configure it since the one that comes with alsa-driver package
>is rather esotheric for my understanding? Thank you very much!
this is mine.
pc
>You want the ctl entry so that ardour will work properly. When you use
>aplay or any other application, use dsp1 as your alsa device, and when you
>use ardour, use rme9652, because ardour wants the raw access.
3 quick notes:
1) i prefer:
pcm.dsp1 {
type plughw
card 1
}
as
Jeremy has correctly answered many of the points/questions you
raise. I will try to finish off the story :)
>problem is that I cannot get the mixer to have any "elements" (or
>"elems" as the alsamixer calls them) which thus makes the card
>un-openable even with the alsamixer.
there is no mixer.
>NO one has specifically sent a copy of the file for the Delta 66 that I
>can seem to understand and there seem to be a few diferent versions
>floating about on the mailing lists. (ardour-dev,alsa-dev, and
>alsa-user).
>
>If anyone could help here by sending an asoundrc file configured for a
>si
>Same previously said machine configuration, LL RTC 2.4.17 kernel, using
>latest (ALSA 0.9.10a) drivers and pmidi 1.5.4 (both compiled and
>installed by hand here).
>Every MIDI played with pmidi has "eaten" notes, even a very simple MIDI
>file I wrote to test (one channel, max 3 notes playing s
>What I found quite astounding is how brave pmidi keeps its timing: It
>uses no extra threads, no RTC, no suid-root privileges (and my kernel
>doesn't have LL or PE patches built in right now), but still plays back
>a 10-track MIDI file very time-stable even if I do something like "start
>Gimp, Mo
20 matches
Mail list logo
