22 Sep
2008
22 Sep
'08
12:51 p.m.
Am Montag, 22. September 2008 schrieben Sie:
On Mon, Sep 22, 2008 at 4:05 PM, Arnold Krille
<arnold(a)arnoldarts.de> wrote:
Probably the most common problem: /dev/raw1394 is not accessible by the
user...
Arnold
PS: surely you want this to stay on the list?
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a "rm -rf /". Or ask your
administrator to do so...
Am Montag, 22. September 2008 schrieb
simone-www.io-lab.org:
ok here it is:
[io@localhost ~]$ /usr/bin/jackd -dfreebob -dhw:0 -r44100 -p256 -n3 -D
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
SSE2 detected
Freebob using Firewire port 0, node -1
Ieee1394Service::initialize: Could not get 1394 handle: Invalid argument
Is ieee1394 and raw1394 driver loaded?
Fatal (devicemanager.cpp)[68] initialize: Could not initialize
Ieee1349Service object
Fatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device
manager LibFreeBoB ERR: cannot create libfreebob handle
FreeBoB ERR: FREEBOB: Error creating virtual device
cannot load driver module freebob
Segmentation fault i am having hard time to get FreeBob working on
my system ofr it seems
like Jack can t even load the freebob driver, any idea?
[root@localhost io]# /usr/bin/jackd -dfreebob -dplughw:0 -r48000 -p256
-n3 -D jackd 0.109.2
FreeBoB ERR: device (-d) argument not valid
Simply follow the rules: plughw is
alsa-specific. freebob uses hw:X.Y for
numbering the devices and the reason there is a hw: in that term is only
for convenience. The X represents the fw-bus and Y is the device on the
bus. But you shouldn't need to specify any of those...