trafficleft.blogg.se

1. #Saffire mixcontrol program install#
2. #Saffire mixcontrol program drivers#
3. #Saffire mixcontrol program driver#
4. #Saffire mixcontrol program pro#

The FSP40 is currently set to internal clock. When this happens I can hear some chirping fragments of the recorded sound.Īny ideas? It sounds like a syncing problem to me, but I don't know where to look for further cues.

Then I tried to loop a short piece of sound for a while, and in Ardour I can see that the cursor sometimes stops and moves in short skips, as if the transport doesn't work correctly all the time. I also had a look at the settings in the ffado-mixer, and they are identical too, apart from the sample rate. I have tried to increase buffer size in JACK, and still no playback sound. I have compared the setup to the 48kHz project, and all is identical, except the 48kHz still plays back correctly. I tried playing back a file directly to the firewire output with Audacity, and still nothing. The connections are correct, there are output levels at Ardours master out, and master out is connected to the firewire out channels. Connecting Ardour appears to work, as it is able to see input and record input, showing waveforms etc. I can get jackd to start, buffer size 128, and it presents all the firefire ins and outs as it should. However, I have problems getting things to work at 96kHz. I can use a buffer size of 64 samples, and run with a latency of 1.3 ms for tracking. It works prefectly when running at 48kHz.

I tested my friends FSP 40 today using the tweaks above. FYI my CPU is a 3.2 GHz 6 core Intel Xeon (plenty of CPU).

#Saffire mixcontrol program install#

I then installed a low latency kernel by doing "sudo apt install linux-lowlatency" (and of course updating grub), and now I don't see xruns anymore. Adding myself to the "audio" group and running jack in realtime gave fewer xruns than non-realtime mode, but still I would get an xrun once every 20 minutes or so.

Do this by appending the line "blacklist snd_dice" to the end of the correct file in /lib/modprobe.d (the correct file will be the one corresponding to your kernel, which in turn can be determined by running "uname -r").ģ) Lastly, I spent some time chasing down xruns. I could not get jack to start with the "firewire" backend until I blacklisted the snd_dice module.

#Saffire mixcontrol program drivers#

HOWEVER one issue that arises is that the ffado and snd_dice drivers do not play nice with eachother. This allows many other choices of buffer size, and provides access to the ADAT inputs for recording (I haven't tried sending audio to the ADAT outs, but I'm guessing it works). I am achieving this by selecting "firewire" as the jack backend, which only works after you do "sudo apt install jackd2-firewire".

#Saffire mixcontrol program driver#

It will only provide access to the analog line ins + SPDIF ins.Ģ) To get around these issues, you need to use the ffado driver instead of snd_dice. Secondly, the snd_dice driver cannot access the ADAT inputs. First of all, when using jack with the alsa backend (which uses the snd_dice driver), the interface can only be opened with two specific settings of the buffer size (256/3 and 256/2 in my case).

#Saffire mixcontrol program pro#

Because this driver comes stock with the kernel, it is possible to plug n play the Pro 40 (assuming your kernel version is high enough, mine is currently 4.4.0). This module is a driver for the DICE chip in the Saffire series interfaces. I wanted to contribute a few notes to anyone out there who might be trying to do the same as me (or possibly using a related Saffire interface).ġ) Currently, there is a kernel module called snd_dice that comes with the linux kernel, and is integrated into alsa. My specific use case is multi-track recording into reaper (I'm sure most people here know this, but there is a native reaper build for linux now).

I have been playing with getting my Pro 40 running in Ubuntu using jack.