On Fri, 8 Jun 2018 14:21:02 -0400
Greg Wooledge wrote:
> On Fri, Jun 08, 2018 at 08:13:24PM +0200, Holger Nessen wrote:
> > I'am not sure which sound backend you are using.
> > As far as I can remember, ALSA didn't allow multiple processes to
> > output sound at the same time.
>
> Depends on th
On Fri, Jun 08, 2018 at 08:13:24PM +0200, Holger Nessen wrote:
> I'am not sure which sound backend you are using.
> As far as I can remember, ALSA didn't allow multiple processes to
> output sound at the same time.
Depends on the hardware. If the hardware allows mixing natively, then
you can get
Hi,
I'am not sure which sound backend you are using.
As far as I can remember, ALSA didn't allow multiple processes to
output sound at the same time.
With other sound backends, e. g. PulseAudio this may change.
However, I don't have any clue, why this problem arises just after the
upgrade.
B
On Fri, 8 Jun 2018 16:33:45 +0200 (CEST)
Roger Price wrote:
> For nearly 20 years, I have had a cron job in which a dog (yes, it's Biff)
> barks
> the hours. The lines in /etc/crontab are
>
> 0 0,12 * * * rprice /mnt/home/rprice/bark/bark.sh 12
> ...
> 0 11,23 * * * rprice
For nearly 20 years, I have had a cron job in which a dog (yes, it's Biff) barks
the hours. The lines in /etc/crontab are
0 0,12 * * * rprice /mnt/home/rprice/bark/bark.sh 12
...
0 11,23 * * * rprice /mnt/home/rprice/bark/bark.sh 11
In the bark.sh script, the sound is produced
5 matches
Mail list logo
