You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
(22) |
May
(36) |
Jun
(27) |
Jul
(55) |
Aug
(86) |
Sep
(8) |
Oct
(78) |
Nov
(58) |
Dec
(40) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(100) |
Feb
(29) |
Mar
(176) |
Apr
(64) |
May
(199) |
Jun
(84) |
Jul
(31) |
Aug
(57) |
Sep
(61) |
Oct
(148) |
Nov
(125) |
Dec
(106) |
2009 |
Jan
(15) |
Feb
(34) |
Mar
(42) |
Apr
(66) |
May
(101) |
Jun
(41) |
Jul
(12) |
Aug
(14) |
Sep
(41) |
Oct
(82) |
Nov
(52) |
Dec
(76) |
2010 |
Jan
(158) |
Feb
(53) |
Mar
(32) |
Apr
(43) |
May
(44) |
Jun
(40) |
Jul
(49) |
Aug
(43) |
Sep
(123) |
Oct
(78) |
Nov
(41) |
Dec
(135) |
2011 |
Jan
(67) |
Feb
(70) |
Mar
(83) |
Apr
(97) |
May
(47) |
Jun
(65) |
Jul
(48) |
Aug
(8) |
Sep
(84) |
Oct
(28) |
Nov
(8) |
Dec
(9) |
2012 |
Jan
(26) |
Feb
(19) |
Mar
(220) |
Apr
(262) |
May
(107) |
Jun
(145) |
Jul
(49) |
Aug
(38) |
Sep
(111) |
Oct
(32) |
Nov
(34) |
Dec
(45) |
2013 |
Jan
(28) |
Feb
(4) |
Mar
(6) |
Apr
(26) |
May
(38) |
Jun
(79) |
Jul
(49) |
Aug
(70) |
Sep
(76) |
Oct
(85) |
Nov
(80) |
Dec
(70) |
2014 |
Jan
(167) |
Feb
(114) |
Mar
(181) |
Apr
(95) |
May
(211) |
Jun
(41) |
Jul
(41) |
Aug
(14) |
Sep
(52) |
Oct
(60) |
Nov
(59) |
Dec
(72) |
2015 |
Jan
(88) |
Feb
(20) |
Mar
(89) |
Apr
(15) |
May
(40) |
Jun
(25) |
Jul
(50) |
Aug
(97) |
Sep
(41) |
Oct
(90) |
Nov
(88) |
Dec
(152) |
2016 |
Jan
(60) |
Feb
(52) |
Mar
(63) |
Apr
(79) |
May
(41) |
Jun
(66) |
Jul
(31) |
Aug
(28) |
Sep
(4) |
Oct
(48) |
Nov
(45) |
Dec
(3) |
2017 |
Jan
(44) |
Feb
(23) |
Mar
(42) |
Apr
(39) |
May
(24) |
Jun
(42) |
Jul
(1) |
Aug
(14) |
Sep
|
Oct
(4) |
Nov
(7) |
Dec
(14) |
2018 |
Jan
(67) |
Feb
(70) |
Mar
(19) |
Apr
(35) |
May
(25) |
Jun
(9) |
Jul
(1) |
Aug
(6) |
Sep
(13) |
Oct
(29) |
Nov
(15) |
Dec
(20) |
2019 |
Jan
(35) |
Feb
(4) |
Mar
(4) |
Apr
(1) |
May
(6) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
(6) |
Oct
(5) |
Nov
(3) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
(15) |
Apr
|
May
(13) |
Jun
(2) |
Jul
(4) |
Aug
(48) |
Sep
(15) |
Oct
(2) |
Nov
(9) |
Dec
(5) |
2021 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(34) |
Jun
(8) |
Jul
(4) |
Aug
|
Sep
(6) |
Oct
(28) |
Nov
(2) |
Dec
(4) |
2022 |
Jan
(1) |
Feb
(5) |
Mar
|
Apr
(16) |
May
|
Jun
|
Jul
(1) |
Aug
(6) |
Sep
(6) |
Oct
|
Nov
(1) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2024 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
(45) |
May
|
Jun
(3) |
Jul
(16) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: FFADO <ffa...@ff...> - 2009-02-24 14:59:12
|
#198: FFado 2.0~rc1 FTBFS on HPPA -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: closed Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: invalid Keywords: ftbfs | Device_name: -------------------------------------+-------------------------------------- Comment (by rexbron): Ok, will do adi. As for g++ segfaulting, I noticed that but do not have access to an hppa machine. The one that this ftbfs on is an ubuntu build machine and iirc is fully automated. -- Ticket URL: <http://subversion.ffado.org/ticket/198#comment:2> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-24 11:12:51
|
#200: FFado 2.0~rc1 FTBFS on armel -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: | Device_name: -------------------------------------+-------------------------------------- Comment (by adi): See #199 for additional comments. Exactly the same issue. -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/200#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-24 11:12:17
|
#199: FFado 2.0~rc1 FTBFS on IA64 -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: | Device_name: -------------------------------------+-------------------------------------- Comment (by adi): Same as #197 on SPARC: atomic operations and the build system. For atomic operations, I'd go for the gcc-4.1 builtins. We don't have the manpower for everything else. For the build system, we could simply ditch the default target. Don't know if this works: {{{ Index: SConstruct =================================================================== --- SConstruct (revision 1518) +++ SConstruct (working copy) @@ -412,7 +412,7 @@ elif re.search("powerpc", config[config_cpu]) != None: env['DIST_TARGET'] = 'powerpc' else: - env['DIST_TARGET'] = 'i686' + env['DIST_TARGET'] = config[config_cpu] print "Detected DIST_TARGET = " + env['DIST_TARGET'] if ((re.search ("i[0-9]86", config[config_cpu]) != None) or (re.search ("x86_64", config[config_cpu]) != None) or (re.search ("powerpc", config[config_cpu]) != None)): }}} -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/199#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-24 10:30:18
|
#198: FFado 2.0~rc1 FTBFS on HPPA -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: closed Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: invalid Keywords: ftbfs | Device_name: -------------------------------------+-------------------------------------- Changes (by adi): * status: new => closed * resolution: => invalid Comment: The reason: {{{ g++ -o src/bebob/terratec/terratec_cmd.os -c -DDEBUG -Wall -g -DDBUS_HAS_THREADS_INIT_DEFAULT -DENABLE_BEBOB -DENABLE_FIREWORKS -DENABLE_MOTU -DENABLE_GENERICAVC -fPIC -I. -Isrc -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 -Iexternal/libconfig src/bebob/terratec/terratec_cmd.cpp Segmentation fault make: *** [debian/stamp-scons-build] Error 139 }}} One would probably need to investigate why g++ segfaults on HPPA. Anybody with a login to such a machine? rexbron: This is currently no FFADO problem, only triggered by FFADO. I'll close this ticket for now. Feel free to reopen it once the toolchain is stable ;) -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/198#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Andrew H. <an...@ae...> - 2009-02-24 04:33:13
|
Hey everyone, Just thought I'd revive this thread and let you guys know that I was able to get ffado 2.0~rc1 into the ubuntu archives for jaunty (9.04) and Ubuntu Studio will be shipping ffado in the next release. As a member of the Ubuntu Studio team, I will be responsible for forwarding any bugs upstream and getting any fixes out. Looking forward to a great release! Andrew Hunter |
From: <ad...@dr...> - 2009-02-21 22:27:23
|
Hi! I don't know if it's only my io14 or DICE in general, but MIDI-in works just occasionally. I haven't figured out what influences working or broken midi-in, but it seems to work a little more often when running a PCM playback before asking for MIDI data. decodeMidiPorts in AmdtpReceiveStreamProcessor.cpp has a comment: // FIXME: this assumes that 2X and 3X speed isn't used, // because only the 1X slot is put into the ringbuffer if(IEC61883_AM824_GET_LABEL(sample_int) != IEC61883_AM824_LABEL_MIDI_NO_DATA) { What does 2x and 3x speed mean here? Does anybody have an idea regarding this issue? -- mail: ad...@th... http://adi.thur.de PGP/GPG: key via keyserver We are born for Appelkorn! |
From: FFADO <ffa...@ff...> - 2009-02-21 14:21:10
|
#200: FFado 2.0~rc1 FTBFS on armel ----------------------------------------+----------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Keywords: Device_name: | ----------------------------------------+----------------------------------- Hey Everyone, FFado fails to build from source on armel Build log: http://launchpadlibrarian.net/22933591/buildlog_ubuntu-jaunty- armel.libffado_2.0~rc1-0ubuntu1_FAILEDTOBUILD.txt.gz -- Ticket URL: <http://subversion.ffado.org/ticket/200> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-21 14:19:35
|
#199: FFado 2.0~rc1 FTBFS on IA64 ----------------------------------------+----------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Keywords: Device_name: | ----------------------------------------+----------------------------------- Hey everyone, FFado fails to build from source on IA64. Build log: http://launchpadlibrarian.net/22906616/buildlog_ubuntu-jaunty- ia64.libffado_2.0~rc1-0ubuntu1_FAILEDTOBUILD.txt.gz -- Ticket URL: <http://subversion.ffado.org/ticket/199> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-21 14:16:35
|
#198: FFado 2.0~rc1 FTBFS on HPPA ----------------------------------------+----------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Keywords: ftbfs Device_name: | ----------------------------------------+----------------------------------- Hey everyone, FFado fails to build from source on the HPPA arch. Build log is available here: http://launchpadlibrarian.net/22898867 /buildlog_ubuntu-jaunty-hppa.libffado_2.0~rc1- 0ubuntu1_FAILEDTOBUILD.txt.gz As per the discussion with Sparc, this is a minor bug but I think it is still worth reporting. -- Ticket URL: <http://subversion.ffado.org/ticket/198> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Sean M. P. <pe...@re...> - 2009-02-20 23:32:26
|
Hello again. Am I correct in understanding that the SCS.1m shows up as two firewire devices, one audio and one raw/HSS1394? (Looks that way in Windows. They both seems to be AVC devices. Please verify this.) Obviously my first concern with regards to Linux support is handling the HSS1394 part. I've just been reading http://www.linux1394.org/doc/libraw1394/general.html and it looks like what Jim said here http://forums.stantondj.com/viewtopic.php?f=11&t=129 is indeed very doable, we'll just need your HSS1394 implementation/API if you are willing to share it. Whether we add HSS1394 support to Mixxx or have it as a separate "helper" library remains to be discussed internally, but it looks like this won't be too difficult in either case. As for the audio side, has Stanton been in contact with the ffado group? (http://www.ffado.org/) I have CC'ed them as well to bring them into the discussion. Can you tell us/them what audio chipset you use in the .1m? (If it happens to be the same as in the FS2/Open, all the better, since it seems some amount of work has been done to support that.) Again, on behalf of all of the Linux users represented here, thank you very much for your time and support! Sincerely, Sean M. Pappalardo <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> |
From: FFADO <ffa...@ff...> - 2009-02-20 14:17:18
|
#197: FFado 2.0~rc1 FTBFS on Sparc -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: ftbfs | Device_name: -------------------------------------+-------------------------------------- Changes (by adi): * priority: major => minor Comment: I'd also opt for "amd64 and x86, nothing more". Other target architectures seem to vanish, and I guess the typical FFADO user won't neither have slow SparcStations nor Sun Servers like my V880 (way too loud, to large). Anyway, I've added a second patch, enabling gcc builtin atomics for sparc v9. That's sparc64, and afaik, these CPUs have been on the market for ages (so not a big restriction, probably comparable to 386 vs. Pentium, where v9 is the "Pentium"). Though we don't have manpower to support it, we could add this second patch. I claim there won't be a single person actually using it ;) As for "gcc >= 4.1 check": we just mention it in the README file. "On SPARC, you'd need gcc >= 4.1 to compile FFADO. This will only work for UltraSparc (sun4u), SPARCv8 and earlier is not supported." -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/197#comment:3> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-19 21:13:25
|
#197: FFado 2.0~rc1 FTBFS on Sparc -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: ftbfs | Device_name: -------------------------------------+-------------------------------------- Comment (by holin): The foremost question is, do we really want to support each of debian's gazillion archs? Is there man-power to back that up? In the long run, I don't think it will be useful to add skin-deep support for archs that will bit-rot in no time. I wouldn't be surprised if firewire support was shaky from the kernel upwards with anything but the most common archs, which these days has really come to include only x86 and x86_64. As to the problem at hand, an easy, but not entirely trouble-free, solution is to use the atomic builtins that gcc >= 4.1 has. Of course a check for the gcc version has to be added, but from there on it's easy sailing. -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/197#comment:2> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-19 17:09:36
|
#197: FFado 2.0~rc1 FTBFS on Sparc -------------------------------------+-------------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: ftbfs | Device_name: -------------------------------------+-------------------------------------- Comment (by adi): Hi. It's way more than just Atomic.h: {{{ Trying to find the system triple: (cached) sparc64-unknown-linux-gnu Doing a DEBUG build Detected DIST_TARGET = i686 }}} The whole build system doesn't know anything about SPARC at the moment. I have a SPARC64 Debian system available, if anybody (developer) is interested in getting a login, just ping me. It has no firewire port (Sun Fire V880), but if need be, I could probably add a PCI 1394 controller and my io14. Find attached a first patch. It adds sparc(64) to the build system and provides a generic compare-and-swap operation, though not atomic. Since there are different sparc processor versions, we'd probably need to code different versions for sparc v8 and v9. Don't know if the Linux kernel, the gcc or libc provides something like atomic_cas_32 (see [http://forums.sun.com/thread.jspa?threadID=5085084]) on Solaris. JFTR: http://developers.sun.com/solaris/articles/atomic_sparc/ Poll: should we just mark FFADO-2.0 as unsupported on SPARC? The attached patch fixes the build issue, but I have no runtime testing at all. Last remark: Debian on Sparc64 is a 64bits kernel with a 32bits userland, only few apps are compiled for 64bits. The attached patch defaults to 32bit output, supporting also builds for 64bits. Hopefully. ;) -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/197#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-18 15:50:35
|
#197: FFado 2.0~rc1 FTBFS on Sparc ----------------------------------------+----------------------------------- Reporter: rexbron | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Keywords: ftbfs Device_name: | ----------------------------------------+----------------------------------- As FFado has made it into the Ubuntu Jaunty archives, it is being built on more archs than just i386 and amd64. Relevant section from the build log: {{{ g++ -o src/bebob/bebob_avdevice.os -c -DDEBUG -Wall -g -DDBUS_HAS_THREADS_INIT_DEFAULT \ -DENABLE_BEBOB -DENABLE_FIREWORKS -DENABLE_MOTU -DENABLE_GENERICAVC -fPIC -I. -Isrc \ -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 \ -Iexternal/libconfig src/bebob/bebob_avdevice.cpp In file included from src/libutil/Thread.h:56, from src/libstreaming/StreamProcessorManager.h:32, from src/devicemanager.h:33, from src/bebob/bebob_avdevice.cpp:26: src/libutil/Atomic.h: In function 'long int INC_ATOMIC(volatile int32_t*)': src/libutil/Atomic.h:170: error: 'CAS' was not declared in this scope src/libutil/Atomic.h: In function 'long int DEC_ATOMIC(volatile int32_t*)': src/libutil/Atomic.h:179: error: 'CAS' was not declared in this scope src/libutil/Atomic.h: In function 'long int ADD_ATOMIC(volatile int32_t*, int32_t)': src/libutil/Atomic.h:188: error: 'CAS' was not declared in this scope src/libutil/Atomic.h: In function 'long int SUBSTRACT_ATOMIC(volatile int32_t*, int32_t)': src/libutil/Atomic.h:197: error: 'CAS' was not declared in this scope src/libutil/Atomic.h: In function 'long int ZERO_ATOMIC(volatile int32_t*)': src/libutil/Atomic.h:206: error: 'CAS' was not declared in this scope scons: *** [src/bebob/bebob_avdevice.os] Error 1 scons: building terminated because of errors. make: *** [debian/stamp-scons-build] Error 2 }}} Full build log: http://launchpadlibrarian.net/22779537/buildlog_ubuntu- jaunty-sparc.libffado_2.0~rc1-0ubuntu1_FAILEDTOBUILD.txt.gz -- Ticket URL: <http://subversion.ffado.org/ticket/197> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-16 17:35:44
|
#186: Jack crashes after export in Ardour, or just on some Ardour crash -------------------------------------+-------------------------------------- Reporter: blindekinder | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: | Device_name: -------------------------------------+-------------------------------------- Comment (by blindekinder): I just compiled jack new version (jackdmp 1.9.1): still exactly the same problem. -- Ticket URL: <http://subversion.ffado.org/ticket/186#comment:11> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-14 16:16:25
|
#187: could not start jack with saffire pro on 64bit -------------------------------------+-------------------------------------- Reporter: adamix | Owner: Type: bug | Status: closed Priority: blocker | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: invalid Keywords: | Device_name: focusrite saffire pro 10i/o -------------------------------------+-------------------------------------- Changes (by ppalmers): * status: new => closed * resolution: => invalid Comment: According to your log: 00564474090: [31mWarning (ffado.cpp)[ 121] ffado_streaming_init: Realtime scheduling is not enabled. This will cause significant reliability issues. you are not running jackd in realtime mode. You have to run jack in realtime mode to use ffado. -- Ticket URL: <http://subversion.ffado.org/ticket/187#comment:2> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-11 12:55:04
|
#196: Alesis Multimix16 support ------------------------------+--------------------------------------------- Reporter: adi | Owner: Type: enhancement | Status: closed Priority: trivial | Milestone: FFADO 2.1 Version: FFADO SVN (trunk) | Resolution: fixed Keywords: | Device_name: ------------------------------+--------------------------------------------- Changes (by holin): * status: new => closed * resolution: => fixed Comment: Fixed in r1515. -- Ticket URL: <http://subversion.ffado.org/ticket/196#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-02 22:55:47
|
#196: Alesis Multimix16 support ---------------------------------+------------------------------------------ Reporter: adi | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: FFADO 2.1 Version: FFADO SVN (trunk) | Keywords: Device_name: | ---------------------------------+------------------------------------------ Chris Garrett has a working Multimix16. The attached patch enables the necessary vendor hacks, thus extending the support in the Alesis series. Please apply it to the trunk. -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/196> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-02-02 22:25:35
|
#152: Alesis io14 playback support ------------------------------+--------------------------------------------- Reporter: adi | Owner: ppalmers Type: enhancement | Status: closed Priority: minor | Milestone: FFADO 2.1 Version: FFADO SVN (trunk) | Resolution: fixed Keywords: | Device_name: Alesis io14 ------------------------------+--------------------------------------------- Changes (by adi): * status: assigned => closed * resolution: => fixed Comment: I'm closing this ticket. io14 worked great over the last months, xruns vanished with realtime priorities for jackd. Operation is very stable, few to no xruns or crashes. I suggest to change the device DB's entry to "reported to work", "basically supported" or something like this. It's surely more than "Not supported", though only in the trunk. -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/152#comment:6> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-01-31 16:22:05
|
#195: Saffire LE device not recognized through a cardbus firewire card (ti chipset) ---------------------------------+------------------------------------------ Reporter: mlee | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO SVN (trunk) | Keywords: Device_name: Saffire LE | ---------------------------------+------------------------------------------ Hi. I am running archlinux (x86_64) with all the latest updates on a lenovo t61 notebook (ffado-diag.log attached). I am using ffado compiled from trunk (r1514). I just purchased a Belkin F5U513v firewire adapter which has a Texas Instruments chipset. It turns out that my laptop actually has an expresscard slot so I'm going to return the the Belkin card today. But I wanted to file this bug as it seems that ffado actually saw the Saffire LE but could not match it as one. I've attached in the zip file logs from connecting via the internal Ricoh based firewire and the Belkin firewire. Of course, the ricoh based port has occasional latency glitches which produce xruns in jack. Log commands: sudo ffado-diag > ffado-diag.log jackd --verbose -R -P89 -dfirewire -v 6 -r44100 -n3 -p1024 2> ffado- jack.ti.log jackd --verbose -R -P89 -dfirewire -v 6 -r44100 -n3 -p1024 2> ffado- jack.ricoh.log The problem is that ffado is not configuring the Saffire LE through the Belkin interface. Here's an excerpt from the log: 50453427075: Debug (devicemanager.cpp)[ 534] discover: Probing node 0... 50453486283: Debug (configrom.cpp)[ 560] printConfigRomDebug: Config ROM 50453486299: Debug (configrom.cpp)[ 561] printConfigRomDebug: Current Node Id: 0 50453486312: Debug (configrom.cpp)[ 562] printConfigRomDebug: GUID: 0x00130E0100042D67 50453486325: Debug (configrom.cpp)[ 563] printConfigRomDebug: Vendor Name: Focusrite 50453486339: Debug (configrom.cpp)[ 564] printConfigRomDebug: Model Name: SaffireLE 50453486351: Debug (configrom.cpp)[ 565] printConfigRomDebug: Node Vendor ID: 0x00130e 50453486364: Debug (configrom.cpp)[ 566] printConfigRomDebug: Model Id: 0x00000000 50453486377: Debug (configrom.cpp)[ 567] printConfigRomDebug: Unit Specifier ID: 0x00a02d 50453486389: Debug (configrom.cpp)[ 568] printConfigRomDebug: Unit version: 0x00010001 50453486402: Debug (configrom.cpp)[ 569] printConfigRomDebug: ISO resource manager: 0 50453486415: Debug (configrom.cpp)[ 570] printConfigRomDebug: Cycle master capable: 1 50453486432: Debug (configrom.cpp)[ 571] printConfigRomDebug: Bus manager capable: 1 50453486444: Debug (configrom.cpp)[ 572] printConfigRomDebug: Cycle clock accuracy: 100 50453486455: Debug (configrom.cpp)[ 574] printConfigRomDebug: Max rec: 8 (max asy payload: 512 bytes) 50453486480: Debug (DeviceStringParser.cpp)[ 162] match: match 0xd59260 50453486493: Debug (devicemanager.cpp)[ 583] discover: Device doesn't match any of the spec strings. skipping... It could still be a ricoh problem. From lspci: 15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) I expect better results from an expresscard: 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) I'll post my results once I pick up an 1394a expresscard. Thanks for your help. -- Ticket URL: <http://subversion.ffado.org/ticket/195> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-01-25 06:35:34
|
#187: could not start jack with saffire pro on 64bit -------------------------------------+-------------------------------------- Reporter: adamix | Owner: Type: bug | Status: new Priority: blocker | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: | Device_name: focusrite saffire pro 10i/o -------------------------------------+-------------------------------------- Comment (by rgreen): I'm successfully running jackd 0.113.0 with ffado 2.0-rc1 on ubuntustudio 8.04 (64 bit) with a saffire pro26. -- Ticket URL: <http://subversion.ffado.org/ticket/187#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-01-20 12:20:32
|
#194: MIDI: Device present in "MIDI", not in "Alsa" (qjackctl) -------------------------------------+-------------------------------------- Reporter: blindekinder | Owner: Type: feature | Status: new Priority: minor | Milestone: FFADO 2.x Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: | Device_name: -------------------------------------+-------------------------------------- Changes (by adi): * priority: major => minor * type: bug => feature * milestone: FFADO 2.0 => FFADO 2.x Comment: Hi. That's completely normal. There are multiple different frameworks to access a MIDI port. Your application only supports the alsa-seq interface, not the jack-midi (jack-midi is what you see in qjackctl's "MIDI" page). Three ways to fix: * convince your application developer to support jack midi (probably a good idea) * convince FFADO to export the MIDI port to alsa-seq (don't know what FFADO's alsa plugin does) * use a software bridge to export your jack midi ports to alsa-seq. (http://home.gna.org/a2jmidid/) The last option is your instant fix, giving you the ports immediately. HTH PS: Linuxsampler is an example for an application supporting the jack-midi API. -- Ticket URL: <http://subversion.ffado.org/index.fcgi/ticket/194#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-01-20 00:32:02
|
#194: MIDI: Device present in "MIDI", not in "Alsa" (qjackctl) ----------------------------------------+----------------------------------- Reporter: blindekinder | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Keywords: Device_name: | ----------------------------------------+----------------------------------- Hi, I use an Edirol FA-101 with ffado 2.0, jack 0.116.1 and qjackctl 0.3.4. Sound works, but midi physical port doesn't appear in "Alsa", only in "Midi". In "Patchage", I see the port (firewire_pcm midi-port), but it doesn't let me connect it to anything. -- Ticket URL: <http://subversion.ffado.org/ticket/194> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-01-19 07:27:28
|
#193: Failed to execute dbus-launch to autolaunch D-Bus session ----------------------------------------+----------------------------------- Reporter: rooker | Owner: Type: bug | Status: new Priority: minor | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Keywords: dbus x11 ffado-dbus-server Device_name: | ----------------------------------------+----------------------------------- When starting ffado-dbus-server on Ubuntu Hardy, the following errormessage appears: Failed to execute dbus-launch to autolaunch D-Bus session This is fixed by installing the package "dbus-x11". Maybe, "dbus-x11" should be set as dependency for the ffado-dbus-server package to avoid this problem for new users? -- Kubuntu Hardy (updated 18.Jan.2009) ffado 2.0rc1 (1.999.40) -- Ticket URL: <http://subversion.ffado.org/ticket/193> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2009-01-19 07:14:43
|
#184: fix qt4 version of phase88 mixer -----------------------------------------------+---------------------------- Reporter: ppalmers | Owner: Type: bug | Status: new Priority: major | Milestone: FFADO 2.0 Version: FFADO 2.0-rc1 (1.999.40) | Resolution: Keywords: terratec phase88 mixer upside-down | Device_name: -----------------------------------------------+---------------------------- Changes (by rooker): * keywords: => terratec phase88 mixer upside-down * version: FFADO 2.0-beta7 (1.999.38) => FFADO 2.0-rc1 (1.999.40) Comment: I've also got both problems (faders and front/back switch) with my Terratec phase 88 rack. Took me a while to figure it out. The ffado-dbus output shows that the faders produce negative values when you move them up, like this: bottom = 0 top = -32767 -- Ticket URL: <http://subversion.ffado.org/ticket/184#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |