AudioGNU/LinuxTechnology

Digidesign 002/003R/003R+ LINUX DRIVER!

digi002rack

003r+

003_Rack__31371_zoom

Linux_Logo

 

Digidesign Digi002, 003 Rack and 003 Rack+ now work in the Linux kernel using this driver.

 

Please consider donating a token amount for this work if you find it useful. ^^ See above donate page.

Get the driver code here on github.


sudo apt-get install build-essential linux-headers dkms
git clone git://git.zammit.org/snd-firewire-improve
sudo ln -s $(pwd)/snd-firewire-improve /usr/src/alsa-firewire-3.19
sudo dkms install alsa-firewire/3.19
sudo modprobe snd-digi00x

55 thoughts on “Digidesign 002/003R/003R+ LINUX DRIVER!

  1. Picked up a Digidesign Digi 003R to play around with and for the most part it worked. It can connect at 4800/4100 256 and all of the routing appears to work in Ardour 5.12.

    Unfortunately it generates a little pop/click every 5 to 7 seconds in the recording and output. This was using kernel 4.19 and 5.4 with and without snd-firewire-improve from takaswie.

    I’ve tried every possible combination of sample rates and periods within reason. No joy.

    Leaving a comment here in the hopes someone has encountered this issue and might know of a solution since I would like to keep it around as a backup for our FCA1616 interface.

    Cheers,
    Venn

  2. Hi Venn, I know about this issue, but currently there is nothing I can do about it. The driver needs to be redesigned to align to system timestamps because the packets themselves have zero in the timestamp SYT field. This is not easy to fix. Ask Takashi Sakamoto if he intends to fix this one day. See issue I raised in github here https://github.com/takaswie/snd-firewire-improve/issues/24 and looks like there is another report here: https://github.com/takaswie/snd-firewire-improve/issues/26

  3. Thanks for this. I got a very good deal on one of these and it indeed works with the 5.14 kernel. I can use it with ardour using ALSA directly and it works beautifully. I cannot start JACK however (cadence-logs gives very non-descriptive errors). Whenever I do get it to start, xruns just pile up very quickly. Have others had the same issues? Is there anything I can do to further examine the issue?

    Thanks again for this work.

Leave a Reply

Your email address will not be published.