> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/francais/systemes-and-emulateurs/supported-game-systems/autres/karaoke.md).
# Karaoke
Karaoké
{% embed url="" %}
## Information
| |
|---|
| Émulateurs | |
| Dossier des jeux | 📂 roms \ 📂 karaoke |
| Extensions | .cdg |
## Bios Information
Aucun BIOS nécessaire.
## Contrôles
| Retrobat | PocketCDG |
|---|
| START | Start |
| SELECT | Pause |
| D-PAD | D-PAD |
| Stick analogique gauche | |
| Stick analogique droit | |
 | Gauche |
 | Bas |
 | Droite |
 | Haut |
| L1 | |
| R1 | Extinction |
| L2 | |
| R2 | |
| L3 | |
| R3 | |
## Information spécifique au système
### Organisation des fichiers
Vous pouvez créer des sous-dossiers, ou bien directement ajouter les fichiers avec les extensions `.mp3` et `.cdg` dans le dossier `\roms\karaoke`. Le core PocketCDG chargera n'importe quelle combinaison de fichiers MP3+CDG, a partir du moment ou les deux fichiers possèdent le même nom. Les paroles apparaitront à l'écran comme un vrai karaoké, et les paroles seront mis en surbrillance en même temps que le texte sera chanté.
---
# 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://wiki.retrobat.org/francais/systemes-and-emulateurs/supported-game-systems/autres/karaoke.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.