No idea if this helps or not, but FWIW, I had two 1010's working in my studio for years without problems. I blogged about how I got em' to work. Link below:<br><br><a href="http://www.ilovemyjournal.com/?action=view_entry&eid=4773" target="_blank">http://www.ilovemyjournal.com/?action=view_entry&eid=4773</a><br>
<br>--Jason<br><a href="http://www.advancedbudgetstudios.com" target="_blank">www.advancedbudgetstudios.com</a><br><br><div class="gmail_quote">On Wed, Feb 1, 2012 at 2:24 PM, mn0 <span dir="ltr"><<a href="mailto:mn0@fukked-up.de" target="_blank">mn0@fukked-up.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just compiled jack1 but conflicts with jack2.<br>
Won't checkinstall...<br>
tried make install<br>
and it installs but doesn't work -<br>
undefined symbols.<br>
Doesn't overwrite all libs, as it seems.<br>
would have been good to test, if it's a jack2 specific problem.<br>
/mn0<br>
<br>
<br>
Am 01.02.2012 21:48, schrieb mn0:<br>
<div><div>> Am 01.02.2012 19:56, schrieb Joe Hartley:<br>
>> Hi, I've been using 2 Delta 1010s together for a while, I hope I can<br>
>> help a bit here. I've tried to put most of what I've learned on the<br>
>> web at <a href="http://delta.brainiac.com/deltasync.html" target="_blank">http://delta.brainiac.com/deltasync.html</a><br>
>><br>
>> On Tue, 31 Jan 2012 05:40:35 +0100 mn0 <<a href="mailto:mn0@fukked-up.de" target="_blank">mn0@fukked-up.de</a>> wrote:<br>
>>> I use Jack2, where can I find the exact version?<br>
>>> Only thing I know, it's jackdmp 1.9.7.<br>
>><br>
>> That should be fine, it's what I use as well.<br>
><br>
> compiled jack 1.9.8 yesterday - didn't help. Now back on 1.9.7.<br>
><br>
>>> The cards are hardware synced via S-PDIF.<br>
>>> In envy24control, a mixer program that knows about these features, hw:0<br>
>>> is set to internal clock and hw:1 is set to S-PDIF.<br>
>><br>
>> So far, so good. I'll assume you're using a real S-PDIF cable and not<br>
>> just an audio RCA cable.<br>
><br>
> Yep.<br>
><br>
>>> a)use .asoundrc<br>
>>> I have a .asoundrc from the web.<br>
>>> After a few seconds, it crashes saying this:<br>
>>><br>
>>> Unknown request 4294967295<br>
>>> Destination port in attempted (dis)connection of system:monitor_6 and<br>
>>> system:monitor_6 is not an input port<br>
>>> Unknown request 4294967295<br>
>>> Unknown request 0<br>
>>> Unknown request 0<br>
>> [ snip ]<br>
>><br>
>> Using the .asoundrc file to combine the cards into one logical device is<br>
>> what I consider to be the "correct" way of doing this, so I'll focus on<br>
>> that. Assumptions I'm making here:<br>
>> - the Deltas are the only 2 sound devices in the system. This can be<br>
>> verified by the command "cat /proc/asound/cards". On my system, this<br>
>> is the output I see:<br>
>><br>
>> [jh@xtc ~]$ cat /proc/asound/cards<br>
>> 0 [M1010 ]: ICE1712 - M Audio Delta 1010<br>
>> M Audio Delta 1010 at 0xdf80, irq 21<br>
>> 1 [M1010_1 ]: ICE1712 - M Audio Delta 1010<br>
>> M Audio Delta 1010 at 0xdf40, irq 20<br>
>><br>
>> If you have a motherboard that has an integrated sound chip, you might<br>
>> find your zero device is not a Delta, which is a problem. I had to disable<br>
>> my onboard sound card in my motherboard's BIOS settings.<br>
><br>
> Already is disabled.<br>
>><br>
>> - You have hw:0 and hw:1 identified correctly. Unfortunately, sometimes<br>
>> Linux has an issue with being able to consistently identify 2 identical<br>
>> soundcards. I've had this happen in the past and it gets annoying. I<br>
>> found it most liable to happen if I've made some other hardware change<br>
>> to the machine, otherwise it's usually stable across reboots. It's<br>
>> easily tested by using hw:0 to start jack and verifying that it<br>
>> addresses the ports on the card you believe to be hw:0.<br>
><br>
> Already done. They're both recognized and I know which hardware card<br>
> belongs to which device (always wondering after some time, so I check<br>
> that, first).<br>
>><br>
>> - You've got the right cards set as master clock and S/PDIF slave and that<br>
>> the correct ports on each are connected. I've gotten this incorrect on<br>
>> at least 2 occasions, so it's worth re-checking!<br>
><br>
> Already checked, now re-checked, it's ok.<br>
><br>
><br>
>> - The 2 1010LT's are not sharing any IRQs with other devices. "lsmod -v"<br>
>> command will show you the IRQs of all the PCI devices. The Deltas should<br>
>> have IRQs all to themselves. Here's my output edited to show just the<br>
>> Deltas. IRQs 20 and 21 are not shared with any other device.<br>
>><br>
><br>
> You mean "lspci -v". There seems to be a silly situation:<br>
><br>
> lspci -v | grep IRQ -B2 output(shortened to relevant IRQs):<br>
><br>
> 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI<br>
> Controller #3 (rev 01)<br>
> Subsystem: Foxconn International, Inc. Device 0c7e<br>
> Flags: bus master, medium devsel, latency 0, IRQ 18<br>
> --<br>
> 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE<br>
> Controller (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])<br>
> Subsystem: Foxconn International, Inc. Device 0c7e<br>
> Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18<br>
> --<br>
> 04:01.0 Multimedia audio controller: VIA Technologies Inc. ICE1712<br>
> [Envy24] PCI Multi-Channel I/O Controller (rev 02)<br>
> Subsystem: VIA Technologies Inc. Device d63b<br>
> Flags: bus master, medium devsel, latency 64, IRQ 22<br>
> --<br>
> 04:05.0 Multimedia audio controller: VIA Technologies Inc. ICE1712<br>
> [Envy24] PCI Multi-Channel I/O Controller (rev 02)<br>
> Subsystem: VIA Technologies Inc. Device d63b<br>
> Flags: bus master, medium devsel, latency 64, IRQ 18<br>
><br>
> So...SATA, USB and ICE1712 share one interrupt.<br>
> How can I change the interrupt of the devices, except by moving them to<br>
> another slot? Though I'd really like to get rid of this, I can't<br>
> imagine, this is responsible for<br>
> Jack: JackGraphManager::AssertPort port_index = 4294967295<br>
> Looks like a dangling or uninitialized pointer to me.<br>
><br>
><br>
><br>
>> 02:09.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)<br>
>> Subsystem: VIA Technologies Inc. M-Audio Delta 1010<br>
>> Flags: bus master, medium devsel, latency 64, IRQ 21<br>
>> I/O ports at df80 [size=32]<br>
>> I/O ports at dfa0 [size=16]<br>
>> I/O ports at df60 [size=16]<br>
>> I/O ports at df00 [size=64]<br>
>> Capabilities: <access denied><br>
>> Kernel driver in use: ICE1712<br>
>> Kernel modules: snd-ice1712<br>
>><br>
>> 02:0c.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)<br>
>> Subsystem: VIA Technologies Inc. M-Audio Delta 1010<br>
>> Flags: bus master, medium devsel, latency 64, IRQ 20<br>
>> I/O ports at df40 [size=32]<br>
>> I/O ports at ded0 [size=16]<br>
>> I/O ports at dec0 [size=16]<br>
>> I/O ports at de80 [size=64]<br>
>> Capabilities: <access denied><br>
>> Kernel driver in use: ICE1712<br>
>> Kernel modules: snd-ice1712<br>
>><br>
>> If the hardware's setup is verified as OK, look at how you're starting<br>
>> Jack. You didn't post the command used to start jack, so I can't say if<br>
>> it's starting the way you expect. If you use QJackCtl to start jack,<br>
>> the command that starts jack can be found by looking at the .jackdrc<br>
>> file.<br>
> I normally use QJackCtl, except for debugging this. QJackCtl froze and I<br>
> wasn't able to read the output. The command normally is:<br>
> /usr/bin/jackd -P89 -v -dalsa -r48000 -p256 -n4 -m -D -Cmulti_capture<br>
> -Pmulti_playback<br>
> but other frames/period, Priority etc. settings don't help.<br>
> I tried the settings from your page but without success.<br>
><br>
>><br>
>> Hope this helps, or at least gives you a starting point for troubleshooting.<br>
> Oh yes, I found the shared IRQs and I know for certain, it's possible to<br>
> use jack 1.9.7 with .asoundrc and two ICE1712.<br>
> Thank you!<br>
> /mn0<br>
><br>
> _______________________________________________<br>
> Linux-audio-user mailing list<br>
> <a href="mailto:Linux-audio-user@lists.linuxaudio.org" target="_blank">Linux-audio-user@lists.linuxaudio.org</a><br>
> <a href="http://lists.linuxaudio.org/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/listinfo/linux-audio-user</a><br>
><br>
_______________________________________________<br>
Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org" target="_blank">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/listinfo/linux-audio-user</a><br>
</div></div></blockquote></div><br>