Re: [LAU] JACK not working with Audiophile 2496 anymore

On 08/17/2014 02:56 PM, Roger wrote:
> On 17/08/14 18:04, david wrote:
>> I get these messages from JACK when I start it using QJackCtl,
>> trying to use my AudioPhile 2496. This is running on Debian Sid,
>> uname -a reports "3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09)
>> x86_64 GNU/Linux" (but I was getting the same error on kernel
>> 3.02.4 before that.) I am a member of the audio group.
>>
>> JACK starts and runs fine if I pick the "default" interface, but
>> that doesn't play any audio through the Audiophile. (I have no idea
>> what it's playing through.)
> I had a similar issue on my siduction audio workstation install. I'm
> using Cadence rather than QJackCtl but that shouldn't make any
> difference. I think Jack was trying to use hdmi audio which was
> card0. You need to make the 2496 card0 instead. I made an alsa conf
> file in /etc/modprobe.d/ with these lines: options snd_ice1712
> index=0 options snd_hda_intel index=1
>
> Now it works perfectly. Kernel is currently
> 3.16-1.towo-siduction-amd64 #1 SMP PREEMPT but 3.15 worked well
> also. siduction so far seems to be excellent for audio. I started
> building this dedicated to audio after several crashes with Mixbus in
> KXStudio which most likely related to Ubuntu-specific window
> management.

Thanks, that puts the cards in the right order ... will see if it
addresses my problem. Specifically selecting the Audiophile in QJackCtl
doesn't make it work, so I don't think it's because JACK is trying to
use audio device 0.

Anyway, it didn't fix the problem.

I tried this suggestion from Ralf:

> Four mails aren't allowed [1] , but perhaps you missed to uncheck
> something in the QjackCtl Setup... > Misc tab > [ ] Enable D-Bus
> interface

Enabling that option and restarting QJackCtl informs me:
ERROR: Driver is not running.
ERROR: Cannot open client name = dbusapi
ERROR: Failed to create dbusapi jack client

Selecting the HW:M2496 option from QJackCtl's dropdown and starting JACK
gave me this message:

DBUS: Jack server could not be started.

I never had to have DBUS enabled under QJackCtl's Misc tab to make the
2496 work before.

Also from Ralf:

>> self-connect-mode is "Don't restrict self connect requests"
>
> What does this message mean?

Haven't a clue. Don't particularly recall noticing it before.

> Perhaps you should start jackd by command line instead of QjackCtl.
>
> jackd -dalsa -dhw:0 -r48000 -p256 -n2

Tried that. The terminal window hangs a moment, then reports
"JackAudioDriver::ProcessAsync: read error, stopping..." Trying to start
Yoshimi with that window open only adds "Driver is not running, cannot
create new client." Changing the -dhw:0 to -d:hw:M2496 gives me the same
results.

Now let's try Ralf's other suggestion:

> At first I would clean the card configurations
>
> sudo -i mv /etc/asound.conf /root/ mv ~/.asoundrc /root/ mv
> /etc/modprobe.d/alsa-base.conf /root/
>
> and after that add a
>
> /etc/modprobe.d/alsa-base.conf
>
> with this content only:
>
> options snd slots=snd_ice1712
>
> Reboot and then start jackd again, using hw:0.

Can't find any "/etc/asound.conf"; wrong file name?

There's no .asoundrc in my home directory.

There's no alsa-base.conf file in /etc/modprobe.d. There's only the
alsa.conf created per Roger's instructions earlier. Let's try renaming
that to alsa-base.conf ... well, that was interesting. Doing that leaves
me with only the built-in devices: HDMI (card 0) and HDA ATI SB (card
1). Let's go back to what it was called before, at least the Audiophile
appeared on the list of options.

Now let's try Ralf's version of alsa-base.conf. That brought back the
Audiophile as card 0, but the other audio devices are still listed. And
JACK still reports "read error, stopping..."

Finally, a private email from James:

> You need to change your alsa configuration to force ICE1712 driver to
> card 1. I would also disable on board sound then troubleshoot the no
> sound issue. It only complicates things to have 2 cards..

Someone mentioned an alternative to QJackCtl, Cadence? Can't find that
in Debian Sid repository.

I see a qdbus and a qdbus-qt5 package in the repository. qdbus is
installed. Do I need to add the qdbus-qt5 package? The libqd5dbus5
package IS installed ... Trying to remove that lib offers to remove a
bunch of other QT5 libs, along with Luminance HDR graphics app.

Lets add the qdbus-qt5 package ... well, JACK still won't start from the
command line when I specify the Audiophile, which aplay -l lists as card 0.

When I had the onboard sound disabled before (via BIOS), ALSA would not
start at all. Let's try that again, just in case it simplifies things.
OK, now that aplay shows me the Audiophile as card 0 and HDMI as card 1.
Still doesn't work. Tried with default, Audiophile and ice_1712. They
all report the same problem.

For further test, booted an old Ubuntu Studio 12.10 CD I have here and
the Audiophile worked just fine. So I copied the
/etc/modprobe.d/alsa-base.conf file from the running US12 environment to
my system partition, rebooted, and QJackCtl starts jack with no problems
and Yoshimi is currently making lovely sounds through the Audiophile.
The only audio devices that appear are the Audiophile (card 0) and HDMI
(card 1).

So we can call this one fixed. Thanks for the info and help!

-- 
David W. Jones
gnome@email-addr-hidden
authenticity, honesty, community
http://dancingtreefrog.com
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user