Shawn Eary wrote:
I have a 1212M (firewire) that works fine in XP, but FC8 thinks it is
a Creative Labs SB Audigy. When I try to play the test sound, I get
nothing through the Analog Outputs.
Alsa Driver Version 1.0.15
Alsa Lib Package 1.0.15-1.fc8
Alsa Utils Package 1.0.15-1.fc8
Someone said
Mihaela Vitalariu wrote:
The application IS multithreaded. The async callback is invoked from
more than one thread until at some point SIGIO simply interrupts the
whole program
So, is it my bug or is it from ALSA?
Hmmm, not sure. My first impression is that alsa cannot know how many
threads
Mihaela Vitalariu wrote:
I am coding a Linux sound application using the PCM interface.
It plays fine but at unexpected intervals i sometimes get a SIGIO
directly in my program, which exits printing the message I/O possible.
What can be happening?
Looks like you enable asynchronous I/O one
Mihaela Vitalariu wrote:
Well, i use async I/O because this is the way my program works, using
callbacks,
and i just can't disable it :(
Huh?
Normally, using asynchronous I/O, your program would do whatever it's
meant to do, then it would get SIGIO signals every now and then, and in
the
John Haxby wrote:
I bet someone somewhere is using signal(3) instead of sigaction(2).
signal() is the old interface which has some unpleasant side effects --
for example, the handler is reset to the default once the signal has
been delivered. In the bad old days the first thing your signal
Lee Revell wrote:
I have one sound card onboard of my PC which I have disabled from BIOS.
My question is can I activate the second sound card and for example
duplicate all that is played on my front speakers of the primary card and
pass it to the output of the second card ?
If the answer is yes
Adrian McMenamin wrote:
Please try aplay -Dhw0,0 file the device syntax is mandatory afaik. If
that works you can start building a proper alsa config file with all
kinds of useful stuff on top of that.
Does this
$ aplay -Dhw0,0 /aine-email.wav
ALSA lib pcm.c:2144:(snd_pcm_open_noupdate)
Adrian McMenamin wrote:
# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
# aplay /aine-email.wav
Playing WAVE '/aine-email.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
ALSA lib pcm_plug.c:773:(snd_pcm_plug_hw_refine_schange) Unable to
find an usable
Adrian McMenamin wrote:
aplay -L reports:
$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
while aplay -l reports the card exists
$ aplay -l
List of PLAYBACK Hardware Devices
card 0: AICA [AICA], device 0: AICA PCM [AICA PCM]
Adrian McMenamin wrote:
aplay -L onmly reports pseudo-devices defined in software (afaik)
(asound.conf etc.)
Using aplay -Dhw:0,0 it should work, and probably also using the default
device which gives you dmix and conversion.
I get this:
$ aplay -Dhw:0,0 aine-email.wav
Playing WAVE
Adrian McMenamin wrote:
On 02/01/2008, Erik Slagter [EMAIL PROTECTED] wrote:
Adrian McMenamin wrote:
Your device probably isn't capable of reproducing phone-format audio.
It is!. It used to play this sample without any problem (but only
using oss emulation - aplay wouldn't work
John Haxby wrote:
Erik Slagter wrote:
As imho pulseaudio doesn't add significant functionality if you're not
using remote (over the network) audio, you'd be better off without it,
i.e. remove all pulseaudio packages alltogether.
That must be a different pulseaudio to the one I'm using
Carles Pina i Estany wrote:
On Dec 31, 2007 5:32 AM, Carles Pina i Estany [EMAIL PROTECTED] wrote:
Make sure you have the capture mixer control(s) unmuted and volume
raised. Some hardware inexplicably does not generate any interrupts
otherwise.
it is up for sure :-) checked using
Peteris Krisjanis wrote:
In nutshell, I have nothing so much against PA (some features are
really promising, but GUI and ease of use is seriously lacking),
I don't think the -G-UI is lacking (the pa* tools). My problem is that
there are no command line tools! I need to set some mixer
John Haxby wrote:
I've lost the bit where you said about you're against putting an
unmatured[sic] system in a distro. Fedora is a proving ground for
relatively immature systems -- compiz and beryl are a good example: if
you want a guaranteed stable distro pick up RHEL or CentOS.
Carles Pina i Estany wrote:
[..]
(and HDA Intel interrupts doesn't change)
[..]
I probably won't be able to solve your problem, but at least I can help
get useful data that might others enable to solve your problem...
So the card doesn't use MSI, which seems to be a common problem with
Lennart Poettering wrote:
- pulseaudio, using hal-detection and combined device: doesn't work
because a removed device is never reinserted into the combined
device;
Of course it is. Just install PA 0.9.7 or newer.
Nope, really.
The relevant config file sections (using pa 0.9.7):
***
[EMAIL PROTECTED] ~]# alsamixer
*** PULSEAUDIO: Unable to connect: Connection refused
alsamixer: function snd_ctl_open failed for default: Connection refused
With FC8 esd/esound has been replaced by pulseaudio (+ esound
emulation). This that every program that has esound as it's default,
Sorry for crossposting, but this is a problem I am not quite sure might
be solved by users or developers. Also I am not too lazy to do a little
development myself, if that appears to be necessary.
This is my setup:
- internal snd-hda soundcard connected to speakers in the bathroom
playing 24x7
Carles Pina i Estany wrote:
In poll. I tried to boot the kernel with noacpi (same result) and
with pci=noacpi (kernel hangs when loading).
Hmm, I don't think this is the direction to search for the problem. ACPI
is OK nowadays.
What is your hardware (motherboard)? Does it have pci express and
Hi,
I recently bought a new motherboard, which, completely to my suprise,
had on-board audio that actually was supported, so I could bounce my
Soundblaster Live that had been around for years and which I had only be
using for it's optical sp/dif output that actually works from linux ;-)
My new
21 matches
Mail list logo
