# Performance The software itself is around 9mb, and when running during a VJ performance and in use, it is currently requiring around 15-25mb RAM (yes, megabytes). So generally speaking, it's not getting in the way.\ \ Bugs are likely in these early stages though.\ \ MIDI Mimic is currently in alpha. Here's what to be aware of: **Platform:** * Windows 11 only. macOS support will come if this turns into a hit :fingers\_crossed: **Address Collisions:** * There's no clean way to be able to find out which addresses your device is already configured to output without interacting with all the controls, manually getting the exact correct next address:\ \&#xNAN;*\*i'll not be adding support to import mapping files from device softwares, as it'll be inconsistent which ones I can actually do something with\** * However! The easiest fix for this is to simply [toggle-off](/midi-mimic/settings.md#automapping) the channels your device uses, in the device settings in Mimic. * Note that any input that becomes a Macro is part of the list Mimic knows about too, there's no need to assign Macros just to 'teach' Mimic about those inputs. **SysEx and other message:** * This really comes down to the manufacturers and what information they make available to the public. [Support for the AKAI LPD8](/midi-mimic/midi-feedback.md#sysex) is in place, if you have one of those, you can now send Resolume's MIDI Out and get colours back. **Debug Logging:** * A debug log file (`routing_debug.log`) is written to `%APPDATA%\MIDIMimic\` during alpha. This helps me diagnose issues but may have a minor performance impact under very high MIDI throughput, though it does store only 20s worth at a time. It will be removed in the alpha release. **Crash Reporting:** * BugSplat is included for silent, automatic crash reporting. If the app crashes, a report is sent to help me fix it. No personal data is collected. --- # 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/performance.md?ask= ``` 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.