Hi All:
Im using ALSA 1.0.14 and bluez 3.20 and linux 2.6.18.The linux 2.6.18
(montavista) is running on an embeded development board(using S3C2410).
When i tried to use 'aplay' to connect my bluetooth headset, i got
the following error from ALSA:
$ aplay -D bluetooth /1.wav
audio[326]
On Sun, 14 Oct 2007 20:21:52 +0100
Barry Samuels <[EMAIL PROTECTED]> wrote:
> > Another possible source of trouble after an upgrade
> > is /var/lib/alsa/asound.state
> > You must stop alsa:
> > /etc/init.d/alsasound stop
> > remove this file and restart alsa.
> >
> > Dominique
>
> I use the alsa
On Mon, 15 Oct 2007 17:30:59 -0400
"W. Ryan Nestor" <[EMAIL PROTECTED]> wrote:
>
> Sorry, in addition to the above post, I have this info,
>
> >From the PCI section of dmesg;
>
> pcmcia: parent PCI bridge I/O window: 0x0 - 0x7f
> pcmcia: parent PCI bridge Memory window: 0xf300 - 0xf3fff
Aleksander Kamenik wrote:
> Anyway, how do I set plughw:0,0 to be used as the default sound output
> for all apps?
[[ replying to myself ]]
Almost all apps work with this addtition to alsa.conf. It even resamples
everything to 44100Hz (48kHz are playable!). Here's the diff from
original alsa.
James Courtier-Dutton wrote:
> Toggle one of the extension controls. It should change it between 44.1
> and 48kHz
> The USB device only works at fixed speeds, so I need to do a bit of work
> on the driver to ensure that the user does not try to send the wrong
> speed stream to the USB device when
Aleksander Kamenik wrote:
> Hi,
>
> I'm using the daily snapshot from 18 oct.
>
> I am able to get sound when using plughw:0,0 and only for 44100Hz.
> Although the wiki, dated 7. Oct, says:
>
> "The support for the EMU USB cards has started, and basic support is now
> in the latest alsa hg. It o
Hi,
I'm using the daily snapshot from 18 oct.
I am able to get sound when using plughw:0,0 and only for 44100Hz.
Although the wiki, dated 7. Oct, says:
"The support for the EMU USB cards has started, and basic support is now
in the latest alsa hg. It only supports _48000_ rate, but all the
I'm running Red Hat 5 on a Dell 690 workstation. I'm getting a
screeching noise when nothing is playing. I've tried
options snd-hda-intel position_fix=1 model=3stack in my
modprobe.conf with no joy. Any suggestions?
Thanks,
Steve
--
Steven J. BackusComputer Specialist
On 10/18/07, Jan Widera <[EMAIL PROTECTED]> wrote:
> > Hm, I'm puzzled. I actually have no idea why OSS is muted, when ALSA
> > is playing just fine. Maybe some other programm is using the
> > soundcard? With ALSA, you can open the "default" device several times,
> > with OSS this might not work. T
Regards!
> This may have to reasons: Do the clicks go away if you play something
> with 48kHz samplerate instead if 44.1kHz? Often USB cards work better
> with "even" samplerates, that are multiples of 1000Hz.
Yes, if I listen a song with a multiple of 1000, subjectively seen, then
the clicks ar
Jerry Geis wrote:
> I downloaded 1.0.15 and the ./configure in the alsa-lib package seems to
> now
> be using something called python-config.
# rpm -qf /usr/bin/python-config
python-2.5-12.fc7.x86_64
# cat /etc/fedora-release
Fedora release 7 (Moonshine)
--
Aleksander Kamenik
system administr
Hi all,
I did post this yesterday - but have not heard anything.
I downloaded 1.0.15 and the ./configure in the alsa-lib package seems to
now
be using something called python-config. Version prior to this did not.
I am using centos 4 and centos 5 and neigher have this python-config.
I would ha
Hallo,
Jan Widera hat gesagt: // Jan Widera wrote:
> I followed your instructions, aplay and arecord seems to be working
> without reservation!
Great! So at least we know that the card is working and not broken. ;)
> > If you happen
> > to have a 6-channel soundfile as well, you may try to use
Many thanks, that will greatly help me :)
-fx
On Thursday 18 October 2007 15:53:42 Aleksander Kamenik wrote:
> fx wrote:
> > Hi James
> >
> > Do you have some news about the fix ?
> > I just wanted to know if it's included on the last release of
> > alsa-drivers, or if we must wait for futur rel
fx wrote:
> Hi James
>
> Do you have some news about the fix ?
> I just wanted to know if it's included on the last release of alsa-drivers,
> or
> if we must wait for futur release ? (or is there a way getting the fix, maybe
> via cvs ?)
I don't know anything about the fix, but you can get da
Georg Mainik wrote:
> Hi,
>
> I am trying to find out whether I would get the Soundblaster Connect
> (external USB card) working.
The web site mentions a driver, so it's likely that the standard driver,
which assumes a USB audio class-compliant device, does not work.
It's possible that only sma
Hi James
Do you have some news about the fix ?
I just wanted to know if it's included on the last release of alsa-drivers, or
if we must wait for futur release ? (or is there a way getting the fix, maybe
via cvs ?)
Thanks :)
-fx
On Friday 12 October 2007 17:27:14 fx wrote:
> Hi
>
> Great to se
I am running 1.0.14 on a machine with centos 4.5
lspci reports:
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia
Hi there,
I'm giving up for now, hopefully somebody here can help me.
I have an Intel Mac mini (module snd-hda-intel), here's the begining of the
/proc/asound/Intel/codec#0 file:
Codec: SigmaTel STAC9221 A1
Address: 0
Vendor Id: 0x83847680
Subsystem Id: 0x106b0800
Revision Id: 0x103401
I want to
Hi,
I am trying to find out whether I would get the Soundblaster Connect
(external USB card) working. Unfortunately, it is not listed on the
project site.
Any idea? Experience?
thanks
Georg
-
This SF.net email is sponso
20 matches
Mail list logo
