Posted the following in your other mail:<br><br><a href="http://w3.linux-magazine.com/issue/67/JACK_Audio_Server.pdf">http://w3.linux-magazine.com/issue/67/JACK_Audio_Server.pdf</a><br><br>Let's take a look at what QJackCtl is, before we talk about its documentation. Someone else in another related-mail mentioned that the need for documentation isn't that much significant since the application - or rather utility - is a rather straightforward one. It is afterall, a front-end to the JACK server. It lets you manage connections, execute commands/scripts alongside, set server options with a GUI, and err..that's about it. Your best friend indeed, but one whom you can understand easily, given the right attitude.<br>
<br>Start == Self-explanatory<br>Stop == " "<br> Messages == " " (jack-specific)<br>Status == " "<br>Connect == " "<br>Patchbay == " " (you could find out what it does by just checking it out; experimenting)<br>
Quit == You really need an explanation?<br>Setup == " "<br><br>Ok so we now take a look at Setup. Sure, things need to be explained here. That's just what the above JACK document in PDF format does. Other things which aren't brought into detail are fairly common knowledge, or sense. Alright now try searching for this PDF file from Google, that way we can gauge how difficult/easy it is to stumble upon. True enough, there isn't anything else similar out there so we can say "proper" documentation of the program is scarce. I really like your stance on this issue and with more people like you this particular lack of "professionalism" can definitely be nullified. Now I'm inspired enough to do some writing too ;) <br>
<br><div><span class="gmail_quote">On 17/04/2008, <b class="gmail_sendername">schoappied</b> <<a href="mailto:schoappied@gmail.com">schoappied@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
Hi,<br><br> Thinking about linux audio and documentation... Isn't it strange that<br> there isn't a good documentation for qjackctl (in combi with jack)?<br> qjackctl is such a core app if you want to work with linux audio. And<br>
qjackctl/ jack is often a high 'threshold' to get started to use linux<br> audio software...<br><br> Ok, we've patchbay explained now, but what about the parameter settings,<br> options, display, misc, connections (and the different tabs,<br>
audio/midi/alsa), messages and status?<br><br> I think we can lower the threshold to start use linux audio apps if this<br> important part is better explained in a good and clear (with pictures)<br> documentation, which can be updated when there is a new qjackctl with<br>
new features. I also like to know more about it myself!<br><br> Kind regards,<br><br> Dirk<br> _______________________________________________<br> Linux-audio-user mailing list<br> <a href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br></blockquote></div><br>