21 Oct
2005
21 Oct
'05
5:28 p.m.
Are you using a customized jackd? What version? What
command line? Do
you have any evidence that anyone has ever made this work?
Opps, sorry for skipping obviously needed details. Was really upset.
I tried freebob + jackd from freebob.sf.net.
libavc from svn, libiec61883 1.0, libraw1394 1.2
cmdline: jackd -d iec61883 -o osc.udp://localhost:31000
FreeBoB wiki's list of working setups contains FA-101 + gentoo (my distro).
When run in the first time, jackd starts, but there's no sound, and
seems processing callbacks aren't called (no interrupts?).
Dmitry.
21 Oct
21 Oct
5:51 p.m.
On Fri, 2005-10-21 at 23:27 +0400, Dmitry S. Baikov wrote:
I think this would be a better question for the Freebob list, and cc:
the jackit-devel list, as you're using a version of JACK that the
Freebob people have customized. I've never heard anyone on LAD or LAU
report that this works.
First and foremost, we need to get the iec61883 driver into JACK CVS, so
that Paul Davis and the other JACK experts can help you.
Lee
Are you using
a customized jackd? What version? What command line? Do
you have any evidence that anyone has ever made this work?
Opps, sorry for skipping obviously needed details. Was really upset.
I tried freebob + jackd from freebob.sf.net.
libavc from svn, libiec61883 1.0, libraw1394 1.2
cmdline: jackd -d iec61883 -o osc.udp://localhost:31000
FreeBoB wiki's list of working setups contains FA-101 + gentoo (my distro).
When run in the first time, jackd starts, but there's no sound, and
seems processing callbacks aren't called (no interrupts?). 
7:48 p.m.
On 10/21/05, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Fri, 2005-10-21 at 23:27 +0400, Dmitry S. Baikov
wrote:
I think this would be a better question for the Freebob list, and cc:
the jackit-devel list, as you're using a version of JACK that the
Freebob people have customized. I've never heard anyone on LAD or LAU
report that this works.
First and foremost, we need to get the iec61883 driver into JACK CVS, so
that Paul Davis and the other JACK experts can help you.
Lee
In case some folks don't know this stuff iec61883 is part of the 1394
stack. Why would it go into Jack CVS?
My rudimentary understanding (from a good awful number of years
working on 1394 OHCI Link and Phy chips - not software) is that
iec61883 is an encapsulation process that places timing info and data
packets into a larger chunk of data most commonly moved across, but
not limited to, the 1394 bus. 61883 is a really basic way to get MPEG
data broken apart and put back together so that you can move movies
across 1394.
NOTE: There are multiple parts, 6 or 7 now, to iec61883. I'm not sure
which ones Linux-1394 is supporting.
Are you
using a customized jackd? What version? What command line? Do
you have any evidence that anyone has ever made this work?
Opps, sorry for skipping obviously needed details. Was really upset.
I tried freebob + jackd from freebob.sf.net.
libavc from svn, libiec61883 1.0, libraw1394 1.2
cmdline: jackd -d iec61883 -o osc.udp://localhost:31000
FreeBoB wiki's list of working setups contains FA-101 + gentoo (my distro).
When run in the first time, jackd starts, but there's no sound, and
seems processing callbacks aren't called (no interrupts?). From a cursory reading of the Freebob list I have not
heard of any
special versions of Jack required to run it, but I frankly haven't
paid a huge amount of attention to it. Does anyone know?
I do agree that this question belongs there. They seem to respond
pretty quickly to questions like this.
- Mark
10 p.m.
On Fri, 2005-10-21 at 14:48 -0700, Mark Knecht wrote:
Sorry, I mean "the iec61883 backend". JACK used to call these
"drivers"
but as you can see it's confusing. JACK does not need to include the
iec61883 stack but it does need to know how to talk to it, just like
with ALSA, OSS, etc.
Look at his command line:
jackd -d iec61883 -o osc.udp://localhost:31000
If I run this I get:
rlrevell@mindpipe:~/kernel-source/linux-2.6.13$ jackd -d iec61883
jackd: unknown driver 'iec61883'
So he must be using a third party patch to jackd from the Freebob people
that implements the 'iec61883' backend.
Lee
I think this
would be a better question for the Freebob list, and cc:
the jackit-devel list, as you're using a version of JACK that the
Freebob people have customized. I've never heard anyone on LAD or LAU
report that this works.
First and foremost, we need to get the iec61883 driver into JACK CVS, so
that Paul Davis and the other JACK experts can help you.
Lee
In case some folks don't know this stuff iec61883 is part of the 1394
stack. Why would it go into Jack CVS?
10:29 p.m.
On 10/21/05, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Fri, 2005-10-21 at 14:48 -0700, Mark Knecht wrote:
Sorry, I mean "the iec61883 backend". JACK used to call these
"drivers"
but as you can see it's confusing. JACK does not need to include the
iec61883 stack but it does need to know how to talk to it, just like
with ALSA, OSS, etc.
Look at his command line:
jackd -d iec61883 -o osc.udp://localhost:31000
If I run this I get:
rlrevell@mindpipe:~/kernel-source/linux-2.6.13$ jackd -d iec61883
jackd: unknown driver 'iec61883'
So he must be using a third party patch to jackd from the Freebob people
that implements the 'iec61883' backend.
Lee
I'm probably whacked. I just assumed that was the name available when
the amdtp driver was modprobed. Most likely you are right and they
have developed an iec61883 Alsa driver which they have Jack talking
to.
For kicks I've just built all the 61883 stuff for this kernel I'm
working on. I'll modprobe it sometime after rebooting and convince
myself that you are correct.
Cheers,
Mark
I think
this would be a better question for the Freebob list, and cc:
the jackit-devel list, as you're using a version of JACK that the
Freebob people have customized. I've never heard anyone on LAD or LAU
report that this works.
First and foremost, we need to get the iec61883 driver into JACK CVS, so
that Paul Davis and the other JACK experts can help you.
Lee
In case some folks don't know this stuff iec61883 is part of the 1394
stack. Why would it go into Jack CVS?
22 Oct
22 Oct
12:23 a.m.
Look at his command line:
jackd -d iec61883 -o osc.udp://localhost:31000
If I run this I get:
rlrevell@mindpipe:~/kernel-source/linux-2.6.13$ jackd -d iec61883
jackd: unknown driver 'iec61883'
So he must be using a third party patch to jackd from the Freebob people
that implements the 'iec61883' backend.
Lee
I'm probably whacked. I just assumed that was the name available when
the amdtp driver was modprobed. Most likely you are right and they
have developed an iec61883 Alsa driver which they have Jack talking
to.
For kicks I've just built all the 61883 stuff for this kernel I'm
working on. I'll modprobe it sometime after rebooting and convince
myself that you are correct.
Cheers,
Mark
1:01 a.m.
Mark Knecht <markknecht(a)gmail.com> writes:
I wonder if they have changed Jack to suit their
needs. or is this
just easier for them than trying to embed their freebob driver into
the existing Jack direcories? Not sure it matters. It's just what they
are doing.
The FreeBob developers currently use a prototype JACK backend. They
plan to rewrite it, then integrate the cleaned up version into the
main JACK distribution.
Lee is correct to send the original requester to freebob-devel for
answers and support with this backend. They can probably help him.
--
joq
6786
days inactive
6786
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Dmitry S. Baikov -
Jack O'Quin -
Lee Revell -
Mark Knecht