From: Pieter P. <pi...@jo...> - 2008-04-28 08:15:21
|
Jonathan Woithe wrote: > Hi Kostis > >>>> Is there something something a humble U/l owner could do to help :-) ? >>> To get me back on the right wavelength, could you describe to me what the >>> current ffado svn revision does with the ultralite in your case? >> Here's the post: >> http://sourceforge.net/mailarchive/forum.php?thread_name=478B9DC5.1070603%40gmail.com&forum_name=ffado-user >> >> The behaviour is exactly the same with the original author's both with jack >> and motutest. To sum it up for you: >> >> - Discover test seems to work fine. >> >> - In qjackctl I can see my INs/OUTs but no linking can be made and jackd >> gets stuck on the following: >> >> ... >> >> registered port system:playback_15, offset = 0 >> firewire MSG: Registering playback port P15_dev0_pbk_SPDIF20 >> registered port system:playback_16, offset = 0 >> firewire MSG: Don't register playback port dev0_pbk_MIDI0 >> ++ jack_rechain_graph(): >> client firewire_pcm: internal client, execution_order=0. >> -- jack_rechain_graph() > > Ah yes, it's slowly coming back to me. Thanks for this. > >> - Motutest fails with the following: >> ... >> Using first MOTU fw audio interface found: port 0 node 0 >> Read reg 0x4000 (mix 1 analog 1 mix controls): 0xff004000 >> Write 0xff004000 to reg 0x4000): 0 >> Read reg 0x4000 (mix 1 analog 1 mix controls): 0xff004000 >> Starting iso streaming tests. >> Note: code tries to set MOTU to 48 kHz and assumes ADAT is on. >> If the frequency setting doesn't work and/or ADAT is not enabled, >> operation of the iso test may not be as expected. >> Setting clock to internal 48kHz... >> Enabling iso streaming... >> Error doing motu write to register 0x000b00 >> Started >> stop > > Right, the problem is that the ultralite's streaming is not started in the > same way as for other MOTU interfaces. > > As I mentioned I will give some thought as to a way forward. The easiest > way to unravel the mystery is to do some protocol analysis but that requires > some specialised hardware. I'll be in touch with yourself and the other > Ultralite owners once I've cleared the remaining mixer-related tasks off my > plate. Something comes to mind here. What I did for the focusrite devices (before I had the mixer info) was scan the device's memory space using a second machine/host controller. Then I would compare it to the previous state. That would reveal the changes made by the windows control panel. And it doesn't need special hardware. Greets, Pieter |