20 Oct
2003
20 Oct
'03
6:27 a.m.
Hi,
I've recently been learning to use JACK, and I had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
If this is well received, I'll write about more advanced topics as I
get to them - mixing, the transport, threading without blocking the
process callback, etc.
I'll probably be asking a lot of questions later on, especially
about best practise.
Thanks peeps,
James
20 Oct
20 Oct
6:45 a.m.
Hi James,
Monday 20 October 2003 10.26 skrev james(a)dis-dot-dat.net:
Hi,
I've recently been learning to use JACK, and I had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
Good stuff!
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
I just browsed it very quickly so I can't really comment about the contents.
I have some reading up on jack to do so I think I will try to read it more
thorougly later this week!
Nice format anyway. The only thing I'm missing is a link from one page to the
next page without going back to the TOC.
If this is well received, I'll write about more
advanced topics as I
get to them - mixing, the transport, threading without blocking the
process callback, etc.
That be very nice. Transport is something that I would personally find useful
(though I haven't checked what is available).
/Robert
I'll probably be asking a lot of questions later
on, especially
about best practise.
Thanks peeps,
James
7:06 a.m.
On Mon, 20 Oct, 2003 at 10:40AM +0200, Robert Jonsson spake thus:
Thanks for the comments
James
Hi James,
Monday 20 October 2003 10.26 skrev james(a)dis-dot-dat.net:
Good point. Navigation coming up...
Hi,
I've recently been learning to use JACK, and I had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
Good stuff!
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
I just browsed it very quickly so I can't really comment about the contents.
I have some reading up on jack to do so I think I will try to read it more
thorougly later this week!
Nice format anyway. The only thing I'm missing is a link from one page to the
next page without going back to the TOC. If this is
well received, I'll write about more advanced topics as I
get to them - mixing, the transport, threading without blocking the
process callback, etc.
That be very nice. Transport is something that I would personally find useful
(though I haven't checked what is available). /Robert
I'll probably be asking a lot of questions
later on, especially
about best practise.
Thanks peeps,
James
1:39 p.m.
New subject: [Jackit-devel] Re: [linux-audio-dev] JACK tutorial
Robert Jonsson <robert.jonsson(a)dataductus.se> writes:
That be very nice. Transport is something that I would
personally
find useful (though I haven't checked what is available).
Nothing as readable as James' excellent tutorial. But there is a
section in the Fine Manual...
http://jackit.sourceforge.net/docs/reference/transport-design.html
Also, there is the usual collection of example-clients: showtime.c,
transport.c and intime.c have some useful snippets of code.
--
joq
9:19 a.m.
Great, great, great! Thanks a lot! IMHO, documentation like this one is
definitely needed and something we're currently lacking. I've only skimmed
it, but I'm going to read it more thoroughly later on, since it's stuff I
need to read up on.
That said, I'm a newbie on the subject, but I guess that makes me part of the
targeted audience for the tutorial. I think you're explaining things very
well. Of course, one can always look through code and find out what is going
on when learning about things like these, but it's much better to also get
the general idea of things before looking through the code. You're explaining
both concepts and give examples, and do both very well. Good job!
/Mathias
Hi,
I've recently been learning to use JACK, and I had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
If this is well received, I'll write about more advanced topics as I
get to them - mixing, the transport, threading without blocking the
process callback, etc.
I'll probably be asking a lot of questions later on, especially
about best practise.
Thanks peeps,
James
21 Oct
21 Oct
12:16 p.m.
On Mon, 20 Oct, 2003 at 01:19PM +0200, Mathias Lundgren spake thus:
Great, great, great! Thanks a lot! IMHO, documentation
like this one is
definitely needed and something we're currently lacking. I've only skimmed
it, but I'm going to read it more thoroughly later on, since it's stuff I
need to read up on.
That said, I'm a newbie on the subject, but I guess that makes me part of the
targeted audience for the tutorial. I think you're explaining things very
well. Of course, one can always look through code and find out what is going
on when learning about things like these, but it's much better to also get
the general idea of things before looking through the code. You're explaining
both concepts and give examples, and do both very well. Good job!
Thanks for the comments. Let me know if you have any suggestions for
improvement.
/Mathias
Hi,
I've recently been learning to use JACK, and I had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
If this is well received, I'll write about more advanced topics as I
get to them - mixing, the transport, threading without blocking the
process callback, etc.
I'll probably be asking a lot of questions later on, especially
about best practise.
Thanks peeps,
James
17 Nov
17 Nov
12:13 a.m.
Thanks for this tut.
Just one thought : the include statements in your code snipnets do not appear
correctly because of the <>. You could pass them through vim to take care of
the html characters (and add some color :).
$ vim +f +"syntax on" +"so $VIMRUNTIME/syntax/2html.vim"
+"wq" +"q" *.c
cheers, piem
On Tuesday 21 October 2003 14:56, james(a)dis-dot-dat.net wrote:
On Mon, 20 Oct, 2003 at 01:19PM +0200, Mathias
Lundgren spake thus:
Great, great, great! Thanks a lot! IMHO,
documentation like this one is
definitely needed and something we're currently lacking. I've only
skimmed it, but I'm going to read it more thoroughly later on, since it's
stuff I need to read up on.
That said, I'm a newbie on the subject, but I guess that makes me part of
the targeted audience for the tutorial. I think you're explaining things
very well. Of course, one can always look through code and find out what
is going on when learning about things like these, but it's much better
to also get the general idea of things before looking through the code.
You're explaining both concepts and give examples, and do both very well.
Good job!
Thanks for the comments. Let me know if you have any suggestions for
improvement.
> /Mathias
>
> > Hi,
> > I've recently been learning to use JACK, and I had a look around for
> > some kind of introductory article. I couldn't find one, so I wrote
> > the tutorial I would have wanted, as I learnt.
> >
> > The tutorial is here:
> > http://dis-dot-dat.net/jacktuts/starting/index.html
> >
> > Please have a look, make suggestions. Flames are fine, too. Let me
> > know if I've made some huge error. Or maybe I'm not doing things
> > the best way? Whatever, let me know.
> >
> > If this is well received, I'll write about more advanced topics as I
> > get to them - mixing, the transport, threading without blocking the
> > process callback, etc.
> >
> > I'll probably be asking a lot of questions later on, especially
> > about best practise.
> >
> > Thanks peeps,
> >
> > James
6:18 p.m.
New subject: [linux-audio-dev] re: JACK tutorial
On Mon, 17 Nov, 2003 at 04:12AM +0000, Paul Brossier spake thus:
Thanks for this tut.
Just one thought : the include statements in your code snipnets do not appear
correctly because of the <>. You could pass them through vim to take care of
the html characters (and add some color :).
Gah! I can't believe I didn't notice that.
Thanks for the proofreading, and thanks for the vim tip.
$ vim +f +"syntax on" +"so
$VIMRUNTIME/syntax/2html.vim" +"wq" +"q" *.c
cheers, piem
On Tuesday 21 October 2003 14:56, james(a)dis-dot-dat.net wrote:
On Mon, 20 Oct, 2003 at 01:19PM +0200, Mathias
Lundgren spake thus:
Great, great, great! Thanks a lot! IMHO,
documentation like this one is
definitely needed and something we're currently lacking. I've only
skimmed it, but I'm going to read it more thoroughly later on, since it's
stuff I need to read up on.
That said, I'm a newbie on the subject, but I guess that makes me part of
the targeted audience for the tutorial. I think you're explaining things
very well. Of course, one can always look through code and find out what
is going on when learning about things like these, but it's much better
to also get the general idea of things before looking through the code.
You're explaining both concepts and give examples, and do both very well.
Good job!
Thanks for the comments. Let me know if you have any suggestions for
improvement.
> /Mathias
>
> > Hi,
> > I've recently been learning to use JACK, and I had a look around for
> > some kind of introductory article. I couldn't find one, so I wrote
> > the tutorial I would have wanted, as I learnt.
> >
> > The tutorial is here:
> > http://dis-dot-dat.net/jacktuts/starting/index.html
> >
> > Please have a look, make suggestions. Flames are fine, too. Let me
> > know if I've made some huge error. Or maybe I'm not doing things
> > the best way? Whatever, let me know.
> >
> > If this is well received, I'll write about more advanced topics as I
> > get to them - mixing, the transport, threading without blocking the
> > process callback, etc.
> >
> > I'll probably be asking a lot of questions later on, especially
> > about best practise.
> >
> > Thanks peeps,
> >
> > James 
20 Oct
20 Oct
10:02 a.m.
I've recently been learning to use JACK, and I
had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
this is an excellent piece of work. i'd like to more-or-less
immediately add it the documentation available on the web site. there
are a few picky details that need fixing (e.g. we don't actually have
32 bits of sample resolution), but the overall sense of this is great.
are you OK with the idea of this going into the jack-www CVS
repository? i can give you write access there so that you can commit
new changes if you want, or you can just feed them through the
jack-devel mailing list.
actually, this seems like the perfect sort of document to put into a
wiki, but at present, we don't one set up for the JACK web site. i
don't know if antti has time to do this, but either way, it would be
very nice to set that up so that we can get real community feedback
and have the document improve in many different ways.
--p
10:39 a.m.
Paul Davis wrote:
actually, this seems like the perfect sort of document
to put into a
wiki, but at present, we don't one set up for the JACK web site. i
don't know if antti has time to do this, but either way, it would be
very nice to set that up so that we can get real community feedback
and have the document improve in many different ways.
I can take care of that. Naturally, all updates to the tutorial will
have to be made in the Wiki, so I need James' opinion on whether he's
interested in Wiki or maintaining his own version.
Just let me know.
-a
21 Oct
21 Oct
11:56 a.m.
On Mon, 20 Oct, 2003 at 08:02AM -0400, Paul Davis spake thus:
*blushing*
Thanks. If you let me know exactly what it is that I screwed up, I'll
amend the tutorial straight away.
I've
recently been learning to use JACK, and I had a look around for
some kind of introductory article. I couldn't find one, so I wrote
the tutorial I would have wanted, as I learnt.
The tutorial is here:
http://dis-dot-dat.net/jacktuts/starting/index.html
Please have a look, make suggestions. Flames are fine, too. Let me
know if I've made some huge error. Or maybe I'm not doing things
the best way? Whatever, let me know.
this is an excellent piece of work. i'd like to more-or-less
immediately add it the documentation available on the web site. there
are a few picky details that need fixing (e.g. we don't actually have
32 bits of sample resolution), but the overall sense of this is great. are you OK with the idea of this going into the
jack-www CVS
repository? i can give you write access there so that you can commit
new changes if you want, or you can just feed them through the
jack-devel mailing list.
That's absolutely fine with me.
actually, this seems like the perfect sort of document
to put into a
wiki, but at present, we don't one set up for the JACK web site. i
don't know if antti has time to do this, but either way, it would be
very nice to set that up so that we can get real community feedback
and have the document improve in many different ways.
7668
days inactive
7696
days old
linux-audio-dev@lists.linuxaudio.org
10 comments
7 participants
participants (7)
-
Antti Boman -
Jack O'Quin -
james＠dis-dot-dat.net -
Mathias Lundgren -
Paul Brossier -
Paul Davis -
Robert Jonsson