the LYNCH report

The Power of Clear Insight

Setting up an M-Audio FireWire Solo with Ubuntu/Linux…

with 247 comments

M-Audio FireWire Solo

***IMPORTANT UPDATE: one of our readers has advised that recent versions of the firmware for the FireWire Solo are responsible for issues relating to an inability to get sound output from the unit in Linux. If you encounter this issue, and have already tried the suggestions in the Comments section, please consider changing your firmware version to FW_WDM_5.10.0.5036.exe (the last known good version – many thanks, laban!)

You can find it here (opens in new window):

Please also note that you shouldn’t have to update or install any firmware – it ought to work out of the box.***

***UPDATE: we’ve received some feedback from the good people at M-Audio, who have advised against leaving the unit plugged in: “…we advise against using the AC power adapter when bus power is available; this often causes problems and can possibly damage the device.” Our previous instructions to leave the unit plugged in have therefore been deleted.***

I’ve responded to a number of questions as to how to get the M-Audio Firewire Solo recording interface up and running with Ubuntu/Linux. The Firewire Solo is a device which allows one to connect a microphone or guitar/instrument to a firewire input on your computer and allows for excellent transfer rates and low latency.

I’ve promised to put together complete instructions, so, at long last, here they are. If you have any questions/ issues/ suggestions/ comments or selected curse words, please feel free to comment below.

Before starting, I’d highly recommend installing the real time kernel if you want to get the lowest latency possible – you can find the kernel in the multiverse repository of Ubuntu’s Synaptic Package Manager as “linux-rt”.

The first thing you’ll need to do is get the JACK Audio Connection Kit and the qjackctl graphical interface. JACK is a tool which allows you to route sound signals to and from various applications, while qjackctl is a simple way to control JACK instead of using the command line. If they aren’t available from your distro (Ubuntu has them in the Multimedia (universe) repository and you can simply install them using Synaptic Package Manager) you can get them here:

You’ll also need QT4 (Ubuntu repository: “libqt4-core”) and freebob (Ubuntu universe repository under “libfreebob0″ – that last digit is a zero; NOTE: freebob support is now built into JACK, so you can skip installing it unless, for some bizarre reason, you insist on using an old version of JACK):

We’re also going to use Ardour to test/troubleshoot the M-Audio Firewire Solo, so you’ll need to install that. Ardour is an excellent digital audio workstation that works great with the Solo to create super-low latency recordings. Ubuntu users can get it via Synaptic (universe repository) – just search for “ardour”, mark it for installation and hit the “Apply” button. If you’re using a distribution that doesn’t make ardour available, you can download it here:

And, one last program you’ll want: gscanbus. This is a program you can use to reset your firewire bus if you run into problems – I’ve found it invaluable. Ubuntu users can find it in the universe repository and install it using Synaptic. Others can find it here:

Next you need to make the following change to add your user name to the “disk” group so that you’ll be able to get a 1394 handle (read: so you’re able to use the firewire port):

# useradd -G disk username

replacing your user name in “username”.

In order to run JACK with real time priority without being root, you’ll need to edit your /etc/security/limits.conf file. Open a terminal and type:

#sudo gedit /etc/security/limits.conf

That’ll bring up a text editor showing the contents of limits.conf. Add the following to the end of the file (but before the line “End of file” – that should remain the last line) and save it:

@audio – rtprio 99
@audio – memlock unlimited
@audio – nice -10

This allows the audio group the ability to get a priority of 99, allows it to use all the memory (you can use finite number if you want, expressed in bytes (ie: “512000″)), and makes it very unlikely to share resources (the lower the nice number the more CPU time a process gets). (**Thanks to Minghio for noticing I’d missed this important step!**).

OK, now you’re ready to start hooking up the FireWire Solo. Run a firewire cable from the back of your FireWire Solo to a firewire port on your computer. ***EDIT: we’ve received some feedback from the good people at M-Audio, who have advised against leaving the unit plugged in: “…we advise against using the AC power adapter when bus power is available; this often causes problems and can possibly damage the device.” Our previous instructions to leave the unit plugged in have therefore been deleted.***

Next, you’ll need to make a decision about what you’re going to route the output of the FireWire Solo to. There are several options: you can run a S/PDIF cable from the Out socket on the back of the Solo to the input of a receiver; you can run balanced outputs to an amp; you can connect a cable to the headphone output on the front of the Solo unit and run that to the sound card line-in input on your computer or you can simply use headphones – your call.

Once you’ve hooked up your output, plug a guitar or a mike or what have you into the Solo’s front panel. Make sure the “Input Select” button on the front of the Solo is in the out position (ie “front” is selected). Set the input dial to 3/4 and the output dial to 1/2.

Start up qjackctl. If you’ve installed it via Synaptic it should appear under the Sound & Video sub-menu of the Applications menu. Otherwise, you can simply type the following into a console:

#qjackctl

Click the “Setup…” button on the qjackctl panel and you’ll see the “Settings” page. Here are the settings you’ll want to select to get the M-Audio FireWire Solo up and running – you’ll be adjusting these later:

  • Server Path: /usr/bin/jackd
  • Driver: freebob
  • Interface: hw:0 (<–that’s a zero)
  • Audio: duplex
  • Input Latency: 0
  • Output Latency: 0
  • Realtime: check this box so an “X” appears
  • Priority: 89
  • Frames/Period: 256
  • Sample Rate: 48,000
  • Periods/Buffer: 3
  • Port Maximum: 256
  • Timeout (msec): 2000
  • Start Delay (secs): 2
  • Verbose Messages: check this box so an “X” appears

This will result in a latency of 16 ms, fairly high but you can reduce this later, once the M-Audio FireWire Solo is up and running. Click the “OK” button, closing the Setup menu. You’ll have to restart JACK for the settings to take effect: click the “Stop” button, then the “Start” button. Now click the “Messages” button so you can monitor the output of JACK, and also click the “Connections” button – this is where you can connect inputs and outputs of different applications to route them through JACK.

A word about latency: the formula for latency is:

Frames per Period X Periods per Buffer
Sample Rate

With our settings above therefore, it is 256 X 3 / 48000 = 0.016 secs or 16 ms.

Now a word about X-Runs: X-Runs occur when either there’s too much data flowing into your buffers and the buffers get overwhelmed or there’s not enough data flowing into the buffers and the program find the buffers empty. You want to avoid X-Runs at all costs – they cause popping and other noises in your recordings and just generally wreak havoc. Your goal should be to get the latency as low as possible without causing X-Runs. How low can you get it? On my set up the latency is 2 ms round trip and 0.7 ms one way to Ardour. The human ear can’t detect anywhere near there, but it’ll probably pick up the 16 ms we’re using for now.

OK, start up Ardour: if you used Synaptic it should appear under the Sound & Video sub-menu of the Applications menu. Otherwise, you can simply type the following into a console:

#ardour2

In the dialogue box, type “test” and click the “OK” button. The Ardour editor will appear. Click “Session” at the top left of the menu bar and select “Add Track/ Bus”, then click “+Add”. You now have a track to use for testing purposes.

If all has gone well, the connections box should now look like this:

qjackctl connections box

If the connection box doesn’t show the connections, you’ll have to connect manually: simply click “ardour” on the left, then “freebob_pcm” (the name may vary), then click “Connect”. Also click “freebob_pcm” on the left and “ardour” on the right and again click “Connect”.

Now in Ardour, click the red record dot on the track you added (Audio 1, left side of Ardour’s screen) and the master record button at the top of Ardour:

arm_ardour_to_record.png

Now click “Windows” in the menu bar and select “Show Mixer” – this will allow you to confirm your signal is making it through JACK.

OK, pick up your microphone/ guitar/ whatever and make some noise!

Do you hear anything? Does the level meter in the mixer window show any signal? If so, you’re good to go! Now you can go back to the Setup menu in qjackctl and start experimenting with reducing the latency – start by lowering the Frames/Period and testing for X-Runs. Other options to change (see explanation of latency above) are the Periods/Buffer (decrease this) and the Sample Rate (increase this).

If not, here are some common errors and their solution:

1) JACK won’t start and displays the error message:

15:39:14.900 Could not connect to JACK server as client. Please check the messages window for more info.

-Here’s where gscanbus comes in handy to reset your firewire bus. In a terminal console type:

#gscanbus

A box will pop up showing your firewire connections. Click “Control” and select “Force Bus Reset”. Now start up qjackctl and it should work.

2) The message window of qjackctl shows numerous X-Runs.

-Stop qjackctl, open the Setup window and change your settings to increase the latency. Try changing the Frames/Period to 1024 or reduce the sample rate to 44,100 and then restart qjackctl. Experiment with lowering the settings to find the lowest latency you can get without any X-Runs. Here’s a screenshot of my setup, which is rock-solid (I can leave it up for days on end without ever encountering an X-Run):

jack_settings_2ms.png

My computer is an AMD X2 6400+ (3.2Ghz) with 4GB RAM (at CAS latencies of 4-4-4-12). The OS and Ardour are on one HDD while recordings go onto 2 X 320GB Seagate drives in a RAID 0 array.

3) The mixer window in Ardour shows a signal but no sound comes out.

- Click “Options” from Ardour’s menu bar, select “Monitoring” and pick “Software Monitoring”.

4) Ardour’s mixer window shows nothing in the level meter while playing your instrument.

- Check the “Connections” box in qjackctl and make sure you have Ardour (“ardour”) connected to the Solo (“freebob_pcm” – may vary) and the Solo connected to Ardour. Expand each of the connections and make sure that you’re using the correct input (the guitar plug on the front of the FireWire Solo should be the second input); also ensure your outputs are connected properly in the right window: if you’re using S/PDIF, the connections from Ardour should go into the S/PDIF outputs in freebob_pcm (these should be the lower 2 connections). Otherwise, use the top 2 connections.

If your connections are OK and you’re still not getting sound, plug some headphones into the front of the FireWire Solo unit. Do you hear anything in the headphones? If so, check the physical connections between the outputs of the Solo and your receiver/ amp/ etc.

-If you don’t hear anything in the headphones, try cranking up the input dial on the front of the Solo and play your instrument (suggest you remove the headphones first – ear damage happens quickly and permanently) – does the clip light on the front of the Solo come on? If not, check the cable between your instrument and the FireWire Solo unit.

If none of that works, please leave a message in the comment box explaining your situation and I’ll try to help as best I can.

Please feel free to leave any comments/ suggestions/ corrections and happy recording!

About these ads

Written by westcoastsuccess

March 23, 2008 at 11:25 pm

247 Responses

