KX mini manual

[danboid]

I'm not totally sure if you're joking Wolfman JACK but no this is nothing that need be added to the manual.

As it turned out its 1 less thing needed to be written about because we don't (shouldn't) need to mention running regsvr32 to get wineasio running according to F.

I may have intentionally nuked .wine experimenting with Teamviewer - nothing to do with KX.

[wolftune]

Well, two things:

1. I indeed removed my .wine when I was experimenting. I don't actually think this should be in the newbie-focused get-going with KXStudio docs, but I do want it documented somewhere. If one removes their .wine folder, then what command should be run? I personally want to know if I should do something right now.

2. Instead of Team Viewer, I found the FLOSS solution for screen sharing to help newbies trouble-shoot etc.: Jitsi. Jitsi is like Kopete except when using XMPP it includes a full screen sharing and remote desktop control function! Plus it works with portaudio and is cross-platform so works well with all systems and desktops!

Regarding #2: I'm inclined to include some separate page in the docs on the general topic of "how to get more help and tech support" and mentioning Jitsi there makes sense to me, although I'm not absolutely stuck on the idea.

[danboid]

.wine is auto-created when you run any app via wine if it doesn't already exist. winecfg prob does the same.

I was using Teamviewer because I have recently been helping someone who already uses it on their Windows machines. I wasn't planning to mention it in the KX manual. Just because I may mention something in this thread doesn't mean I intend for it to be in the manual. Yet again - see OP for my intended contents. I may need to make that my new sig.

I dunno about Jitsi for remote desktop but it was crap for voip when I tried it a year or so ago.

Please don't recommend stuff if you've not tried and tested it. As I'm sure you know by now there are thousands of apps out there that don't do live up to their hype.

[wolftune]

Dan,

I have been testing and using this. I don't recommend things I haven't tested. Jitsi 2.0 came out just last month. Although even before that, it did work for me. I have it installed and use it and it is the only simple screen-sharing FLOSS option (aside from Empathy which is similar but is strictly tied to all the GNOME stuff and not inter-operable).

And I never thought that everything you mention is necessarily for the docs, but I already (as you'll see in my notes on my other thread) have a section of "how to get help" as an idea. So I want to see that included. It references this forum, the IRC channel, where else to search for help, and the prospect of using Jitsi with someone else who is willing to provide more personal tech support. So this was already an item in my own list.

[Thad E Ginathom]

Trouble-shooting section. How to get yourself out of the trouble you just got in section.

People accidentally delete files. People accidentally overwrite software with updates from other sources. People, of course, means me ...and its always nice to be able to read up how to recover from such stuff. It's also one of the differences compared to certain commercial software where the PR department won't allow the tech writers to admit that anything can go wrong

[danboid]

Wolftune:

Thats good to know about Jitsi being good for something but you have proved now that regardless of me constantly repeating

EVERYBODY - READ THE OP

You have clearly failed to look at it as the last section listed is called 'Getting Help' and intends to cover exactly what you mentioned. Do you not know what OP means? It means 'Original post' of a thread. Please read it now and stop suggesting things I've already suggested in the OP! I'm tired of repeating myself over and over on this!

[wolftune]

ok sorry

[danboid]

Updated OP with a bit more detail on what I'd like to cover in the sound systems and config dept.

I planned to get some of it written tonight but its unlikely now.

[danboid]

Updated the TOC in the OP again, mainly the contents and names of the meaty chapters so I think the key chapters should now look something like:

Linux audio overview

A short introduction to ALSA, JACK, FFADO and PA, their purposes and pitfalls

ALSA

(un)muting and controlling devices with kmix, common ALSA-only apps, Cadence ALSA bridges, key ALSA commands

JACK prerequisites

Adding user to audio group, configure rtirq

Configuring JACK with Cadence

Tips on configuring ALSA and firewire devices

Controlling JACK with Cadence

Starting, stopping, restarting JACK. Driver switching and checking for errors in logs

JACK tips and troubleshooting

Explanation of xruns and latency, JACK troubleshooting tips like resolving IRQ conflicts, using setpci, list common xrun causes

[danboid]

danboids overview of Linux audio is done!

The demystification continues!

http://www.wiki.linuxmusicians.com/doku ... o_overview

[danboid]

Wolftune and other potential contributors - please remember that latest page is intended ONLY for brief definitions and explanations of the main Linux sound systems. I don't want a history of JACK plus every JACK app listed on there etc!

I made a few other tweaks and additions to the LM wiki, most importanly adding a link to a Ubuntu SSD optimization guide to the filesystems sub-section of the system page and I wanted to give TAL Noisemaker and Rui's proto tools a bit more exposure.

[wolftune]

Dan,

That explanation made far more sense than the crazy complaining diagrams I saw when I was a newbie!
I made a few edits. Looks good!

[danboid]

Lovely!

Thats some great feedback and some good edits Wolftune!

I've just cleaned it up a little bit and now its a shining diamond of a Linux doc, if I do say so myself!

[wolftune]

Oh one thought: I'd love to see a newbie-friendly instructions for alsa_in and alsa_out, i.e. the way to access multiple devices simultaneously. I am personally still confused about it. I thought of it when I realized it might make sense to link the ALSA stuff to a page that included that.

[danboid]

I don't see why a newb would need to know that Mr Wolf.

I wasn't planning on covering any .asoundrc wizardry in this manual although that file will get mentioned in the ALSA chapter one way or another.