> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/vehicles/cuxial-chipeo.md).

# Cuxial Chipeo

Car audio systems for FiveM: an installable head unit with USB sticks, equalizer, subwoofer, portable speakers and overheating.

Cuxial Chipeo adds installable car audio systems to your server ("chipeo" is Caribbean slang for a loud custom sound system in a car). A player installs the equipment in a vehicle with an item, opens the head unit and plays music from direct audio links that everyone nearby hears in sync.

## What it does

* **Installable equipment.** One item installs the system in a vehicle and another removes it and gives the equipment back. The installation is saved per plate.
* **Head unit with six tabs**: player, bass, equalizer, library, vehicle and settings. The frame can be dragged and each player keeps its position.
* **Synchronized playback.** The server keeps what is playing and where; every client nearby hears the same second of the track.
* **USB sticks.** Each stick stores a number of songs given by its capacity. The songs travel with the stick: it can be ejected, lent, used in another car or cloned onto an empty one.
* **Subwoofer and equalizer.** Bass level, cut-off frequency and punch, a six-band equalizer with styles, A/B comparison and personal presets.
* **Realistic acoustics.** 3D audio, walls that muffle the sound, and a cabin that sounds different with doors, windows, trunk or roof open.
* **Overheating.** Bass kept too high for too long fries the equipment: fire and smoke in the trunk, and volume and bass stay limited until a mechanic repairs it.
* **Cabin pressure.** A fully closed car at very high volume ends up bursting a window.
* **Portable speakers ("medusas").** A prop placed on the ground that pairs with the nearest car with equipment and repeats its music. It can be made public so others control the radio from it.
* **Vehicle controls** from the head unit: doors, windows, hood, trunk and extras.
* **Workshop repair** with a command, restricted to the jobs and materials you choose.

## Requirements

| Resource                            | Required         | Used for                                                                      |
| ----------------------------------- | ---------------- | ----------------------------------------------------------------------------- |
| OneSync                             | Yes              | The server reads vehicle positions and shares the playback state              |
| `ox_lib`                            | Yes              | Callbacks, key binding, progress bars, texts                                  |
| `oxmysql`                           | Yes              | Installations, USB sticks, songs and presets                                  |
| `cuxial_bridge`                     | Yes              | Connects to your framework, inventory and target                              |
| `ox_inventory`                      | For the items    | Using the items and reading the USB sticks                                    |
| A target supported by Cuxial Bridge | For the speakers | Opening the radio from a portable speaker, making it public and picking it up |

{% hint style="warning" %}
The items of Cuxial Chipeo require `ox_inventory`: they are used through its item exports, and each USB stick keeps its songs in the item metadata.
{% endhint %}

{% hint style="info" %}
The resource does not include the models of the portable speakers. Each speaker item points to a prop that must exist on your server. See [Installation](/scripts/vehicles/cuxial-chipeo/installation.md).
{% endhint %}

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Installation</strong></td><td>Dependencies, items, speaker props, staff permission and start order.</td><td><a href="/scripts/vehicles/cuxial-chipeo/installation.md">Installation</a></td></tr><tr><td><strong>Configuration</strong></td><td>Every option in <code>shared/config.lua</code>, block by block.</td><td><a href="/scripts/vehicles/cuxial-chipeo/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Commands, keys, items and who can do what.</td><td><a href="/scripts/vehicles/cuxial-chipeo/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Install, remove or read the equipment from your own resources.</td><td><a href="/scripts/vehicles/cuxial-chipeo/developers.md">Exports &amp; events</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and how to fix them.</td><td><a href="/scripts/vehicles/cuxial-chipeo/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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://docs.cuxial.com/scripts/vehicles/cuxial-chipeo.md?ask=<question>&goal=<user_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.