# SNES Audio Tinkering

The BSNES Core in Bizhawk can let you mess with the internals of the emulated SPC700 chip. Technically, all engine templates can give you interesting results when blasting to the **APURAM** domain alone.

There are a few particular effects that you can obtain via certain workflows. These effects, when obtained, can be sanitized and merged with other effects. Here's some examples:

**Vector engine with SPC700 lists** : Targeting the APURAM with \[SPC700]\_NOP as the Limiter and \[SPC700]\_GIGA as the Value is an easy way to get audio corruptions. These list can be found in the Package Downloader as SPC700\_Basic\_by\_BLiNX\_Person.

**Distortion Engine with Auto-Corrupt on APURAM** : The Distortion engine will always corrupt addresses using values that did previously exist in the past. This will cause things that previously happened to come back later. This will most likely desync the song tracks. Instrument changes may revert back to previous instruments.

**Pipe Engine on APURAM** : Pipe Engine on APURAM (only) with 100 Intensity and 100 Max Infinite Units is a good setup to mess up the audio rendering. Using the Glitch Harvester, you can easily Corrupt over and over to obtain particular music corruptions. The secret to this technique is that you can end up piping legal values from an address to another that cause the audio to mess up while staying stable.


---

# 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://corrupt.wiki/systems/snes/snes-audio-tinkering.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.