[nama] Re: No sound output
- From: Joel Roth <joelz@xxxxxxxxx>
- To: nama@xxxxxxxxxxxxx
- Date: Mon, 31 Dec 2018 09:58:39 -1000
On Thu, Dec 27, 2018 at 08:09:22AM +0100, Lars Bjørndal wrote:
Hi, Joel!
Thanks a lott for your help!
I just realized that if I wait 15-20 seconds after starting the play, the
sound is heard. Strange.
Below is a relevant posting on the debian-user mailing list
and bug report. In short, if you have an Intel soundcard, try:
options snd-hda-intel power_save=0
in /etc/modprobe.d/snd_hda_intel.conf.
In answer to your other question, yes Nama
can generate setpos events. When loading a project, the
engine is set to the previous playback position for that
project. When stopping the engine, the volume fades out,
then a setpos returns the engine to the position when the
stop was issued.
Hope this helps,
Joel
--
From: "Miguel A. Vallejo" <ea4eoz@xxxxxxxxx>
Subject: Disabling sound fade-in in Debian Buster^M
To: debian-user@xxxxxxxxxxxxxxxx
Since I moved my desktop to Buster I noticed each time a sound is
played there is a fade-in effect at the begining. The problem is short
duration sounds, like notifications, does not sound at all, or you
hear only the very end at low volume. A second play of the same sound
just after the first sounds fine.
This happens with any program playing sounds: DragonPlayer, VLC,
Audacity, System notifications...
It seems there is a tmeout somewhere and everytime the sound stars a
fade-in is produced. I revised pulseaudio configuration files, KDE
preferences and googled a lot but I found nothing.
--
A responder of the list mentioned this report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904822#17
Where this was suggested:
The audio issue is indeed fixed with:
options snd-hda-intel power_save=0
in /etc/modprobe.d/snd_hda_intel.conf.
--
Joel Roth
Other related posts:
