{5} Assigned, Active Tickets by Owner (Full Description) (12 matches)

When starting ffadomixer I get the following:

mir@robotnik:~/Downloads/ffado/ffado-svn/libffado$ sudo ffado-mixer 
00:29:53 dbus             DEBUG    connecting to: Updated on /org/ffado/Control/DeviceManager (server: org.ffado.Control)
00:29:53 panelmanager     DEBUG    PanelManager::updatePanels()
00:29:53 panelmanager     DEBUG    going to add 00130e0401400fb0
00:29:53 panelmanager     DEBUG    Adding device 0: 00130e0401400fb0
00:29:53 panelmanager     DEBUG     Found (00130e0401400fb0, 130E, 5) Focusrite SAFFIRE_PRO_40
00:29:53 registration     DEBUG    version/GUID combo already registered
00:29:54 matrixmixer      DEBUG    Mixer has 16 rows and 18 columns
Traceback (most recent call last):
  File "/usr/local/lib/python2.6/site-packages/ffado/panelmanager.py", line 345, in updatePanels
    mixerwidget.buildMixer()
  File "/usr/local/lib/python2.6/site-packages/ffado/mixer/saffire_dice.py", line 222, in buildMixer
    model = MonitoringModel(self.hw, self)
  File "/usr/local/lib/python2.6/site-packages/ffado/mixer/saffire_dice.py", line 74, in __init__
    self.globaldims.append(BooleanControl(self.hw, self.hw.basepath + ("/EAP/Monitoring/GlobalDim/AffectsCh%i" % i)))
  File "/usr/local/lib/python2.6/site-packages/ffado/mixer/saffire_dice.py", line 34, in __init__
    self.value = self.iface.selected()
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "selected" with signature "" on interface "org.ffado.Control.Element.Boolean" doesn't exist

This is on Ubuntu 9.10. ffado-diag gives the following output (excerpt, CPU info omitted):

mir@robotnik:~/Downloads/ffado/ffado-svn/libffado$ sudo ffado-diag 


FFADO diagnostic utility 2.999.0-1788M
============================
(C) 2008 Pieter Palmers


=== CHECK ===
 Base system...
  kernel version............ 2.6.31-17-generic
FIXME: implement test for RT kernel
   RT patched............... False
  old 1394 stack present.... True
  old 1394 stack loaded..... True
  old 1394 stack active..... True
  new 1394 stack present.... True
  new 1394 stack loaded..... False
  new 1394 stack active..... False
  /dev/raw1394 node present. True
  /dev/raw1394 permissions.. True
 Prerequisites (dynamic at run-time)...
   gcc................ gcc (Ubuntu 4.4.1-4ubuntu8) 4.4.1
   g++................ g++ (Ubuntu 4.4.1-4ubuntu8) 4.4.1
   PyQt............... Python User Interface Compiler 3.18.1 for Qt version 3.3.8b
   jackd.............. jackd version 0.118.2 tmpdir /dev/shm protocol 24
     path............. /usr/local/bin/jackd
     flags............ Package jack was not found in the pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
   libraw1394......... 2.0.4
     flags............  -lraw1394  
   libavc1394......... 0.5.3
     flags............  -lavc1394 -lrom1394 -lraw1394  
   libiec61883........ 1.2.0
     flags............  -liec61883 -lraw1394  
   libxml++-2.6....... 2.26.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/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0  
   dbus-1............. 1.2.16
     flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include  -L/lib -ldbus-1 -lpthread -lrt  
 Prerequisites (static at compile-time)...
   gcc................ gcc (Ubuntu 4.4.1-4ubuntu8) 4.4.1
   g++................ g++ (Ubuntu 4.4.1-4ubuntu8) 4.4.1
   PyQt............... sh: pyuic: not found
   jackd.............. jackd version 0.118.2 tmpdir /dev/shm protocol 24
     path............. /usr/local/bin/jackd
     flags............ Package jack was not found in the pkg-config search path.
   libraw1394......... 2.0.4
     flags............  -lraw1394  
   libavc1394......... 0.5.3
     flags............  -lavc1394 -lrom1394 -lraw1394  
   libiec61883........ 1.2.0
     flags............  -liec61883 -lraw1394  
   libxml++-2.6....... 2.26.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/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include  -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0  
   dbus-1............. 1.2.16
     flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include  -L/lib -ldbus-1 -lpthread -lrt  
 Hardware...
   Host controllers:
01:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024] (prog-if 10)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (500ns min, 1000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at faeff800 (32-bit, non-prefetchable) [size=2K]
	Region 1: Memory at faef8000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME+
	Kernel driver in use: ohci1394
	Kernel modules: firewire-ohci, ohci1394

   CPU info:
   ... (Intel Quadcore)

I am using ffado SVN (trunk). Compilation and installation went OK, my device is recognized (e.g. with "ffado-test Discover) but jackd fails with error:

firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver

My system is ubuntu lucid beta1 (I upgraded from ubuntu hardy with the hope that it would solve the problem with ffado, but it did not).

when jackd load driver it says:

loading driver ..
06772398406:  (ffado.cpp)[  92] ffado_streaming_init: libffado 2.999.0-1788 built Jan 16 2010 22:55:55
06772574477: Warning (dice_eap.cpp)[1396] read: No routes found. Base 0x7, offset 0x4000
06772609554: Warning (dice_eap.cpp)[ 879] updateNameCache: What is this function about?

but it loads and jackd works

hi to all. i started from a minimal install CD of karmic to get my light audio server based on mpd and a firewire device (echo). device is correctly detected on ffado test list devices. kernel module 1394, permissions and so on, all done. i think to have installed all the stuff, even dbus-launch, which is part of X11 package, but when i start ffado-dbus-server i get an error from dbus-launch: Auto launch error: X11 initialization failed. any dep to satisfy? i did not want to install the graphical server, want to handle a minimal OS, how could i fix this error? thanks, in advance.....

Jackd crashes within minutes when using it with a Focusrite SAFFIRE PRO 40 FIRMWARE VERSION 914 (uptodate).

After an afternoon of attempts with adi, few things appeared:

1. there is a channel name vector mismatch when using RX0 with 10 channels and RX1 with 10. 00112311367: ESC[31mWarning (dice_avdevice.cpp)[ 813] prepare: The audio channel name vector is incorrect, using default names

The warning disappears with the following hack in src/dice/dice_avdevice.cpp:

if (i == 0) {

nb_audio = 12;

} else {

nb_audio = 8;

}

Though, the routing works in a very weird way: one cannot hear anything when linking an audio source to any analog channel, but if monitor know is raised up, one can hear audio source plugged on any analog channel via headphone busses (7-8 and 9-10). Probably, the problem is not fully solved on this point.

2. There is a certain amount of late wakeups.

3. Instantanous estimated samplerate differs from nominal:

04105452738: ESC[31mWarning (StreamProcessor?.cpp)[ 743] getPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 23964.895173, diff: 24035.104827 ( 0.500731)]

and, as one may see, it looks like estimated is half the nominal (or almost). Though, just before in the logs, one may read:

Framerate : Nominal: 48000, Sync: 47998.832731, Buffer 47998.752626

and then, it totally goes crazy with jitter!

04105860685: Warning (StreamProcessor?.cpp)[ 743] getPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 50789.976750, diff: -2789.976750 ( -0.058125)] 04105860715: Debug (StreamProcessor?.cpp)[ 754] getPacket: cy 1248, rather large TSP difference TS=01576708940 => TS=01576712811 (3871, nom 4096) 04105860820: Warning (StreamProcessor?.cpp)[ 743] getPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 50789.976750, diff: -2789.976750 ( -0.058125)]

4. Linux kernel and drivers don't seem to be involved, as we've tested that with 2 kernels (2.6.26.8-rt16 and 2.6.29.1-rt7)

5. Focusrite firmware has been updated, but it didn't change anything, even if the firmware update spoke about MAJOR FIRMWARE REVISION.

6. The FW controller is onboard controller VIA: 03:03.0 FireWire? (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0) But it doesn't seem to be a problem, as Focusrite recommends it, and adi could test his own io14 on such a chip with success.

7. A very weird thing happens with error_ticks calculous and comparison to 1*CYCLE_PER_SECOND:

04106847249: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545671780, max: +/- 1239901223783424 (try: 10) 1600647067 04106847420: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545667577, max: +/- 1239901223783424 (try: 9) 1600651270 04106847560: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545664136, max: +/- 1239901223783424 (try: 8) 1600654711 04106847704: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545660572, max: +/- 1239901223783424 (try: 7) 1600658275 04106847853: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545656910, max: +/- 1239901223783424 (try: 6) 1600661937 04106847995: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545653419, max: +/- 1239901223783424 (try: 5) 1600665428 04106848154: Debug (CycleTimerHelper?.cpp)[ 393] Execute: (0x834160) have to retry CTR read, diff unrealistic: diff: 1545649511, max: +/- 1239901223783424 (try: 4) 1600669336 04106848311: Debug (CycleTimerHelper?.cpp)[ 475] Execute: Rather late wakeup: 1072 usecs

diff is much less than max, and though it's considered as bigger.

Grab the newest version of the DBUS-C++ code and refresh our tree.