# Ω Audio Library

Sound is used to communicate with the user, provide (emotion identity style) for a brand, and improve the experience through sensory feedback. There are three primary types of sound "audio" communication… interface, musical, and voice.

<figure><img src="/files/fw8kdRoxbMoHJvdUbldt" alt=""><figcaption></figcaption></figure>

## Resources

These resources are stored in the snippets library as pieces of code that can be used across the application and referenced through the token assigned to it in the snippets library.

{% embed url="<https://storage.googleapis.com/material-design/downloads/material_product_sounds.zip>" %}

## Properties

**Name**: \[textField] The human readable way we refer to this "Sound" in the dictionary

**Type**: \[selectList(Interface, Music, Voice; Interface)] Interface, Music, Voice

**Family**: \[selectList(Assets.Sound)] The sound family that this sound is in. The list of available sound families is pulled from the Assets > Sounds folder. Those sound families that have been uploaded into the system.

**Resource**: \[searchGallary(selectedFamily)] Every sound will have a source file that it references to provide the source file for the sound

**Metaphor**: \[textField] Every sound acts as a metaphor for something. Some sounds can carry multiple metaphors (i.e. "success" and "win" for a positive result) This allows us to reuse these sound metaphors as a design token which is referenced throughout our components while all referencing the same file.

**Token**: \[textField] The short-code we use to refer to this metaphor (i.e.. #audWin, #audAdd, #audWarn, etc.)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://able.bucca.com/overview/styles/audio.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.