Changes between Version 39 and Version 40 of digi003rack
- Timestamp:
- 07/04/12 21:14:58 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
digi003rack
v39 v40 160 160 ------ 161 161 162 It seems that after patching libraw1394 with the start_cycle patch, the iso streams turn on. 163 164 Since the maximum number of bytes the device can stream is 624 per packet, and there are 8000 iso firewire packets per second, and the device only supports 8 frames per packet, the maximum sample rate is 48000Hz using all 19 channels. I believe the device does not support ADAT channels in modes above 48000Hz. 162 Update July 2012: 163 Having done some more bus snooping, I discovered: 164 165 The device supports at least 2 main modes: 166 96/24 with 10 ins and 10 outs and 1 midi. 167 48/24 with 18 ins and 18 outs and 1 midi. 168 169 I modified the experimental DICE driver and this resulted in playback over all channels. Unfortunately the streams are glitching due to some async status packet being sent repeatedly from the device to the host for an unknown reason and causing iso dropouts (i think). 165 170 166 171 ------ 167 I have written a working ffado driver for playback. However there is one glitch: the device keeps sending the following async packet (during iso transmission) to the host expecting a response, and I don't know how to handle it, the pc just returns address error and the device continues sending the packets interrupting playback... update: this is because I have not initialised and allocated the ISO resources for the receive stream and the device is repeatedly sending a packet to ask me to do it (I think).168 {{{169 dest=0xffc2 (PC), write_block_request, src=0xffc1 (003Rack), offs=0xffff00000040, data=[00007051]170 offs=0xXXXXXXXXXXXX171 data=[00007058] if the stream dies.172 }}}173 174 where XXXXXXXXXXXX is a configurable address using a control packet which I have worked out.175 176 ----177 172 178 173 == 003 Rack Internal Mixer ==
