Subject: [linux-audio-dev] re: JACK tutorial
From: james_AT_dis-dot-dat.net
Date: Tue Nov 18 2003 - 00:17:19 EET
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_AT_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
>
>
This archive was generated by hypermail 2b28 : Tue Nov 18 2003 - 00:20:46 EET