Saffire LE

Support Status: 
Full Support
Manufacturer: 
Focusrite

Comments

Hi,

I have the Saffire LE connected to my installation of Studio to Go 2.0, which now supports Firewire audio through Freebob.

The audio side of things work fine. I can see all inputs and outputs of the Saffire LE. However, when the system boots and recognises the device, it says there are no usable Midi ports available.

Using the JACK connections utility, on the Midi tab the Midi In/Out/through ports show up, but when I connect anything to them, no midi commands are received or sent. I also have an old cheap sound card on this system and the Midi In/Outs on that are recognised and are working.

Any ideas?

Thanks

Ian

Hi, is your Saffire LE working properly ?
I'm intending to buy one, but I would like to be sure it actually works under Linux.

Thank you

Hi fellow focusrite owners,

My unit is still not functioning because jackd does not see the drivers.

I have posted my progress to my blog.

http://livemorelightly.com/2008/09/21/ubuntu-hardy-free-firewire-drivers...

If anyone can help me sort this out I would appreciate the help.

I seem to have the driver installed and now my problem is with jackd.

See the blog post for details.

Vixmusic01

I have a working Saffire LE using Ubuntu 8.10. Everything worked with packages downloaded from launchpad but the ffado mixer would not work. I compiled from source and everything works perfectly. My laptop is a Gateway 450ROG with the dreaded Ricoh chipset. I am having no problems at all.

# jackd -d firewire -d fw1 -v
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2009 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
00178445258: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0- built Jun 15 2010 22:27:01
00178696367: Warning (ieee1394service.cpp)[ 375] initialize: Could not set SPLIT_TIMEOUT to min requested (1000000)
00178696537: Warning (ieee1394service.cpp)[ 379] initialize: Set SPLIT_TIMEOUT to min requested (1000000) did not succeed
00179980387: Warning (StreamProcessor.cpp)[ 707] getPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 24000.000000, diff: 24000.000000 ( 0.500000)]
00199455745: Warning (devicemanager.cpp)[ 994] waitForPeriod: XRUN detected
00199483558: Warning (StreamProcessor.cpp)[ 389] putPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 271.186441, diff: 47728.813559 ( 0.994350)]
00199483707: Warning (TimestampedBuffer.cpp)[1053] incrementFrameCounter: (0x7fbea80094f0) difference rather large (+): diff= 720896.332, max= 1536.000, 1960719916.000, 1959999019.668
00199732586: Warning (StreamProcessor.cpp)[ 707] getPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 27.957299, diff: 47972.042701 ( 0.999418)]
00199748288: Warning (StreamProcessor.cpp)[ 707] getPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 22901.339546, diff: 25098.660454 ( 0.522889)]
JackAudioDriver::ProcessAsync: read error, skip cycle

hi, after a wile playing well,
it stops with this error message
and jackd cant be restarted

any hints?

40174625835: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0- built Jun 15 2010 22:27:01
11:36:20.833 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the oPCR[0] plug for node 0.
firewire ERR: Could not start streaming threads
Cannot start driver
JackServer::Start() failed with -1
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
Cannot connect to the server
no message buffer overruns
Failed to start server

Hi,

have spent significant time trying to get to the bottom of this problem. I'm running a the realtime kernel, have enabled 1394raw, compiled and installed ffado related packages and jack. FFADO mixer seems fine in that it detects the saffire when its plugged in and displays normally. However, when I start jack i get the following error

23:29:19.031 Patchbay deactivated.
23:29:19.078 Statistics reset.
23:29:19.382 ALSA connection graph change.
23:29:19.579 ALSA connection change.
23:29:51.763 Startup script...
23:29:51.765 artsshell -q terminate
sh: artsshell: not found
23:29:52.167 Startup script terminated with exit status=32512.
23:29:52.168 JACK is starting...
23:29:52.168 /usr/bin/jackd -P70 -dfirewire -dhw:0 -r48000 -p128 -n2
jackd 0.119.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 758211
23:29:52.201 JACK was started with PID=4522.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
00092820543: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0-1883 built Sep 5 2010 23:29:43
23:29:54.252 Server configuration saved to "/home/ori-cool/.jackdrc".
23:29:54.254 Statistics reset.
23:29:55.056 Client activated.
23:29:55.058 JACK connection change.
firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver
23:29:57.740 JACK connection graph change.
23:29:57.864 JACK connection change.
no message buffer overruns
cannot read server event (Success)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)

One strange thing is that jack still says:

Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 758211

but I have since edited limits.conf and removed the memlock unlimited line. It is as if its not reading the updated file????

any suggestions very welcome also am new to ubuntu

cheers,

Orion.

First: by removing that line from limits.conf, you basically limited locked memory to a much smaller value (most probably 0). And it only "updates" that value when you log in.

I can't say anything about your firewire-problem as you didn't show us any of the things asked for in the README-file...

Thanks for your reply

Sorry for being such dunderhead. I didn't delete the any lines I just modified it from:

@audio - memlock unlimited

to

@audio - memlock 758211

as suggested in the JACK messages dialogue. Limits.conf now contains the following:

@audio - rtprio 70
@audio - memlock 758211
@audio - nice -10

But I still get the warning about setting th memory lock to unlimited when i start jack?

Am rel new to ubuntu and ffado so forgive my ignorance. Which README file contains relevant troubleshooting info?

thanks again fo your help,

Orion.

My guess: You are not part of the audio-group. Or you haven't done logout-login after the change.

But this is very much a jack (usage) issue, nothing ffado-specific. You will get the same messages/complains when using jack with the alsa-backend on your internal soundcard.

I agree that the problem is to do with JACK functionality not specifically FFADO. However I am a member of the audio group and successfully use JACK with a USB audio interface. So the problem is specific to JACK cooperating with the FFADO driver, but unfortunately I can't isolate the problem.