You are not logged in.

#1 2014-07-31 07:02:30

thorjelly
Member
Registered: 2009-02-15
Posts: 52

[SOLVED] Use FireWire device as JACK interface.

FFADO seems to see my device fine, but I have no idea how to use it as the JACK interface. When I select Firewire as the driver in JACK, there are no interfaces listed. Some output:

$ ffado-diag

FFADO diagnostic utility 2.2.1-Unversioned directory
============================
(C) 2008 Pieter Palmers
    2009-2010 Arnold Krille


=== CHECK ===
 Base system...
  kernel version............ 3.15.5-2-ARCH
    Preempt (low latency)... True
    RT patched.............. False
  old 1394 stack present.... False
  old 1394 stack loaded..... False
  old 1394 stack active..... False
  new 1394 stack present.... False
  new 1394 stack loaded..... True
  new 1394 stack active..... True
  /dev/raw1394 node present. False
  /dev/fw* permissions:
crw-------  1 root root  251, 0 Jul 30 07:53 /dev/fw0
crw-rw----+ 1 root audio 251, 1 Jul 30 22:29 /dev/fw1
  User IDs:
uid=1000(dunder) gid=1000(dunder) groups=1000(dunder),10(wheel),92(audio),108(vboxusers)
 Prerequisites (dynamic at run-time)...
   gcc ............... gcc (GCC) 4.9.1
   g++ ............... g++ (GCC) 4.9.1
   PyQt4 (by pyuic4) . Python User Interface Compiler 4.11.1 for Qt version 4.8.6
   jackd ............. sh: jackd: command not found
     path ............ 
     flags ........... -ljack 
   libraw1394 ........ 2.1.0
     flags ........... -lraw1394 
   libavc1394 ........ 0.5.4
     flags ........... -lavc1394 -lrom1394 -lraw1394 
   libiec61883 ....... 1.2.0
     flags ........... -liec61883 -lraw1394 
   libxml++-2.6 ...... 2.36.0
     flags ........... -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lglib-2.0 -lsigc-2.0 
   dbus-1 ............ 1.8.6
     flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 
 Prerequisites (static at compile-time)...
   gcc ............... gcc (GCC) 4.9.0 20140521 (prerelease)
   g++ ............... g++ (GCC) 4.9.0 20140521 (prerelease)
   PyQt4 (by pyuic4) . Python User Interface Compiler 4.10.4 for Qt version 4.8.5
   jackd ............. jackd version 0.124.1 tmpdir /dev/shm protocol 25
     path ............ /usr/bin/jackd
     flags ........... -ljack -lpthread 
   libraw1394 ........ 2.1.0
     flags ........... -lraw1394 
   libavc1394 ........ 0.5.4
     flags ........... -lavc1394 -lrom1394 -lraw1394 
   libiec61883 ....... 1.2.0
     flags ........... -liec61883 -lraw1394 
   libxml++-2.6 ...... 2.36.0
     flags ........... -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lglib-2.0 -lsigc-2.0 
   dbus-1 ............ 1.8.2
     flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 
 uname -a...
   Linux vertex 3.15.5-2-ARCH #1 SMP PREEMPT Fri Jul 11 07:56:02 CEST 2014 x86_64 GNU/Linux
 Hardware...
   Host controllers:
01:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] (rev 01) (prog-if 10 [OHCI])
        Subsystem: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f7b00000 (64-bit, non-prefetchable) [size=2K]
        Region 2: I/O ports at e000 [size=256]
        Capabilities: <access denied>
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire_ohci

   CPU info:
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 58
Model name:            Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Stepping:              9
CPU MHz:               3586.042
CPU max MHz:           3700.0000
CPU min MHz:           1600.0000
BogoMIPS:              6602.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3
 Configuration...
  IRQ information
