ubuntustudio-bugs team mailing list archive

[Len Ovens <len@xxxxxxxxxxxxx>]

There have been problems using the jack firewire backend if the alsa
firewire module is loaded. From: http://lists.linuxaudio.org/pipermail
/linux-audio-user/2015-August/102283.html try: rmmod snd_dice
snd_firewire_lib to see if this is the case for you. Note that the first
driver listed (snd_dice) may not be the right one in your case, but
looking for for modules that depend on snd_firewire_lib using lsmod
should show what you are using.

The other thing to try (maybe first) is using pavucontrol, in the config
panel, turn the profile for the firewire device "off". so that you can
be sure the alsa firewire driver is not being used.

The thing that mostly just works is to tell jackd to just use the same
firewire device as an alsa device instead of using the jack firewire
back end.

This not a jack bug, but a kernel module usage bug. The firewire device
can only be used one way and whichever way it is used the kernel modules
for the other way need to be black listed by the user. The intent of the
default install is to use the alsa modules.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to Ubuntu Studio.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1484627

Title:
  jackd won't start again in the same session after having exited

Status in Ubuntu Studio:
  New

Bug description:
  Actual behavior with pulseaudio-module-jack installed:

  1. start jackd with firewire device.
  2. stop jackd
  3. run application which requires audio, using pulseaudio
  4. exit the application
  5. try to start jackd with firewire device

  result: jackd will fail

  expected behavior: jackd should start

  Without pulseaudio-module-jack the expected result is just fine.

  system: ubuntustudio 15.04 64bit, audio device: audiofire12 (echo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1484627/+subscriptions