From Fedora Project Wiki
(added "Testing PulseAudio & JACK Algorithms")
(removed PulseAudio/JACK testing stuff; added proof-reading)
Line 1: Line 1:
== Testing PulseAudio and JACK Algorithms ==
== How to Submit Comments ==
This phase of testing focusses on ensuring that the algorithms specified for using the PulseAudio and JACK sound servers, specifically together, work as intended.
* On IRC, contact the user "crantila" in Freenode's #fedora-docs or #fedora-summer-coding channel.
=== More Important: Ensuring That PulseAudio Works with JACK ===
* Send an email to crantila at gmail
The recommended way to use JACK on Fedora is in conjunction with PulseAudio.  When done this way, there is no reason to choose between one of the two sound servers, and PulseAudio remains available for day-to-day use.  Follow these instructions:
 
# Visit the [[User:Crantila/FSC/SoundServers/JACK#How_to_Setup_Your_System_for_JACK|JACK page]], and follow the instructions in those four sections.  Then test the following:
== What Requires Testing ==
#* The JACK server starts and stops, according to the QjackCtl window.
Please see [[User:Crantila/FSC/Drafts|this page]] for a list of documents which require proof-readingAll documents on that page are still drafts.
#* QjackCtl indicates "RT" in the status window, meaning that it is in real-time mode.
 
#* PulseAudio applications will not work while the JACK server is running.
The documents are currently in a "first draft" state. This means that, while the overall format and content is unlikely to change dramatically, small-scale things like sentence structure, text formatting, use/definition of technical terms, and consistency, are almost certain to change.
#* A JACK-aware application can successfully play audio while the JACK server is running (perhaps Audacity).
 
#* A JACK-aware application can successfully record audio while the JACK server is running (perhaps Audacity).
As you read sections, please take note of things that should be changed or which require additional thought, and submit them in one of the ways listed above.
# If one of the above statements is not true, then please contact [[User:Crantila|me]] or post a bug report, as appropriate.  If you don't know whom to contact, then contact [[User:Crantila|me]].
 
# Visit the [[User:Crantila/FSC/SoundServers/Pulse#Integrating_PulseAudio_with_JACK|PulseAudio page]], and follow the "Integrating PulseAudio with JACK" instructionsThen test the following:
Thank you.
#* The JACK server is automatically started by PulseAudio.
#* Upon opening QjackCtl, it registers that an instance of JACK is already running, and that the PulseAudio virtual devices are connected to the system virtual devices.
#* A JACK-aware application can successfully play audio while the JACK server is running (perhaps Audacity).
#* A JACK-aware application can successfully record audio while the JACK server is running (perhaps Audacity).
#* A PulseAudio application can successfully play audio while the JACK server is running (perhaps Amarok).
#* A PulseAudio application can successfully record audio while the JACK server is running (perhaps Audacity - properly configured).
# If one of the above statements is not true, then please contact [[User:Crantila|me]] or post a bug report, as appropriate.  If you don't know whom to contact, then contact [[User:Crantila|me]].
=== Less Important: Being Able to Remove PulseAudio ===
This is a less-compatible method to avoid PulseAudio interference, but it is not recommended unless the computer is to be used only for audio production.
# Visit the [[User:Crantila/FSC/SoundServers/Pulse#How_to_Remove_PulseAudio|PulseAudio page]], and follow the instructions on "How to Remove PulseAudio."
# You'll probably want JACK, too.
# If you think that it works, then it does.
# If you feel that this section needs to be preserved and included in the Guide, then please help to find a universally-applicable algorithm. It must leave all audio applications operable.

Revision as of 23:03, 30 June 2010

How to Submit Comments

  • On IRC, contact the user "crantila" in Freenode's #fedora-docs or #fedora-summer-coding channel.
  • Send an email to crantila at gmail

What Requires Testing

Please see this page for a list of documents which require proof-reading. All documents on that page are still drafts.

The documents are currently in a "first draft" state. This means that, while the overall format and content is unlikely to change dramatically, small-scale things like sentence structure, text formatting, use/definition of technical terms, and consistency, are almost certain to change.

As you read sections, please take note of things that should be changed or which require additional thought, and submit them in one of the ways listed above.

Thank you.