Hardware Interrupts:
--------------------
 IRQ    0: PID:  None, count:      [18, 0, 0, 0], Sched None (priority None), drivers: ['timer']
 IRQ    1: PID:  None, count:       [1, 2, 0, 0], Sched None (priority None), drivers: ['i8042']
 IRQ    5: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['parport0']
 IRQ    8: PID:  None, count:       [0, 1, 0, 0], Sched None (priority None), drivers: ['rtc0']
 IRQ    9: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['acpi']
 IRQ   12: PID:  None, count:       [3, 1, 0, 0], Sched None (priority None), drivers: ['i8042']
 IRQ   16: PID:  None, count: [21140, 5708, 3502, 2566], Sched None (priority None), drivers: ['firewire_ohci', 'ehci_hcd:usb3', 'ath9k']
 IRQ   23: PID:  None, count: [1145333, 332215, 222282, 158541], Sched None (priority None), drivers: ['ehci_hcd:usb4']
 IRQ   40: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['dmar0']
 IRQ   41: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['dmar1']
 IRQ   42: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['PCIe PME']
 IRQ   43: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['PCIe PME']
 IRQ   44: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['PCIe PME']
 IRQ   45: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['PCIe PME']
 IRQ   46: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['PCIe PME']
 IRQ   47: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['PCIe PME']
 IRQ   48: PID:  None, count:       [0, 0, 0, 0], Sched None (priority None), drivers: ['xhci_hcd']
 IRQ   49: PID:  None, count: [8204, 44918, 753, 555], Sched None (priority None), drivers: ['ahci']
 IRQ   50: PID:  None, count: [91466, 46650, 30083, 21516], Sched None (priority None), drivers: ['ahci']
 IRQ   51: PID:  None, count:      [13, 0, 0, 0], Sched None (priority None), drivers: ['mei_me']
 IRQ   52: PID:  None, count: [1017654, 332763, 224946, 154909], Sched None (priority None), drivers: ['enp5s0']
 IRQ   53: PID:  None, count: [30030249, 6761060, 3733011, 2554538], Sched None (priority None), drivers: ['snd_hda_intel']
 IRQ   54: PID:  None, count: [671, 321, 75, 151], Sched None (priority None), drivers: ['snd_hda_intel']
 IRQ   55: PID:  None, count: [12681864, 0, 0, 0], Sched None (priority None), drivers: ['fglrx']

Software Interrupts:
--------------------


=== REPORT ===
FireWire kernel drivers:

The new FireWire kernel stack is loaded. 
If running a kernel earlier than 2.6.37 and problems are experienced, either 
try with the old Firewire kernel stack or upgrade to a newer kernel 
(preferrably 2.6.37 or later).

$ ffado-test Discover

-----------------------------------------------
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Version: 2.2.1-Unversioned directory
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

57830017485: Debug (devicemanager.cpp)[ 354] discover: Starting discovery...
57830094875: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
57830094905: Debug (Configuration.cpp)[ 185] showSetting:     vendorid = 16555 (0x000040AB)
57830094910: Debug (Configuration.cpp)[ 185] showSetting:     modelid = 65609 (0x00010049)
57830094923: Debug (Configuration.cpp)[ 209] showSetting:     vendorname = EDIROL
57830094926: Debug (Configuration.cpp)[ 209] showSetting:     modelname = FA-66
57830094930: Debug (Configuration.cpp)[ 209] showSetting:     driver = BEBOB
57830094932: Debug (Configuration.cpp)[ 209] showSetting:     mixer = EdirolFa66Control
57830094935: Debug (Configuration.cpp)[ 185] showSetting:     xmit_max_cycles_early_transmit = 4 (0x00000004)
57830095081: Debug (devicemanager.cpp)[ 616] discover: driver found for device 0
57830180981: Debug (bebob_avdevice.cpp)[ 846] loadFromCache: filename /home/dunder/.ffado/cache/0040ab0000c37041/0000006005070703.xml
57830182995: Debug (serialize_libxml.cpp)[ 230] checkVersion: Cache version: 2.2.1-Unversioned directory, expected: 2.2.1-Unversioned directory.
57830280315: Debug (avc_unit.cpp)[ 489] discoverPlugConnections: Discovering PCR plug connections...
57830447679: Debug (avc_unit.cpp)[ 500] discoverPlugConnections: Discovering External plug connections...
57830807616: Debug (bebob_avdevice_subunit.cpp)[ 102] discoverConnections: Discovering connections...
57830807629: Debug (avc_subunit.cpp)[ 148] discoverConnections: Discovering connections...
57830807642: Debug (avc_subunit.cpp)[ 148] discoverConnections: Discovering connections...
57830807643: Debug (bebob_avdevice_subunit.cpp)[ 102] discoverConnections: Discovering connections...
57830807646: Debug (avc_subunit.cpp)[ 148] discoverConnections: Discovering connections...
57830807648: Debug (avc_subunit.cpp)[ 148] discoverConnections: Discovering connections...
57830807664: Debug (bebob_avdevice.cpp)[ 870] loadFromCache: could create valid bebob driver from /home/dunder/.ffado/cache/0040ab0000c37041/0000006005070703.xml
57830808182: Debug (devicemanager.cpp)[ 653] discover: discovery of node 0 on port 0 done...
57830808208: Debug (devicemanager.cpp)[ 661] discover: Discovery finished...
57830808214: Debug (devicemanager.cpp)[1258] showDeviceInfo: ===== Device Manager =====
57830808219: Debug (Element.cpp)[ 121] show: Element DeviceManager
57830808222: Debug (devicemanager.cpp)[1266] showDeviceInfo: --- IEEE1394 Service  0 ---
57830808227: Debug (devicemanager.cpp)[1276] showDeviceInfo: --- Device  0 ---
57830808253: Debug (bebob_avdevice.cpp)[ 592] showDevice: Device is a BeBoB device
57830808281: Debug (devicemanager.cpp)[1279] showDeviceInfo: Clock sync sources:
57830808288: Debug (devicemanager.cpp)[1288] showDeviceInfo:  Type: Erratic type      , Id:  0, Valid: 1, Active: 0, Locked 1, Slipping: 0, Description: Device Controlled
no message buffer overruns

$ grep . /sys/bus/firewire/devices/fw*/*_name

/sys/bus/firewire/devices/fw0/model_name:Juju
/sys/bus/firewire/devices/fw0/vendor_name:Linux Firewire
/sys/bus/firewire/devices/fw1.0/model_name:EDIROL FA-66
/sys/bus/firewire/devices/fw1/model_name:EDIROL FA-66
/sys/bus/firewire/devices/fw1/vendor_name:EDIROL

So... how do I tell JACK to use my FA-66? JACK seems to be configured correctly for ALSA, and it works fine with my onboard audio.

Thanks!

Last edited by thorjelly (2014-08-01 17:03:39)

Offline

#2 2014-07-31 15:07:23

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: [SOLVED] Use FireWire device as JACK interface.

can you use the FA-66 on bare ALSA (without jack)?
post the output of 'aplay -l' and 'aplay -L'

Offline

#3 2014-08-01 04:31:17

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

I don't think that's possible.. I know libffado requires jack so I figured you pretty much had to use jack to use a firewire audio device. But never saw my firewire device or any of its inputs or outputs in alsa.

$ aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC898 Analog [ALC898 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC898 Digital [ALC898 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

$ aplay -L

null
    Discard all samples (playback) or generate zero samples (capture)
pulse
    PulseAudio Sound Server
default
    Default ALSA Output (currently PulseAudio Sound Server)
sysdefault:CARD=PCH
    HDA Intel PCH, ALC898 Analog
    Default Audio Device
front:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    Front speakers
surround21:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
    HDA Intel PCH, ALC898 Digital
    IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=PCH,DEV=0
    HDA Intel PCH, HDMI 0
    HDMI Audio Output
hdmi:CARD=PCH,DEV=1
    HDA Intel PCH, HDMI 1
    HDMI Audio Output
hdmi:CARD=PCH,DEV=2
    HDA Intel PCH, HDMI 2
    HDMI Audio Output
hdmi:CARD=HDMI,DEV=0
    HDA ATI HDMI, HDMI 0
    HDMI Audio Output
hdmi:CARD=HDMI,DEV=1
    HDA ATI HDMI, HDMI 1
    HDMI Audio Output
hdmi:CARD=HDMI,DEV=2
    HDA ATI HDMI, HDMI 2
    HDMI Audio Output
hdmi:CARD=HDMI,DEV=3
    HDA ATI HDMI, HDMI 3
    HDMI Audio Output
hdmi:CARD=HDMI,DEV=4
    HDA ATI HDMI, HDMI 4
    HDMI Audio Output
hdmi:CARD=HDMI,DEV=5
    HDA ATI HDMI, HDMI 5
    HDMI Audio Output

It appears to only see my onboard audio and my HDMI audio.

Last edited by thorjelly (2014-08-01 04:32:19)

Offline

#4 2014-08-01 05:25:36

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: [SOLVED] Use FireWire device as JACK interface.

Do you use a gui for jack like qjackctl?

Out of curiosity:
Does your hardware have hybrid graphics? What graphics card model is the ati?

Offline

#5 2014-08-01 06:39:05

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

Yes I use qjackctl.

My card is the 7850. I do have onboard intel graphics as well, but I do not use it; I don't use hybrid. I am using the open source radeon drivers.

Offline

#6 2014-08-01 13:04:09

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: [SOLVED] Use FireWire device as JACK interface.

Usually you shouldn't be able to use any soundcard with jack, if it's not recognized by alsa, or other audio subsystem supported by jack.
However I have zero experience with firewire soundcards on linux so I'm not sure if it should be handled by alsa or some other subsystem.

I also noticed that there's 'firewire' driver option in qjackctl. maybe that could work?

EDIT: typo

Last edited by ooo (2014-08-01 16:56:58)

Offline

#7 2014-08-01 13:52:36

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: [SOLVED] Use FireWire device as JACK interface.

There must be some information in 'messages' window or run 'jackd -d firewire -v'. I do not have a firewire device at hand right now to test any of this. There is also a 'jack2-no-dbus-firewire-git' package in aur.

@ooo does it really state 'firefire' or 'firewire'? If the former or both, what libraries for firewire do you have installed?

Last edited by emeres (2014-08-01 13:54:37)

Offline

#8 2014-08-01 16:24:22

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

ooo wrote:

Usually you shouldn't be able to use any soundcard with jack, if it's not recognized by alsa, or other audio subsystem supported by jack.
However I have zero experience with firewire soundcards on linux so I'm not sure if it should be handled by alsa or some other subsystem.

Well JACK seems capable of using other systems other than ALSA and I believe firewire-ohci is one of them. That's what the Firewire driver option you point out is.

ooo wrote:

I also noticed that there's 'firefire' driver option in qjackctl. maybe that could work?

And yes.. I mentioned this in my original post that I tried this but I do not see any 'interfaces' associated with it. At least, I am assuming you mean 'firewire'. Even though it appears two interfaces are being made: fw0 and fw1. I believe fw0 is the firewire adapter I have plugged in as a PCI card and fw1 is my actual firewire audio device -- which appears to be detected fine.

emeres wrote:

There must be some information in 'messages' window or run 'jackd -d firewire -v'. I do not have a firewire device at hand right now to test any of this. There is also a 'jack2-no-dbus-firewire-git' package in aur.

Well, I am using jackdbus and I don't really know how to run that command using jackdbus.  I'm beginning to suspect maybe that jackdbus doesn't include firewire support...? But I can't find any information anywhere for this to be the case. I need jackdbus for jack to be able to interact smoothly with pulseaudio.

Offline

#9 2014-08-01 16:56:17

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: [SOLVED] Use FireWire device as JACK interface.

emeres wrote:

@ooo does it really state 'firefire' or 'firewire'? If the former or both, what libraries for firewire do you have installed?

sorry that was a typo, meant 'firewire'

thorjelly wrote:

Well, I am using jackdbus and I don't really know how to run that command using jackdbus.  I'm beginning to suspect maybe that jackdbus doesn't include firewire support...? But I can't find any information anywhere for this to be the case. I need jackdbus for jack to be able to interact smoothly with pulseaudio.

In my experience, jackdbus can be real PITA to set up. I'd try to get legacy jackd working first, and migrate the options to jackdbus when you got it working.
If you've installed jack2 (not jack2-dbus) you should already have both jackd and jackdbus installed.

Last edited by ooo (2014-08-01 17:00:32)

Offline

#10 2014-08-01 17:00:24

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: [SOLVED] Use FireWire device as JACK interface.

thorjelly wrote:

I don't really know how to run that command using jackdbus.

You should find some useful information following these references, I use the classic case (alsa and jack only), so can be little of help here..
http://trac.jackaudio.org/wiki/WalkThro … ck_control
http://trac.jackaudio.org/wiki/JackDbusPackaging

@ooo a funny one though.

Offline

#11 2014-08-01 17:01:57

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

Okay! I got it to work! Sorry. Basically my sample rate wasn't set correctly. I had it set to 48000hz and my firewire device only supported 41100hz.

I uninstalled jack2-dbus and installed jack2, and everything worked fine with the same setup I had before, which wasn't what the arch linux wiki indicated would happen at all. It stated that setup would only work with jack2-dbus. Oh well.

Then I could start the server with the 'jackd -d firewire -v' command as instructed:

jackdmp 1.9.9.5
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
1406912171211876:  (ffado.cpp)[  92] ffado_streaming_init: libffado 2.2.1-Unversioned directory built Jun  5 2014 20:16:21
00329769308: Warning (avc_plug.cpp)[ 974] setSampleRate: output plug signal format command not accepted
00329829468: Error (avc_plug.cpp)[1085] setSampleRate: setSampleRatePlug: PCR Compound Input plug 0 does not support sample rate 48000
00329829516: Error (avc_avdevice.cpp)[ 261] setSamplingFrequency: setSampleRate: Setting sample rate failed
00329850331: Warning (avc_plug.cpp)[ 974] setSampleRate: output plug signal format command not accepted
00329899643: Error (avc_plug.cpp)[1085] setSampleRate: setSampleRatePlug: PCR Compound Input plug 0 does not support sample rate 48000
00329899683: Error (avc_avdevice.cpp)[ 261] setSamplingFrequency: setSampleRate: Setting sample rate failed
00329899704: Fatal (devicemanager.cpp)[ 802] initStreaming: Could not set sampling frequency to 48000
00329899716: Fatal (ffado.cpp)[ 181] ffado_streaming_init: Could not init the streaming system
firewire ERR: FFADO: Error creating virtual device
Cannot attach audio driver
JackServer::Open failed with -1
no message buffer overruns
Segmentation fault

I have -no idea- why it didn't give me these messages in the 'messages' window with qjackctl, but it didn't. So I fired up qjackctl, switched the driver to firewire, changed the sample rate to 44100, and it worked. It is also possible it didn't output those messages for me before because it really wouldn't have work with jack2-dbus. I don't know.

Anyway, thanks for the help, guys.

Offline

#12 2014-08-01 17:31:30

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: [SOLVED] Use FireWire device as JACK interface.

thorjelly wrote:

I uninstalled jack2-dbus and installed jack2, and everything worked fine with the same setup I had before, which wasn't what the arch linux wiki indicated would happen at all. It stated that setup would only work with jack2-dbus. Oh well.

If you certain there is incorrect or insufficient information, update the wiki.

Offline

#13 2014-08-01 20:09:08

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

Okay. For some reason, somehow, Skype crashes this setup. Everything works fine until I run Skype. Then the PulseAudio JACK Sink and PulseAudio JACK Source interfaces no longer work, only when using the firewire device in jack.

Ugh. Skype is the only reason I bother with PulseAudio in the first place.

Last edited by thorjelly (2014-08-01 20:09:41)

Offline

#14 2014-08-01 20:51:16

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: [SOLVED] Use FireWire device as JACK interface.

Tox just went into alpha if I recall correctly, it is nowhere near Skype as for now, but it is an aspiring alternative. If you want this fixed write Skype/Microsoft, hacking around those binaries would be a waste of time. Let them have it.

Offline

#15 2014-08-01 21:44:41

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

I kind of think it's some kind of driver problem, because exiting skype doesn't bring anything back, neither does restarting pulseaudio, and trying to restart jack at this point causes it to be unable to start. Skype doesn't just not work, it renders my audio utterly unusable until I reboot. But I suppose I should make another topic about this, since my original problem was solved nicely.

Offline

#16 2014-08-01 21:47:40

emeres
Member
Registered: 2013-10-08
Posts: 1,570

Re: [SOLVED] Use FireWire device as JACK interface.

thorjelly wrote:

I kind of think it's some kind of driver problem, because exiting skype doesn't bring anything back, neither does restarting pulseaudio, and trying to restart jack at this point causes it to be unable to start. Skype doesn't just not work, it renders my audio utterly unusable until I reboot. But I suppose I should make another topic about this, since my original problem was solved nicely.

That is what I experienced many times when one application forced a different samplerate than the one jack was using with audio running. Only a reboot would bring audio back. Probably for the best to start a new thread, you are right.

Last edited by emeres (2014-08-01 21:49:18)

Offline

#17 2014-08-01 22:49:34

thorjelly
Member
Registered: 2009-02-15
Posts: 52

Re: [SOLVED] Use FireWire device as JACK interface.

Thanks for your idea. I created the new topic here: https://bbs.archlinux.org/viewtopic.php?id=185133

Offline

Board footer

Powered by FluxBB