From: Jan Depner (eviltwin69_at_cableone.net)
Date: 01/06/04 20:53 EST
Subject: Re: [Jamin] JAMin documentation
From: Jan Depner <eviltwin69@cableone.net>
Message-Id: <1073440428.1692.26.camel@eviltwin>
Date: 06 Jan 2004 19:53:47 -0600
On Tue, 2004-01-06 at 19:33, Jack O'Quin wrote:
> Jan Depner <eviltwin69@cableone.net> writes:
>
> > I've added documentation on how to use JAMin on our web site. Please
> > take a look and provide corrections. You can find it under the
> > Documentation section->Using JAMin.
>
> Outstanding!
>
> No corrections, but a few suggestions (by section).
>
> (Contents) There is probably no need to describe the command line
> parameters, but the man page should be mentioned somewhere. I see
> the man page needs some updates.
Send me what you want fixed in the man page and I'll put it in. I
think we should definitely mention the man page.
>
> (2) I think the "connecting applications" section should start with
> a recommendation to use qjackctl and a simple example of its use.
> We don't want to scare people off.
>
Only one small problem with qjackctl - you have to download and build
the latest version of Qt to build qjackctl. Anyone on RH 7.3 or earlier
will have a problem with this. I think it's well worth it but it is a
PITA.
> The script is great for power users, but we don't want new users
> getting the impression that you need to understand all that to use
> JAMin. Some simplification would help.
If we tell people about the dependency for qjackctl but recommend
qjackconnect as as alternate we only need the killall lines, lowlatency
setting, jackd, alsaplayer, JAMin... wait, that's just about everything
;-)
The initial cleanup and
> setting of lowlatency is probably not needed, for example.
If you're using qjackctl.
And,
> please don't `killall -9 jackd' unless it's hung badly and the
> normal `killall -15 jackd' won't work.
qjackctl does this by default.
Give JACK a chance to clean
> up its session state.
>
> (3) You should tell people how to configure their display to look
> like your fine examples. They're not the default.
>
They're not??? I didn't change anything. I just used the .jamrc that
comes with the package.
> (3.3) The ports example should use an input group. That's usually
> what people want. It's much more convenient than connecting each
> channel separately.
>
That's something I didn't know anything about ('cause I've been using
qjackctl ;-) Can you provide some verbiage for that?
> (3.5) The <- and -> controls skip backward or forward five seconds
> rounded to the nearest whole second.
Another point that I wasn't sure of. I knew it skipped some but I
wasn't sure how much so I left it out.
BTW, ardour doesn't currently
> slave to JACK transport correctly, but it probably will soon.
>
I thought that was the case but, again, I wasn't sure.
> (3.9) FWIW, the correct term is "visually impaired", rather than
> "sight impaired". My wife teaches at the "Texas School for the
> Blind and Visually Impaired". :-)
>
I just didn't know if blind was PC or not. I'll change it.
> (3.19) I don't believe `bypass' changes the latency. Steve??
> --
It used to but may have been changed.
I'm glad you liked it. I just wanted to get a starting point for the
documentation.
Jan
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Jamin-devel mailing list
Jamin-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jamin-devel
This archive was generated by hypermail 2.1.7 : 01/06/04 20:54 EST