# Resolume MIDI XML Helper

## What is it?

{% hint style="warning" %}
Video slightly out-of-date, this tool is now found in Documents/MIDI Mimic/Tools/
{% endhint %}

{% embed url="<https://youtu.be/uf_HPLOeBm4>" %}

Switching to MIDI Mimic means the devices you're outputting from are now named "mmDevice", which technically breaks any saved mapping you've got in Resolume, if that mapping is linked to the device and not just the address.\
\
This helper tool takes the work out of migrating all those maps, simply create a lightweight reference XML in Resolume and combine it with your main XML in the helper, you'll get a duplicated XML that tells Resolume to look at Mimic's devices instead.\
\
Same addresses, same controls, new source.<br>

<figure><img src="/files/YlJo9HB7SJg2o3MHqAd5" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
It isn't fully automated, unfortunately you do have to go through a few steps, but the whole thing can be done in under 5 minutes.
{% endhint %}

### How it works

The Resolume MIDI Renamer is a lightweight browser-based tool bundled with MIDI Mimic.

{% hint style="success" %}
**Nothing is uploaded to any server.** It just parses a file, shows you the devices for confirmation, does a rename and gives you a new file. **Your original file remains untouched.**
{% endhint %}

{% stepper %}
{% step %}

### Step 1: Create A Reference XML

1. Connect all your devices, launch Mimic and then launch Resolume and make sure you're listening to Mimic's virtual outputs.

   <div align="left"><figure><img src="/files/FOQA0QRLxlhZK2l5BEXz" alt="" width="116"><figcaption></figcaption></figure></div>
2. Enter the MIDI shortcuts mode (CTRL+M) and create a new MIDI mapping file, name it whatever you like, it's disposable, I called mine mmConfig.

   <div align="left"><figure><img src="/files/PPHgi9PaY5tFXQa7yOq2" alt=""><figcaption></figcaption></figure></div>
3. Map 1 control to anything, from each device. Remember! If you're using MIDI Out as well, you'll need to set that up, as different Ports come with different IDs

   <div align="left"><figure><img src="/files/FMylWvEa8hgz6QGZNgDN" alt="" width="172"><figcaption></figcaption></figure></div>
4. Save and Quit Resolume
   {% endstep %}

{% step %}

### Step 2: Add your XMLs to the helper.

1. Go to Program Files/MIDI Mimic/tools and open the helper, it will run in your browser but it doesn't require an internet connection.
2. You'll be asked to import your <mark style="color:blue;">original</mark> XML first, this is the one you've spent all that time on.<br>

   <figure><img src="/files/NSVkrcIpPIOCk2NjAdQA" alt="" width="563"><figcaption></figcaption></figure>
3. Import the newly created <mark style="color:$danger;">reference</mark> XML next.<br>

   <figure><img src="/files/6Ho52C5YBMRQFctSo3kw" alt="" width="563"><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Step 2: Review devices

1. The tool reads your XML and lists every MIDI device it finds. Each device shows a toggle and a count of how many mappings reference it.&#x20;
2. Devices that already have the `mm` prefix are shown as "already prefixed" and skipped automatically.&#x20;
3. All unprefixed devices are selected by default.
4. Any devices in your *<mark style="color:blue;">**original**</mark>* XML that are not present in your *<mark style="color:$danger;">**reference**</mark>* XML will be flagged, you may want to go back add make sure they're mapped in the reference.
5.

```
<figure><img src="/files/EnOVGCk6AqHjllatUmda" alt="" width="563"><figcaption></figcaption></figure>
```

{% endstep %}

{% step %}

### Step 3: Preview and download

1. Click **Preview Changes** to see exactly what will change (e.g. `APC 40 MK II` becomes `mmAPC 40 MK II`).&#x20;
2. When you're happy, click **Apply & Download XML** to get your renamed file. <br>
3. The output file is named with the `mm` prefix (e.g. `mmAPC 40 MK II.xml`).

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

Either save it straight to your Resolume Shortcuts folder, or put it in here afterwards:

<figure><img src="/files/BFVpozAjmFbtvViolNmZ" alt="" width="375"><figcaption></figcaption></figure>

<p align="center"><em><strong>Your original XML never gets written to, only read.</strong></em> </p>
{% endstep %}

{% step %}

### Step 4: Load new XML

In Resolume, jump back into MIDI shortcuts mode and load the newly generated "mm..." configuration and you're off. All mapping will now retain addresses and other settings but listen on the mmDevices created by Mimic.<br>

<div align="left"><figure><img src="/files/wldGbXz616vkH0yzdyKu" alt="" width="169"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

## Where to find it

The Resolume MIDI Renamer can be found here

```
Documents\MIDI Mimic\Tools\resolume-midi-renamer.html
```

## FAQ

<details>

<summary>Does this upload my files anywhere?</summary>

No. Everything runs locally in your browser. Your XML never leaves your machine.

</details>

<details>

<summary>What if some devices already have the mm prefix?</summary>

They're detected automatically and left untouched. You'll see them labelled "already prefixed" in the device list.

</details>

<details>

<summary>Can I undo the rename?</summary>

The tool never modifies your original file. It always produces a new download, so your original XML stays safe.

</details>

<details>

<summary>What if I have multiple XML files to rename?</summary>

Run each one through the tool individually.&#x20;

</details>


---

# 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://midi-mimic.gitbook.io/midi-mimic/resolume-midi-xml-helper.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.