Subscribe to comments with RSS.

  1. Thanks for the guide. It has been very useful for me, but I still have a problem.
    I’ve a lot of xrun, also not segnalated in the message window. What else should I try?

    Minghio

    April 9, 2008 at 12:27 am

  2. Thanks Minghio.

    Can you reply with your qjackctl settings for:

    -Frames per Period
    -Periods per Buffer
    -Sample Rate

    Also, what are you system’s specs? CPU? Memory?

    westcoastsuccess

    April 9, 2008 at 12:40 am

  3. Hi, I’ve an Acer notebook Intel Centrino Duo mobile with 2mb l2 cache and 2gb Ram DDR2 and an external usbdisk.
    I’ve installed Ubuntu Hardy beta with all the updates. Then I’ve installed the linux-rt kernel.
    I’ve configured Qjackctl like you in the second picture. But I received xruns also with an higher latency.
    I’ll post a picture of Qjackctl when I’ll be at home.
    I’ve read a lot of tread, maybe could be a problem of priority of my sound card?
    Thanks.

    Minghio

    April 9, 2008 at 1:07 am

  4. It can take a while to find the right combinations of settings – when I first set mine up I’d get X-runs all the time, then I got it down to once every 10 minutes (exactly), then none at all, ever.

    Couple of things it could be:

    -Make sure you have a check mark in the “realtime” box in qjackctl.
    -Try setting the “Priority” number to 89.
    -Are the X-runs happening at precise intervals (you can check this by setting the counter in qjackctl to show elapsed time since the last X-run). If it’s a consistent interval, you may have processes scheduled to run at that same interval, which are taking priority away from JACK. To make sure JACK is getting a good priority, start qjackctl, then try this, in a terminal:

    #ps -e

    (Omit the “#”). That will show all your running processes. Find “jackd” and “qjackctl”, and make a note of the PID numbers.

    #sudo chrt -f -p 99 3359

    Replace “3359″ with the PID number you noted in the prior step. Do this for both “jackd” and “qjackctl”.

    Type in terminal:

    #uname -a

    That will show which kernel you’re running and confirm you are indeed using the rt kernel. It should show something like this:

    #2.6.22-14-rt #1 SMP PREEMPT RT Tue Feb 12 03:54:33 UTC 2008 x86_64 GNU/Linux

    -Try launching qjackctl using sudo in a terminal:

    #sudo qjackctl

    If that cuts down the X-runs, it’s likely a permission issue.

    westcoastsuccess

    April 9, 2008 at 2:00 am

  5. Ok, I’ve tried to do what you told me.
    The xruns don’t happens at precise intervals. However I’ve done the commands about priority that you said.
    I’ve noticed that if I mark the “realtime” box, I can start jack server only if I run Qjackctl as a root.
    This is my kernel.
    Linux minghio-laptop 2.6.24-15-rt #1 SMP PREEMPT RT Tue Apr 8 02:25:55 UTC 2008 i686 GNU/Linux .
    I still have xruns, but no xruns messages in the message windows.
    Here you can see my setup of qjackctl
    http://farm4.static.flickr.com/3091/2400553699_c9d358f3e4_b.jpg
    Thank you very much

    Minghio

    April 9, 2008 at 9:30 am

  6. It’s a bit hard to see in the screen shot, but it looks to me like your settings are:

    Frames/Period: 64
    Sample Rate: 48,000
    Periods/Buffer: 3

    Which makes sense since 64 X 3 / 48000 = 0.004 and your latency is showing 4 ms.

    Try changing the Frames/Period to 128 and see if that reduces your number of X-runs (your latency will increase to 8 ms). I know you mention you’ve already tried higher latencies but give this a try if you haven’t already. It’s strange: it’s much more art than science trying to coax the best performance out of JACK. You might also try increasing the Periods/Buffer – I remember I had decent performance using 5 at one point. Everything else remaining unchanged in your settings, that should produce 6.67 ms latency.

    Also, what do you mean that the X-runs aren’t showing up in the message windows? How are you determining you’re experiencing X-runs then? Just by hearing cracks and pops in the sound?

    I’ll do some more research on the permission issue that prevents you from using Realtime except as root. When you do run it as root, does it reduce the number of X-runs?

    Cheers!

    westcoastsuccess

    April 9, 2008 at 6:59 pm

  7. PS: can you post the output of:

    #cat /proc/interrupts

    That will show the IRQ your M-Audio FireWire Solo is set to – here’s what mine looks like:

    ~$ cat /proc/interrupts
    CPU0 CPU1
    0: 322 0 IO-APIC-edge timer
    1: 0 2 IO-APIC-edge i8042
    7: 0 0 IO-APIC-edge parport0
    8: 0 0 IO-APIC-edge rtc
    9: 0 0 IO-APIC-fasteoi acpi
    12: 0 4 IO-APIC-edge i8042
    14: 56726 28432876 IO-APIC-edge ide0
    16: 67807 44710230 IO-APIC-fasteoi sata_sil24, ohci1394, nvidia
    20: 18892 3545983 IO-APIC-fasteoi sata_nv
    21: 25358 17970327 IO-APIC-fasteoi ehci_hcd:usb2, HDA Intel
    22: 6002 4302623 IO-APIC-fasteoi ohci_hcd:usb1, sata_nv
    23: 98924 67423091 IO-APIC-fasteoi sata_nv, eth0
    NMI: 0 0
    LOC: 847511201 735926713
    ERR: 0

    You can see mine’s at IRQ 16 (“ohci 1394″).

    You can then use:

    #chrt -f -p 90 `pidof “IRQ-16″`

    to set the priority of your FireWire Solo to 90 (it should be higher than your JACK priority, which you can set inside qjackctl; I recommend 89). The “-f” in the above command means “Set policy to SCHED_FIFO”, the “-p” is the priority you want to assign, and make sure you use the little tick marks – on a typical keyboard it’s found above the “tab” key at the top left corner of the keyboard.

    “SCHED_FIFO” means “First In First Out” scheduling. Here’s more info:

    SCHED_FIFO: First In-First Out scheduling

    SCHED_FIFO can only be used with static priorities higher than 0, which means that when a SCHED_FIFO processes becomes runnable, it will always preempt immediately any currently running normal SCHED_OTHER process.

    SCHED_FIFO is a simple scheduling algorithm without time slicing. For processes scheduled under the SCHED_FIFO policy, the following rules are applied: A SCHED_FIFO process that has been preempted by another
    process of higher priority will stay at the head of the list for its priority and will resume execution as soon as all processes of higher priority are blocked again. When a SCHED_FIFO process becomes runnable,
    it will be inserted at the end of the list for its priority. A call to sched_setscheduler or sched_setparam will put the SCHED_FIFO (or SCHED_RR) process identified by pid at the start of the list if it was runnable. As a consequence, it may preempt the currently running process if it has the same priority. (POSIX 1003.1 specifies that the process should go to the end of the list.) A process calling
    sched_yield will be put at the end of the list. No other events will move a process scheduled under the SCHED_FIFO policy in the wait list of runnable processes with equal static priority. A SCHED_FIFO process runs until either it is blocked by an I/O request, it is preempted by a higher priority process, or it calls sched_yield.

    westcoastsuccess

    April 9, 2008 at 7:19 pm

  8. I’m so sorry for the screenshot: I was in a hurry and I didn’t check it.
    Yes, I’m determining xruns just by hearing cracks and pops in the sound, beacause I’ve read something about it in the Freebob Faq: is it wrong?
    With the actual setup I’ve not xruns message.
    This evening I’ll try to do all the other thing you told me.
    Thank you very much. I really appreciate your support.

    Minghio

    April 10, 2008 at 12:47 am

  9. One thing to test is record something to Ardour, then play it back and see if the pops/noise appear in the same place when you play it back a few times. If they don’t, it may simply be a bad wire.

    westcoastsuccess

    April 10, 2008 at 12:50 am

  10. Ok, when I record it’s alright. I still have to run qjacktl as root. However thank you very much. I can start to learn Ardour now.

    Minghio

    April 10, 2008 at 2:21 pm

  11. That’s great, Minghio – glad to hear it!

    Feel free to post if you run into any other issues, and good luck with Ardour – it’s an excellent piece of software!

    Cheers!

    westcoastsuccess

    April 10, 2008 at 6:27 pm

  12. I’ve found the way to run Qjackctl without being root.
    I had to change these lines at /etc/security/limits.conf .
    @priv – rtprio 99
    @priv – memlock 512000
    @priv – nice -19

    Hope to be helpful. Cheers

    Minghio

    April 12, 2008 at 2:52 am

  13. Thanks Minghio – that’s a step I forgot to include in the instructions – I’ll amend them to include.

    Note that mine uses the “audio” group:

    @audio – rtprio 99
    @audio – memlock unlimited
    @audio – nice -10

    Thanks again!

    westcoastsuccess

    April 12, 2008 at 12:01 pm

  14. Hi again. Is it possible to send the normal output of Ubuntu, like mp3, film, etc to the Firewire Solo?
    I don’t know what to do because when I watch a film for example, I don’t have a new input in Jack and it goes automatically to the internal soundcard.

    Minghio

    April 14, 2008 at 3:16 pm

  15. You need to use a JACK enabled media player (you may need to compile them with JACK enabled).

    Try this: start qjackctl, then open m-player. Right-click anywhere in m-player, select “Preferences”, then select the “Audio” tab. Look for JACK in the list of available drivers and select it. Close m-player and then open a video or audio file with m-player (you can right-click on the file and select, “Open With”). A connection for the m-player should appear in the connections box of qjackctl.

    Have a look at this link:

    http://jackaudio.org/applications

    Scroll down to find a list of media players that are compatible with JACK.

    Cheers!

    westcoastsuccess

    April 14, 2008 at 3:45 pm

  16. A couple of days ago I switched from windows to ubuntu. I’m pleased, but I can’t get my firewire solo CD to run in Linux. Therefore I wonder if freebob work as a kind of replacement for the m-audio installation program, or if I have to somehow install the CD. If so, how can I install the program?

    hr_tetra

    April 26, 2008 at 5:14 am

  17. I also can’t find this in repository:

    linux-rt
    libqt4-core
    gscanbus

    hr_tetra

    April 26, 2008 at 5:56 am

  18. I found them! Looked the wrong place.

    hr_tetra

    April 26, 2008 at 7:29 am

  19. ok, now I’ve come a long way. I still wonder about the first question tough.

    when I try starting JACK with freebob it won’t start and I get this message:Is ieee1394 and raw1394 driver loaded?

    hr_tetra

    April 26, 2008 at 7:55 am

  20. If you’re talking about an installation disk for the M-Audio FireWire Solo, no, you don’t need it at all.

    The message you’re seeing tells you the firewire driver (raw1394) isn’t loaded. You can confirm this by typing the following in a terminal (omit the “#”):

    #lsmod

    and looking for “raw1394″.

    Do you have it installed (you can check by going to Synaptic and searching for libraw1394)? If not, install it. If it is installed, type this in a terminal:

    #modprobe raw1394

    If you want it to load automatically, you can add it to /etc/modules, however mine doesn’t appear in /etc/modules – it loads automatically at startup. To add to /etc/modules:

    #sudo gedit /etc/modules

    In the text editor that appears, add:

    raw1394

    Then save. You can reboot to check if it work – once rebooted, use the lsmod command as above to see your loaded modules.

    Let me know if that works or, if not, any error messages you’re seeing.

    Good luck and welcome to Ubuntu!

    westcoastsuccess

    April 26, 2008 at 12:34 pm

  21. Thanks for helping!!

    I still can’t get it to work, and I’ve done all above. It’s still the same message:

    new client: freebob_pcm, id = 1 type 1 @ 0x80700d8 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 : 3
    LibFreeBoB MSG: Directions : 0
    Ieee1394Service::initialize: Could not get 1394 handle: Permission denied
    Is ieee1394 and raw1394 driver loaded?
    Fatal (devicemanager.cpp)[68] initialize: Could not initialize Ieee1349Service object
    Fatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager
    LibFreeBoB ERR: cannot create libfreebob handle
    FreeBoB ERR: FREEBOB: Error creating virtual device
    cannot load driver module freebob

    hr_tetra

    April 26, 2008 at 1:31 pm

  22. Have you tried resetting your bus using gscanbus as described in the tutorial? If that doesn’t work, you have a permission problem. Try this:

    #modprobe raw1394
    #chmod a+rw /dev/raw1394

    Then re-open qjackctl and see if it starts. It should.

    To let all users access the firewire, do this (as always, omit the “#”):

    #sudo gedit /etc/udev/rules.d/40-linux1394.permissions

    In the text editor which appears, type this:

    #raw1394:root:root:0666
    #dv1394/*:root:root:0666
    #video1394/*:root:root:0666

    Then save the file.

    I think (but can’t recall) you may need to reboot (or at least log out and back in), but try it without and see if it works (ie start up qjackctl as your regular user; don’t use “sudo”).

    Let me know if that works.

    Cheers!

    westcoastsuccess

    April 27, 2008 at 5:33 am

  23. PS: do you have anything else connected via firewire (ie a camera, or MythTV with a firewire connection from a set top box)?

    westcoastsuccess

    April 27, 2008 at 5:38 am

  24. thanks again! really appreciate it!

    I actually can get JACk going, but only with “system” available in the connection window, and for that to happen I always have to have ardour going, or typing

    #sudo qjackctl

    in terminal.

    I have tried to type

    #gscanbus

    but then it says that raw1394 isn’t loaded. If I type

    #sudo gscanbus

    it opens fine and I can see my m-audio icon.

    I’ve done what you told me above. After typing

    #chmod a+rw /dev/raw1394

    it says I don’t have permission.

    I don’t know what to make of it. I don’t have anything else connected to firewire either.

    Thanks again for your help.

    hr_tetra

    April 27, 2008 at 9:26 am

  25. Sorry, I just upgraded my system to Hardy and I see it now shows “System” in the Connections window of qjackctl instead of “freebob” – same connections, just labeled differently.

    Sorry also, the correct command is:

    #sudo chmod a+rw /dev/raw1394

    Bad brain day…

    westcoastsuccess

    April 27, 2008 at 12:43 pm

  26. When I connect ardour from the output to the system input in the jack connection kit I get this static(? like a detuned radio) noise! Really freaks me out. When I connect a mic into the computer(not in m-audio, but directly to the computer) this sound is increasing and becoming whiny at really high-pitch. It’s also a little fascinating. I can actually hear every movement in line from the mic to the computer. Can’t get any signal from m-audio tough…:/

    hr_tetra

    April 27, 2008 at 4:14 pm

  27. Can you describe the physical output from the M-Audio? Also, what input are you using? If you plug the mic into the M-Audio, turn the input dial all the way up and speak (or yell) into the mic, does the red clipping light come on or blink on the front panel of the M-Audio?

    Also, can you post a screen shot of your alsa mixer settings? If you’re on Ubuntu, look for the icon that looks like a speaker at the top right. Right click and select “Open Volume Control”, then post a screen shot of each tab.

    Cheers!

    westcoastsuccess

    April 29, 2008 at 2:53 am

  28. I am using a firewire cable to connect the m-audio to the computer, just like the grey one in your picture, I presume. I got the exact same box. I have a mic in input 1 in m-audio. I get a signal and can see the clip react.

    I found out that the static starts when I choose software in monitoring(ardour). The static also dissapears when I turn off capture mux in alsa mixer(or the capture option in the recording tab i alsa mixer).

    Everything is turned up in alsamixer(sorry, don’t know how to put up screenshots here and I’m in a hurry right now). I have tried to click on/off in the switches tab where the only alternative is IEC958. The mic tab only hace the “mic” option.

    I also discovered there’s a lot of x-runs, I don’t really know what that is!

    It seems to me that the programs isn’t connected to the m-audio. I know I have sound in m-audio and the m-audio shows a connection to linux in gscanbus, but the levels in the mixer window only reacts to a mic directly in the computer. When I record from that mic the sound clip is filled with the same static as I’ve described earlier.

    hr_tetra

    April 29, 2008 at 9:22 am

  29. hi,
    I still cant get this to work,
    jack crashes every time with messages like:
    “FreeBoB ERR: FREEBOB: Error creating virtual device
    cannot load driver module freebob”

    and

    “JACK: unable to mlock() port buffers: Cannot allocate memory”

    also, gscanbus doesn’t seem to see my firewire solo at all,
    the only thing that appears in gscanbus is called “S400 Linux – ohci1394″
    i have the firewire solo plugged into my laptop through a firewire extension card plugged into the side of the machine,
    would that be whats causing the problem??

    Shane Kilkelly

    May 10, 2008 at 1:31 pm

  30. ^^^
    the firewire connection is a PCMCIA card

    Shane Kilkelly

    May 11, 2008 at 12:12 pm

  31. Sorry for the delay in responding, Shane.

    I don’t think gscanbus will work if the firewire connection is via an adaptor of any sort – I’ll do some more research and get back to you…

    Cheers!

    westcoastsuccess

    May 11, 2008 at 3:20 pm

  32. hr_tetra: check your connections in qjackctl – if you’re using a mic plugged into the Input 1, you need to set the connections differently than I’ve shown. You’ll need to use the top connection (“Capture 1″ ) in “freebob” (or “system”, as it’s called in the latest version) connection, rather than the second from the top, on the left side of the Connections box. The options in the Connections box correlate to the physical connections on the M-Audio FireWire solo as follows:

    From top to bottom on the left side of the Connections box under “freebob” or “system”:

    1. Microphone (“Input 1″ – the 3-pronged input on the far left of the FireWire Solo unit. Make sure the Input Selector button to the right of this input is in the out position (“front”)).

    2. Guitar (“Input 2″ – the guitar cord plug in the middle of the front of the FireWire Solo unit. Again, make sure the Input Selector button to the left of this input is in the out position (“front”)).

    3. S/PDIF Left

    4. S/PDIF Right

    If you want to use the Unbalance Inputs on the back of the FireWire Solo unit, push the Input Selector on the front of the unit so that “Rear” is selected (ie the button is in). The top input in the Connections box represents Unbalanced Input 1; the 2nd from the top represents Input 2.

    Let me know if that helps; if not, we’ll dig further into it.

    Cheers!

    westcoastsuccess

    May 11, 2008 at 3:35 pm

  33. Shane: can you please post the details of your PCMCIA card (model no., etc.)? Also, what kind of laptop are you using? There are known issues with IBM Thinkpads…

    Cheers!

    westcoastsuccess

    May 11, 2008 at 3:58 pm

  34. ah its ok, i just went out and bought a proper firewire cable for my 4-pin firewire socket,

    im getting the signal into ardour fine but i cant hear anything in tne headphones on playback,
    how do i connect this up in qJackctl? this is important because i mostly monitor off of the headphones.

    im not even sure if i have routed the signal in ardour properly either. can you give a quick rundown of the proper connections??

    thanks

    Shane Kilkelly

    May 15, 2008 at 2:59 pm

  35. ***EDIT: please see update at beginning of article – please DO NOT leave the unit plugged in if you have power available from the bus*** If you’re using a 4 pin firewire cable, make sure you always plug the FireWire solo into a wall jack.

    Here’s how the connections should look in qjackctl Connections window for a single mono audio track:

    Readable Clients____Writable Clients

    Ardour____________Ardour
    Audio 1/out1—–> master/in1
    Audio 1/out2—–> master/in2

    Ardour_________System
    auditioner/out1—> playback_1
    auditioner/out2—> playback_2
    click/out1———-> playback_1
    master/out1——> playback_1
    master/out2——> playback_2

    System_________Ardour
    capture_2——–> Audio 1/in1

    ***this assumes you’re using the guitar jack input (input2) on the front of the FireWire Solo and also that you’re not using S/PDIF.

    Which headphone plug are you connecting to, Shane? The computer’s or the FireWire Solo’s? If you want to use the computer’s, try running a cable from the headphone output on the FireWire Solo to a mic or line input on the computer. Use the dial on the far right of the FireWire Solo to control output. You should also make sure headphone output is enabled on the computer – on Ubuntu, click the speaker icon in the top panel and select Open Volume Control. Click the Switches tab and make sure there’s a check mark in the checkbox for Headphones.

    Also, in Ardour, click Options in the top menu bar, select Monitoring and try each of the 3 options. Mine’s set to External Monitoring.

    westcoastsuccess

    May 16, 2008 at 12:12 pm

  36. I’m having the nastiest time with this interface. I purchased it because it appeared to be well supported by freebob, but jeez.

    I can get sound out no problem, and have no xruns or other particularly weird behavior. load = 3.5338 max usecs: 200.000, spare = 5604.000 is typical for my output.

    But, when I play sound through jack, it’s constantly skipping! It’s extremely annoying and makes the system useless. There are no errors being reported, so I haven’t the foggiest where to try to fix things. Clips, brief pauses, it’s just nasty.

    To isolate the problem to jack, I used audacious. When I play a .mp3 through jack, it clicks like a yak in heat. When I play it through pulseaudio, it’s perfect. Neither uses any CPU really, so I just don’t get it.

    Please help! This makes no sense to me at all! My internal sound card is a POS, it shouldn’t be performing better than the solo.

    Brian Neltner

    May 16, 2008 at 1:00 pm

  37. Aha! For anyone else running into my problem, I fixed it by upgrading to the freebob 2.0 (i.e. ffado). It seems that the freebob driver is no longer under development, but the ffado driver has a lot of bugfixes (although I have no idea what bug, exactly, could have been causing my problem).

    Brian Neltner

    May 16, 2008 at 1:46 pm

  38. Glad to hear you found a solution, Brian – I’d have guessed it was a sample rate mismatch between qjackctl & the source material…

    westcoastsuccess

    May 16, 2008 at 1:56 pm

  39. na, im trying to use the Firewire solo headphone jack but not getting anything,
    any idea how to sort this out?

    Shane Kilkelly

    May 16, 2008 at 2:11 pm

  40. Shane: if you’re getting a signal in Ardour but nothing in the headphones on the FireWire Solo unit, the problem is likely the sound is not being routed back to the Solo properly.

    In the Connections box, click on Audio1 at the left pane, then try, in sequence, each of the outputs under freebob (may be shown as “System” ) in the right pane – just click on one of them, then click the Connect button.

    In case it’s not obvious, you click the litte “+” symbols to expand the connections and see the individual inputs/outputs – if you just click “Ardour” on the left and “freebob” (or “System” ) on the right, qjackctl makes a guess at your connections which may be incorrect.

    westcoastsuccess

    May 16, 2008 at 3:27 pm

  41. still nothing in the headphones,
    the outputs on the right in the connections window are labeled “Playback_1…4″
    and none of the 4 them seem to do anything.
    needless to say this is getting very frustrating! :)

    Shane Kilkelly

    May 17, 2008 at 9:28 am

  42. I’m having the problem with headphone outputs. It seems to be recording fine in Ardour, but I can’t get any output to the headphones. I’ve had every output from ardour going into every spot in freebob. My maudio outputs are labeled as

    dev1p_LineOut L
    dev1p_LineOut R
    dev1p_SpdifOut L
    dev1p_SpdifOut R

    Zach

    May 17, 2008 at 8:29 pm

  43. I upgraded to hardy and that fixed the having to start the programs as root user problem. And it renamed my freebob to system in qjackctl. But I still can’t get the headphone output to work.

    Zach

    May 17, 2008 at 11:27 pm

  44. I had a working setup for about a month. I recently used my interface with my friend’s mac, and when I plugged it back into my ubuntu laptop, all the in and out ports had been renamed and I can’t get any output from the headphones jack. The “guitar” input used to be input 2, but is now 4. I’ve tried connecting to all 4 outputs but I still can’t get any sound. I can see a signal in the ardour mixer, and “software monitoring” is checked. Does any one have any suggestions?

    Lynn

    May 22, 2008 at 9:24 am

  45. Lynn-
    that sounds like either the firmware was updated to a nasty version, OR the internal mixer settings changed.
    try this: plug into a mac or windows again, mess with the internal mixer software thing and then plug into the Ubuntu.
    i intend to try this out tomorow, i’ll let ye know how it goes.

    as far as i know,the internal mixer settings are persistent once they are set.
    i recall having to mess around with the internal settings while setting up to record on windows.
    id assume the same principal applies here but the difference is that this time we dont have access to the software mixer applet.

    Shane Kilkelly

    May 22, 2008 at 2:11 pm

  46. Apologies for the delay responding to everyone – just back from a trip to Vegas…

    Lynn: you can rename any of the connections in qjackctl – just right click on the connection you want to rename and select (not surprisingly… ) “Rename”. In fact, when you rename a track in Ardour, it should automatically appear under the same name in qjackctl’s Connections box. If it doesn’t, click “Setup” in qjackctl, select the “Display” tab, and make sure there’s an “x” next to “Allow client/port aliases editing”.

    For those of you having problems with getting sound OUT of Ardour (ie into the headphone jack on the Solo or otherwise), here’s what I’d suggest, starting with the most obvious:

    1) MAKE SURE THE TRACK YOU’RE PLAYING BACK IN ARDOUR IS NOT ENABLED FOR RECORDING. This means the little red button on the track should not be illuminated and the Record button should be neither red nor flashing. Also, obviously, the tracks should not be muted.

    2) Again, may seem obvious, but test the headphones in your computer’s headphone jack – do they work when you playback from Ardour? If not, do they work if you playback an MP3? If not, chuck them and get another pair.

    3) Try a different JACK-enabled application and see if that works. You can try M-Player – simply right click on the transport, select “Preferences”, then select the “Audio” tab. From the list of drivers, select JACK. Click OK. Then right click on the transport again and select “Open”, “From file…” and pick an MP3 or other audio material. You should see “MPlayer” in the left Connections panel in qjackctl – it ought to automatically connect to your outputs – if not, simply connect MPlayer to your outputs in the right pane. Can you hear anything in the headphones plugged into the FireWire Solo? What about plugging them into the onboard sound card’s headphone jack? If you can hear via either of those, there’s a problem with Ardour.

    4) Get a copy of Patchage – it’s in the Multimedia (universe) repository of Synaptic. Open it with qjackctl running and it’ll show you a different view of your connections – you can drag the different elements around if you need to get a better view of the connections. See if the connections make sense – to get sound out of Ardour, you need the tracks from Ardour to route to the output connections of the M-Audio FireWire Solo.

    5) In Ardour, click “Windows” in the menu bar, select “Track/Bus Inspector”, then click on one of the tracks, which you know has audio, in the left pane. Then click the “Outputs” tab – that’ll show you your connections in another way. Make sure the outputs you want are assigned to the track. Try each one and see if any work.

    6) Find a site that allows you to post screenshots and post a shot of the following, then leave a link for me here:

    a) Connections box (qjackctl).
    b) Ardour editor screen where you’ve captured tracks.
    c) Setup in qjackctl – ideally each of the tabs.
    d) Right click on the icon of a speaker in your desktop panel, select “Show Volume Control”, then take a screenshot of all the settings (you may need to widen the box to see all the sliders). Post the pictures.

    Leave either a detailed description of your physical connections or take a picture of the Solo unit showing what’s plugged where.

    7) Try a different firewire cable between the Solo and your computer. ***EDIT: Please see update at beginning of article: M-Audio advises against leaving the power plug in when you have power available from the bus.*** Always keep the power plug plugged into a wall outlet when using the M-Audio FireWire Solo.

    8)Re-read the instructions posted above – have you followed each and every step? What’s the contents of your /etc/security/limits.conf? Does it include the changes from the instructions?

    9) Have you recently upgraded to Hardy Heron? If so, pulse audio may be causing conflicts. take a screenshot of your settings and post them ona free site. Leave a link for me.

    10) Check Ardour’s log and see if any error messages are in there – if so, post them here.

    westcoastsuccess

    May 25, 2008 at 1:27 am

  47. Thx for the great tutorial. I am new to linux, so far I have my linux all setup except this firewire solo.. this is really killing me haha, I am still trying to make it work. good tutorial tho :) Thx man.

    Tim

    June 15, 2008 at 12:50 am

  48. Thanks Tim.

    If you’re still having trouble, please feel free to post the specific problem(s) and we’d be happy to help you get it up and running.

    Good luck!

    westcoastsuccess

    June 15, 2008 at 12:51 pm

  49. I have installed Ubuntustudio 8.04 for AMD64. I have followed your steps but I can’t to record no sound. Do you know if he is compatible with 64 bits? Do you know if besides recording it can serve like the card of sound predetermined by the system? Thanks

    Fran

    July 18, 2008 at 2:42 am

    • I had the same problem with ubuntu. I found the problem to be the firmware in my fw-solo device. The solution was to install an older firmware( from 2004) and then sound flows out of my earphones

      the firmware was named “FW_WDM_5.10.0.5036.exe”
      just remember to wash your hands after shuting down Windows.

      laban

      August 4, 2009 at 12:38 pm

  50. Hi Fran,

    Yes, it’s compatible with 64 bit systems – mine is an AMD_x64 6000+.

    When you try to record with Ardour, are the level meters in Ardour showing anything? What happens if you plug headphones into the front of the M-Audio FireWire Solo? Do you hear anything? What about headphones into your computer?

    If you’re getting a signal (indicated by the level meters in Ardour), make sure you have disabled the tracks you recorded on, otherwise they’ll remain enabled and will mute output. Click the small red button on the track(s) so they are no longer red. Then try playing the tracks.

    Anonymous

    July 18, 2008 at 4:20 am

  51. The level meters don’t show any signal.
    The headphones give the sound of the microphone but only in the left side.
    As much the clip of imput 1 as the clip of imput 2 is illuminated with a strong signal.
    The connections box in the Jack Audio connections Kit look like this: the name “freebob_pcm” vary for “system”). It is correct?

    Fran

    July 18, 2008 at 6:54 am

  52. OK, the signal is not making it out of the FireWire Solo (but it is making it in). If you know the cables you’re using are good, then it’s a connection issue in the Connections box of qjackctl.

    Have another look at the illustrations for the connections: in the Connections box, make sure you have this:

    system………………..ardour

    capture_2 —-> Audio1/In 1

    ardour………………..system

    Audio1/Out 1 —–> master/in 1
    Audio1/Out 2 —–> master/in 2
    master/out 1 —–> playback_1
    master/out 2 —–> playback_2

    You’re only hearing it in one side because you only have the output from Audio1/Out1 connected, in all likelihood.

    In the latest version of qjackctl, “system” substitutes for “freebob_pcm”.

    Let us know if that solves it for you.

    Good luck!

    westcoastsuccess

    July 18, 2008 at 8:56 am

  53. The connections are:

    system………….ardour:
    capture_1—> audio 1/in 1
    capture_2—> audio 2/in 2
    etc

    ardour……………ardour:
    Audio1/Out 1 —–> master/in 1
    Audio1/Out 2 —–> master/in 2

    ardour………………system:
    audiotioner/out 1 —–> playback_1
    audiotioner/out 2 —–> playback_2
    master/out 1 —–> playback_1
    master/out 2 —–> playback_2

    I have connected it as you say and follows without receiving signal.Some suggestion?

    Fran

    July 18, 2008 at 10:09 am

  54. Those connections are incorrect.

    If you have your mic plugged into “Input 2″ on the front of the FireWire Solo, then you’re going to need to go from “capture_2″ to “audio 1/in1″. If the track you set up in Ardour is a stereo track (it looks to me like you’ve set up 2 tracks, with at least the 2nd track being stereo), then run another connection from “Input 2″ to “audio 1/in2″. The way you have it set up explains why you’re only hearing output on one side when you use the headphones – you’re only connecting to the left side of a stereo track.

    Your Ardour to Ardour connections are correct, as are your Ardour to System connections.

    Does the change above work for you?

    westcoastsuccess

    July 18, 2008 at 4:22 pm

  55. I have the mic plugged into “Imput 1″ and the guitar into “Imput 2″. Bouth signals are received by the Firewire Solo. The PC detects the Firewire Solo (recognized in the administrator of devices), but Ardour don’t receive the signal. I have changed the connections of JACK but I can’t work with him. I have proven the changes with mono tracks and stereo tracks of Ardour.
    I hear the signal of the mic by the left side of the headphones and the signal of the guitar by the right side (independent of how they are the connections of Jack) but I dont hear any sound by the loudspeakers of the PC.
    Is it necessary to make some change in the configuration of the sound of Ubuntu?
    Can I send you the images of the configuration of the programs (JACK Control, Jack Audio connections Kit, Ardour, Mixer Ardour and Alsa mixer)? Perhaps you detect some error.

    Anonymous

    July 19, 2008 at 3:41 am

  56. Yes, please do. Enter your email address when you post a comment – it won’t display on the site, but I’ll be able to view it. I’ll send you my email address in return and you can send me some screen shots. We don’t use our visitor’s emails for anything, period. That’s our privacy policy. You should also review wordpress.com’s privacy policy, as they may have access to addresses input here.

    Alternatively, if you’re not comfortable with that, post the screen shots on a public site and post a link to them in a comment here.

    Also:

    1) Where are your headphones plugged in? Into the FireWire Solo? Or into your computer?

    2) How is the FireWire Solo connected to your computer? Which outputs are you using on the Solo and which inputs of your computer? Are you using a known good cable?

    3) Can you also post a screen shot of your volume applet? On your desktop panel, you should have an icon that looks like a speaker. Right click, then click “Open Volume Control”. Take screen shots of each tab (“Playback”, “Recording”, “Switches” and “Options”).

    4) A screen shot of Ardour’s editor window, showing your tracks.

    westcoastsuccess

    July 19, 2008 at 11:52 am

  57. My email address is : ********************
    1) I connect the headphones into the Firewire Solo
    2) With cable firewire and the output with a cable jack stereo from balanced outputs to the amp
    3) OK. I’ll send you in the email
    4) OK. Idem

    My PC configuration is in spanish. Some problems?

    Fran

    July 19, 2008 at 4:53 pm

  58. I’m having problems with the email service. They return the sender the messages that I sent you. When you had received nine images, please confirm the arrival. I’ll try to send you again.

    Fran

    July 20, 2008 at 6:28 am

  59. Fran: we’ve received all your images and have responded privately to your email address.

    Once the situation is resolved, we’ll post the solution here in the comments section for other visitors.

    westcoastsuccess

    July 21, 2008 at 1:56 am

  60. I’m still having problems with the email service. The say: “Failed; 5.1.2 (bad destination system address)”
    I’ve received your screen shots by means of friend’s email. I’m going to prove all the configurations that you sent me.
    There is something that I don’t understand: the connection of audio between the Solo and the PC:
    - It’s neccesary to run a firewire cable from the Solo into the computer. OK
    - It’s neccesary to run a cable from the headphone output of the Solo into a line-input on my computer. OK
    - But is it neccesary to run a cable from the bal outputs 1 of the Solo into the amp ?
    - Or is it neccesary to run a cable from the output of the computer into the amp?

    Fran

    July 21, 2008 at 6:45 am

  61. Martin: I have sent to you a email with two screen shots of Ardour in which I
    say to you that I have managed to record in audio 2 but not in audio 1
    and other questions.
    I don’t know if this email arrives to you. Please
    confirm it.
    Thanks
    Fran

    Fran

    July 23, 2008 at 2:21 am

  62. We’ve responded directly to you, Fran, including screen shots showing how you should be connecting.

    In case you don’t receive it, your problem is you have your guitar (or whatever you’re using) plugged into Input 2 on the front of the M-Audio FireWire Solo but are trying to record from capture_1 in the Connections box of qjackctl. When you add a second track, your connections change and now show (in the second screen shot you forwarded) a connection from capture_2 to Audio2/in1.

    Here’s the important thing to remember: the capture connections in the left side of qjackctl’s Connections box represent physical inputs on the Solo unit: capture_1 represents the microphone input on the front of the FireWire solo, labelled “Input 1″. Capture_2 is the guitar plug labelled “Input2″. The other connections represent the unbalanced inputs in the back of the Solo and the S/PDIF input, also on the back of the unit. If you have a guitar plugged into Input 2, you’ll ALWAYS use capture_2, whether you’re recording track 1 or track 10 or track 100.

    Have a look at the screen shots we sent and see if your set up works if you duplicate those connections – we’re pretty sure it will.

    westcoastsuccess

    July 23, 2008 at 2:49 am

  63. Firstly, thank you very much for detailing this process. I have had a Solo for 2 years now running on Windows and will be moving it to my beloved Linux box tonight, using your instructions.

    Now for the question. What is the advantage of recording through a firewire (or even USB for that matter) interface when you could simply use the “Line In” of a normal sound card ? That way would result in no latency, or buffer overruns whatsoever. Would the signal quality be inferior ?

    Grant Smith

    August 12, 2008 at 11:23 am

  64. Let us know if you run into any problems, Grant – we’ll be happy to help.

    There are a number of reasons why you would never want to plug into the line in on your computer (at least if you are doing anything other than screwing around a bit for fun only). The line in will direct the signal to your on board sound card. Many of these are extremely low quality, versus professional-level sound standards. They typically use very poor quality digital-to-analog converters (DAC) – among the worst are any soundblaster cards. The fidelity is awful, something which may not be immediately noticed if you output to typical computer speakers (also very poor), but which is decidedly noticeable if your intent is to ultimately have your music played over any system designed solely for the reproduction of sound – anything from a car deck to a proper stereo system. To be fair, soundblaster has gotten better over the years, but I can’t imagine any professional music being produced via SB, or any on board sound card!

    Additionally, you’d need to use an adaptor to convert a guitar or mic plug to the 1/8″ jack of your line in, which again can introduce sound degradation. On top of that, a guitar’s output signal (and most mics too, except those with built-in pre-amps) is too weak to be used in any meaningful way without a pre-amp, which the FireWire Solo provides. That boosts the signal to a line-level output, which you can then route to an amp, a stereo, back into your computer, etc. (Of course if you’re using a distortion pedal or some such, it would act as a pre-amp also).

    Contrary to your statement above, there would indeed be latency using the line in, and typically a LOT of it (relatively speaking). Our latency between the guitar/mic to Ardour is 0.7ms. Round trip it’s 2ms. That’s with a rock-solid setup (ie no X-runs, ever). You’ll really notice latency when you’re playing a guitar and there’s an ever-so-slight delay between when you strum the string and the sound actually gets recorded – you’re playing to tracks or a drum beat that you’re hearing immediately (and responding to) but it isn’t being recorded at that precise moment, so it throws the entire feel off. You still need a method to route the signal from your sound card into your recording software – even if you’re using an on board card, you’ll still need to use JACK or similar to get the output of the sound card to the input of your recording software.

    You’d still have to deal with buffers – the sound heading into the card doesn’t immediately get written to disk without delay, particularly when you’re playing back tracks and recording tracks simultaneously, which is almost always, unless you’re only ever recording live material. On board sound cards are designed to handle sound output (from games or apps or the internet or whatever), with sound input treated incidentally, and they allocate resources accordingly, both in their design and in their function.

    As an aside, in real-world situations, firewire is significantly faster than USB 2.0.

    But don’t take our word for it – we’d encourage you to experiment and come to your own conclusions. Depending on what you’re attempting to accomplish, an on board card can be the answer. We used to use a laptop with just the on board card and Cakewalk on a windows setup to put ideas down on, where accuracy and latency aren’t really important but capturing a moment’s inspiration is paramount. Nowadays it’s equally simple to set up a quick track in Ardour for a quick, down and dirty scratch take (and we also burned through three hard drives in the laptop…).

    Good luck, Grant! If you hit any snags, have a peek at the comments then leave a post if you’re still stuck.

    westcoastsuccess

    August 12, 2008 at 6:18 pm

  65. Wow !

    Thank you for a very detailed and interesting reply. You have convinced me to do some in-depth testing once I get this beast installed. I’m currently downloading the ISO for Ubuntu Studio and will be purchasing a new machine dedicated to recording with the FireWire Solo tomorrow. “Unfortunately” I’m off on a vacation trip for a week, so will only be able to focus on this in about two weeks :)

    Thanks once again for your valuable help!

    Grant Smith

    August 13, 2008 at 1:00 am

  66. Make sure you get the real time kernel – I can’t recall if it’s included in Ubuntu Studio or not – you can check by typing the following into a terminal (excluding the “#”):

    #uname -r

    The kernel version uname returns should be appended with “rt” – here’s ours:

    $ uname -r
    2.6.24-19-rt

    If it doesn’t come with the real time kernel, just go to Synaptic Package Manager and search for “real time”, then select “linux-image-rt” and it’ll install the real time kernel.

    If you’re new to Linux/Ubuntu, you may want to check our list of useful commands – we add to it regularly:

    https://westcoastsuccess.wordpress.com/2008/03/23/ubuntu-linux-workarounds/

    Enjoy the vacation – I’m envious!

    Cheers!

    westcoastsuccess

    August 13, 2008 at 2:17 am

  67. Howdy,
    Thanks for the wonderful tutorial. I can get JACK to work if I launch it from the terminal with SUDO, but it always throws up a permission error if launched via the menu. Using the latest version of Ubuntu Studio from the DVD ISO. I’ve gone through the process of adjusting the permission; however, I get an odd error message when trying to save the permissions file. Do you know if the ieee1394 permission are handled through some other mechanism in Ubuntu Studio that I’m trying to circumvent?

    Also, I too see levels and signal coming from the Firewire Solo; however, i cannot get playback to happen. The monitor panel in JACK look a bit different from your example in the tutorial. I see 4 different capture_1, etc. under system on the left and 4 playback_1, etc. on the right under system. There is no mention of freeBoB PCM, just system which can be expanded to show the ins and outs. I see a signal in Ardour with connections 3 and 4 going to a stereo track “Audio1″ on Ardour, but nothing comes out! I think I have the right connections for the output. I cannot se any signal from the S/PDIF which I have attached to a Tascam DAT deck either. I’ve checked all 4 capture_x ports by individually patching them to the “Audio1″ track in Ardour. I feel like i must be missing something, but I haven’t figured it out yet.

    Any help would be much appreciated.

    Dave

    August 28, 2008 at 9:04 am

  68. Glad you found the tutorial useful!

    Re: permissions: did you add your user to the “disk” group? See this part of the tutorial:

    Next you need to make the following change to add your user name to the “disk” group so that you’ll be able to get a 1394 handle (read: so you’re able to use the firewire port):

    # useradd -G disk username

    replacing your user name in “username”.

    In order to run JACK with real time priority without being root, you’ll need to edit your /etc/security/limits.conf file. Open a terminal and type:

    #sudo gedit /etc/security/limits.conf

    That’ll bring up a text editor showing the contents of limits.conf. Add the following to the end of the file (but before the line “End of file” – that should remain the last line) and save it:

    @audio – rtprio 99
    @audio – memlock unlimited
    @audio – nice -10

    Re: connection names: yes, these changed in a recent update to qjackctl – we’ll update the tutorial asap.

    Re: audio out: follow this trouble shooting procedure:

    1) Make sure you have dis-armed for recording the tracks you recorded to in Ardour. This means the red armed-for-recording square next to the track’s name should not be red, but rather black (or whatever your background is). Otherwise, your tracks will be precluded from playing back sound.

    2) Check your mixer settings. To do this, right-click on the icon which looks like a speaker on your desktop panel, select “Open Volume Control” and make sure none of the outputs are muted.

    3) Plug headphones into the M-Audio FireWire Solo unit and report back if you hear any playback.

    4) Plug headphones into your computer and report back if you hear any playback. You may need to enable headphones via your mixer – see 2) above, click the “Switches” tab in the Volume Control and ensure the “Headphones” box is checked.

    You’re 99% of the way there: sound is making it through the Solo and into Ardour and being recorded; it’s simply an issue now of routing the playback – you won’t see anything in the Tascam connection if the S/PDIF is routed from the Solo to the Tascam if it’s not making it back from Ardour to the Solo. The “Audio1-L” and “Audio1-R” in the LEFT side of the Connections window in qjackctl should route to “Master-L” and “Master-R”, respectively, on the RIGHT side of the Connections window. “Master-L” and “Master-R” on the LEFT side should route to the outputs you’re using on the RIGHT side (“Playback_1″, etc.).

    Let us know the results.

    Cheers!

    westcoastsuccess

    August 28, 2008 at 9:27 am

  69. Thanks for the prompt response, but I’ve already added ‘disk’ to my user account. In fact, when I attempted to add:

    #useradd -G disk ‘username’ //I get:
    useradd: user ‘username’ exists

    I’ve also added the 3 lines to the limits.conf file as well. Regardless, I still get permissions errors when starting either JACK or Ardour unless I launch from a terminal screen with sudo.

    Dave

    Dave

    August 29, 2008 at 5:54 pm

  70. Can you post the changes you made to /etc/security/limits.conf?

    westcoastsuccess

    August 30, 2008 at 3:01 pm

  71. PS: also, try adding your username to the group “audio”.

    westcoastsuccess

    August 30, 2008 at 3:06 pm

  72. Hi! I’m an absolute newbie of Linux. I’m starting of trying to manage this software. I have Musix, and it runs under Debian. There is any posibility of get some kind of paralell explanation about M-Audio Firewire solo configuration for this OS?

    Thanks in advance

    Mariano

    September 1, 2008 at 3:28 pm

  73. Ubuntu is also based on Debian, so the instructions should work word-for-word under your OS. Musix comes with Ardour and JACK – I’m not sure if it comes with qjackctl – if it doesn’t, you can get it as described in the instructions.

    I’m assuming you’ve installed Musix, as opposed to running it from the CD?

    westcoastsuccess

    September 1, 2008 at 5:23 pm

  74. Maybe do you know if ffado support is now built in jack? I see the backend “firewire” into qjackctl but I don’t know I’ve to build ffado from source however.
    Thanks. bye, this guide is very useful.

    Minghio

    September 4, 2008 at 3:04 am

  75. Hi Minghio,

    Sorry for the delay responding – we’ve been in Vegas for a much needed break!

    We’re using qjackctl 0.31a, which lists “freebob” (there’s also “firewire”). We haven’t built a newer version of qjackctl for a while, since this version has been running rock solid for nearly a year now and there just hasn’t been a good reason to update.

    According to the official JACK site, JACK v.0.109.0 change log indicates “firewire” was included to use ffado, so I suspect selecting “firewire” in qjackctl will indeed enable ffado.

    Hope this helps.

    Cheers!

    westcoastsuccess

    September 7, 2008 at 5:27 am

  76. Hi again.

    Yes, I’ve installed Musix, and still triyng to run the Firewire solo.

    I’ve followed the step by step proccess, but i’m unable to resolve this order: “#sudo gedit /etc/security/limits.conf”
    simply it said “gedit: command not found” I tried to continue after this, but the result (obviously) wasn’t good.

    Another way option, maybe?

    Thanks in advance

    Mariano

    September 7, 2008 at 11:52 pm

  77. Try this, Mariano:

    #sudo vi /etc/security/limits.conf

    westcoastsuccess

    September 9, 2008 at 1:41 am

  78. Hi again.

    Tried

    #sudo vi /etc/security/limits.conf

    but same answer (vi: command not found)

    Mariano

    September 9, 2008 at 7:17 am

  79. Hmmm…that’s strange.

    Both gedit and vi are typical linux text editors which allow you to open and edit text files – usually a linux distribution will have one or the other installed by default, but perhaps musix doesn’t.

    Try:

    #sudo apt-get install gedit

    That should download and install gedit. Then try:

    #sudo gedit /etc/security/limits.conf

    again.

    westcoastsuccess

    September 9, 2008 at 7:32 am

  80. thanks for your patience.

    I can continue, I can configure qjackctl… on root terminal, but when I close console, it dissapear (and doesn’t keep working. So I open qjackctl on my user, as usual, and I have to X I can’t uncheck (to configure as you said).

    One is “Force 16 bit”
    The other is something like “Tolerant mode”

    The other things are exactly as you told in the article.

    I try to run qjack, I start the aplication… and get this message

    13:18:10.284 JACK está iniciándose…
    13:18:10.285 /usr/bin/jackd -v -R -P89 -t2000 -dfreebob -dhw:0 -r48000 -p256 -n3 -D
    13:18:10.289 JACK was started with PID=15255.
    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
    loading driver ..
    registered builtin port type 32 bit float mono audio
    registered builtin port type 8 bit raw midi
    clock source = system clock via clock_gettime
    new client: freebob_pcm, id = 1 type 1 @ 0x806fe28 fd = -1
    Freebob using Firewire port 0, node -1
    new buffer size 256
    showDevice: not implemented
    13:18:11.185 ALSA connection graph change.
    FreeBoB MSG: Streaming thread running with Realtime scheduling, priority 93
    FreeBoB MSG: Registering audio capture port C0_dev1c_LineIn 1+2 left
    FreeBoB MSG: Registering audio capture port C1_dev1c_LineIn 1+2 right
    FreeBoB MSG: Registering audio capture port C2_dev1c_SpdifIn 1+2 left
    FreeBoB MSG: Registering audio capture port C3_dev1c_SpdifIn 1+2 right
    FreeBoB MSG: Registering playback audio port P0_dev1p_LineOut 1+2 left
    FreeBoB MSG: Registering playback audio port P1_dev1p_LineOut 1+2 right
    FreeBoB MSG: Registering playback audio port P2_dev1p_SpdifOut 1+2 left
    FreeBoB MSG: Registering playback audio port P3_dev1p_SpdifOut 1+2 right
    registered port system:capture_1, offset = 1024
    registered port system:capture_2, offset = 2048
    registered port system:capture_3, offset = 3072
    registered port system:capture_4, offset = 4096
    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
    ++ 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: iec61883_cmp_create_p2p_output: Failed to set the oPCR[0] plug for node 1.
    FreeBoB ERR: Could not start streaming threads
    LibFreeBoB MSG: FreeBoB Streaming Device Init
    LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.0
    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 : 3
    LibFreeBoB MSG: Directions : 0
    LibFreeBoB ERR: Could not do CMP for connection 0
    DRIVER NT: could not start driver
    cannot start driver
    starting server engine shutdown
    stopping driver
    13:18:21.189 Could not connect to JACK server as client. – Overall operation failed. – Server communication error. Please check the messages window for more info.
    jackd watchdog: timeout – killing jackd
    could not attach as JACK client (server has exited)
    13:18:21.200 ALSA connection graph change.
    13:18:21.204 JACK ha sido detenido satisfactoriamente.
    13:18:21.204 Script de post – apagado…
    13:18:21.205 killall jackd
    13:18:21.205 JACK has crashed.
    jackd(15175): Operación no permitida
    jackd: no process killed
    13:18:21.610 El script de post – apagado finalizó con estado 256

    That’s too hard for me, but i’m convinced to change… tired of f***ng W****ws so, help me to change!!!!

    Thanks for everything

    Mariano

    September 10, 2008 at 4:26 am

  81. The problem appears to be the permissions for JACK – qjackctl tries to start JACK, but can’t because JACK requires root permissions. That goes directly back to the modifications to /etc/security/limits.conf.

    Were you able to install gedit? The proper (and more secure) way to fix this is with the changes to /etc/security/limits.conf but as a workaround, you can try:

    #sudo chmod 777 /dev/raw1394

    This changes the permissions for raw1394, which should give you access.

    If you’re having trouble getting gedit to install, please post the output of:

    #sudo apt-get install gedit

    westcoastsuccess

    September 10, 2008 at 9:24 am

  82. THanks for everything!!!!! It worked…

    very pleased!!!!!

    Mariano

    September 10, 2008 at 2:44 pm

  83. Really glad to hear that, Mariano – did you change /etc/security/limits.conf or use the work around?

    westcoastsuccess

    September 11, 2008 at 12:56 am

  84. First, thank you so much for the walk through.

    I’m very close (at least I think I am).

    I have a bouncing meter for my input, so I know that we have at least some connection with the FW-Solo. Unfortunately, I cannot get any output.

    I have an existing wav file and my guitar. Both will cause the meter on the master channel to bounce. In the connections page, I have tried connecting the master to 3/4 as well as 1/2. Neither seems to work. I have checked with both headphones and my monitors.

    The analog inputs on my FW-Solo were assigned as 3/4. I’m not sure if that makes any difference.

    I would greatly appreciate any input you might be able to offer.

    Here’s some output from commands that I think you have requested:

    andy@kentoo:~$ lsmod | grep “raw1394″
    raw1394 31624 4
    ieee1394 106968 4 sbp2,raw1394,dv1394,ohci1394

    andy@kentoo:~$ ls -la /dev/raw1394
    crw-rw—- 1 root audio 171, 0 2008-09-14 02:13 /dev/raw1394

    AndyDavis

    September 14, 2008 at 12:25 am

  85. Glad to hear you’ve found our site helpful, Andy!

    The most common reason for this in first time users seems to be leaving the tracks armed for recording when trying to play back, which precludes them outputting the audio, since the tracks are expecting you to record on them. Make sure the record button on your tracks are not red when playing back. That’s the button immediately to the right of the track name (if you look at the manual, it’s what the screen shot with the white arrows is pointing to).

    Next try changing the Monitoring options in Ardour under the Options menu on the top menu bar. Try each of them (Software monitoring, Hardware Monitoring; External Monitoring). Ours is set to Software Monitoring.

    If that’s not it, try routing the recorded tracks directly to the output in the Connections box of qjackctl. In other words, rather than going from Audio1_L and Audio1_R under Ardour in the left side of the Connections box to Master_L and Master_R under Ardour on the right side of the Connections box, route Audio1_L and Audio1_R directly to the outputs under System or freebob or whatever on the right side. Connect to all four outputs and see if that works, then start eliminating connections on the right side to see which ones are your active outputs. If that works, it indicates your original connection routing was the issue, and the problem lies in how you’re managing connections in qjackctl’s Connections box. Test this using headphones connected to the FireWire Solo.

    You’re 99% of the way there, Andy – if none of the above works, please let us know and we’ll tackle the physical connections next.

    Good luck!

    westcoastsuccess

    September 14, 2008 at 10:38 am

  86. I have no idea what changed, but when I tried it today it all worked. Even my MIDISport 2×2 showed up on the ALSA tab.

    Is there any way via Jack, FreeBob, or whatever to control the routing in the FW-Solo? When it started working, it left the unit so that the hardware was echoing the analog inputs to the analog outputs. That’s usually how I want things to work, but it might be nice to know how to change it.

    Again, thank you for the site and the help.

    BTW – Is there a decent site that gives a comprehensive overview of the various sound APIs and how they fit together? It seems like there is very little in between, “hook it all up and everything works!” and “here’s how to set up Jack to get inhuman latency with your FW-Solo”.

    AndyDavis

    September 14, 2008 at 12:39 pm

  87. That’s great news, Andy!

    1) Check your connections in the Connections box of qjackctl. If you have a direct connection between the inputs on the left side under System or freebob or whatever to the outputs under the same heading in the right side, that results in the input of the FireWire Solo going directly to the output of the Solo unit. Disconnect these so you only have the Solo inputs going into Ardour and only Ardour outputs (typically Master L&R and the click track) going into the Solo outputs. I hope that makes sense!

    2) The documentation for Ardour is pretty good – go to http://www.ardour.org and click, not surprisingly, Documentation. In general documentation in linux is spotty (which is why we wrote the manual): some is incredibly detailed; most is not or is non-existent.

    If you have a background in recording or have worked with an old four track or some such, Ardour is pretty intuitive. We got up to speed by simply playing around with it and googling any specific issues that stumped us.

    The official JACK site lists all the apps that work with JACK – see here: http://jackaudio.org/applications

    Other things to google: “ladspa”, the Linux Audio Developers Simple Plugin API, which has some great effects; “fmit”, which is the tuner we use on all our instruments (make sure you run JACK at 44.1K with fmit or you’ll get massive X-runs and probably crash JACK – we speak here from experience); the community pages of UbuntuStudio. Ubuntu has a great community – whenever we search for any linux info we stick “ubuntu” at the end as Ubuntu has remarkable support sites.

    If you need any help with linux in general, there’s a cheat sheet elsewhere on this site – click: https://westcoastsuccess.wordpress.com/2008/03/23/ubuntu-linux-workarounds/. It includes, for example, command line instructions for how to convert a sound file exported by Ardour in the .wav format into .mp3 using lame, which is incredibly fast and easy and flexible.

    Of course, you can always try posting here and we’ll do our best to help!

    Happy recording, Andy!

    westcoastsuccess

    September 14, 2008 at 1:18 pm

  88. In order to record in Linux I have bought the microphone Samson C01U and have put the Firewire Solo for sale. The microphone is recognized perfectly by Linux via USB and records perfectly by means of Audacity or Ardour. Thank you very much to try to help me but the Firewire Solo is apt only for certain machines between that is not mine.

    Fran

    September 15, 2008 at 12:56 pm

  89. Sorry to hear that, Fran – you’re the first person that we weren’t able to get up and running.

    Good luck with your recordings!

    westcoastsuccess

    September 15, 2008 at 4:34 pm

  90. Hi. This looks great… But.. Anything for M-Audio FW1814? I have one of them, and i can’t use it in Linux (Musix).. I used to visit ffado website, but nothing for me there.

    I think that you will not be able to help me. However, i post for give you a w00t for your work for M-Audio FW solo.

    Keep it!

    Regards.

    Arturo

    September 19, 2008 at 4:22 pm

  91. Thanks for the kind words, Arturo.

    Here’s what I was able to find out about the 1814:

    “Will the M-Audio 410 / 1814 be supported?

    Maybe. The problem is that the M-Audio 410 / 1814 does not support the AV/C commandos for device discovering. Though for transporting the signals the IEC 618863-6 standard is used. So that means that streaming is no problem while controlling the device is.

    The M-Audio 410 is BridgeCo’s first product and differs heavily from the rest. FW410 tries to collect information about this device.

    The state about the M-Audio 1814 is unknown.”

    That’s from the Freebob FAQ (http://freebob.sourceforge.net/index.php/FAQ#Will_the_M-Audio_410_.2F_1814_be_supported.3F).

    Sorry we can’t be of more help.

    westcoastsuccess

    September 20, 2008 at 12:52 pm

  92. Hello! I`m having the same problem of hr_tetra. I’ve done everything you told. If I type gscanbus I can see my firewire solo conected. I’ve a mic plugged into the input 1, but in the mixer of ardour there’s no signal. I also tried with my bass in the input 2 (front of M audio), and nothing.

    mattnick

    October 22, 2008 at 9:01 am

  93. Hi Mattnick,

    Your problem is likely your connections in qjackctl – can you post a screen shot of your connections on a picture hosting site?

    Cheers!

    westcoastsuccess

    October 22, 2008 at 11:11 pm

  94. Sorry, i had a problem and had to reinstall kubuntu. I’ve to set up everything again. When I finish, I’ll try to post a screenshot.

    Thanks for your answer!

    mattnick

    October 27, 2008 at 6:39 pm

  95. mattnick

    October 27, 2008 at 7:26 pm

  96. Hmmm…your connections look correct to me, however try switching the connection from “capture 1″ to “capture 2″, then try the bass again.

    Also, make sure you’ve record-enabled your track in Ardour – click the “record” button on the track such that it shows red (there’s a screen shot of what I’m describing in the instructions above).

    Let me know if that helps.

    Cheers!

    westcoastsuccess

    October 30, 2008 at 8:57 am

  97. It doesn’t work. I’ve tried with the bass again, but nothing happens. I’m sure I’m doing everything ok. I don’t know where the problem could be.

    Anyway, thanks!

    mattnick

    October 30, 2008 at 1:07 pm

  98. I’ve a question: Limits.conf should be:

    http://www.imagehostingsite.com/gallery.php?entry=images/immnjygdgro5iwkzmnjz.jpg

    or

    http://www.imagehostingsite.com/gallery.php?entry=images/oyqmvzymmyzjnxmwwwmi.jpg

    I don’t know if has something to do with the problem I’m having, but…

    Thanks again.

    mattnick

    October 30, 2008 at 2:05 pm

  99. There should NOT be “#” before the “@audio” in your limits.conf file.

    If you plug headphones into the jack on the M-Audio FireWire Solo unit, do you hear the instrument/mic you have plugged into the Solo?

    westcoastsuccess

    October 30, 2008 at 9:50 pm

  100. I would like to route all the system sounds from pulseaudio to jack.
    In this way I could listen to Banshee, flash video using my firewire solo.
    Do you know how to do it? I can’t find any helpful guide.

    Thank you.

    Minghio

    November 6, 2008 at 4:43 am

  101. Hi Minghio,

    I don’t know off hand how to do this, but I’ll do some experimenting and let you know if I figure it out.

    Cheers!

    westcoastsuccess

    November 11, 2008 at 1:57 am

  102. Hi,
    I have done everything you have said on the guide but no matter what I do JACK wont successfully load. I was hoping you could help; I’m running fedora 10 with KDE, but I think it is similar to Ubuntu and can do the job.

    this is JACK’s log

    19:28:07.507 Patchbay deactivated.
    19:28:07.572 Statistics reset.
    19:28:07.584 ALSA connection graph change.
    19:28:07.994 ALSA connection change.
    19:28:09.723 Startup script…
    19:28:09.723 artsshell -q terminate
    19:28:10.152 Startup script terminated with exit status=256.
    19:28:10.153 JACK is starting…
    19:28:10.154 /usr/bin/jackd -v -R -P89 -t2000 -dfreebob -dhw:0 -r48000 -p256 -n3 -D
    getting driver descriptor from /usr/lib/jack/jack_dummy.so
    getting driver descriptor from /usr/lib/jack/jack_freebob.so
    getting driver descriptor from /usr/lib/jack/jack_alsa.so
    jackd 0.116.1
    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.
    19:28:10.166 JACK was started with PID=4381.
    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 ..
    start poll on 3 fd’s
    new client: freebob_pcm, id = 1 type 1 @ 0x8553e78 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.11
    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 : 3
    LibFreeBoB MSG: Directions : 0
    showDevice: not implemented
    19:28:10.938 ALSA connection graph change.
    FreeBoB MSG: Streaming thread running with Realtime scheduling, priority 89
    FreeBoB MSG: Registering audio capture port C0_dev1c_SpdifIn L
    FreeBoB MSG: Registering audio capture port C1_dev1c_SpdifIn R
    registered port system:capture_1, offset = 1024
    FreeBoB MSG: Registering audio capture port C2_dev1c_LineIn L
    registered port system:capture_2, offset = 2048
    FreeBoB MSG: Registering audio capture port C3_dev1c_LineIn R
    registered port system:capture_3, offset = 3072
    FreeBoB MSG: Registering playback audio port P0_dev1p_SpdifOut L
    registered port system:capture_4, offset = 4096
    FreeBoB MSG: Registering playback audio port P1_dev1p_SpdifOut R
    registered port system:playback_1, offset = 0
    FreeBoB MSG: Registering playback audio port P2_dev1p_LineOut L
    registered port system:playback_2, offset = 0
    FreeBoB MSG: Registering playback audio port P3_dev1p_LineOut R
    registered port system:playback_3, offset = 0
    registered port system:playback_4, offset = 0
    ++ jack_sort_graph
    ++ jack_rechain_graph():
    +++ client is now freebob_pcm active ? 1
    client freebob_pcm: internal client, execution_order=0.
    – jack_rechain_graph()
    – jack_sort_graph
    FreeBoB MSG: MIDI threads running with Realtime scheduling, priority 88
    FreeBoB MSG: MIDI queue thread started
    libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the oPCR[0] plug for node 0.
    LibFreeBoB ERR: Could not do CMP for connection 0
    FreeBoB ERR: Could not start streaming threads
    DRIVER NT: could not start driver
    cannot start driver
    starting server engine shutdown
    server thread back from poll
    stopping driver
    19:28:10.954 JACK was stopped successfully.
    19:28:10.954 Post-shutdown script…
    19:28:10.955 killall jackd
    19:28:10.955 JACK has crashed.
    jackd: no process killed
    19:28:11.369 Post-shutdown script terminated with exit status=256.
    19:28:12.202 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.

    TIA,
    Omer

    omerole

    January 19, 2009 at 5:28 pm

  103. Thanks for the great information on this site. I am running Ubuntu 8.10 with the latest repository versions of Ardour, JACK, qjackctl, etc.

    Like some others, I am able to get sound into Ardour, but not out. (On my system capture 3 is the xlr input on the Firewire Solo and capture 4 is the front guitar input). When I route the output from Ardour’s track 1 to Master 1 in, I can see the meter bouncing, but I don’t get any sound from my headphones that are plugged into the headphone jack on the Solo. I’ve checked my connections against everything above. I’ve tried all the monitoring options in Ardour, to no avail. I tried connecting Master 1 out to all four playback channels on the Solo, as well as connecting the output from track 1 directly to the playback channels.

    I don’t have studio monitors or any equipment that takes balanced TRS or s/pdif input. Is there a way to hook the balanced outputs of the Firewire solo to a guitar amp or a stereo receiver to check whether I get output there? I don’t want to damage any of my equipment by connecting a line level input to something that can’t take it.

    I think the Solo is set up correctly itself (firmware or whatever); on my Mac it works perfectly with GarageBand, as well as for iTunes playback. Does it matter what version of the Firewire Solo firmware I am running? What versions have people used successfully?

    Thank you!

    Aaron

    January 20, 2009 at 11:46 am

  104. I found my answer on another site. If I follow these steps I am able to get audio out: 1) Plug the Firewire Solo into my Mac and boot up; 2) Plug in a power supply to the Solo; 3) Shut down the Mac and disconnect the firewire cable; 4) Attach the Solo to my Linux machine and boot up, without unplugging the power supply from it.

    Now I just need to figure out how I can get this to work without leaving it plugged in all the time.

    Aaron

    January 22, 2009 at 6:09 am

  105. I’m considering buying a solo purely to record some vinyls. Is all the talk of connecting outputs to inputs (with cables, not settings) purely to get sound listenable? It’s nice to find a guide thats too detailed for a change :)

    In short if I plug in using 6 pin firewire cable, press record it will record? No other cables required?

    Thanks in advance

    Joe

    January 31, 2009 at 4:41 am

  106. That’s an interesting question – and makes me wonder why _I_ haven’t done the same with all my vinyls that have been sitting here unlistened to in the past 15 years!

    All you’d need to connect would be the firewire cable, of course, and then the cables from the turntable to the M-Audio Firewire Solo. Not sure if you’d use the balanced or unbalanced, but either way, just plug into the back of the Solo. You could monitor it via the headphone jack on the Solo.

    If you intend to use Ardour, just set up 2 audio tracks and follow the instructions – connect (in the Connections box of qjackctl) your Solo outputs to the Audio inputs and the Audio outputs to the Solo inputs. Once you’re done, select Export from the File menu in Ardour and export a .wav file.

    In short, if you’re not concerned with listening as you go, you won’t need to worry about running physical cables from the headphone output on the Solo to the input of your computer, etc.

    If that’s not clear, let us know. Meanwhile, we’re off to record some records!

    westcoastsuccess

    January 31, 2009 at 10:54 am

  107. Hi guys, thanks for your help.

    Im thinking on install ubuntu in my computer. And i also have a firewire solo card. I don’t know if my question is too much stupid but ill take the risk.

    Setting up the firewire solo as explained above, will let me use it at general purpose output sound card or just for recording?

    I mean, can i watch a movie driving the sound through the maudioFWsolo through my speakers as i do on windows?

    Thanks for your time and excuse my ignorance.

    ubuntu newbie

    February 27, 2009 at 5:17 am

  108. Hi!

    I am running Hardy Heron and I do not seem to have neither audio nor disk groups on my system. What might be their equivalents?

    K

    K

    March 7, 2009 at 2:23 pm

  109. We’re running Hardy too.

    In a terminal, type:

    #cat /etc/group | grep disk
    #cat /etc/group | grep audio

    (Omitting the “#”). What’s the output? Anything?

    westcoastsuccess

    March 8, 2009 at 12:50 pm

  110. Hi!

    Thanks for answering. Grep shows my user just fine. This seems a bit odd because if I try to manage groups directly from gnome I cannot see either of these groups. Guess this is normal for some reason.

    As I said, grep says that my user is there. At least in the audio group. In the case of the disk group my username is not shown. When I try to add it I get something like: ‘user already exists’ though.

    Actually I have two more questions:

    1) Is it possible to somehow determine the strength of the signal that comes out of the computer (JACK)?

    Currently, my amplifier has to work a bit too hard when I use the audio card. Of course audacious has a volume control bar but that doesn’t do much. It works though. The volume button of the card is at max.

    2) Should Jack and audacious work happily together when the rt kernel is used or is there a special trick one must be aware of? In my case audacious and JACK do not cooperate when the rt kernel is used.

    I haven’t got the error message at the moment but I decided to ask since there’s always a chance that I’ve missed something obvious.

    As far as I can remember the problem was that audacious just could not connect to JACK while the rt kernel was used. I’ll try to look at the log in the nearest future to get some more details.

    K

    March 8, 2009 at 2:51 pm

  111. Btw, don’t convert your vinyls to files. It is much more reasonable (and fun :) ) to get a turntable:)

    K

    March 8, 2009 at 2:56 pm

  112. Ok, please forget that I ever posted the above comment:D

    K

    March 8, 2009 at 2:57 pm

  113. We’ve found the groups interface on gnome terrible and don’t use it – you’re better off using the command line.

    #useradd -G disk username

    replacing “username” with your username.

    If it’s reporting that the user already is a member of that group, it should certainly show up if you

    #cat /etc/groups

    That’ll show every group in existence along with every member of each group.

    Are you saying you’re running a line from the computer’s sound card to an amp??? That’s defeating the purpose of the M-Audio FireWire Solo. Run a cable from the back of the Solo to the input of your amp (I’m assuming here you mean a guitar amp). Also, check your input and output levels on the front of the Solo, if you’re running a cable from the headphone output on the Solo to the input of your computer per the instructions.

    Right click on the icon that looks like a speaker on your (typically) top panel (to the right, by default, I think), then click “Open Volume Control” and you’ll see a bunch of volume and input controls.

    Sorry, but we don’t use Audacious and don’t know anything about it – we use Ardour exclusively.

    If what you’re simply trying to do is convert vinyl to digital, it should be a very simple process – just run the output from your turntable into the Solo. The firewire connection should transfer the signal to Ardour, provided you’ve followed the instructions and set your connections properly in qjackctl. You can monitor the signal either at the headphone jack on the Solo or the headphone jack on your computer. Just make sure you NEVER exceed 0db in the faders – it’s always better to record too low than too loud in digital. And you can always normalize the tracks later.

    westcoastsuccess

    March 8, 2009 at 8:13 pm

  114. Hi again!

    I am sorry, my questions were a bit messy.
    If I wrote:

    ’1) Is it possible to somehow determine the strength of the signal that comes out of the computer (JACK)?’

    I actually meant the signal that comes out of my computer’s firewire port. Also, when I wrote: ‘Currently, my amplifier has to work a bit too hard when I use the audio card’ I accidentally misled you.

    Namely, I actually meant the M-audio and not my computer’s audio chip.

    Currently my setup is quite simple: a firewire cable connects the computer and the M-Audio interface and the unbalanced outputs of the interface are connected to my amplifier. The latter is not a guitar amp but an ordinary one (dunno the term unfortunately) in the sense that it amplifies my turntable, cd deck etc.

    As for my purpose, it is not to convert vinyl records to digital but to enjoy the true quality of flac audio. At the moment, I have not managed to notice a huge jump in quality when using m-audio. Strangely, at some point my laptop’s integrated card even seems to beat m-audio which is definitely a nonsense…

    With my somewhat failed comment on vinyls and turntables I tried to express my opinion that digitalizing vinyls is a rather strange thing to do.

    Of course, my recommendation about getting a turntable was a silly one since you probably already have one if you are talking about ‘recording your vinyls’. Anyway, my point was and still is that in my opinion, one should enjoy true vinyls if possible as they sound far better than digital sound. But that is of course only my opinion and not the final truth.

    Best Wishes,

    K

    K

    March 9, 2009 at 3:46 am

  115. hi again! I’ve been able to make my M-Audio FW Solo working in my PC finally! I’ve used the “jackd-firewire-driver” that appeared all of a sudden in Synaptic after adding the FFADO apt repository dir. Now I’m hoping to use my audio interface with my laptop. I’m using a pcmci firewire card, and the system can see my M-Audio via gscanbus. I’m having problems with jackd, I can’t start it without being root when the realtime option is enabled. I’ve tried changing my limits.config several times. I also tried:

    @priv – rtprio 99
    @priv – memlock 512000
    @priv – nice -19

    as Minghio proposed
    .
    I also tried:

    sudo chmod a+rw /dev/raw1394
    modprobe raw1394
    useradd -G disk username——username alredy exists

    but nothing.

    With “cat /etc/group” (not groups) I can find between all:
    audio:x:29:pulse
    but I don’t know what that means.

    I’ve got 1Gb of RAM, and I’m using Ubuntu Studio 8.10, but not with a realtime kernel.
    Anyway, I hope to get some help, and sorry about not commenting before.

    Thanks in advance!

    mattnick

    March 11, 2009 at 7:44 am

  116. You need to add your username to the audio group – the line:

    audio:x:29:pulse

    shows that you are not part of the audio group.

    #useradd -G audio username

    where “username” is your username will add you to the audio group.

    If that doesn’t work, let us know.

    westcoastsuccess

    March 11, 2009 at 8:26 am

  117. Hello K,

    If you’re really interested in getting the best quality sound out of your set up, use the S/PDIF input and output on the back of the Solo (provided your turntable has S/PDIF output and your amplifier has S/PDIF input, of course).

    If you want to compare your onboard soundcard to the M-Audio Solo, try using headphones in your computer’s headphone jack and then again in the Solo’s jack, with the same material as a test source.

    I don’t think the unbalanced outputs are the way to go with your setup – that explains why you’re having volume issues – the signal from those outputs is designed to go into a guitar-type amp, and that kind of amp is designed for a much lower input level (ie to match the output level of a guitar, which is very, very low, which is why a guitarist needs a box like the Solo to act as a pre-amp for the signal to the computer), and if you don’t have S/PDIF, try using a cable from the headphone output on the Solo to the input on your amplifier. Use a splitter if you need to split the inputs for your amp.

    Let us know how you make out!

    westcoastsuccess

    March 11, 2009 at 8:38 am

  118. Thanks very much for your quick answer! I’m with a final project at University about Ardour, and this is driving me crazy!

    I’ve done what you said:

    useradd -G audio “myusername” and the output is that the user exists.

    When I type:

    “cat /etc/group”, I still can see: audio:x:29:pulse. Nothing has changed.
    I still can’t run jack at realtime, I’m getting:

    “cannot use real-time scheduling (FIFO at priority 10) [for thread -1209731408, from thread -1209731408] (1: Operation not permitted)
    cannot create engine”

    Is there any way to manipulate groups in graphic mode? I read above in this page that groups in gnome are terrible, I don’t know what did you mean by that.

    Oh, another important thing: I’ve installed a realtime kernel: and tried in both generic and rt. My rt kernel is:

    Linux localhost 2.6.27-3-rt #1 PREEMPT RT Mon Oct 27 03:05:19 UTC 2008 i686 GNU/Linux

    The generic kernel is 2.6.27.11-generic.

    Anyway, thanks for being there and help all of us!

    I

    mattnick

    March 11, 2009 at 5:37 pm

  119. I’ve solved my problem. I found in my system preferences the way to manipulate user and groups, and now I’m a group member of audio, so the limits.conf you proposed work for me. Now I’m able to run jack with realtime option.
    My problem is the following: I can get audio in, with the mic input, and also the instrument input, but can’t get audio out. I recorded some things in ardour, but can’t get them out of FW Solo. I also tested with vlc media player, and audacity. I tried with all of the 4 outputs in jack connections, but nothing, nothing in m-audio headphones, nothing in m-audio line outs. Couldn’t test Spdif because I haven’t anything to connect. I run jack with freebob driver and also firewire driver, always realtime, with no xruns. With both drivers I can see 4 captures and 4 playbacks. I was who compiled and installed the ffado 2.0 drivers.
    If someone has had the same problems, please help.

    Thanks!

    mattnick

    March 13, 2009 at 2:52 pm

  120. Hi again!

    I actually suspected that the signal from unbalanced outputs is just weak but I did not want to believe it…

    Why? Because for some reason getting the signal out from phones output seems to be tricky. At a local sound shop ‘phones’ output was their first recommendation as well but unfortunately they were unable to find a solution for me.

    To tell the truth, I did not quite understand the difficulty. It appears that the cable I’m after is just so rare that they do not keep such things in stock.

    The thing I do not understand is: what makes it so rare? Ok, I have an amp which doesn’t have RCA inputs but 5 pin DINs instead but it is rather easy to convert two RCA plugs to DIN so there should not be a problem with it.

    Anyway, I’d be grateful if anyone would point me to a web site where they offer suitable cables. A cable with a DIN plug would be nice but as I said, I can convert as well.

    K

    K

    March 14, 2009 at 4:09 am

  121. Well, I just discovered that I am using using balanced outputs after all. My bad. Would I still benefit from using phones output?

    K

    March 19, 2009 at 2:18 am

  122. Hi again. I’ve discovered that after restarting ubuntu and booting up windows, and then booting up ubuntu again, I can get the outputs of my m audio work. It’s very strange. Alway when I can’t get audio out, I do this and works. I don’t know why this happens, but by now, it’s my only solution to the problem.
    Anyway, thanks!

    mattnick

    March 30, 2009 at 6:10 pm

  123. Just got my Firewire Solo last week and it *was* working great. I’m using this on a dual boot laptop (Fedora 10 x86_64 and Vista x86).

    I saw “was” because after playing with the Solo in Fedora for a few days and feeling pretty pleased with my purchase I decided to boot into Windows and give it a try. After installing the latest driver I’m now having the problem everyone else is having where the outputs don’t work unless I boot into Windows first and then reboot into Linux.

    We really need a *real* workaround for this. This is a great device for a great price. If only it worked in Linux without having to rely on having some other OS near by.

    Steve

    April 13, 2009 at 5:32 pm

  124. This guide was really helpful, but there were a few things I personally had to do to get it working:
    (1)I had to manually add a “disk” and “audio” group to the Ubuntu Studio installation, I did it through system-admin-users and groups. (2) I had to configure Ubuntu Studio to start the Real time kernel at boot, which it was not doing by default (3) I had to add libxml++2.6c2a, then the ffado items: libffado2 and libffado2-dev ffado-dbus-server ffado-tools ffado-mixer-qt4 ffado-mixer-qt3 Jack Version: 0.3.2. I used your settings, but then with the newer “firewire” driver, rather than the Freebob. That was the only way I can seem to get it to work with Ubuntu Studio 8.10. It does work wonderfully, though!!

    Chris Rowland

    April 19, 2009 at 11:58 pm

  125. Hi Chris,
    Just a quick warning: As you may know 8.10 has real time disabled because RT will only run on one core – so if you have dual or quad cores you’re losing out. Most of us are still stuck on 8.01 as a result. You might want to risk 9.04 which has just come out, but may not be very stable!

    Stephen Parry

    April 27, 2009 at 10:38 am

  126. That’s a great comment, Stephen.

    We use 8.04 (which I think you’re referring to when you say “…stuck on 8.01…”) because it’s a long-term support version. We also very specifically do not use ubuntustudio – just a regular hardy heron with the real time kernel installed. Dual core support isn’t an issue on 8.04.

    I’ve seen conflicting reports on the stability of the real time kernel in 9.04 – ubuntu claims it’s “heavily tested” but others report significant issues.

    Our set up is _rock_ solid and we use it to record daily (in fact, we’ll announce a release date for our project within the next two months, recorded entirely with Ardour and other open source tools).

    westcoastsuccess

    April 27, 2009 at 9:45 pm

  127. Hi to everyone, I need help with Qjackctl.
    I need help because I can’t find anything that can help me.
    I’ve followed these istruction but it didnt’t help me
    https://westcoastsuccess.wordpress.com/2008/03/23/m-audio-firewire-solo-ubuntu/

    If I run gscanbus I receive this message:
    couldn’t get handle: Permission denied
    This probably means that you don’t have raw1394 support in the kernel or that
    you haven’t loaded the raw1394 module.

    If I try to start jack I get this message:
    00562797044: (ffado.cpp)[ 92] ffado_streaming_init: libffado 1.999.40- built Feb 24 2009 00:53:39
    firewire ERR: Error creating FFADO streaming device
    cannot load driver module firewire
    00562798063: Error (ieee1394service.cpp)[ 163] detectNbPorts: Could not get libraw1394 handle.
    This usually means:
    a) The device-node /dev/raw1394 doesn’t exists because you don’t have a
    (recognized) firewire controller.
    b) The modules needed aren’t loaded. This is not in the scope of ffado but of
    your distribution, so if you have a firewire controller that should be
    supported and the modules aren’t loaded, file a bug with your distributions
    bug tracker.
    c) You don’t have permissions to access /dev/raw1394. ‘ls -l /dev/raw1394′
    shows the device-node with its permissions, make sure you belong to the
    right group and the group is allowed to access the device.

    I need to use jack for doing audio, why it’s alway hard to use it?
    Thanks,

    Minghio

    April 28, 2009 at 3:06 pm

  128. Hi, Minghio!

    As a temporary solution you could try running qjackctl and other relevant (sound)apps (mplayer etc) as sudo. This is as I said a temporary solution and not a good one actually.

    I’d really like to know how to avoid using sudo. I have modified the limits.conf and added my user to the disk group but qjackctl still isn’t working without sudo.

    K

    April 28, 2009 at 3:22 pm

  129. Minghio: can you please post the output of:

    #lsmod | grep 1394

    It should show something like:

    raw1394 32136 0
    dv1394 23656 0
    ohci1394 37172 1 dv1394
    ieee1394 109656 4 sbp2,raw1394,dv1394,ohci1394

    PS: make sure you follow the instruction re: modifying /etc/security/limits.conf contained in the instructions – if you’re having a problem running qjackctl or JACK as anyone other than root (ie “sudo”), that’s almost certainly where your problem is.

    westcoastsuccess

    April 28, 2009 at 4:56 pm

  130. Hi, I’ve typed
    #lsmod | grep 1394

    and I get

    minghio@minghio-laptop:~$ lsmod | grep 1394
    dv1394 25948 0
    raw1394 32732 0
    ohci1394 38576 1 dv1394
    ieee1394 94660 3 dv1394,raw1394,ohci1394

    Minghio

    April 29, 2009 at 9:50 am

  131. That shows the necessary modules are properly loaded, Minghio.

    Can you please post the output of:

    #groups username

    substituting your user name in place of “username”? This will show all the groups your user name belongs to.

    westcoastsuccess

    April 29, 2009 at 9:57 am

    • minghio@minghio-laptop:~$ groups minghio
      minghio adm disk dialout cdrom audio plugdev lpadmin admin sambashare

      Minghio

      April 29, 2009 at 11:38 am

  132. Hi, thx for the toturial it is very thorough. I’ve managed to get the audio in and out of Ardour and other programs but I still have some problems and questions.

    1)Even when having the realtime kernel (Ubuntu 9.04 latest kernel), being in the disk and audio groups in all ways imaginable
    (tomas@tomas-desktop:~$ groups tomas
    tomas adm disk dialout cdrom audio plugdev lpadmin admin sambashare firewire)
    , having edited the limit.conf to have the @audio and @priv entries, am I still not able to run JACK as a normal user. Can you think of any other thing i might be missing?

    2)I know that by using the jackd command you can run JACK without the controller, but the problem is that the connection it uses for default are not the ones my speakers are connected to… is there a way to configure this per terminal? My goal is to run JACK with scripts at startup (in the background) with the right configuration.

    3) I believe someone mentioned connecting Pulse to Jack so that all the normal sounds in the computer could play through the m-audio and you said you would experiment to see if it is possible… have you come to any answers as to that matter?

    Thx beforehand… if I come across any solution I will post it here

    Ernesto

    April 29, 2009 at 3:40 pm

  133. Ernesto:

    1) can you post specifically your “@audio” lines from /etc/security/limits.conf?

    They should look like this:

    @audio – rtprio 99
    @audio – memlock unlimited
    @audio – nice -19

    Sorry if that seems obvious, but that’s the first place to look.

    2) Can you specify the entire command you’re using to run jackd from the command line?

    If you type:

    #man jackd

    in the command line, you’ll get the man page for jackd, which shows all the possible options. I’m not certain I’m understanding what you’re getting at, but have a look at what man jackd says under “Alsa Backend Options” and, specifically, the “–device” option.

    Also, try:

    #jackd -d alsa –help

    for a list of alsa options.

    It’s in no way clear to us how you manage connections when running jackd from the command line. If you can figure that out, then writing the script to run at start up should be very simple – just write the commands in a text file and then set a cron job pointing at the script using “@reboot” (I’m probably telling you things you already know here…if so, my apologies).

    3) No, I’m sorry but we haven’t had the chance to experiment with running all the pulseaudio output thru jack – we’ve been very busy with recording an album for the past 6 months and this item has just dropped off the to-do list.

    westcoastsuccess

    May 1, 2009 at 1:15 am

  134. Minghio:

    Type:

    #ls -l /dev/raw1394

    into a terminal and see what it says about permissions – I suspect you don’t have read permission for the owner or group.

    If you don’t have the correct permissions, it’ll look something like this:

    #crw——- 1 root disk 171, 0 2009-04-30 09:11 /dev/raw1394

    If that’s the case, in order to change it permanently, modify a file called “permissions.d” – in Ubuntu you can find it in /etc/udev/rules.d/

    You may also have a file called 40-linux1394.permissions in the same folder.

    Comment out the line that has “raw1394″ in it by placing a “#” before it – we’ll keep this so you can always revert back to the way it was if you need to. Then type a new line like:

    raw1394:root:audio:0640

    Save the file, log out and back in again and see if that works.

    For those of you having trouble with the permissions/groups/etc, be aware that you need to log out and back in before any changes take effect.

    westcoastsuccess

    May 1, 2009 at 1:31 am

  135. Ernesto:

    Take a look at a file in your home folder called “.jackdrc”.

    It’ll contain something like:

    /usr/bin/jackd -v -R -P89 -t2000 -dfreebob -dhw:0 -r44100 -p32 -n3 -D

    You could probably call this file at boot (using crontab) to start the JACK server automatically.

    westcoastsuccess

    May 2, 2009 at 9:07 pm

  136. PS: check out jackdbus – you can compile JACK with dbus support which, if I’m reading it correctly, will automatically start a JACK server instance as needed by client apps.

    You can learn more here:

    http://lwn.net/Articles/310230/

    We’re going to compile a newer version of JACK tomorrow and will test out jackdbus at that time.

    westcoastsuccess

    May 2, 2009 at 9:14 pm

  137. Thanks for the tutorial. I’m a total newb w/ linux but I believe I did everything right. I must be missing something.

    When I start JACK I get this message…

    Could not connect to JACK server as client.
    - Overall operation failed.
    - Unable to connect to server.
    Please check the messages window for more info.

    Any help will be appreciated.

    mike

    May 19, 2009 at 8:07 pm

    • oops. solved moving on to next problem

      mike

      May 19, 2009 at 10:22 pm

    • Glad you got it solved, Mike.

      In case anyone else comes across this problem, it’s most commonly caused by having more than one instance (usually different versions) of JACK installed simultaneously.

      Check for a folder called “jack” in /usr/local/lib/ and if it exists, rename it “jack.old”. Then try restarting qjackctl – it should work. If that doesn’t solve it, post here and we’ll do our best to help you troubleshoot the issue.

      westcoastsuccess

      May 19, 2009 at 11:09 pm

  138. So I’m still getting the

    Could not connect to JACK server as client.
    - Overall operation failed.
    - Unable to connect to server.
    Please check the messages window for more info.

    error message.

    I tried forcing a bus reset but nothing changed.
    My kernel is still generic inspite of sudo apt-get install linux-rt

    thanks if you can help.

    mike

    May 19, 2009 at 11:18 pm

  139. I’m a bit of a linux newb.

    I tried ls /usr/local/lib/ and the only thing that showed up was python 2.5

    I assume this means I only have 1 version of jack?

    mike

    May 19, 2009 at 11:20 pm

  140. In qjackctl, click “Setup”. On the “Settings” tab, what appears in the “Server Path” field?

    It should show:

    /usr/bin/jackd

    Check if that is indeed where the jackd binary is – in a console type (omitting the “#”):

    #ls -l /usr/bin/jackd

    This should show something like:

    #-rwxr-xr-x 1 root root 78272 2009-05-02 22:48 /usr/bin/jackd

    We’ll start with that.

    westcoastsuccess

    May 20, 2009 at 1:04 am

  141. PS: if you’ve installed the real-time kernel, you still need to select it in the GRUB menu during boot-up.

    Restart your system. As it’s booting, you should see a few lines from GRUB appear – it could be just a flash. Get ready to hit the “Esc” key – as soon as you see the GRUB lines, hit “Esc”.

    From within GRUB, you can then select which kernel the system should boot into, and also set a kernel as the default. The instructions within GRUB should be self-explanatory – if not (or you’re uncomfortable experimenting), google for “select kernel grub”.

    If you’re using Ubuntu, you can type, in a terminal:

    #sudo gedit /boot/grub/menu.lst

    (the third last letter is a lower-case “L”, not a “1″ or an upper-case “I”).

    You’ll see a file open in a text editor which, among other things, lists all the kernels you have available. You’ll see a line that says:

    default 0

    This tells the computer which kernel to use by default, and “0″ corresponds to the first one in the list lower down in the file. For example, ours is:

    title Ubuntu 8.04.2, kernel 2.6.24-24-rt
    root (hd0,3)
    kernel /vmlinuz-2.6.24-24-rt root=UUID=df42c8bd-2596-426f-89e1-797fcd2bb3cb ro quiet splash
    initrd /initrd.img-2.6.24-24-rt
    quiet

    Find the kernel with the “-rt” at the end of the kernel version number. Count down to it, starting at the first kernel listing as “0″, then the next “1″, etc. until you get to the kernel you want. Then change the number after the “default” line to the number corresponding to the kernel you want.

    Make sure you “Save”, then reboot. That will boot into your real-time kernel every time by default.

    westcoastsuccess

    May 20, 2009 at 1:18 am

  142. THanks for the reply. The server path field is set to what you say it should be and this is what appears when I enter the command you supplied.

    -rwxr-xr-x 1 root root 67372 2008-06-12 16:09 /usr/bin/jackd

    Now that I read your second reply I’m seeing the problem with getting to the rt kernel. I will try that and then return.

    Do I really want to set the rt kernel as my default kernel? I’ve been reading a lot about this kernel being very unstable.

    mike

    May 20, 2009 at 10:09 am

  143. Mike: regarding the real-time kernel, it’s our understanding that it depends on the Linux distribution you’re using. Specifically, the real-time kernel on any version of Ubuntu beyond 8.04 (Hardy Heron) is, apparently, problematic.

    We’ve been using 8.04 since it came out, specifically because it’s the long-term support release, and therefore supported for 3 years – we haven’t upgraded to the later versions (Intepid Ibex; Jaunty Jackalope) and won’t be – we’ll upgrade at the next LTS release.

    We’ve also been using the real-time kernel as our default kernel in 8.04 all along, and haven’t experienced any problems with stability whatsoever.

    We’d suggest you may wish to switch to 8.04, but do some research first.

    As for your jackd issue, go back into the “Setup” screen of qjackctl and try un-checking the “Real Time” box.

    Also, try starting qjackctl as root and see if that works – just type (in a terminal):

    #sudo qjackctl

    westcoastsuccess

    May 20, 2009 at 10:57 am

  144. OK I’m using intrepid.

    I did try deselecting the real time option with no change in the error message.

    Im in the PREEMPT RT kernel right now. (nope I couldn’t post this while I was there) I got some error messages at start up but other than the screen being a 1/4 inch off center I don’t see a difference.

    Here’s my memory of the error message.

    low graphics mode
    error found – need to update configuration
    (EE) NVIDIA (0): Failed to load NVIDIA kernel module
    (EE) NVIDIA (0):***Aborting***
    (EE) screen(s) found, but none have usable configuration

    While I’m here I tried JACK. I’m still getting the same error message.

    and this
    13:34:27.180 Patchbay deactivated.
    13:34:27.215 Statistics reset.
    13:34:27.266 ALSA connection graph change.
    13:34:27.610 ALSA connection change.
    13:34:30.470 Startup script…
    13:34:30.470 artsshell -q terminate
    sh: artsshell: not found
    13:34:30.871 Startup script terminated with exit status=32512.
    13:34:30.871 JACK is starting…
    13:34:30.871 /usr/bin/jackd -v -t2000 -dfreebob -dhw:0 -r96000 -p64 -n3 -D
    13:34:30.874 JACK was started with PID=5861.
    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_dummy.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 @ 0x89bd130 fd = -1
    Freebob using Firewire port 0, node -1
    new buffer size 64
    LibFreeBoB MSG: FreeBoB Streaming Device Init
    LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.11
    LibFreeBoB MSG: Device information:
    LibFreeBoB MSG: Device options:
    LibFreeBoB MSG: Port : 0
    LibFreeBoB MSG: Device Node Id : -1
    LibFreeBoB MSG: Samplerate : 96000
    LibFreeBoB MSG: Period Size : 64
    LibFreeBoB MSG: Nb Buffers : 3
    LibFreeBoB MSG: Directions : 0
    Ieee1394Service::initialize: Could not get 1394 handle: Permission denied
    Is ieee1394 and raw1394 driver loaded?
    #[31mFatal (devicemanager.cpp)[68] initialize: Could not initialize Ieee1349Service object
    #[0m#[31mFatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager
    LibFreeBoB ERR: cannot create libfreebob handle
    FreeBoB ERR: FREEBOB: Error creating virtual device
    #[0mcannot load driver module freebob
    starting server engine shutdown
    stopping driver
    13:34:32.273 JACK was stopped successfully.
    13:34:32.273 Post-shutdown script...
    13:34:32.273 killall jackd
    13:34:32.274 JACK has crashed.
    jackd: no process killed
    13:34:32.702 Post-shutdown script terminated with exit status=256.
    13:34:34.133 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
    13:53:19.176 Startup script...
    13:53:19.177 artsshell -q terminate
    sh: artsshell: not found
    13:53:19.581 Startup script terminated with exit status=32512.
    13:53:19.582 JACK is starting...
    13:53:19.582 /usr/bin/jackd -v -t2000 -dfreebob -dhw:0 -r96000 -p64 -n3 -D
    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_dummy.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
    13:53:19.609 JACK was started with PID=6002.
    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 @ 0x8adf130 fd = -1
    Freebob using Firewire port 0, node -1
    new buffer size 64
    LibFreeBoB MSG: FreeBoB Streaming Device Init
    LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.11
    LibFreeBoB MSG: Device information:
    LibFreeBoB MSG: Device options:
    LibFreeBoB MSG: Port : 0
    LibFreeBoB MSG: Device Node Id : -1
    LibFreeBoB MSG: Samplerate : 96000
    LibFreeBoB MSG: Period Size : 64
    LibFreeBoB MSG: Nb Buffers : 3
    LibFreeBoB MSG: Directions : 0
    Ieee1394Service::initialize: Could not get 1394 handle: Permission denied
    Is ieee1394 and raw1394 driver loaded?
    #[31mFatal (devicemanager.cpp)[68] initialize: Could not initialize Ieee1349Service object
    #[0m#[31mFatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager
    LibFreeBoB ERR: cannot create libfreebob handle
    FreeBoB ERR: FREEBOB: Error creating virtual device
    #[0mcannot load driver module freebob
    starting server engine shutdown
    stopping driver
    13:53:19.717 JACK was stopped successfully.
    13:53:19.718 Post-shutdown script…
    13:53:19.718 killall jackd
    13:53:19.719 JACK has crashed.
    jackd: no process killed
    13:53:20.130 Post-shutdown script terminated with exit status=256.
    13:53:21.785 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.

    mike

    May 20, 2009 at 11:01 am

  145. Mike: that’s very informative – thanks for posting the entire error message.

    Try this:

    # sudo modprobe raw1394
    # sudo chmod a+rw /dev/raw1394

    Then restart qjackctl.

    westcoastsuccess

    May 20, 2009 at 11:41 am

  146. tried it. nothings changed. Thanks again for all your help. I guess I might just be stuck in windows when I want to use this thing. I’m not giving up but I wouldn’t blame you if you did.

    mike

    May 20, 2009 at 12:06 pm

  147. In /etc/udev/rules.d/ make sure you have the following files:

    40-linux1394.rules
    40-linux1394.permissions

    These should contain the following:

    40-linux1394.rules:

    KERNEL=”raw1394″, NAME=”%k”
    KERNEL=”dv1394*”, NAME=”dv1394/%n”
    KERNEL=”video1394*”, NAME=”video1394/%n”

    40-linux1394.permissions:

    raw1394:root:root:0666
    dv1394/*:root:root:0666
    video1394/*:root:root:0666

    If you don’t have these, in a terminal, type:

    #sudo gedit /etc/udev/rules.d/40-linux1394.rules

    Then paste this in the blank document which opens:

    KERNEL=”raw1394″, NAME=”%k”
    KERNEL=”dv1394*”, NAME=”dv1394/%n”
    KERNEL=”video1394*”, NAME=”video1394/%n”

    Save this.

    Then, in a terminal:

    #sudo gedit /etc/udev/rules.d/40-linux1394.permissions

    And paste this in:

    raw1394:root:root:0666
    dv1394/*:root:root:0666
    video1394/*:root:root:0666

    Save.

    Now log out and back in, and try qjackctl again. If it doesn’t work, please post the exact error messages appearing in the message window.

    westcoastsuccess

    May 20, 2009 at 12:46 pm

  148. PS: the following lines in your error output tell us exactly what the problem is:

    “Ieee1394Service::initialize: Could not get 1394 handle: Permission denied”

    jackd does not have the necessary permissions to access the firewire, or the firewire module is not loaded/configured correctly.

    We’re tackling the module loading here first.

    To see if the module is loaded, you can try:

    #lsmod | grep 1394

    It should show something like:

    raw1394 32136 0
    dv1394 23656 0
    ohci1394 37172 1 dv1394
    ieee1394 109656 4 sbp2,raw1394,dv1394,ohci1394

    The next step is to post the contents of /etc/security/limits.conf.

    Then, post the output of:

    #groups username

    substituting your user name in place of “username”. This will show all the groups your user name belongs to – specifically, we’re looking for “audio”.

    westcoastsuccess

    May 20, 2009 at 12:54 pm

    • mike@desktop:~$ lsmod | grep 1394
      raw1394 32348 0
      ohci1394 37936 0
      ieee1394 96324 3 raw1394,sbp2,ohci1394

      mike

      May 20, 2009 at 1:46 pm

  149. contents of limits.conf

    # can be:
    # – an user name
    # – a group name, with @group syntax
    # – the wildcard *, for default entry
    # – the wildcard %, can be also used with %group syntax,
    # for maxlogin limit
    #
    # can have the two values:
    # – “soft” for enforcing the soft limits
    # – “hard” for enforcing hard limits
    #
    # can be one of the following:
    # – core – limits the core file size (KB)
    # – data – max data size (KB)
    # – fsize – maximum filesize (KB)
    # – memlock – max locked-in-memory address space (KB)
    # – nofile – max number of open files
    # – rss – max resident set size (KB)
    # – stack – max stack size (KB)
    # – cpu – max CPU time (MIN)
    # – nproc – max number of processes
    # – as – address space limit (KB)
    # – maxlogins – max number of logins for this user
    # – maxsyslogins – max number of logins on the system
    # – priority – the priority to run user process with
    # – locks – max number of file locks the user can hold
    # – sigpending – max number of pending signals
    # – msgqueue – max memory used by POSIX message queues (bytes)
    # – nice – max nice priority allowed to raise to values: [-20, 19]
    # – rtprio – max realtime priority
    # – chroot – change root to directory (Debian-specific)
    #
    #
    #

    #* soft core 0
    #* hard rss 10000
    #@student hard nproc 20
    #@faculty soft nproc 20
    #@faculty hard nproc 50
    #ftp hard nproc 0
    #ftp – chroot /ftp
    #@student – maxlogins 4
    @audio – rtprio 99
    @audio – memlock unlimited
    @audio – nice -10

    # End of file

    mike

    May 20, 2009 at 1:53 pm

  150. mike@desktop:~$ groups mike
    mike adm dialout fax cdrom tape audio dip video plugdev scanner fuse lpadmin netdev admin sambashare

    mike

    May 20, 2009 at 1:54 pm

  151. I don’t see a 40-linux1394.rules

    mike

    May 20, 2009 at 1:57 pm

  152. ok I had the permissions file, i added the rules file, logged out and logged in. I still get the same error message and here’s the result in messages.

    17:01:44.849 Patchbay deactivated.
    17:01:44.851 Statistics reset.
    17:01:44.961 ALSA connection graph change.
    17:01:45.159 ALSA connection change.
    17:01:46.335 Startup script…
    17:01:46.336 artsshell -q terminate
    sh: artsshell: not found
    17:01:46.737 Startup script terminated with exit status=32512.
    17:01:46.737 JACK is starting…
    17:01:46.738 /usr/bin/jackd -v -R -P89 -t2000 -dfreebob -dhw:0 -r96000 -p64 -n3 -D
    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_dummy.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
    cannot use real-time scheduling (FIFO at priority 10) [for thread -1210239312, from thread -1210239312] (1: Operation not permitted)
    cannot create engine
    cleaning up shared memory
    cleaning up files
    unregistering server `default’
    17:01:46.753 JACK was started with PID=6610.
    17:01:46.757 JACK was stopped successfully.
    17:01:46.758 Post-shutdown script…
    17:01:46.758 killall jackd
    jackd: no process killed
    17:01:47.168 Post-shutdown script terminated with exit status=256.
    17:01:48.840 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.

    mike

    May 20, 2009 at 2:03 pm

  153. Well, you’re making progress – that’s a different error message, and it’s complaining about real-time.

    Uncheck the real-time box and try again – start qjackctl from a terminal with:

    #qjackctl

    westcoastsuccess

    May 20, 2009 at 4:39 pm

    • mike@desktop:~$ qjackctl
      Warning: no locale found: /usr/share/locale/qjackctl_en_US.qm

      Here is the message I get when I start JACK.

      20:04:21.868 Patchbay deactivated.
      20:04:21.956 Statistics reset.
      20:04:21.980 ALSA connection graph change.
      20:04:22.268 ALSA connection change.
      20:04:26.735 Startup script…
      20:04:26.735 artsshell -q terminate
      sh: artsshell: not found
      20:04:27.137 Startup script terminated with exit status=32512.
      20:04:27.138 JACK is starting…
      20:04:27.138 /usr/bin/jackd -v -t2000 -dfreebob -dhw:0 -r96000 -p64 -n3 -D
      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_dummy.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
      20:04:27.151 JACK was started with PID=6435.
      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 @ 0x8ec5130 fd = -1
      Freebob using Firewire port 0, node -1
      new buffer size 64
      LibFreeBoB MSG: FreeBoB Streaming Device Init
      LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.11
      LibFreeBoB MSG: Device information:
      LibFreeBoB MSG: Device options:
      LibFreeBoB MSG: Port : 0
      LibFreeBoB MSG: Device Node Id : -1
      LibFreeBoB MSG: Samplerate : 96000
      LibFreeBoB MSG: Period Size : 64
      LibFreeBoB MSG: Nb Buffers : 3
      LibFreeBoB MSG: Directions : 0
      Ieee1394Service::initialize: Could not get 1394 handle: Permission denied
      Is ieee1394 and raw1394 driver loaded?
      Fatal (devicemanager.cpp)[68] initialize: Could not initialize Ieee1349Service object
      Fatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager
      LibFreeBoB ERR: cannot create libfreebob handle
      FreeBoB ERR: FREEBOB: Error creating virtual device
      cannot load driver module freebob
      starting server engine shutdown
      stopping driver
      20:04:27.526 JACK was stopped successfully.
      20:04:27.527 Post-shutdown script…
      20:04:27.527 killall jackd
      20:04:27.528 JACK has crashed.
      jackd: no process killed
      20:04:27.937 Post-shutdown script terminated with exit status=256.
      20:04:29.409 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.

      mike

      May 20, 2009 at 5:05 pm

  154. Have a look at /etc/udev/rules.d/40-permissions.rules – around line 28, do you have something like:

    KERNEL==”raw1394″, GROUP=”disk”
    KERNEL==”dv1394*”, GROUP=”video”
    KERNEL==”video1394*”, GROUP=”video”

    westcoastsuccess

    May 20, 2009 at 5:24 pm

  155. You said,

    #lsmod | grep 1394

    It should show something like:

    raw1394 32136 0
    dv1394 23656 0
    ohci1394 37172 1 dv1394
    ieee1394 109656 4 sbp2,raw1394,dv1394,ohci1394

    I’m noticing that I don’t have that second line… the “dv” one… could that be the problem?

    mike

    May 20, 2009 at 5:25 pm

  156. looks like I have that exactly

    # IEEE1394 (firewire) devices
    # Please note that raw1394 gives unrestricted, raw access to every single
    # device on the bus and those devices may do anything as root on your system.
    # Yes, I know it also happens to be the only way to rewind your video camera,
    # but it’s not going to be group “video”, okay?
    KERNEL==”raw1394″, GROUP=”disk”
    KERNEL==”dv1394*”, GROUP=”video”
    KERNEL==”video1394*”, GROUP=”video”

    mike

    May 20, 2009 at 5:28 pm

  157. If I recall, dv1394 is actually deprecated, so perhaps it not longer appears in the version of ubuntu you’re using. That shouldn’t be the problem, as JACK uses raw1394.

    In /etc/udev/rules.d/40-permissions.rules try changing:

    KERNEL==”raw1394″, GROUP=”disk”

    to:

    KERNEL==”raw1394″, GROUP=”audio”

    Then reboot.

    westcoastsuccess

    May 20, 2009 at 5:32 pm

  158. One other thing: in a terminal, type:

    #plugreport

    Does that show something like:

    Host Adapter 0
    ==============

    Node 0 GUID 0x000d6c0b0027cddb
    ——————————
    oMPR n_plugs=2, data_rate=2, bcast_channel=63
    oPCR[0] online=1, bcast_connection=0, n_p2p_connections=1
    channel=0, data_rate=2, overhead_id=0, payload=130
    oPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0, data_rate=0, overhead_id=0, payload=130
    iMPR n_plugs=2, data_rate=2
    iPCR[0] online=1, bcast_connection=0, n_p2p_connections=1
    channel=1
    iPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0

    This will confirm the firewire connection between the FireWire Solo and your computer is OK.

    westcoastsuccess

    May 20, 2009 at 5:36 pm

    • I changed the line you suggested and ran into problems with “plugreport.” It says it isn’t installed so I followed the terminals recommendations and this is the result…

      I’ll be back after I reboot.

      mike@desktop:~$ plugreport
      The program ‘plugreport’ is currently not installed. You can install it by typing:
      sudo apt-get install libiec61883-dev
      bash: plugreport: command not found
      mike@desktop:~$ sudo apt-get install libiec61883-dev
      Reading package lists… Done
      Building dependency tree
      Reading state information… Done
      The following NEW packages will be installed:
      libiec61883-dev
      0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
      Need to get 44.0kB of archives.
      After this operation, 205kB of additional disk space will be used.
      Get:1 http://us.archive.ubuntu.com intrepid/main libiec61883-dev 1.1.0-2ubuntu2 [44.0kB]
      Fetched 44.0kB in 0s (88.5kB/s)
      Selecting previously deselected package libiec61883-dev.
      (Reading database … 169079 files and directories currently installed.)
      Unpacking libiec61883-dev (from …/libiec61883-dev_1.1.0-2ubuntu2_i386.deb) …
      Setting up libiec61883-dev (1.1.0-2ubuntu2) …
      mike@desktop:~$ plugreport
      raw1394 – couldn’t get handle: Permission denied
      This error usually means that the raw1394 driver is not loaded or that /dev/raw1394 does not exist.
      mike@desktop:~$

      mike

      May 20, 2009 at 5:43 pm

  159. Do you have a file called “raw1394″ in /dev?

    If not, in terminal:

    #sudo modprobe raw1394

    Then check /dev again.

    What I can’t understand is why:

    #lsmod | grep 1394

    is showing that the module is installed!

    westcoastsuccess

    May 20, 2009 at 5:55 pm

  160. here’s the new error message. everything before the group of “LibFreeBoB MSG:” lines is still the same.

    Root node has no children!
    Root node has no children!
    LibFreeBoB ERR: No connections specified, bailing out
    FreeBoB ERR: FREEBOB: Error creating virtual device
    cannot load driver module freebob
    starting server engine shutdown
    stopping driver
    20:50:21.019 JACK was stopped successfully.
    20:50:21.019 Post-shutdown script…
    20:50:21.020 killall jackd
    20:50:21.020 JACK has crashed.
    jackd: no process killed
    20:50:21.447 Post-shutdown script terminated with exit status=256.
    20:50:22.790 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.

    mike

    May 20, 2009 at 5:55 pm

  161. yes the file raw1394 is there. If you want I’ll list all the files in the /dev

    mike

    May 20, 2009 at 5:57 pm

  162. Sorry, we were tied up in a recording session…

    Does:

    #plugreport

    work now?

    westcoastsuccess

    May 21, 2009 at 12:29 am

    • No sweat I appreciate that you’ve stuck w/ me this long.

      So after a complete shutdown and a few hours off I restarted the computer this morning and ran JACK just for the hell of it. Apparently it works. I’m getting xruns every few seconds but it isn’t shutting down.

      Here are the results for plugreport…

      mike@desktop:~$ plugreport
      Host Adapter 0
      ==============

      Node 0 GUID 0x00e0180000c5883f
      ——————————
      libiec61883 error: error reading oMPR
      libiec61883 error: error reading iMPR

      Node 1 GUID 0x000d6c0b0031afec
      ——————————
      oMPR n_plugs=2, data_rate=2, bcast_channel=63
      oPCR[0] online=1, bcast_connection=0, n_p2p_connections=1
      channel=0, data_rate=2, overhead_id=0, payload=130
      oPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
      channel=0, data_rate=0, overhead_id=0, payload=130
      iMPR n_plugs=2, data_rate=2
      iPCR[0] online=1, bcast_connection=0, n_p2p_connections=1
      channel=1
      iPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
      channel=0

      mike

      May 21, 2009 at 6:42 am

  163. Also, in qjackctl “Setup”, on the “Settings” tab, try changing the Interface drop-down from “HW0″ to “HW1″ and see if that helps.

    westcoastsuccess

    May 21, 2009 at 12:49 am

  164. since HW0 seems to be working now I’m not changing it until further notice. I’m going back to the tutorial and the previous comments to see where I can get to with this.

    mike

    May 21, 2009 at 6:48 am

  165. ok moving down the steps, i’ve got ardour and jack up. When I go to the “connections” box on JACK the audio option doesn’t display anything. Both boxes are empty. There is nothing to connect.

    mike

    May 21, 2009 at 7:04 am

  166. ok sorry solved that. JACK wasn’t running

    mike

    May 21, 2009 at 7:06 am

  167. ok in the connection box I don’t have freebob. I have system and ardour.

    mike

    May 21, 2009 at 7:14 am

  168. ok just saw your comment about that above I guess that isn’t the problem.

    mike

    May 21, 2009 at 7:25 am

  169. so after another shutdown and restart it seems the mic is being detected in ardour.

    I’m having problems hearing anything though. I don’t have the appropriate jack on my headphones to plug into the firewire solo… they are plugged into my crap computer speakers.

    I’m open to suggestions but I think the solution to this may already be in the comments above. I’ll be back later.

    mike

    May 21, 2009 at 9:34 am

  170. That’s great to hear, Mike!

    Have a good read through the various comments posted above re: getting sound out of Ardour.

    If you’ve tried all those, post back (post if you solve it, too!).

    Our setup runs a cable from the headphone output to the line input on the computer’s sound card (which in turn runs through an amplifier to some speakers). That’s just for quick and dirty reviews of material – much of the work is done using headphones out of the FireWire Solo’s headphone jack, or S/PDIF cables out the back and into an amp, then to proper monitor speakers.

    Good luck!

    westcoastsuccess

    May 21, 2009 at 12:33 pm

  171. ok first thanks for getting me this far wcs.

    I got a jack adapter for my headphones and I can now hear what I’m recording.

    A few issues to go…

    The first one is when I play back what I’ve recorded I can only hear sound in the left headphone. I thought I saw something here explaining that but now I can’t find it.

    Second I’m getting regular X runs and the settings are set to the starting settings above with a result of 16 ms latency.

    feeling like I’m getting close to this finish line… thanks.

    mike

    May 21, 2009 at 2:23 pm

  172. ok I believe the one speaker thing is related to the jack adapter I bought.

    The xrun thing has me stumped.

    mike

    May 21, 2009 at 3:30 pm

  173. Check your qjackctl connections box – make sure the “Master” outputs on the left side are going to both the left and right inputs on “System” in the right side.

    As for X-Runs, do you have the “Real-time” box checked? If not, do so and see if that helps.

    Also, try backing off the latency even farther – if you’re not using the real-time kernel, it’s unlikely you’ll get down to (or even close to) our 2ms latency.

    In answer to your post in the Ubuntu forum, I’m not at all sure about how to safely downgrade to Hardy – I’ve read many comments that it can’t easily be done and a few that say it can. Apparently it helps if your /home folder is in a separate partition.

    Depending on how much you’ve altered on your system, you may wish to consider backing up your documents/unique config files, etc. and installing Hardy from scratch.

    If you have (or get) an external hard drive, you could back up your relevant folders to it, try the downgrade and then attempt to move back what you need from the external drive. Do so at your own risk – we have no idea how easily this is done, particularly with respect to configuration files.

    As an aside, we use an external 500GB hard drive connected via USB which backs up at 4am each day. Once a week it makes an entire backup of the directories we want; other days it only backups whatever has changed. We use “Simple Backup”, which should be available in Synaptic. External drives like ours are available for about $100. If you’re doing any kind of serious recording, you most certainly want to back up everything you record – one failed hard drive and you can lose thousands of hours of work.

    westcoastsuccess

    May 21, 2009 at 4:15 pm

  174. So setting JACK to “realtime” allows me to hear the mic in the left headphone. However since then ardour isn’t recording the mic anymore. I’ve messed with all the settings trying to figure out why and haven’t come up with anything. Putting things back the way I believed they were hasn’t helped. I must be missing something.

    As far as hearing anything in the right speaker of the headphones that’s the least of my worries right now. I’m fairly certain I have a mono jack adapter. I’ll exchange it tomorrow and if that doesn’t work I’ll worry about that after I solve the other problems.

    mike

    May 21, 2009 at 9:21 pm

  175. I don’t know what happened.

    Everything seems to be working ok except for the fact that sound isn’t being detected by ardour. I have my connections set up exactly like you’ve outlined above except I have capture 1 in place of capture 2 since I’m trying to get the mic. It was working before.

    I try it w/ realtime on and off and no difference.

    any suggestions.

    mike

    May 22, 2009 at 1:39 pm

  176. ok i have a dual boot with windows abd aparently that makes a difference. AI rarely use windows. What do I have to do differently?

    mike

    May 23, 2009 at 2:22 pm

  177. OK so I’m stuck.

    Here’s what I did…
    In windows I uninstalled all the software and drivers associated with the unit and disconnected it. Then I reinstalled everything, including audacity, and got the unit up and running again in windows. I opened the control panel for the unit, made sure it was working properly then booted up ubuntu.

    In ubuntu I made sure my JACK connections were set up the way WCS outlined in one of the earlier comments. I started ardour and jack and messed with the Jack settings.

    Nothing worked for me. Really frustrating since I had it working until I messed with the settings.

    Anyway this is why I still run a dual boot with windows… looks like I’m going to be dependent on MS for a little bit longer.

    I’ve wasted too much time on this. I will check back periodically to see if anyone has any new suggestions.

    Thanks for all the help. It is appreciated in spite of the results. I know each situation is unique.

    mike

    May 28, 2009 at 8:55 am

  178. laban posted the following, which we inadvertently deleted:

    I had the same problem with ubuntu. I found the problem to be the firmware in my fw-solo device. The solution was to install an older firmware( from 2004) and then sound flows out of my earphones

    the firmware was named “FW_WDM_5.10.0.5036.exe”
    just remember to wash your hands after shuting down Windows.

    westcoastsuccess

    August 4, 2009 at 2:10 pm

  179. Many thanks, laban – that’s an important piece of information, which we’ll be sharing with M-Audio.

    westcoastsuccess

    August 4, 2009 at 2:11 pm

  180. For those of you who have followed all the instructions and are still having trouble with sound output from the FireWire Solo, please consider changing firmware to version FW_WDM_5.10.0.5036.exe.

    You can find it here:

    http://www.m-audio.com/index.php?do=support.drivers&f=760

    Please also note that you shouldn’t have to update or install _any_ firmware – it ought to work out of the box.

    westcoastsuccess

    August 4, 2009 at 2:35 pm

    • Is there a way to load this firmware version onto the device without a Windows 32-bit machine? I have access to my Mac and linux box, as well as XP64 at work. I can’t find a way to manually upload firmware to the FW Solo.

      In a pinch I can partition and install windows on the linux box, but the hard drive is rather small and I hate to give up the space (or risk losing data during partitioning).

      Aaron

      August 11, 2009 at 6:02 am

  181. Hi.
    I can’t get gscanbus going. It’s not in Jaunty’s Synaptic so I downloaded it through GDebi Package Installer only to get this – “Error: Dependency is not satisfiable: libglib1.2 (>= 1.2.0)”. I have libglib1.2 installed in Synaptic. Please help, I’d love to get my guitar going with Ubuntu.

    guitarless

    August 24, 2009 at 2:26 am

  182. You can try compiling it yourself:

    Download the source code here:

    http://prdownload.berlios.de/gscanbus/gscanbus-0.7.1.tgz

    Save it to your desktop, then double-click the icon, which should allow you to extract the files. Extract it to your desktop.

    In a terminal, navigate to the extracted folder:

    #cd ~/Desktop/gscanbus-0.7.1

    (without the “#”).

    Then type:

    #./configure
    #make
    #make install

    (hit “enter” after each line, and again, omit the “#”).

    If you get an error message, please post the complete message and we’ll try to troubleshoot.

    Cheers, and good luck!

    westcoastsuccess

    August 24, 2009 at 3:24 am

  183. Hi, thanks for the reply, it’s much apprieciated. I gave it several goes and got it this far:

    qwe321@larstop:~/Desktop/gscanbus-0.7.1$ ./configure
    loading cache ./config.cache
    checking for a BSD compatible install… (cached) /usr/bin/install -c
    checking whether build environment is sane… yes
    checking whether make sets ${MAKE}… (cached) yes
    checking for working aclocal… found
    checking for working autoconf… found
    checking for working automake… found
    checking for working autoheader… found
    checking for working makeinfo… found
    checking for gcc… (cached) gcc
    checking whether the C compiler (gcc ) works… yes
    checking whether the C compiler (gcc ) is a cross-compiler… no
    checking whether we are using GNU C… (cached) yes
    checking whether gcc accepts -g… (cached) yes
    checking for a BSD compatible install… /usr/bin/install -c
    checking for raw1394_new_handle in -lraw1394… (cached) yes
    checking for gtk-config… (cached) /usr/bin/gtk-config
    checking for GTK – version >= 1.2.0… yes
    checking how to run the C preprocessor… (cached) gcc -E
    checking for ANSI C header files… (cached) yes
    checking for sys/time.h… (cached) yes
    checking for unistd.h… (cached) yes
    checking for libraw1394/raw1394.h… (cached) yes
    checking for working const… (cached) yes
    checking for size_t… (cached) yes
    creating ./config.status
    creating Makefile
    qwe321@larstop:~/Desktop/gscanbus-0.7.1$ make
    gcc -DPACKAGE=\”gscanbus\” -DVERSION=\”0.7.1\” -DHAVE_LIBRAW1394=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TIME_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIBRAW1394_RAW1394_H=1 -I. -I. -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -g -O2 -c gscanbus.c
    gscanbus.c:112:31: warning: missing terminating ” character
    gscanbus.c:112: error: missing terminating ” character
    gscanbus.c:114: error: ‘version’ undeclared here (not in a function)
    gscanbus.c:114: error: expected ‘,’ or ‘;’ before ‘that’
    gscanbus.c:115: error: stray ‘\’ in program
    gscanbus.c:115:42: warning: missing terminating ” character
    gscanbus.c:115: error: missing terminating ” character
    gscanbus.c:117:27: warning: missing terminating ” character
    gscanbus.c:117: error: missing terminating ” character
    gscanbus.c:119:10: warning: missing terminating ‘ character
    gscanbus.c:119: error: missing terminating ‘ character
    gscanbus.c: In function ‘main’:
    gscanbus.c:1086: warning: format not a string literal and no format arguments
    gscanbus.c:1089: error: ‘not_loaded’ undeclared (first use in this function)
    gscanbus.c:1089: error: (Each undeclared identifier is reported only once
    gscanbus.c:1089: error: for each function it appears in.)
    gscanbus.c:1089: warning: format not a string literal and no format arguments
    make: *** [gscanbus.o] Error 1

    I did a lot of reading and installing of things just to get it this far. What do you make of it? I’d love to know.

    guitarless

    August 25, 2009 at 2:14 am

  184. Try this, for a start:

    Open the file “gscanbus.c” in your gscanbus-0.7.1 folder (right click and select “Open with Text Editor”).

    Go to line 113 (if Text Editor isn’t showing line numbers, go to Preferences in the Edit menu – under the View tab, put a check mark next to “Display Line Numbers”).

    At the very end of line 113, add the backslash character (“\”).

    Do the same for lines 114 and 118.

    Save, then try to compile it again.

    To explain: as I understand it, without the backslash, the compiler thinks the next line is a new line, rather than a continuation of the same line. The backslash tells it to ignore the line break and continue as tho it’s the same line.

    See if that gets you any farther.

    Good luck!

    westcoastsuccess

    August 25, 2009 at 8:06 am

  185. Okay, I fixed the backslashes then ran ./configure and make again. ./configure was identical to the last time so here’s from make onwards:

    qwe321@larstop:~/Desktop/gscanbus-0.7.1$ make
    make: Nothing to be done for `all’.
    qwe321@larstop:~/Desktop/gscanbus-0.7.1$ make install
    make[1]: Entering directory `/home/qwe321/Desktop/gscanbus-0.7.1′
    /bin/sh ./mkinstalldirs /usr/local/bin
    /usr/bin/install -c gscanbus /usr/local/bin/gscanbus
    /usr/bin/install: cannot remove `/usr/local/bin/gscanbus’: Permission denied
    make[1]: *** [install-binPROGRAMS] Error 1
    make[1]: Leaving directory `/home/qwe321/Desktop/gscanbus-0.7.1′
    make: *** [install-am] Error 2
    qwe321@larstop:~/Desktop/gscanbus-0.7.1$

    I ran make install as well but I guess we’re not ready for that yet.

    guitarless

    August 26, 2009 at 1:31 am

    • Try:

      #sudo make install

      westcoastsuccess

      August 27, 2009 at 8:56 am

  186. I have been trying to get this card working with a 64 bit ubuntu 9.04 laptop:

    Linux rose 2.6.28-3-rt #12-Ubuntu SMP PREEMPT RT Fri Apr 17 10:09:12 UTC 2009 x86_64 GNU/Linux

    But it doesn’t work. I have tried both drivers in qjackctl:

    freebob:

    playback and record work well though there are frequent xruns at 4ms latency. but at some point (say in five minutes) there is a freeze of the entire system, so that the power button is needed to restart.

    firewire (ffado):

    again playback and record work well though there are frequent xruns at 4ms latency. but now at some point (say in five minutes) jackd crashes. the crash message in qjacktl is:

    firewire ERR: wait status < 0! (= -1)
    DRIVER NT: could not run driver cycle

    the complete message contents are pasted here:

    http://pastebin.com/f1ea71acb

    after the crash, i can reset with gscanbus and hit start again in qjackctl and it will work again until another crash.

    this is super annoying!!! can anyone please help?

    Kitty Wallie

    August 26, 2009 at 12:50 pm

  187. hmm… I tried with the latest home compiled jackdmp and now it doesn’t seem to crash but I get a lot of xruns. With your settings (the ones leading to 2ms latency), I get an xrun every zero to five seconds. a message window output for the case of starting jack with the firewire driver, letting a couple of xruns occur, then shutting down, is here:

    http://pastebin.com/f5e1550b3

    the same thing for freebob is here:

    http://pastebin.com/f3eea0e68

    One dubious thing in both of these is this line:

    Jack: JackEngine::NotifyClients: no callback for event = 4

    in both of the outputs and

    Jack: JackEngine::NotifyClients: no callback for event = 3

    additionally in the firewire message window. I cannot find much about this on the net. Has anyone else run into this, or can anyone recommend anything?

    Kitty Wallie

    August 27, 2009 at 2:25 am

  188. There are known, serious problems with the real-time kernel on any version of Ubuntu after 8.04 (Hardy Heron).

    We know of no workarounds or solutions to date (and it’s why our machines haven’t been upgraded beyond 8.04).

    We’ll check to see if any progress has been made…

    westcoastsuccess

    August 27, 2009 at 8:58 am

  189. Sorry I should have seen that in the comments above. Does this mean I need to try to revert to the previous ubuntu somehow? Perhaps it is sufficient to compile a certain version of the kernel?

    Kitty Wallie

    August 27, 2009 at 12:14 pm

  190. Hello.

    I have just tried to set things up as you wrote.

    I did all. I can hear my guitar’s sound from my sound card (( as I can do it without plugging into a computer too )) but the mixer does not show anything.

    And I have the client problem everytime when I start jack. But ıf I push the start button of jack “after” I start ardour, I have no problem.

    I am a lot of confused. I am not wishing to use ardour, I can record on Win, but I want to listen music with my sound card on Ubuntu!

    Nezurian

    September 8, 2009 at 12:46 pm

  191. Nezurian: have you added a track in Ardour and enabled it? Click “File”, select “Add Track/Bus”, add a track, then click the red circle next to the track you’ve added to enable it. Make sure your connections are correct in qjackctl Connections box.

    Can you please post the error messages you’re getting when you try to start JACK?

    westcoastsuccess

    September 11, 2009 at 10:48 am

    • hello :)

      I know all about recording stuff, and yes I (( of course )) added a track and push the record button and checked the mixer.

      I am not able to send you the error files ((I screwed to ubuntu – I cannot use my sound card!)) but I will send you them as soon as I reinstall my ubuntu and try once again.

      Thank you for your interest.

      nezurian

      September 18, 2009 at 2:55 pm

  192. hello.

    I checked it today again, and now jack does not show any error messages.

    But I still have nothing -mixer does not show anything-

    I think this is about the connections. I plug a jack into a guitar input of Solo, and have my noise from my reference monitors (they are pluggred in Balanced Outputs). But nothing more. and in the connetions list I don’t have freebob_pcm or something like that – I have 2 expandable buttons named Ardour and System. and when I expand them, I do not understand anything. Actually I can send you a Screenshot for it too.

    so, What do you think? :)

    Nezurian

    September 19, 2009 at 4:12 am

  193. 19:08:15.301 Patchbay deactivated.
    19:08:15.674 Statistics reset.
    19:08:15.932 ALSA connection graph change.
    19:08:15.937 ALSA connection change.
    19:08:17.503 Startup script…
    19:08:17.504 artsshell -q terminate
    19:08:17.931 Startup script terminated with exit status=256.
    19:08:17.932 JACK is starting…
    19:08:17.932 /usr/bin/jackd -v -R -P89 -t2000 -dfreebob -dhw:0 -r48000 -p256 -n3 -D
    getting driver descriptor from /usr/lib/jack/jack_oss.so
    getting driver descriptor from /usr/lib/jack/jack_dummy.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
    cannot use real-time scheduling (FIFO at priority 10) [for thread -1210292560, from thread -1210292560] (1: Operation not permitted)
    cannot create engine
    cleaning up shared memory
    cleaning up files
    unregistering server `default’
    19:08:17.966 JACK was started with PID=8275.
    19:08:17.985 JACK was stopped successfully.
    19:08:17.986 Post-shutdown script…
    19:08:17.987 killall jackd
    jackd: no process killed
    19:08:18.399 Post-shutdown script terminated with exit status=256.
    19:08:19.971 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.

    BAH! :(

    Nezurian

    September 20, 2009 at 9:10 am

    • You need to run gsanbus.

      Open a terminal (Applications; Accessories; Terminal), type “gscanbus”, then, in the box which opens, click “Control”, then “Force Bus Reset”. Then try qjackctl again – should work.

      As for your connections, if you’re plugging into the front guitar jack, firstly check that the “Input Select” button is out. Secondly, your connections in the Connections box of qjackctl should be:

      System Ardour
      “capture_2″ –> “Audio 1/In 1″
      Ardour Ardour
      “Audio 1/Out 1″ –> “master/in 1″
      “Audio 1/Out 2″ –> “master/in 2″
      Ardour System
      “master/out 1″ –> “playback_1″
      “master/out 2″ –> “playback_2″

      I’m assuming here you are not using S/PDIF cables to connect from your FireWire Solo to a stereo/amp/etc.

      westcoastsuccess

      September 20, 2009 at 11:33 pm

  194. nezurian@nezurian-desktop:~$ qjackctl
    Warning: no locale found: /usr/share/locale/qjackctl_en_GB.qm

    Is this a problem?

    and

    nezurian@nezurian-desktop:~$ gscanbus
    couldn’t get handle: Permission denied
    This probably means that you don’t have raw1394 support in the kernel or that
    you haven’t loaded the raw1394 module.

    Is this a problem?

    I can open gscanbus while I am root. But I click on force reset button, but nothing happens actually. The qjackctl’s behaviour does not change at all.

    I know It’s becoming a headache but I need to solve this :(

    Nezurian

    September 21, 2009 at 10:16 am

  195. Can you post the output of:

    #lsmod | grep 1394

    (omitting “#”)?

    This will list all modules loaded which contain “1394″. The output should show something like:

    raw1394 32136 0
    dv1394 23656 0
    ohci1394 37172 1 dv1394
    ieee1394 109656 4 sbp2,raw1394,dv1394,ohci1394

    From the instructions, make sure you’ve carefully followed these steps:

    Next you need to make the following change to add your user name to the “disk” group so that you’ll be able to get a 1394 handle (read: so you’re able to use the firewire port):

    # useradd -G disk username

    replacing your user name in “username”.

    In order to run JACK with real time priority without being root, you’ll need to edit your /etc/security/limits.conf file. Open a terminal and type:

    #sudo gedit /etc/security/limits.conf

    That’ll bring up a text editor showing the contents of limits.conf. Add the following to the end of the file (but before the line “End of file” – that should remain the last line) and save it:

    @audio – rtprio 99
    @audio – memlock unlimited
    @audio – nice -10

    It seems to me you don’t have permission to access the module as your regular user.

    When you click the reset button in gscanbus, nothing visibly will happen, however it should reset your firewire bus.

    Also, what’s the output of:

    #plugreport

    That will show you if your system is detecting your FireWire Solo – it’ll output something like this:

    Node 0 GUID 0x001371fffea10437
    ——————————
    oMPR n_plugs=1, data_rate=2, bcast_channel=63
    oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
    channel=63, data_rate=2, overhead_id=0, payload=376
    iMPR n_plugs=0, data_rate=2

    Node 1 GUID 0x0011d80000b4fd78
    ——————————
    libiec61883 error: error reading oMPR
    libiec61883 error: error reading iMPR

    Node 2 GUID 0x000d6c0b0027cddb
    ——————————
    oMPR n_plugs=2, data_rate=2, bcast_channel=63
    oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
    channel=63, data_rate=2, overhead_id=0, payload=130
    oPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0, data_rate=0, overhead_id=0, payload=130
    iMPR n_plugs=2, data_rate=2
    iPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
    channel=63
    iPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0

    In our case, node 2 is the Solo.

    westcoastsuccess

    September 21, 2009 at 6:10 pm

  196. Hello!


    root@nezurian-desktop:/home/nezurian# lsmod | grep 1394
    dv1394 20664 0
    raw1394 29272 0
    ohci1394 33584 1 dv1394
    ieee1394 93752 4 sbp2,dv1394,raw1394,ohci1394


    I checked all the steps 3 times again and again:

    root@nezurian-desktop:/home/nezurian# useradd -G disk nezurian
    useradd: user nezurian exists


    Plugreport was not installed, so I installed it with apt-get.

    the results:

    Host Adapter 0
    ==============

    Node 0 GUID 0x0010dc00005da22c
    ——————————
    libiec61883 error: error reading oMPR
    libiec61883 error: error reading iMPR

    Node 1 GUID 0x000d6c0b00c49f12
    ——————————
    oMPR n_plugs=2, data_rate=2, bcast_channel=63
    oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
    channel=1, data_rate=2, overhead_id=0, payload=130
    oPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0, data_rate=0, overhead_id=0, payload=130
    iMPR n_plugs=2, data_rate=2
    iPCR[0] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0
    iPCR[1] online=1, bcast_connection=0, n_p2p_connections=0
    channel=0
    No node 2 section. I guess, That means my system does not detect my FW solo :(

    Nezurian

    September 22, 2009 at 1:10 am

  197. Your system is indeed detecting the Solo, it just so happens that on our system, we have three nodes (0, 1 and 2) and ours happens to be assigned to node 2. You have 2 nodes (0 and 1) and the Solo is assigned to node 1.

    I’m curious why you are logged in as root (ie it shows “root@nezurian-desktop” – if your user name is “nezurian” (which is the user name you’re adding to the “disk” group when you do:

    #root@nezurian-desktop:/home/nezurian# useradd -G)

    you should be logged in as that user).

    Try logging out and then back in as “nezurian”.

    As an aside, it’s not a good idea to regularly run as root – it can expose security vulnerabilities and also opens the possibility of damaging your set up by accidentally running a command with root privileges (ie you’re able to do things to your system you ordinarily would require specific permission to do). If you need to run commands or modify files with root privileges, you should be logged in as your user name (“nezurian”) and preface root commands with “sudo”.

    If logging in as “nezurian” doesn’t solve the problem, then, still logged in as “nezurian”, open a terminal and type:

    #sudo qjackctl

    Then open another terminal and type:

    #sudo ardour2

    Let us know if either solution works.

    Good luck!

    westcoastsuccess

    September 22, 2009 at 7:57 am

  198. Hello :) You seem to think the situation in all dimensions, thats fine but;

    actually, I do login (always) as “nezurian”. I must have happen to use the command “su” and type my password before I use the other commands. So it shows root@nezurian etc….

    So the problem I guess is not about the login. :/

    nezurian

    September 23, 2009 at 12:42 pm

  199. OMG! The sudo trick worked!

    I am (at least) able to record and listen the guitar. Thanks a lot.

    Now I have to find a plugin to use the jack to get sound from the applications. I think there’s one for it.

    Thank you a lot :)))

    Nezurian

    September 23, 2009 at 12:54 pm

  200. ehm, Hello Again :)

    I cannot find any solutions for directing all the system sound to Jack.

    I mean, could be there a way to take all the signal goes to my onboard soundcard (which ubuntu detects) and direct it to jack and then to my FW Solo, and to my monitors?

    AS I wrote, I think there’s a plugin or something like that for it, but I could’nt find it.

    I also tried using some of the media players that supported by Jack but I got no sound from them.

    Thanks a lot, again. It’s very kind of you :)

    Nezurian

    September 23, 2009 at 1:54 pm

  201. For applications like MPlayer to use JACK, I believe you have to compile them with that option.

    You can check this link for more info:

    http://parumi.wordpress.com/2007/12/16/how-to-enable-jack-in-mplayer-ubuntu-gutsy/

    To route all sound thru JACK, check this link:

    http://ubuntuforums.org/showthread.php?t=548178

    Make sure you scroll down as there’s a fix in the second post.

    This is beyond the scope of this instruction set (ie we focus here on getting the M-Audio FireWire Solo to work with Ardour for the purposes of recording guitar), but we’d be happy to hear how it turns out.

    We likewise make no claims of fitness or other warranties about the above links – they’re simply the result of a quick google search on this topic.

    Good luck!

    PS: unless there’s a particularly compelling reason to use “su”, you shouldn’t really ever have to use that with Ubuntu – “su” switches to the root user; use “sudo” instead to run a particular, single command as root without switching back and forth between the regular user and root. It’s safer, smarter and easier.

    westcoastsuccess

    September 25, 2009 at 6:33 pm

  202. PS: the fact you can get it to work with “sudo” tells us that you have a permission problem. Either the limits.conf file is, in fact, not correct, or some files have incorrect permissions set.

    Can you post the output of:

    #ls – l /usr/bin/qjackctl

    Here’s what it should look like:

    -rwxr-xr-x 1 root root 219 2008-02-07 20:47 /usr/bin/qjackctl

    Also:

    #ls -l /usr/bin/qjackctl.bin

    which should return:

    -rwxr-xr-x 1 root root 913808 2008-02-07 20:49 /usr/bin/qjackctl.bin

    And:

    #ls -l /usr/bin/ardour2

    which should show:

    -rwxr-xr-x 1 root root 587 2008-07-12 12:34 /usr/bin/ardour2

    westcoastsuccess

    September 25, 2009 at 6:41 pm

  203. Hello :)

    Actually I wrote the commands you gave but the result is

    nezurian@nezurian-desktop:~$ #ls -l /usr/bin/ardour2
    nezurian@nezurian-desktop:~$ #ls -l /usr/bin/qjackctl.bin
    nezurian@nezurian-desktop:~$ #ls – l /usr/bin/qjackctl
    nezurian@nezurian-desktop:~$

    I copy pasted the commands that you wrote to my terminal. So there mustn’t be a typing problem.

    ?!

    Nezurian

    September 28, 2009 at 10:13 am

  204. Hi,

    I am a Linux newbie. Using Ubuntu Studio 9.10
    I am unable to get Ardour to see any sound from the Firewire Solo.

    gscanbus gives this message:
    Gtk-WARNING **: Failed to load module “libcanberra-gtk-module.so”: libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
    Than shows the Solo connected. I am able to force bus reset but no joy.

    I am in Vancouver Canada. If more convenient, please email me graham2128@gmail.com

    Thanks!
    Al

    graham2128

    December 7, 2009 at 12:18 am

  205. Hi Al,

    That’s interesting – we haven’t come across that error before.

    Can you please post the output of:

    #ls -l /etc/X11/Xsession.d/

    Also, can you search Synaptic for “libcanberra” and report which files are installed (ie version number; full file name)?

    westcoastsuccess

    December 7, 2009 at 1:44 am

    • Thanks WCS. I appreciate all the work you’ve put into this site. Also I am grateful that you did not advise (so far, anyway) to regress from Ubuntu 9.10 to 8.04.

      When I started this, I simply downloaded the latest version of Ubuntu; did not see your reference to Hardy Heron (8.04) until wading into the weeds of all the replies on this site. I’d like to get the Solo working with Ubuntu Studio 9.10 if possible, but if you think I am heading for a brick wall, please go ahead and make the call for me to load 8.04.

      Below is the output of:
      #ls -l /etc/X11/Xsession.d/
      total 56
      -rw-r–r– 1 root root 1878 2008-06-24 19:05 20×11-common_process-args
      -rw-r–r– 1 root root 102 2009-10-12 14:55 25ubuntustudio-menu
      -rw-r–r– 1 root root 899 2008-06-24 19:05 30×11-common_xresources
      -rw-r–r– 1 root root 187 2008-06-24 19:05 40×11-common_xsessionrc
      -rw-r–r– 1 root root 1561 2008-06-24 19:05 50×11-common_determine-startup
      -rw-r–r– 1 root root 197 2009-10-07 16:01 52libcanberra-gtk-module_add-to-gtk-modules
      -rw-r–r– 1 root root 656 2009-10-23 03:49 55gnome-session_gnomerc
      -rw-r–r– 1 root root 80 2009-10-15 05:16 60xdg-user-dirs-update
      -rw-r–r– 1 root root 329 2009-10-26 02:42 70pulseaudio
      -rw-r–r– 1 root root 381 2009-10-23 20:28 75dbus_dbus-launch
      -rw-r–r– 1 root root 2307 2008-01-08 02:41 80im-switch
      -rw-r–r– 1 root root 274 2009-08-23 22:17 90consolekit
      -rw-r–r– 1 root root 642 2008-08-05 16:37 90×11-common_ssh-agent
      -rw-r–r– 1 root root 166 2008-06-24 19:05 99×11-common_start

      Below is a link to a screenshot with the results of searching Synaptic for “libcanberra” :

      http://tinypic.com/r/9zn8qs/6

      Thanks
      Al

      graham2128

      December 7, 2009 at 10:16 am

  206. That’s very odd – Synaptic shows you have libcanberra-gtk-module installed, but it’s not putting libcanberra-gtk-module.so in /etc/X11/Xsession.d/

    Can you search your system for libcanberra-gtk-module.so? In case you’re unfamiliar how to do this, click “Places” on your panel, select “Search for Files…”, put “libcanberra” in the “Name contains” field, select “File system” from the “Look in folder” drop down and make sure the options include “Show hidden and backup files” and “Include other file systems” (just hit the “+Add” button and select from the drop down). Then hit “Find”. Let’s see if it’s on your system elsewhere, which we can then create a link to, which I’m hoping will solve the problem.

    I have no idea why canberra should be required by JACK – it’s not required on our system, as we don’t have it installed and it’s not available in the 8.04 repositories without being specifically added. It does seem there’s some sort of bug in canberra, as there are plenty of reports of other programs having dependency issues with canberra.

    As for 9.10 vs 8.04, I haven’t looked into the real-time issue for a while – as far as I know from prior research, there remains no way to enable real-time scheduling in anything beyond 8.04. We’ll check it out and advise.

    You should still be able to set up your FireWire Solo on a post-8.04 version, you just won’t get the latencies you would with a real-time kernel/scheduling. Depending on what you’re doing, the latencies you get may work for you, or may not.

    If I recall, it’s said that humans can’t pick up latencies below 16ms, but our opinion is that _any_ latency affects the “feel” of the song.

    For example, when recording a guitar solo, the player is responding to the music and intending to place a note at a very particular location in time, which contributes to the “feel” of the song.

    Ardour can compensate somewhat for latency, and there are other things you can do, such as simply move back the recorded track by an amount equal to the one-way latency.

    What’s also important is how the guitar player in the example is listening to his/her guitar as he/she plays. If the sound of the guitar is being monitored at the track, there will be a gap in time between striking a note and hearing it struck. If monitoring the guitar “live” against the track, the note will sound “on” when played, but may sound “off” on the track, because the point in time when the guitarist struck the note is not the same point in time as when Ardour recorded the note being struck, vs the other tracks.

    If, instead, you’re doing a lot of editing or recording digital instruments or samples or such, or splicing together bits and pieces here and there, you’ll never get that “real-time” feel anyway (tho you can approximate it). For example, notes which are “spot-on” the beat, every time, do not sound remotely natural. A human playing an instrument is much more nuanced.

    Hope that makes some sort of sense!

    westcoastsuccess

    December 7, 2009 at 11:30 am

  207. OK, we checked out the status of the real-time kernel in the latest versions of Ubuntu (9.10) and it seems some have it working and most don’t.

    Here are some links:

    https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/407660

    (note that Alessio Igor Bogani calls it a “significant bug in Ubuntu” – Alessio is a key developer of the real time kernel)

    http://ubuntuforums.org/showthread.php?t=1310225

    http://ubuntuforums.org/showthread.php?t=1322074

    It seems some of the problems were related to the proprietary NVidia driver and NVidia appears to have addressed this in subsequent driver releases.

    For our systems, we are not comfortable enough with the status of the real-time kernel post-8.04 to even begin to consider “upgrading”.

    westcoastsuccess

    December 7, 2009 at 11:44 am

  208. Thanks WCS. Makes sense. Thanks for the clear explanation. I think I will give the version 9.10 a shot. (there’s probably a better chance of this working than the Canucks winning the cup this season!

    After doing the search for libcanberra files I came up with 37 files. Here are 3 screen shots of all the files:

    http://tinypic.com/view.php?pic=s4yphx&s=6
    http://tinypic.com/view.php?pic=23vay38&s=6
    http://tinypic.com/r/2is8r9v/6

    I am running this on a 1GHz i386 (kinda like the Kyle Wellwood of PC’s)

    graham2128

    December 7, 2009 at 10:33 pm

  209. That’s more like the Sundin of PCs: old and slow!

    The file that gscanbus is looking for appears to be located at /usr/lib/gtk-2.0/modules/ – but it’s not clear to me where the link should be.

    In re-reading your initial post it only seems to throw up the error for gsanbus, but allows it to function anyway.

    (As an aside, we did some research on canberra – it’s designed to trigger event sounds in gnome. Irritatingly, it automatically hooks into virtually anything which produces a sound – ie it doesn’t just work with programs designed to work with it; rather it just takes over those sound duties. And it’s become a gnome dependency, so I’m not sure it would be easy to remove it – it’ll probably want to remove all sorts of other things like ubuntu-desktop, etc. It seems like the kind of nonsense garbage microsoft bloats their software with).

    When you say, “I am unable to get Ardour to see any sound from the Firewire Solo.” what, exactly, do you mean? Do you mean that qjackctl’s Connections box doesn’t show any Ardour connections? Can you try running Ardour from the command line (ie: #ardour2) and post the terminal’s output? Also, try starting JACK/Ardour and then post a screenshot of the Connections box of qjackctl.

    I’m wondering if canberra tries to hook into JACK and thereby blocks the connection between Ardour and JACK. Can you open qjackctl in a terminal and post the terminal’s output?

    westcoastsuccess

    December 7, 2009 at 11:14 pm

  210. Ok so this is the terminal output for #ardour2

    alex@dhcppc10:~$ ardour2
    Ardour/GTK 2.8.2
    (built using 5396 and GCC version 4.4.1)
    Copyright (C) 1999-2008 Paul Davis
    Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker

    Ardour comes with ABSOLUTELY NO WARRANTY
    not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    This is free software, and you are welcome to redistribute it
    under certain conditions; see the source for copying conditions.
    theme_init() called from internal clearlooks engine
    loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
    loading user ui configuration file /home/alex/.ardour2/ardour2_ui.conf
    Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
    ardour: [INFO]: Ardour will be limited to 1024 open files
    loading system configuration file /etc/ardour2/ardour_system.rc
    loading user configuration file /home/alex/.ardour2/ardour.rc
    ardour: [INFO]: No H/W specific optimizations in use
    ardour: [INFO]: looking for control protocols in /home/alex/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/
    ardour: [INFO]: Control protocol Tranzport not usable
    powermate: Opening of powermate failed – No such file or directory
    ardour: [INFO]: Control protocol powermate not usable
    ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
    ardour: [INFO]: Control surface protocol discovered: “Mackie”
    JACK COMMAND: /usr/bin/jackd -p 128 -T -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0
    no message buffer overruns
    jackd 0.116.1
    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.
    loading driver ..
    apparent rate = 48000
    creating alsa driver … hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
    control device hw:0
    configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
    ALSA: final selected sample format for capture: 16bit little-endian
    ALSA: use 2 periods for capture
    ALSA: final selected sample format for playback: 16bit little-endian
    ALSA: use 2 periods for playback
    loading bindings from /etc/ardour2/mnemonic-us.bindings
    Loading session /home/alex/test2 using snapshot test2 (1)
    Loading history from ‘/home/alex/test2/test2.history’.

    Here is the output for qjackctl. It just says:

    alex@dhcppc10:~$ qjackctl
    Suspending PulseAudio

    thats all.

    When I plug the guitar into the firewire solo the sound isn’t displayed in ardour (no level meters move when I play even though the clip light comes on on the device) but the device is shown on gscanbus and I think it’s shown in jack.

    Here is a screen shot of the jack connections box:
    http://tinypic.com/r/1zmingw/6

    Note: I had to reboot so things may have changed from my earlier posts.

    graham2128

    December 9, 2009 at 5:34 pm

  211. Hi WCS…

    Still no joy. We installed Hardy Heron (8.04), thinking this would make comparison with your setup easier.

    Ardour does not see any input from the M-Audio… the levels in Ardour do not move; unless we connect the guitar to the sound card.

    Could you advise what we should be seeing / setting in Ardour … Session Control… Audio Setup…. especially under Device and Advanced tabs?

    Thanks!

    graham2128

    January 9, 2010 at 6:17 pm

  212. Hi,

    Can you help me with the USB deivces of M-Audio Fast Track Ultra. Will this be compatible with Linux. Is there any way can we make the M-Audio Fast Ultra work with Linux platform. We are using the Inferno 10 OS.

    vbjoshi83

    January 11, 2010 at 11:09 pm

  213. Hello

    Thanks for the great guide, I’ve been able to get most of this operating. The connections in Jack are as they should be,

    system………………..ardour

    capture_1 —-> Audio1/In 1

    ardour………………..system

    Audio1/Out 1 —–> master/in 1
    Audio1/Out 2 —–> master/in 2
    master/out 1 —–> playback_1
    master/out 2 —–> playback_2

    (I’m using Input 1, so it connects capture_1 to Audio1/In1)

    I can hear the audio through the headphone output on the solo. I can get the clipping light to activate. I am getting some XRun messages. At times I get a running feed in the Jack message window. However, I don’t get a signal in the Ardour mixer window – or rather, I’m getting a constant low level signal that doesn’t seem to be related to my microphone input; it flickers at about -40 whether I am providing audio input to the mic or not and doesn’t change. I believe I’m using the correct input (input 1 on the Solo – microphone – Audio 1in Ardour). The Ardour mixer is displaying Audio 1. I’m using a condenser mic, and the mixer display is the same whether I have phantom power on or off. However, I can’t hear anything through the headphones when phantom power is off.

    Any ideas? I have the feeling that I’m missing something simple, which is quite likely given that I have limited experience with linux. BTW, I’m running Karmic

    Thanks

    Mike

    Mike

    April 7, 2010 at 11:52 am

  214. so i do everything according to this manual, but the jack server still won’t start. i’ve tried forcing bus reset via gscanbus, but still no luck

    when i do #ls -l /usr/bin/jackd, the reply is that there’s no such file or catalog

    any clue?

    nickalleye

    March 26, 2011 at 7:16 am

    • Try searching for “jackd” – perhaps it’s in a different location (ie /usr/local/bin/jackd).

      In Ubuntu, on the top panel, click Places–>Search For Files…–>type “jackd” in “Name Contains” field and make sure “Look in Folder:” field says “File System”.

      Let us know if you find it. If not, I suggest you reinstall JACK via Synaptic.

      westcoastsuccess

      March 26, 2011 at 7:25 am

      • okay, thanks for instant reply

        i reinstalled the jackd-stuf, and all i get is

        20:49:58.221 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.
        Cannot connect to server socket err = No such file or directory
        Cannot connect to server socket
        jack server is not running or cannot be started

        by the way, when i first tried to execute the “useradd -G disk kln” command, the reply was “useradd: user ‘kln’ already exists”. does it have something to do with this?

        nickalleye

        March 26, 2011 at 10:52 am

      • oh wait, just found out this message

        jackd: unknown driver ‘freebob’

        what the hell? i installed it, both while installing qt4
        AND from synaptec

        nickalleye

        March 26, 2011 at 11:07 am

      • ANYONE?

        here’s the entire log from jackctl:

        20:42:40.562 Patchbay deactivated.
        20:42:40.563 Statistics reset.
        Cannot connect to server socket err = No such file or directory
        Cannot connect to server socket
        jack server is not running or cannot be started
        20:42:40.684 ALSA connection graph change.
        20:42:40.879 ALSA connection change.
        20:42:42.184 Startup script…
        20:42:42.185 artsshell -q terminate
        Cannot connect to server socket err = No such file or directory
        Cannot connect to server socket
        jack server is not running or cannot be started
        sh: artsshell: not found
        20:42:42.588 Startup script terminated with exit status=32512.
        20:42:42.588 JACK is starting…
        20:42:42.588 /usr/bin/jackd -P89 -t2000 -dfreebob -r48000 -p256 -n3 -D
        20:42:42.593 JACK was started with PID=2300.
        no message buffer overruns
        no message buffer overruns
        Unknown driver “freebob”
        jackdmp 1.9.6
        Copyright 2001-2005 Paul Davis and others.
        Copyright 2004-2010 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
        20:42:42.640 JACK was stopped with exit status=255.
        20:42:42.641 Post-shutdown script…
        20:42:42.642 killall jackd
        jackd: no process found
        20:42:43.049 Post-shutdown script terminated with exit status=256.
        20:42:44.692 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.
        Cannot connect to server socket err = No such file or directory
        Cannot connect to server socket
        jack server is not running or cannot be started
        20:42:53.037 Could not connect to JACK server as client. – Overall operation failed. – Unable to connect to server. Please check the messages window for more info.
        Cannot connect to server socket err = No such file or directory
        Cannot connect to server socket
        jack server is not running or cannot be started

        nickalleye

        April 2, 2011 at 9:43 am

  215. First of all, thanks for posting this. Your article inspired me to buy the Solo and your guide helped me get up and running. I’ve been very happy with the results so far.

    Today I tried using the spdif inputs on the solo with no joy. Jack and ardour all seem to be setup properly to use the spdif inputs but there is no signal.

    Seems like there may be some internal settings to the Solo that need to be tweaked but there is no control app for Linux AFAIK.

    Have you ever used the spdif inputs on the Solo?

    rainman

    March 30, 2011 at 11:00 am

    • When you say there’s no signal, is the signal making it as far as JACK? You should be able to test this by installing the JACK VU (I think that’s what it’s called).

      Of course your output connections need to change in JACK such that your masters are outputting to the S/PDIF outputs.

      I’m afraid we can’t test right now as we’re on the road in Calgary Alberta today and Edmonton tomorrow. We’ll be in Toronto Fri and can test then.
      Sent from my BlackBerry device on the Rogers Wireless Network

      martin.lynch.toronto@gmail.com

      March 30, 2011 at 11:30 am

      • It doesn’t look like the signal is making it through the Solo. I installed meterbridge and monitored the two spdif inputs from the FW Solo and got nothing (even though the VUs on my source were active).

        I tried going the other way and taking the spdif output of the FW Solo into my DAT device and was able to get signals.

        So for some reason the spdif inputs are not happy. I’m wondering if it’s a clock/sync issue.

        rainman

        March 30, 2011 at 11:53 am

    • I should have replied here. see me question below

      Fábio

      February 1, 2012 at 11:43 am

  216. @rainman

    have you ever solved that s/pdif in problem? I can buy it sheap, but without s/pdif working it’s useless for me. thanks

    Fábio

    February 1, 2012 at 11:31 am

  217. Great issues altogether, you just gained a new reader. What might you recommend in regards to your publish that you simply made a few days ago? Any certain?

    Royal Crown Sheet Sets

    April 2, 2012 at 6:05 am

  218. Your own post, “Setting up an M-Audio FireWire Solo with
    Ubuntu/Linux the LYNCH report” ended up being definitely worth writing a comment here!
    Basically wished to mention you really did a fantastic job.
    Thanks for your time -Rubin

  219. Hiya, I was happy to see this guide. However, following it, I got snagged in many places (e.g., ‘disk’ might not be the correct usergroup in my case?; permissions errors might be the culprits of failures of ports to send signals to cards, and of cards passing info. along to applications). This is probably the 50th guide I tried, again with no luck. But this was the nicest. :-)

    I will try to get my hands on a Windows box so I can try the FW_WDM_5.10.0.5036.exe switcheroo.

    Until then, I’m afraid I have to admit defeat: I cannot get Linux to perform anywhere near expectation on the music composition front (mainly due to M-Audio Firewire Solo, which is key to my needs). If anyone asks I CANNOT recommend Linux. But I will secretly keep trying.

    If you get a version together for 12.10 + M-Audio Firewire Solo, I’d love to hear!

    Brendan

    February 25, 2013 at 10:55 am

    • I finally gave up on my Firewire Solo due to the quirks and lack of support and bought an Echo Audiofire 4. The device has similar capabilities, costs about the same as the FW Solo and is well supported in ffado.

      S R

      February 25, 2013 at 10:59 am

      • Thanks for that, SR. I might see how much I can do outside of Linux all together, as work’s buying me an iPad this week. Not what I’d hoped for music comp; but maybe enough. :-(

        Brendan

        February 25, 2013 at 11:03 am

  220. Hi, first I’m sorry about my poor english. ( I’m French)
    Actually I’m using Ubuntu Studio 12.10 with a Firewire Solo
    I try to get sound out with my firewire solo but without success.
    In ardour and Jack (hydrogen etc…), I’ve signal going out, I tried all connections to have sound out but nothing happened. I read that updating the fireware was a solution, but I’m sorry how to do this when you don’t have dual boot? It’s not possible to install m-audio fireware on Linux. So what can I do?? Thank you for your answers

    francois

    March 9, 2013 at 3:51 am

  221. To all any actually, and I actually acknowledge a Best porn sites is a
    person’s greatest assortment ahead of built.

    porn

    May 2, 2013 at 4:12 pm

  222. It’s actually a great and useful piece of info. I’m happy that you just shared this helpful information with us.
    Please keep us informed like this. Thank you for sharing.

  223. Mobile lindsay lohan sex tape, a person’s hate of christian apply appear to be encompassing on racism.

    go here

    July 20, 2013 at 5:43 am

  224. Free kim kardashian full sex video a friend, as answering any ask yourself.

    watch

    August 7, 2013 at 5:21 am

  225. Farrah abraham sex tape, her is an arresting attention!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: