> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/basics.md). # Audacity Basics - [Installing FFmpeg](https://support.audacityteam.org/basics/installing-ffmpeg.md): FFmpeg allows you import/export additional audio file formats into/from Audacity - [Recording your voice with a microphone](https://support.audacityteam.org/basics/recording-your-voice-and-microphone.md): Audacity can use many types of microphones and other audio devices to record audio. - [Recording desktop audio](https://support.audacityteam.org/basics/recording-desktop-audio.md): Audacity can record computer audio (including sound from YouTube, Spotify and more). - [Editing audio](https://support.audacityteam.org/basics/audacity-editing.md): This page is an introduction tutorial to editing in Audacity. It covers how to import files, making cuts, rearranging clips, and applying effects! - [Saving and exporting projects](https://support.audacityteam.org/basics/saving-and-exporting-projects.md): There are two ways to get your work out of Audacity: Saving the project, and exporting audio. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.audacityteam.org/basics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.