On Mon, 31 Dec 2012 11:10:31 -0500, Paul Davis wrote: Hello Paul. Thanks for asking. I'm hoping this is the way to use jack on both cards at the same time. I'd also like to configure most inputs as stereo pairs. I'm hoping mixers will then provide a single fader and pan control. -- John. (sorry the reply didn't go to the list initially)

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. 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'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. 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.

On Tue, 1 Jan 2013 08:51:45 +0000, Ben Bell wrote: Thanks. I've read the Jrigg article which Len linked to, so it's all a little clearer now. I'm optimistically hoping the quality of lock with RME cards, and smaller project size, will mean I don't get the problems you've encountered, initially at least. One noticeable difference between the .asoundrc for two 9652s I've been trying and the Jrigg example is that the latter doesn't use semicolons, where the former does. I guess they're optional/ignored. Do your two cards always get the same card number allocations after a reboot? Mine do not, which is why I want to use an alias assigned by Udev rather than card 0 (hw:0)... -- John.

On Tue, 1 Jan 2013 14:47:53 +0000, Ben Bell wrote: IRQ would be good, but I vaguely remember they can be set either by the OS or by the BIOS. A setting in the BIOS could be either "Plug and Play OS" or not, iirc. I wonder if that setting has any bearing on this. -- John.

On Tue, 1 Jan 2013 10:24:18 -0800, Len Ovens wrote: Great stuff again Len. Thank you. I now have a file in /etc/modprobe.d/ called blacklist-hdmi_sound.conf which contains: blacklist snd_hda_intel blacklist snd_hda_codec Now aplay -l just lists the two RMEs, which is just what I wanted. I've also had more success modifying the JRigg .asoundrc, to the extent that qjackctl now shows all 52 channels as r/w clients in the connections widget. I won't be needing quite so many output channels, so I'll probably use the separate in/out configuration as demonstrated in the JRigg article. It's currently an all duplex config. -- John.