Show
Ignore:
Timestamp:
05/01/08 16:09:34 (4 years ago)
Author:
jwoithe
Message:

MOTU: Name channel pair control widgets in mixer. Disable channel pair widgets for the moment since they are not implemented.
MOTU: In mixer python glue code, renamed pan object handlers to generic control handlers since they can be used for more than just the pan controls.
Fix minor grammar issues in registration dialog.
In registration module, ensure the ffado configuration directory exists before trying to save information into it. The test is still a bit rough and could be made more robust.
ffadomixer: explicitly set the size of the toplevel tab widget to that of the mixer it contains. Without this for me on Qt 3.3.8 the ffado mixer window is created way too small. The solution is a bit hacky and could possibly do with refinement.
ffadomixer: don't include the generic mixer controls for MOTU devices since they don't give us anything useful yet and could be a source of confusion for users.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/libffado/doc/motu_firewire_protocol.txt

    r1064 r1085  
    1 Notes on the MOTU Traveler/828MkII firewire protocol 
    2 ==================================================== 
     1Notes on the firewire protocol used by MOTU audio devices 
     2========================================================= 
    33 
    44Author: Jonathan Woithe 
    5 Document version: 20080428-1 
     5Document version: 20080501-1 
    66 
    77 
    …… 
    5656packet) and 0x488 at 4x rates (giving 32 blocks per iso data packet). 
    5757 
    58 The traveler usually becomes the IRM on the firewire bus it is plugged into; 
     58The Traveler usually becomes the IRM on the firewire bus it is plugged into; 
    5959when functioning as the IRM it also broadcasts "cycle start" packets on a 
    6060regular basis as would be expected. These appear to be as per ieee1394-1995.  
    …… 
    3493490x00000009 for Traveler).  Therefore the best bet at this stage appears to be  
    350350a probe for a vendor ID of 0x000001f2 with one of the above version values 
    351 in the unit directory of the config ROM. 
     351in the unit directory of the config ROM.  Unit directory versions for MOTU 
     352hardware are as follows: 
     353 
     354  0x00000001 = The original 828 
     355  0x00000003 = 828 Mk 2 
     356  0x00000005 = 896HD 
     357  0x00000009 = Traveler 
     358  0x0000000d = Ultralite 
     359  0x0000000f = 8pre 
    352360 
    353361Alternatively one could probe for registers known to exist on only one of 
    354 the interfaces.  The trim gain / 20 dB pad status register (0x0c1c) is an 
    355 obvious choice since these features are only present on the Traveler.  At 
    356 this stage however this seems to be unnecessary. 
     362the interfaces.  The trim gain / 20 dB pad status register (0x0c1c) for 
     363example can be used to differentiate a Traveler from an 828Mk2 since these 
     364features are only present on the Traveler.  At this stage however the unit 
     365version number is probably sufficient and far less complicated in the long 
     366run. 
    357367 
    358368 
    …… 
    657667Bits 9-8 specify the mode of the optical input port: 
    658668  00 = off, 01 = ADAT, 10 = TOSLink (numbers given are in binary) 
    659 Register 0xb10 also plays a role in setting the optical input port mode. 
     669The "TOSLink" option is not available on the 896HD.  Register 0xb10 also 
     670plays a role in setting the optical input port mode. 
    660671 
    661672Bits 11-10 specify the mode of the optical output port in the same way 
    …… 
    863874 
    864875 
    865 Gain and pan value-dB mappings 
    866 ============================== 
     876Gain and pan value-dB mappings for the Traveler 
     877=============================================== 
    867878 
    868879The following gain map runs from 0x00 (-inf) to 0x80 (0 dB).  The dB values