>
>
> nope - try, if it works with 64Studio
>
> Your card is detected an switched ON it only crashes immediately. I have
> simlar trouble with my firebox, that works just fine with 64studio and
> jad
>
Will do - Pieter on the L-A-U list mentioned it might be a kernel issue.
And thanks to Phil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Wenn schrieb:
> The saga continues.
>
> libiec61883 warning: Established connection on channel 1.
> You may need to manually set the channel on the transmitting node.
> 20268 waiting for signals
> Aborted
>
> I cannot begin to describe how vex
On Tue, 24 Jun 2008 23:09:43 +1000
Chris Wenn <[EMAIL PROTECTED]> wrote:
> The saga continues.
>
> Having purchased an Expresscard/34 with Texas Instruments ieee1394a
> (Firewire 400) chipset, as recommended here:
> http://www.ffado.org/?q=node/251 for my Focusrite Saffire
The saga continues.
Having purchased an Expresscard/34 with Texas Instruments ieee1394a
(Firewire 400) chipset, as recommended here:
http://www.ffado.org/?q=node/251 for my Focusrite Saffire LE, which has
been reported by many users as working perfectly with Ubuntu - and other
distros (and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
antoine clémot schrieb:
> Hello,
>
> I've just moved from Hardy to Studio 64. I had really too much problem with
> jackd using my Firewire card edirol FA101 (always crashing, qjackctl
> indicating 30% of work while there is no more soft' running)
Hello,
I've just moved from Hardy to Studio 64. I had really too much problem with
jackd using my Firewire card edirol FA101 (always crashing, qjackctl
indicating 30% of work while there is no more soft' running)
I installed the AMD64 version and jack works perfectly well. When starting
jackd,
> Yeah - voodoo ;-)
> try running jack from a commandline and start qjackctl afterwards (jackd
> is shown then as active all the ports can be managed as usual...)
>
> This helped the case for me at least...
The problem is that jack is crashing within a second of being started,
so by the time qjac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Wenn schrieb:
> OK.
>
> Booting to 64Studio gave better verbose logging from jackd particularly
> here:
>
> new client: qjackctl-7381, id = 2 type 2 @ 0xb6d44000 fd = 15
> ++ jack_rechain_graph():
> client freebob_pcm: internal client, executio
OK.
Booting to 64Studio gave better verbose logging from jackd particularly
here:
new client: qjackctl-7381, id = 2 type 2 @ 0xb6d44000 fd = 15
++ jack_rechain_graph():
client freebob_pcm: internal client, execution_order=0.
client qjackctl-7381: start_fd=5, execution_order=0.
client qjackctl-738
On Mon, 2008-06-02 at 09:24 +0200, Hartmut Noack wrote:
>
> basically all external devices - be it USB or FW, need periods/buffer
> set to 3 instead of 2.
>
> The jack-settings, that work for my Presonus Firebox in 64Studio are:
>
> /usr/bin/jackd -R -v -t1000 -dfreebob -r96000 -p256 -n3
>
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ming schrieb:
> Two weird things I
> noticed about Saffire LE and JACK:
> 1. It just won't work on 44.1KHz, mine only works at 48 and 96 KHz.
> 2. I need to set the number of max I/O channel both to 64. QJackCtl's
> max value of 32 just don't work, so
7;t work, so I have to modify QJackCtl's config
file.
Hope it helps :)
===
> From: Chris Wenn <[EMAIL PROTECTED]>
> Subject: More Problems [was: Re: Focusrite Saffire LE]
> To: Ubuntu Studio Users Help and Discussion
>
> Message-I
OK
I now have a firewire ExpressCard - the cheapest I could get, because
they're VERY expensive here! lspci shows:
0e:00.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link
Layer Controller (rev 01) (prog-if 10 [OHCI])
Subsystem: Unknown device 0ee4:3884
Flags: bus
On Wed, May 21, 2008 at 8:36 PM, antoine clémot <[EMAIL PROTECTED]> wrote:
> Maybe you have to install gscanbus (which I did for my firewire soundcard)
> to reset the fireport connection before starting jack. But I'm not an expert
> enough to read your lines...
> Maybe a problem of rights for ieee
Maybe you have to install gscanbus (which I did for my firewire soundcard)
to reset the fireport connection before starting jack. But I'm not an expert
enough to read your lines...
Maybe a problem of rights for ieee1394 : did you check you're
/etc/security/limits.conf ???
Does your user have the r
Looking through syslog, I discovered the following lines:
May 21 09:19:28 zakalwe kernel: [ 3204.754527] ieee1394: Node suspended:
ID:BUS[0-01:1023] GUID[00130e0100041bbc]
May 21 09:19:44 zakalwe kernel: [ 3218.944011] ieee1394: Node resumed:
ID:BUS[0-01:1023] GUID[00130e0100041bbc]
May 21 09:
On Sun, 2008-05-18 at 19:48 +0200, antoine clémot wrote:
> luck
>
> P.s. : what is the name of your outputs ports in qjackctl? ?
The output ports are playback_1 through playback_8. Capture ports are
capture_1 through capture_6.
I've now updated the firmware by installing the device on a Mac, and
On Sun, 2008-05-18 at 19:48 +0200, antoine clémot wrote:
> For hydrogen I think that maybe you have to edit your file .hydrogen
> which is in /home/"user"/ (hiden file).
> For instance with gedit and replace "alsa_pcm:playback_1" and
> "alsa_pcm:playback_2" by "freebob:playback..." (if you're under
For hydrogen I think that maybe you have to edit your file .hydrogen which
is in /home/"user"/ (hiden file).
For instance with gedit and replace "alsa_pcm:playback_1" and
"alsa_pcm:playback_2" by "freebob:playback..." (if you're under Gutsy look
out in the qjackctl what is the exact name of your ou
for me disabling few processes helped a lot. Wifi card, network manager,
and some processes started from cron and anacron. Also improved a lot
compiling Jack and freebob from source but it wasnt easy.
Chris Wenn(e)k dio:
> On Fri, 2008-05-16 at 10:25 +0200, altern wrote:
>
>> some Ricoh chips c
On Fri, 2008-05-16 at 10:25 +0200, altern wrote:
>
> some Ricoh chips cause problems, my laptop is a IBM has a Ricoh chip and
> Freebob is very unstable. Sorry i cannot give more detailed info maybe
> someone can?
Having spent near enough to A$500 on this device I'm in no position to
go findin
Chris Wenn(e)k dio:
> Does anyone have this device working on Ubuntu Studio 8.04?
>
> Mine is recognized, and I can start jackd using it, but I get no sound
> from the device and repeated error messages saying
>
> "cannot complete execution of the processing graph (Resource temporarily
> unavaila
On Fri, 2008-05-16 at 07:56 +0300, Asmo Koskinen wrote:
> Chris Wenn kirjoitti:
> > Does anyone have this device working on Ubuntu Studio 8.04?
> >
>
> Here is something, Pau Arumi’s blog:
>
> "I have not tested the non-pro versions (Saffire and Saffire LE), but I
> guess it applies also to t
Chris Wenn kirjoitti:
> Does anyone have this device working on Ubuntu Studio 8.04?
>
Here is something, Pau Arumi’s blog:
"I have not tested the non-pro versions (Saffire and Saffire LE), but I
guess it applies also to them."
"I’m very thankful to Pieter Palmer for the quick help at #ffado
Does anyone have this device working on Ubuntu Studio 8.04?
Mine is recognized, and I can start jackd using it, but I get no sound
from the device and repeated error messages saying
"cannot complete execution of the processing graph (Resource temporarily
unavailable)"
followed by the message "ja
25 matches
Mail list logo
