[FFADO-devel] Working on support for the AVID Adrenaline

[<si...@mu...>]

I picked up an AVID Adrenaline from local recycler for a bargin price, 
and although this is predominately a video capture solution it does have 
quite good audio capabilities. The video/audio capture can be 
dis/enabled independently so it can be used purely for audio....

Media Composer makes you choose a category of input and then you can 
enable up-to 8 inputs. Underlying hardware may be more versatile.

Capture inputs are as per attached image. It also has an onboard mixer 
for latency free listening.




So I started looking at FFADO thinking that it supports the DigiDesign 
Rack 003, turns out that wiki misled me and the files are just place 
holders. A bit of patching and the building now works, but I still need 
to fill in the actual code.

Seems that Alsa driver in Kernel is more complete and might also be a 
good reference. Both drivers misidentify the Adrenaline as the Rack, so 
I have blacklisted the kernel driver for now.
--
01200464437: Debug (devicemanager.cpp)[1253] setVerboseLevel: Setting 
verbose level to 6...
01200464451: Debug (devicemanager.cpp)[ 381] discover: Probing node 0...
01200500156: Debug (devicemanager.cpp)[ 381] discover: Probing node 1...
01200500179: Debug (devicemanager.cpp)[ 384] discover: Skipping local 
node (1)...
01200500252: Debug (DeviceStringParser.cpp)[ 390] show: 
DeviceStringParser: 0x55917adce200
01200500310: Debug (devicemanager.cpp)[ 556] discover: Probing node 0...
01200536103: Debug (configrom.cpp)[ 604] printConfigRomDebug: Config ROM
01200536124: Debug (configrom.cpp)[ 605] printConfigRomDebug:   Current 
Node Id:        0
01200536145: Debug (configrom.cpp)[ 606] printConfigRomDebug:   GUID:    
                0x00A07E0100085257
01200536152: Debug (configrom.cpp)[ 607] printConfigRomDebug:   Vendor 
Name:            Avid Technology
01200536160: Debug (configrom.cpp)[ 608] printConfigRomDebug:   Model 
Name:             Adrenaline
01200536167: Debug (configrom.cpp)[ 609] printConfigRomDebug:   Node 
Vendor ID:         0x00a07e
01200536173: Debug (configrom.cpp)[ 610] printConfigRomDebug:   Model 
Id:               0x00000001
01200536179: Debug (configrom.cpp)[ 611] printConfigRomDebug:   Unit 
Specifier ID:      0x00a02d
01200536186: Debug (configrom.cpp)[ 612] printConfigRomDebug:   Unit 
version:           0x00014001
01200536192: Debug (configrom.cpp)[ 613] printConfigRomDebug:   ISO 
resource manager:   1
01200536197: Debug (configrom.cpp)[ 614] printConfigRomDebug:   Cycle 
master capable:   1
01200536203: Debug (configrom.cpp)[ 615] printConfigRomDebug:   Bus 
manager capable:    0
01200536208: Debug (configrom.cpp)[ 616] printConfigRomDebug:   Cycle 
clock accuracy:   100
01200536214: Debug (configrom.cpp)[ 618] printConfigRomDebug:   Max rec: 
                10 (max asy payload: 2048 bytes)
--

Back to Adrenaline; My biggest challenge is going to be figuring out the 
protocol, as noted above I have Media Composer working on WinXP to drive 
it - but I don't have a Firewire analyzer (as yet).


I have experimented around and found a block of addresses which return 
'conflict' and I am wondering if this is the same behavior with the Digi 
Rack (which uses address like 0xffffe0000004 for setup).
--
$ sudo firewire-request /dev/fw1 read 0xfffff0e00000
conflict error
--
thru...
--
$ sudo firewire-request /dev/fw1 read 0xfffff0e0081c
conflict error
--
Anyone got any hints on what to try next?

Ping me if you want to collaborate on getting the Adrenaline or Digi 
Rack working.
Simon.