From: Bruce Schultz <brulzki@gmail.com>
To: gentoo-user@lists.gentoo.org,Meino.Cramer@gmx.de
Subject: Re: [gentoo-user] Poor mans audio in the world of the great Jack D.
Date: Thu, 21 May 2015 12:59:45 +1000 [thread overview]
Message-ID: <DAC25043-59DA-4AE2-A76D-EEB65ABAF5D2@gmail.com> (raw)
In-Reply-To: <20150520162354.GA6013@solfire>
On 21 May 2015 2:23:54 AM AEST, Meino.Cramer@gmx.de wrote:
>Emanuele Rusconi <emarsk@gmail.com> [15-05-20 17:36]:
>> On 19 May 2015 at 17:24, <Meino.Cramer@gmx.de> wrote:
>> >
>> > The master control program (qsstv) raises its shield against Tron,
>displaying
>> > "Sound card error: Device or resource busy."
>> >
>> > And silence was the only voice heard by the folks...
>> > And nothing was displayed anymore.
>>
>> Oops, I forgot the last line of my koan:
>>
>> pcm.!default { type plug; slave { pcm "rawjack" } }
>>
>> -- Emanuele Rusconi
>>
>
>...and confusion reaches the head of great Jack D. and
>from his mouth the words were heard:
>
>#>sudo /etc/init.d/jackd restart
> * Starting JACK Daemon ...
>* JACK daemon can't be started! Check logfile: /var/log/jackd.log
> [ !! ]
> * ERROR: jackd failed to start
>[1] 6210 exit 1 sudo /etc/init.d/jackd restart
>
>...but none of his words, which were good and wise in the past, were
>written down for those who came after him:
>
>#>ls -l /var/log/jackd.log
>-rw-r--r-- 1 root root 0 2015-05-20 18:18 /var/log/jackd.log
>
>And the children - left alone in the dark of this ancient machine -
>stared into the empty LED eyes of their grandmaster not knowing
>to where to go and whether to flee or stand still...
>
>"Help - Oh help us brotheren of the Gentoo! Help!"
>they cried.
Perhaps the great Jack D. Is talking to itself?
The pcm.!default line says: when opening alsa, connect to rawjack
The earlier .asoundrc says: when opening alsa rawjack, direct the connection to the great Jack D.
If the jackd connects to the default alsa output, aka rawjack, coult it be tripping itself up? Is there maybe a jack option to direct the alsa output to the sound hardware instead?
--
:B
next prev parent reply other threads:[~2015-05-21 3:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 17:54 [gentoo-user] Poor mans audio in the world of the great Jack D Meino.Cramer
2015-05-18 18:39 ` Emanuele Rusconi
2015-05-19 15:24 ` Meino.Cramer
2015-05-20 9:12 ` Emanuele Rusconi
2015-05-20 16:23 ` Meino.Cramer
2015-05-20 17:28 ` Emanuele Rusconi
2015-05-20 17:49 ` Meino.Cramer
2015-05-20 18:59 ` Emanuele Rusconi
2015-05-21 2:08 ` Meino.Cramer
2015-05-21 2:17 ` Meino.Cramer
2015-05-21 2:59 ` Bruce Schultz [this message]
2015-05-21 3:18 ` Bruce Schultz
2015-05-22 8:00 ` Emanuele Rusconi
2015-05-19 0:26 ` [gentoo-user] " James
2015-05-19 15:29 ` Meino.Cramer
2015-05-19 18:03 ` James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DAC25043-59DA-4AE2-A76D-EEB65ABAF5D2@gmail.com \
--to=brulzki@gmail.com \
--cc=Meino.Cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox