Page 1 of 4 123 ... LastLast
Results 1 to 10 of 34

Thread: Focusrite Saffire LE

  1. #1
    Join Date
    Apr 2006
    Beans
    99

    Focusrite Saffire LE

    I've just got a Focusrite Saffire LE (firewire audio device, that is), on the strength of FreeBoB and FFADO support for it. However, even though it's recognised by the system I can't get jackd to play nicely.

    Using qjackctl, I get an error stating "cannot complete execution of the processing graph (Resource temporarily unavailable)", followed by jack crashing. Naturally there's no sound or anything...

    I'm not sure how to debug and fix this problem - can anyone help?

  2. #2
    Join Date
    Apr 2008
    Beans
    3
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Focusrite Saffire LE

    I have the same problem with M-Audio Delta 1010LT card.

    With a lot of googling I was able to get pulseaudio to work at all. (This is due to a fact that the M1010LT uses ice1712 driver that has no channel named 'Master' and that craps the pulse out)

    The system was working flawlessly. jackd, ardour, system sound, the works.

    Then I played some guitar lesson videos with Totem firefox plugin and they did not work. The video was really slow and no sound. Tweaking the plugin enabled / disabled for some reason made the videos to display correctly but only for one web session. Didn't get it working after that at all. Huge problems by the way with almost all good video players with selecting sound driver. Totem was only one to play any sound. However Totem really is NOT my favourite video player (or audio for that matter)

    I don't know if it's anyway related but now I don't have any sound. The pulse audio for some reason does not start any more and jackd was complaining that the alsa hw:0 was already in use.

    So I removed the pulseaudio with apt-get and reinstalled alsa. Reboot. Still the system complains the hw:0 is in use.

    So I restarted alsa with sudo /sbin/alsa force-reload

    After that jackd starts up (using qjackctl) but gives me a tons of 'cannot complete execution of the processing graph (Success)' and then
    jackd: no process killed

  3. #3
    Join Date
    Apr 2008
    Beans
    3
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Focusrite Saffire LE

    Oh yeah, forgot to mention that I will really soon install Ubuntu Studio 7.10 back if this is really the story with hardy. Gutsy version worked without a single hickup.

  4. #4
    Join Date
    Apr 2006
    Beans
    99

    Re: Focusrite Saffire LE

    No, I don't think we have the same problem at all. Mainly because I'm using jackd and a firewire audio card and I'm not doing anything with pulseaudio (`pasuspender qjackctl` is your friend)

    Look, here's the log output:

    Code:
    17:53:42.703 Patchbay deactivated.
    17:53:42.756 Statistics reset.
    17:53:42.765 ALSA connection graph change.
    17:53:42.963 ALSA connection change.
    17:54:12.979 Startup script...
    17:54:12.979 artsshell -q terminate
    17:54:13.401 Startup script terminated with exit status=256.
    17:54:13.401 JACK is starting...
    17:54:13.402 /usr/bin/jackd -v -R -P89 -m -dfreebob -dhw:0 -r48000 -p256 -n2 -D
    17:54:13.404 JACK was started with PID=12942.
    getting driver descriptor from /usr/lib/jack/jack_dummy.so
    getting driver descriptor from /usr/lib/jack/jack_oss.so
    getting driver descriptor from /usr/lib/jack/jack_freebob.so
    getting driver descriptor from /usr/lib/jack/jack_alsa.so
    jackd 0.109.2
    Copyright 2001-2005 Paul Davis 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
    JACK compiled with System V SHM support.
    server `default' registered
    registered builtin port type 32 bit float mono audio
    registered builtin port type 8 bit raw midi
    clock source = system clock via clock_gettime
    loading driver ..
    new client: freebob_pcm, id = 1 type 1 @ 0x8070108 fd = -1
    Freebob using Firewire port 0, node -1
    new buffer size 256
    LibFreeBoB MSG: FreeBoB Streaming Device Init
    LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.7
    LibFreeBoB MSG: Device information:
    LibFreeBoB MSG: Device options:
    LibFreeBoB MSG: Port : 0
    LibFreeBoB MSG: Device Node Id : -1
    LibFreeBoB MSG: Samplerate : 48000
    LibFreeBoB MSG: Period Size : 256
    LibFreeBoB MSG: Nb Buffers : 2
    LibFreeBoB MSG: Directions : 0
    showDevice: not implemented
    17:54:14.039 ALSA connection graph change.
    FreeBoB MSG: Register MIDI IN port dev1c_Midi In
    FreeBoB MSG: Register MIDI OUT port dev1p_Midi Out
    FreeBoB MSG: Streaming thread running with Realtime scheduling, priority 93
    FreeBoB MSG: Registering audio capture port C0_dev1c_Rec 1
    FreeBoB MSG: Registering audio capture port C1_dev1c_Rec 2
    registered port system:capture_1, offset = 1024
    registered port system:capture_2, offset = 2048
    FreeBoB MSG: Registering audio capture port C2_dev1c_Rec 3
    FreeBoB MSG: Registering audio capture port C3_dev1c_Rec 4
    FreeBoB MSG: Registering audio capture port C4_dev1c_Rec 5
    FreeBoB MSG: Registering audio capture port C5_dev1c_Rec 6
    FreeBoB MSG: Don't register capture port for dev1c_Midi In
    FreeBoB MSG: Registering playback audio port P0_dev1p_Play 1
    FreeBoB MSG: Registering playback audio port P1_dev1p_Play 2
    FreeBoB MSG: Registering playback audio port P2_dev1p_Play 3
    FreeBoB MSG: Registering playback audio port P3_dev1p_Play 4
    FreeBoB MSG: Registering playback audio port P4_dev1p_Play 5
    FreeBoB MSG: Registering playback audio port P5_dev1p_Play 6
    FreeBoB MSG: Registering playback audio port P6_dev1p_Play 7
    FreeBoB MSG: Registering playback audio port P7_dev1p_Play 8
    FreeBoB MSG: Don't register playback port dev1p_Midi Out
    registered port system:capture_3, offset = 3072
    registered port system:capture_4, offset = 4096
    registered port system:capture_5, offset = 5120
    registered port system:capture_6, offset = 6144
    registered port system:playback_1, offset = 0
    registered port system:playback_2, offset = 0
    registered port system:playback_3, offset = 0
    registered port system:playback_4, offset = 0
    registered port system:playback_5, offset = 0
    registered port system:playback_6, offset = 0
    registered port system:playback_7, offset = 0
    registered port system:playback_8, offset = 0
    ++ jack_rechain_graph():
    client freebob_pcm: internal client, execution_order=0.
    -- jack_rechain_graph()
    FreeBoB MSG: MIDI threads running with Realtime scheduling, priority 92
    FreeBoB MSG: MIDI queue thread started
    libiec61883 warning: Established connection on channel 0.
    You may need to manually set the channel on the receiving node.
    libiec61883 warning: Established connection on channel 1.
    You may need to manually set the channel on the transmitting node.
    12942 waiting for signals
    17:54:14.219 ALSA connection change.
    17:54:15.434 Server configuration saved to "/home/chris/.jackdrc".
    17:54:15.435 Statistics reset.
    17:54:15.436 Client activated.
    17:54:15.439 JACK connection change.
    17:54:15.442 JACK connection graph change.
    new client: qjackctl, id = 2 type 2 @ 0xb7ed6000 fd = 17
    ++ jack_rechain_graph():
    client freebob_pcm: internal client, execution_order=0.
    client qjackctl: start_fd=7, execution_order=0.
    client qjackctl: wait_fd=16, execution_order=1 (last client).
    -- jack_rechain_graph()
    load = 2.1283 max usecs: 227.000, spare = 5106.000
    load = 3.2393 max usecs: 232.000, spare = 5101.000
    load = 3.8041 max usecs: 233.000, spare = 5100.000
    load = 3.9084 max usecs: 214.000, spare = 5119.000
    load = 3.9043 max usecs: 208.000, spare = 5125.000
    load = 4.0804 max usecs: 227.000, spare = 5106.000
    load = 4.2060 max usecs: 231.000, spare = 5102.000
    load = 4.1469 max usecs: 218.000, spare = 5115.000
    load = 4.0798 max usecs: 214.000, spare = 5119.000
    load = 4.0088 max usecs: 210.000, spare = 5123.000
    load = 4.0951 max usecs: 223.000, spare = 5110.000
    new client: hydrogen-tmp, id = 3 type 2 @ 0xb7ed5000 fd = 20
    removing disconnected client hydrogen-tmp state = Not triggered errors = 0
    removing client "hydrogen-tmp"
    removing client "hydrogen-tmp" from the processing chain
    17:54:27.964 JACK connection graph change.
    ++ jack_rechain_graph():
    client freebob_pcm: internal client, execution_order=0.
    client qjackctl: start_fd=7, execution_order=0.
    client qjackctl: wait_fd=16, execution_order=1 (last client).
    -- jack_rechain_graph()
    new client: Hydrogen-1, id = 4 type 2 @ 0xb7ed5000 fd = 20
    registered port Hydrogen-1:out_L, offset = 7168
    registered port Hydrogen-1:out_R, offset = 8192
    ++ jack_rechain_graph():
    client freebob_pcm: internal client, execution_order=0.
    client qjackctl: start_fd=7, execution_order=0.
    client Hydrogen-1: in subgraph after qjackctl, execution_order=1.
    client qjackctl: wait_fd=19, execution_order=2 (last client).
    -- jack_rechain_graph()
    unknown destination port in attempted connection [alsa_pcm:playback_1]
    ++ jack_rechain_graph():
    client freebob_pcm: internal client, execution_order=0.
    client qjackctl: start_fd=7, execution_order=0.
    client qjackctl: wait_fd=16, execution_order=1 (last client).
    -- jack_rechain_graph()
    removing disconnected client Hydrogen-1 state = Not triggered errors = 0
    removing client "Hydrogen-1"
    removing client "Hydrogen-1" from the processing chain
    ++ jack_rechain_graph():
    client freebob_pcm: internal client, execution_order=0.
    client qjackctl: start_fd=7, execution_order=0.
    client qjackctl: wait_fd=16, execution_order=1 (last client).
    -- jack_rechain_graph()
    17:54:28.018 ALSA connection graph change.
    17:54:28.060 ALSA connection change.
    load = 3.1445 max usecs: 117.000, spare = 5216.000
    load = 3.5505 max usecs: 211.000, spare = 5122.000
    load = 3.7160 max usecs: 207.000, spare = 5126.000
    load = 3.9019 max usecs: 218.000, spare = 5115.000
    load = 4.0792 max usecs: 227.000, spare = 5106.000
    load = 3.9522 max usecs: 204.000, spare = 5129.000
    load = 4.0106 max usecs: 217.000, spare = 5116.000
    load = 4.1242 max usecs: 226.000, spare = 5107.000
    load = 4.2091 max usecs: 229.000, spare = 5104.000
    load = 4.2797 max usecs: 232.000, spare = 5101.000
    load = 4.3337 max usecs: 234.000, spare = 5099.000
    load = 4.2482 max usecs: 222.000, spare = 5111.000
    load = 4.2055 max usecs: 222.000, spare = 5111.000
    load = 4.0622 max usecs: 209.000, spare = 5124.000
    load = 4.1688 max usecs: 228.000, spare = 5105.000
    load = 4.1095 max usecs: 216.000, spare = 5117.000
    17:54:48.050 ALSA connection graph change.
    17:54:48.051 Shutdown notification.
    17:54:48.055 JACK is stopping...
    17:54:48.056 JACK is being forced...
    cannot complete execution of the processing graph (Success)
    zombified - calling shutdown handler
    17:54:48.063 JACK has crashed.
    17:54:48.096 ALSA connection change.
    17:54:48.257 JACK was stopped successfully.
    17:54:48.257 Post-shutdown script...
    17:54:48.257 killall jackd
    jackd: no process killed
    17:54:48.667 Post-shutdown script terminated with exit status=256.
    17:54:57.200 ALSA connection graph change.
    17:54:57.303 ALSA connection change.
    I know a number of users on this forum claim to have got this device working 'out of the box', so I'd really, really like to hear from someone who is using Focusrite Saffire-series devices - no offence, beepo, but I've got an M-Audio Delta 44 that works perfectly with Ubuntu (just not on a laptop, obviously)...

  5. #5
    Join Date
    Aug 2006
    Beans
    141

    Re: Focusrite Saffire LE

    Is this the device that warranted the new freebob release? You may need to compile that from source and see what happens.
    Want to learn about Recording in Linux?
    Need audio hardware you know will work with Linux? http://www.linuxstudiopro.com

    checking whether we are using the GNU Fortran 77 compiler... no

  6. #6
    Join Date
    Apr 2006
    Beans
    99

    Re: Focusrite Saffire LE

    Quote Originally Posted by robeast View Post
    Is this the device that warranted the new freebob release? You may need to compile that from source and see what happens.
    I don't believe it is, but I can't find any information to back up that belief.

    I've got a bit further - the problem with Hydrogen's driver seems to be that the ~/.hydrogen/hydrogen.conf uses the deprecated alsa_pcmlayback swtich rather than systemlayback, ie:

    Change:
    Code:
          <jack_driver>
                <jack_port_name_1>alsa_pcm:playback_1</jack_port_name_1>
                <jack_port_name_2>alsa_pcm:playback_2</jack_port_name_2>
                <jack_transport_mode>USE_JACK_TRANSPORT</jack_transport_mode>
                <jack_connect_defaults>true</jack_connect_defaults>
                <jack_track_outs>false</jack_track_outs>
          </jack_driver>
    to

    Code:
        
            <jack_driver>
                <jack_port_name_1>system:playback_1</jack_port_name_1>
                <jack_port_name_2>system:playback_2</jack_port_name_2>
                <jack_transport_mode>USE_JACK_TRANSPORT</jack_transport_mode>
                <jack_connect_defaults>true</jack_connect_defaults>
                <jack_track_outs>false</jack_track_outs>
            </jack_driver>
    Which stops the driver errors when starting Hydrogen, but I still get no sound. I seem to have found the range of jackd options that keep the driver stable - but I don't get any sound output, and transport controls don't work either.

    I have read somewhere that the device needs to be 'initialised' by installing it on a Windows system first and downloading the latest firmware - does anyone know the truth of this?

  7. #7
    Join Date
    Aug 2006
    Beans
    141

    Re: Focusrite Saffire LE

    Quote Originally Posted by prismatic7 View Post
    I have read somewhere that the device needs to be 'initialised' by installing it on a Windows system first and downloading the latest firmware - does anyone know the truth of this?
    I've also heard this of some devices but not of the Saffire LE. I'm pretty sure that the LE is not officially supported by freebob. Since it is probably very similar to the Pro and regular saffire it should work here and there but will probably be spotty with different computers.
    Want to learn about Recording in Linux?
    Need audio hardware you know will work with Linux? http://www.linuxstudiopro.com

    checking whether we are using the GNU Fortran 77 compiler... no

  8. #8
    Join Date
    Jun 2008
    Beans
    11

    Re: Focusrite Saffire LE

    Quote Originally Posted by prismatic7 View Post
    [/code]Which stops the driver errors when starting Hydrogen, but I still get no sound. I seem to have found the range of jackd options that keep the driver stable - but I don't get any sound output, and transport controls don't work either.

    I have read somewhere that the device needs to be 'initialised' by installing it on a Windows system first and downloading the latest firmware - does anyone know the truth of this?
    Hi,

    I've had lots of issues using the Focusrite Fapphire LE with Ubuntu 8.04 but have finally figured it out, so I may be able to assist.

    1. Forget the Freebob drivers, they don't work properly with this device, I found there was no sound out and the driver would keep crashing.

    2. Forget the windows initialization thing; unless you can keep it powered between each system it's pointless, and is just not practical or necessary. If it is an older unit then updating the firmware may be a good idea but can apparently also be done in linux. My own unit serial number is an 08 (i.e. 2008) and is fine.

    3. You need to install the Freebob driver, which I personally found very tricky, but the main issue is that you need to ensure that you satisfy the dependencies. Make sure you install g++ and follow the instructions on the ffado website which detail installation under Ubuntu 8.04 - but again check the dependencies, you can do this by making sure you have the dependencies for freebob:

    sudo apt-get build-dep freebob

    install all the depencies and follow the installation instructions for ffado AND JACK as per:

    http://www.ffado.org/?q=node/613

    but don't install freebob - if you have installed it remove it then run the above command.

    Under 8.04 generic kernel you will get xruns and I found Jack would drop intermittently (this isn't cpu speed related).

    Therefore install the package for the realtime kernel "linux-rt"

    reboot into the -rt kernel and fix your graphics card if broken. (ensure you sort the graphics driver details before rebooting)

    Optionally when you have sucessfully installed and booted into the realtime kernel you can then do a synapitc search for "ubuntu studio" and install those packages.

    Don't bother running jackd in terminal unless you wish to.

    Open Jack Audio Connection Kit and see if the device will start and run.

    If it won't you may need to change the firewire port from default to 1. Other issues are beyond the scope of this guide and may be beyond me! but you can ask on this forum and I'll do my best, or you can subsribe to ffado-user mailing and/or ffado-dev which is well maintained and extremely helpful.

    The LE version will run a samlpe rate up to 96000 and I've found it rock solid once but you may need to adjust the settings to do that and ensure you firewire connection is up to scratch as this can easily introduce problems.

    I really like "gscanbus" and personally I've found it very stable (though other's haven't) and if the device is working there then your connection is good, if there are errors or a question mark on your device in the gui then you have a more fundemental problem. Once Gscanbus is showing your system is good then your ready to install ffado with some assurance that the basic firewire is working which for me was 25% of the battle!

    Also please register your device on the ffado website, when it is installed (not before).

    Jenny

  9. #9
    Join Date
    May 2008
    Beans
    786
    Distro
    Ubuntu Studio 12.04 Precise Pangolin

    Re: Focusrite Saffire LE

    Hello Jenny,

    So I am taking this as a "Yes" that you managed to get the Saffire LE working in Ubuntu?

    I am seriously considering purchasing this card, but I DID notice that only the Saffire was listed both under the old FreeBob as well as FFADO. The Saffire LE only had a FFADO listing.

    I am a bit hesitant to buy the Saffire LE as supposedly the FFADO support is not fully completed yet. So I wasn't sure if there were any issues or not with the LE. Otherwise if there were still issues with FFADO, then I would opt for the original Saffire, which seems to be supported with both. The only thing is that while the Saffire does have 192khz capability, I do prefer the 4 inputs of the the LE and I know the Saffire's DSP function will not work in Linux. Not to mention it is $50 more.

    But if you managed to get the Saffire LE to work, then great! Do you have the full 96khz support AND midi working with that as well?

    Thanx,

    Geo
    Exit Light, Enter Night, Take My Hand, We're Off To Never Never Land.
    As the Fios Flea says, "W-O-W"!

  10. #10
    Join Date
    Jun 2008
    Beans
    11

    Re: Focusrite Saffire LE

    Hi Geo

    Quote Originally Posted by jukingeo View Post
    So I am taking this as a "Yes" that you managed to get the Saffire LE working in Ubuntu?
    Yes it is working great at up to 96khz. It really is a superb box, and I've kept it running with jack for a couple of days without any drop outs or xruns.

    I haven't used the midi myself but I can tell you that it is recognised by jack so it is fair to say that it is probably working.

    I am seriously considering purchasing this card, but I DID notice that only the Saffire was listed both under the old FreeBob as well as FFADO. The Saffire LE only had a FFADO listing.
    The Sapphire LE doesn't really work with Freebob and from what I've read and on the reasonable assumption that they are basically the same unit from the software perspective the Sapphire (standard) woudn't work reliably with freebob either.

    I tried freebob with my Sapphire LE, there was no sound out and it frequently dropped the connection.

    I am a bit hesitant to buy the Saffire LE as supposedly the FFADO support is not fully completed yet. So I wasn't sure if there were any issues or not with the LE. Otherwise if there were still issues with FFADO, then I would opt for the original Saffire, which seems to be supported with both.
    You will likely have the same issue with the Sapphire and LE version so I wouldn't use that in your reasoning when making the purchasing decision.

    My advise is download and install ffado BEFORE you buy anything, if it installs ok then your ready to connect something to it, I found that this stage can take some time if you've not done it before and is a prerequisite for the Sapphire (inc. LE).

    The only thing is that while the Saffire does have 192khz capability, I do prefer the 4 inputs of the the LE and I know the Saffire's DSP function will not work in Linux. Not to mention it is $50 more.
    I myself struggled with this dilemma myself. For $50 it might be nice to have the Sapphire (standard version) but as I live in rip off Britain the difference is 50 pounds sterling which is significantly more.

    I was advised that the perceptual difference between the 24bit / 96 khz and 24 bit /192 khz is negligible and of course you have to worry more about the disk space it consumes, I use the device for analytical purposes and would have chosen the 192khz version if it wouldn't mean that I would be paying so much for a DSP that I'll never be able to use.

    Fact is 96khz is very detailed, I use it with a Sennheiser K6 / ME66 and it gets all the detail I need for my purposes. There may also be increased likelyhood of xruns when running at 192khz.

    Personally I used the money I saved on the LE to by a better audio monitor! - and with that you CAN tell the difference

    Also the black LE looks better with my black Thinkpad, black Sennheiser Mic, black cables and black and yellow KRK monitor; this probably isn't a big issue but most things seem to have gone black and it is nice if the match - even if they do collect dust like it's going out fashion.

    Like so many things "you pay's yer money - yer takes ya choice!" There both excellent.

    Jenny

Page 1 of 4 123 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •