Re: [LAU] asoundrc questions

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <len@...>
Cc: Linux Audio User <linux-audio-user@...>
Date: Tuesday, January 1, 2013 - 3:08 am

On Mon, 31 Dec 2012 16:42:01 -0800, Len Ovens wrote:

>

Thanks; yes I had a look at that thread, but it seemed to be concerned
with synchronisation, where that wasn't a feature of the cards. I have
the two RMEs connected internally. They have on board headers for the
purpose, and I'm fairly convinced that's working at least.

> As for mixers... which mixers? Any of the applications that provide mixers

It was the assignment of stereo channels in the example .asoundrc
which led me to believe it would be worth setting them up there, but
I'll not bother with those then. Your comments on which inputs are
best used together are much appreciated, thanks.

> I don't know how the rme cards work if they use phase lock loop to sync as

I'm afraid the link is a couple of old motherboard led/switch etc.
leads soldered together (which just happen to fit the headers). :)
Card 2 is showing sync lock on spdif in HDSPconf, so it should be fine.
I read some good things about the RME Multiface sync capabilities, but
I'm not sure how much better they are over the 9652s.

> Best of all, try it and see.

Indeed, and I've had my first core dump of the year already. Trying
to make too many changes at once caused it. But I can only get it
to work with the 'card N' designations. If I change instances of
those in my .asoundrc to the names they are given by the udev rule
(eg. s/card 0/RME_1/g) I get complaints like:

ALSA lib conf.c:1686:(snd_config_load1) _toplevel_:14:1:Unexpected char
ALSA lib conf.c:3406:(config_file_open) /home/john/.asoundrc may be old or corrupted: consider to remove or fix it

Without the ability to always have an alias (even if it's 'card 0')
pointing to the same card; a two card user can never know which one is
which after a reboot, which must be very confusing. I must be missing
some nugget of information somewhere. Or maybe it's just the extra unwanted
'card' in my system which is causing the variation of designation. The only
way I can test currently, is to discover which card is where with aplay -l,
adjust instances of 'card N' in the .asoundrc to reflect that, and then
log off/on and start the jack daemon.

The "unwanted card" is hdmi sound on my graphics card and I don't
know if I can disable it. That may be a workaround if I can...

--
John. 2013! This *must* be the future.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] asoundrc questions, John Murphy, (Mon Dec 31, 4:07 pm)
Re: [LAU] asoundrc questions, Paul Davis, (Mon Dec 31, 4:10 pm)
Re: [LAU] asoundrc questions, John Murphy, (Mon Dec 31, 4:33 pm)
Re: [LAU] asoundrc questions, Len Ovens, (Tue Jan 1, 12:42 am)
Re: [LAU] asoundrc questions, John Murphy, (Tue Jan 1, 3:08 am)
Re: [LAU] asoundrc questions, Len Ovens, (Tue Jan 1, 6:35 pm)
Re: [LAU] asoundrc questions, Len Ovens, (Tue Jan 1, 6:24 pm)
Re: [LAU] asoundrc questions, John Murphy, (Tue Jan 1, 10:48 pm)
Re: [LAU] asoundrc questions, Ben Bell, (Tue Jan 1, 8:51 am)
Re: [LAU] asoundrc questions, John Murphy, (Tue Jan 1, 2:42 pm)
Re: [LAU] asoundrc questions, Ben Bell, (Tue Jan 1, 2:48 pm)
Re: [LAU] asoundrc questions, John Murphy, (Tue Jan 1, 3:30 pm)