Okay, not meaning to spam the mailing list, but I've got something interesting.

Managed to analyze the firewire bus with Perisoft Bus Hound. I'm about to have a look though everything now, but thought I should probably share it with everyone here first.

I just observed a few basic operations. Things such as when the device initially communicates with the Windows driver. Sending and receiving audio. Changing volume and sample rate.

Also, I'm pretty sure it is BeBoB, the first thing that it sends over the Firewire bus is the string "bridgeCo".

Enjoy!

https://www.dropbox.com/s/tmyidxjjypqqoeg/projectmix-dump.zip

Regards,
Darren


On 19 July 2013 15:28, Darren Anderson <darrena092@gmail.com> wrote:
So I went with that idea, added it to the configuration file and rebuilt ffado.

When starting the dbus server, it obviously then tried to use the BeBoB driver for the device, which resulted in a lot of errors. FCP transaction failed, it then couldn't configure the channels. Basically anything that could go wrong did.

Guess it's back to the drawing board. I'm going to have a play around with this to see if I can't managed to get it working even a little. I'll let you know how it goes on.

Regards,
Darren

(Just for clarity, a sample of the command line output is below)

1374243718762658: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1374243718762698: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1374243718762730: Error (bebob_avdevice.cpp)[ 560] getConfigurationIdSampleRate: Stream format command failed
1374243722771741: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1374243722771790: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1374243722771804: Error (bebob_avdevice.cpp)[ 597] getConfigurationIdNumberOfChannel: Number of channels command failed
1374243726779700: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1374243726779733: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1374243726779757: Error (bebob_avdevice.cpp)[ 597] getConfigurationIdNumberOfChannel: Number of channels command failed
1374243727465223: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1374243727465266: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1374243727465280: Error (bebob_avdevice.cpp)[ 629] getConfigurationIdSyncMode: Signal source command failed



On 19 July 2013 13:36, Clemens Ladisch <clemens@ladisch.de> wrote:
> Jonathan Woithe wrote:
> > The first step is to determine what underlying protocol is used by the
> > interface: is it a "standard" generic one like AVC (as used by BeBoB), DICE,
> > etc, or is it a completely proprietary one (like MOTUs use)?

It is obviously a BeBoB device:
http://www.maudio.co.uk/index.php?do=support.drivers&f=1230

Darren Anderson wrote:
> I'll have a go at it myself.

Find out the model ID ("ffado-test ListDevices"), add it to FFADO's
"configuration" file, and it will work as well as the Solo/Lightbridge/
NRV10 devices.  (I don't actually know them; do they need firmware?)

If you want play around with AV/C (FCP) commands, you'll need the
firewire-request tool from the jujuutils package:
<http://code.google.com/p/jujuutils/>.

> In the meantime, is there any recommended reading you would have for
> me on firewire?

The various AV/C standards aren't cheap, and AFAIK there is no
documentation for the BeBoB extensions.


Regards,
Clemens