Hi,
On Tue, 12 Dec 2023, Chumi wrote:
> I did not succeeded to have the sound on my laptop Dell XPS 9320. The
> specifications says that it has speakers. But no sound from the
> headphone neither the speakers.
[...]
> Here is the output from alsa-info.sh :
> https://alsa-project.org/db/?f=cf44
Hi,
On Wed, 19 Jul 2023, Nico Schottelius via Alsa-user wrote:
> I tried to use sof-v2.5 and after adding the module parameters
>
> options snd_sof_pci ipc_type=1
> options snd_sof_intel_hda_common sof_use_tplg_nhlt=1
thank you for the report.
SOF 2.5 (and SOF2.6 still) is opt-in for this gene
Hi,
On Mon, 8 Feb 2021, Blazej Slusarek wrote:
> My laptop HP ZBook Fury 15 G7 Mobile Workstation has the problem that
> there's no sound after I suspend and resume it, the only solution that
[...]>
> logs from alsa-info when sound is working: https://pastebin.com/0CuJWiG1
> When it's not workin
Hi,
On Mon, 12 Oct 2020, Noè Murr wrote:
> When I load the module everything is back to how it was before.
> Attached you can find both the alsa-info before `modeprobe -v
> snd_hda_intel enable=Y,N` and after that.
thanks. The log looks as expected, only the ALC1220 codec is enabled
with the PCH
Hi,
On Mon, 12 Oct 2020, Noè Murr wrote:
> I tried and I still see an error with that card in the log.
> It's attached.
>
> I tried some other options found online like:
> enable_msi=1 and model=auto, but without any luck.
hmm, interesting, with modprobe/kmod v27, the array options are not pick
Hi,
On Mon, 12 Oct 2020, Noè Murr wrote:
> I tried what you suggested and as expected the command aplay -l didn't
> show the hdmi outputs anymore, but it does not solve the problem.
>
> I run the alsa-info script and I attached it to this email.
thanks, seems like the discrete GPU audio enablin
Hi,
On Sat, 10 Oct 2020, Noè Murr wrote:
> Note that if I run xrandr after the suspension I see the HDMI exit as it
> was working.
>
> I found out online that one guy had my same problem found out that
> blacklisting the modules:
> snd_hda_intel
> snd_sof_intel_hda
> snd_sof_in
Hi,
On Fri, 14 Aug 2020, Shapeshifter wrote:
> some months ago, presumably after a kernel update, my system (archlinux)
> started having the following problem.
>
> After booting, it takes pretty much exactly 1 minute for the HDA Intel
> PCH / Realtek ALC898 audio card and devices to become avail
Hey,
On Wed, 24 Jun 2020, Sleep wrote:
> Why does the program below issue errors for
> snd_pcm_hw_params_set_period_size(), snd_pcm_hw_params_set_buffer_size(), and
> snd_pcm_hw_params_set_rate()? If I raise the value of SAMPLES to 768 it only
I highly recommend to review well known clients like
On Wed, 3 Mar 2004, Michael Rausch wrote:
> The four input I would like to use are those of the Delta 66.
[...]
> But when I try something like:
> # ecasound -i:alsahw,1,m,n -o:out.wav
Try:
ecasound -f:32,4,44100 -i alsa,plughw:1 -o out.wav
Or:
ecasound -f:32,12,44100 -i alsa,hw:1 -f:32,
On Tue, 20 Jan 2004, Kai Vehmanen wrote:
> On Tue, 20 Jan 2004 [EMAIL PROTECTED] wrote:
>> My biggest personal issue with ALSA is that I have been so far unable to
>> find any documentation that explains what the configuration file
>> directives represent. I don't know
On Tue, 20 Jan 2004, John W. Cocula wrote:
> represents. But it's as if no one uses their microphone jacks at all, and
> that capturing input is completely unimportant, compared to surround-sound
> output, for example. I think, if this is the case, that voice-over-IP and
> speech recognition wil
On Tue, 20 Jan 2004 [EMAIL PROTECTED] wrote:
>> On Tue, 20 Jan 2004, Don Levey wrote:
>> For me, I want to do music with pro-gear on Linux and like to have source
To correct the quotation, the above text was written by me, not Don.
>> ALSA does work very well and has done so for a long time! Mo
On Tue, 20 Jan 2004, Don Levey wrote:
> Yeah, it was all free - and I'm not asking for my money back. The question
> I continually have is "what is the long-term goal of Linux and the
> open-source community?" Is it a hobbyist OS? Is it something which is
The open-source community doesn't real
Note: this probably belongs to alsa-devel, so please remove alsa-user from
replies.
On Fri, 26 Sep 2003, Jamie Lutch wrote:
> Didnt have any responses on my post of a few days ago, so I'm giving it
> another go:
Sorry for the late reply.
> So I have my setup (pdaudiocf card>ecasound) running fi
On Tue, 9 Sep 2003, Jamie Lutch wrote:
> well, ecasound wouldnt let me record a .raw file over 2gb, so theres a
> limit in place somewhere. Its prob. built into ecasound to make the
> resulting files compliant with ms's .wav standard
Compile ecasound with "--with-largefile" and you get around the
One thing I've noted that if you build (or just run make config) the
kernel in the /usr/src/linux-2.4 source-tree (i.e. the files from the
kernel-source rpm package), building alsa-lib will fail as it finds the
wrong kernel name (2.4.xx-yy-custom instead of the kernel that is actually
running). If
On 12 Jun 2003, Allan Klinbail wrote:
> Has anyone got any suggestions regarding playing cd's while not doing
> audio work? (as there is no cd input on the delta66). Is there a player
> that will read the digital audio and send it to the sound card .. such
Alsaplayer. It also supports JACK output
On Tue, 25 Feb 2003, T.P. Reitzel wrote:
>> Don't forget ecasound (w/ ALSA):
>> ecasound -a:mon -i drums.wav -o alsa,default \
>> -a:rec1,rec2 -f:16,2,44100 -i alsa,default \
>> -a:rec1 -f:16,1,44100 -o first_rec_channel.wav \
>> -a:rec2 -erc:2,1 -f:16,1,44100 -o second_rec_channel.
On Sun, 17 Nov 2002, Magnus Ullberg wrote:
> do you know if there is a way to set a default configuration?
> Another program i've got has no way of specifying a configuration.. I
> dont even think it uses alsa-lib, it just tries to use the soundcard
> (but i could be wrong about that one..)
What
On Sun, 17 Nov 2002, Magnus Ullberg wrote:
> hmm.. im trying to get MPlayer to work but apparently it doesn't
> support ~/.asoundrc or mine is set up wrong.
While asoundrc specifies different configurations, applications must
still select which they will use. I haven't used mplayer recently,
but
On Mon, 18 Nov 2002, Magnus Ullberg wrote:
> Is there a way to force the driver to use plughw instead of hw?
Yup...
> aplay, etc. works fine since they support ~/.asoundrc
> but programs that doesnt support that will not work
... ~/.asoundrc. It's automatically used by all apps that
use alsa-li
Takashi, thanks for these corrections!
It'd be great to see yet more reports about successes, failures, suspected
problems, etc, etc concerning different soundcards and chipsets on
alsa-user (and other lists)! It's much easier to make purchasing decisions
if you know that at least someone has ha
On Tue, 22 Oct 2002, Peter L Jones wrote:
>>> * MidiMan Delta Audiophile 2496 (Envy24)
>>> * Creative SB PCI 128 (ES1371)
>> I've used both of these extensively with JACK and numerous other ALSA apps
>> and they work really well (full-duplex, low-latency use). Other
> Heh. Now, one of these I h
Btw; this a very interesting topic. Please, tell about your
experiences. By discussing these things in a public forum,
we are actually creating a nice searchable knowledgebase
for all current and future ALSA users!
On Tue, 22 Oct 2002, Anthony wrote:
>> - snd-intel8x0 (nice chips
On Tue, 22 Oct 2002, Peter L Jones wrote:
> I don't want to have to learn about DSPs and stuff to be able to identify a
> _good_ sound card. I've currently got a shortlist for my next machine:
> * MidiMan Delta Audiophile 2496 (Envy24)
> * Creative SB PCI 128 (ES1371)
I've used both of thes
On Mon, 16 Sep 2002, Øyvind Stegard wrote:
> Does ALSA (the library or the kernel drivers) support software mixing of
> several PCM streams in the _same_sense_ as aRTSd or esound(which sucks,
> btw), on any kind of soundcard ? If so, are there some simple guidelines
Not yet. This issue has be
On Sat, 31 Aug 2002, Matt Walker wrote:
> I am trying to get the midisport to do rawmidi - just sysex/librarian stuff.
> The following leads me to believe that usb is working, and the driver is
> getting loaded, but the 2 aren't making a connection
[...]
> Aug 27 22:30:35 enki kernel: usb.c
On Fri, 26 Jul 2002, Dave K wrote:
> [root@rme32 root]# ecasound -sr 48000 -i:alsa,hw:1,0 -o:test.wav
How about
ecasound -sr:48000 -f:s16_le,2,48000 -i alsaplugin,1,0 -o test.wav
...?
> [root@rme32 root]# cat /proc/asound/card1/pcm0c/sub0/status
> closed
> Not sure what "closed" means..
This
On Thu, 18 Jul 2002 [EMAIL PROTECTED] wrote:
> What do i have to do, to play just 1 wav file on 1 channel (i mean: not
> 8 at the same time). That would solve all my problems ;). If i play
> something now, it uses all the channels.
Have you tried ecasound - http://www.eca.cx/ecasound ...?
# pla
On Wed, 10 Jul 2002, Kai Vehmanen wrote:
> Although the mixer does show the controls (I can see 'Mic', 'Mic Capt' and
> 'Speaker' with alsamixer), none of the controls seem to have any effect.
> Even with all sliders down I can still both record and play
Hi,
I just managed to get Labtec Axis-712 stereo USB-headset (vend/prod
ids 0x672/0x1041) working with the ALSA (CVS) USB audio module.
Although the mixer does show the controls (I can see 'Mic', 'Mic Capt' and
'Speaker' with alsamixer), none of the controls seem to have any effect.
Even with
Hi,
this isn't a critical issue, but just in case someone is struggling
with the same problem.
Shortly put, with ALSA 0.5.12a, the cs4281 driver works ok (tested
with full-duplex operation in both native and OSS-emul modes). But
when upgrading to 0.9.x, card is not identified anymore. The error
Why is ALSA the better alternative? That's a question I've been asked
quite a few times recently. Below is a reply I just wrote to
ecasound-list. I'd be very interested in hearing your comments on this
issue. Have I missed some important points?
One thing that seems be causing a lot of confusion
On Wed, 20 Feb 2002, Jan Suhr wrote:
> ecasound -i 24bit_test.wav -f:s24,2,44100 -o alsa,default
> it works, no problem!
Ok, good to hear. That means your ALSA drivers are working ok.
> But my own wav file doesnt work; its noise you know.
Now you just need a program that can read it. Few quest
On Tue, 19 Feb 2002, Jan Suhr wrote:
> You know, I would like to play a 24b/96kHz _wav_ file not mp3? Ok, I
> take another mp3 file and test it:
Yes I'm aware of that, but the problem is that 24bit/96kHz is a
problematic parameter combination for RIFF WAVE files as the file format
specification
On Mon, 18 Feb 2002, Jan Suhr wrote:
>> Your soundcard doesn't support the specified s24bit, 96khz, 2ch audio
>> format natively, so you'll have to use ALSA's plugin layer which
>> converts the audio data into a format your soundcard does support. To
>> do this, replace "alsa,hw:0" with "alsa,def
On Thu, 14 Feb 2002, Jan Suhr wrote:
>> ecasound -i 96_24bit_excerpt.wav -f:s24_le,2,96000 -o alsa,hw:0
> I tried this expression with my own wav file; ecasound said:
> ERROR: [ECA-CHAINSETUP] : "Enabling chainsetup: AUDIOIO-ALSA3: Audio
> format not supported."
Your soundcard doesn't support t
On Wed, 13 Feb 2002, Len Moskowitz wrote:
>> Try ecasound, www.eca.cx/ecasound. If it doesn't work for some reason, put
>> a sample 24bit file somewhere on the web (or mail me if it's small), and
>> I'll promise to make ecasound play it. ;)
> Here's a link to a short (only a few seconds, but stil
On Wed, 13 Feb 2002, Len Moskowitz wrote:
> For Linux, I haven't yet found one. For Windows there's "n-Track Studio"
> (www.ntrack.com).
Try ecasound, www.eca.cx/ecasound. If it doesn't work for some reason, put
a sample 24bit file somewhere on the web (or mail me if it's small), and
I'll pro
On Wed, 13 Feb 2002, Jan Suhr wrote:
> I tried ecasound but it doesnt work.
> 1. ecasound dont like the "-o alsa" option, so I changed to "-o
> /dev/dsp". This seems to be ok.
Looks like support for ALSA0.9 is not compiled in. Did you recompile
ecasound against ALSA0.9...? And what version of
On Tue, 12 Feb 2002, Jan Suhr wrote:
> It works! My Audiophile works well with ALSA cvs version. I tested only
> the analog output.
> But I cant play 24bit 96kHz wav files.
What app did you use? You should first try with 'aplay' (comes with
alsa-utils package). In case aplay fails to parse the
On Wed, 30 Jan 2002, Alan Buxey wrote:
> so...does this mean I cant use my soundcard at the same time or do
> I have to initialise the ALSA system BEFORE running the TVCard system?
At least some of the tvcard kernel modules allow you to select whether the
tvcard should register as a OSS device.
The dynamic loading bug (RTDL_GLOBAL-thing) also affects ecasound.
Ecasound 2.0.2 (and older) won't work with the newer ALSA 0.9
beta-releases (at least beta7 and beta8). Problem is fixed in this
ecasound 2.0.3 release.
-- Forwarded message --
Support for the latest ALSA 0.9 beta-
On Thu, 20 Sep 2001, Kai Vehmanen wrote:
> (other programs, drivers, etc), soundcard's buffer area has become
> full with recorded data. So as a result you get the an underrun
> (no place to put more data, so previously recorded data is lost).
Doh, of course, overrun, not u
On Thu, 20 Sep 2001, Adam Wiggins wrote:
>When recording via arecord I frequently see:
> xrun!!! (at least 12.096 ms long)
This is actually an underrun. While your computer is doing something else
(other programs, drivers, etc), soundcard's buffer area has become
full with recorded data. So
46 matches
Mail list logo
