Troubleshooting

MIDI

Hot off the presses! Don't run MIDI-OX when using Wavysn. So far I can't get the data to flow in both directions when doing that, and two-way flow is needed for SYSEX to work.

If you get MIDI errors, verify your input and output ports with another app, like MIDI-OX.

You can also run into problems if the MOD Wheel is not on zero ('off'). The Mirage sends the modulation value over MIDI non-stop and this floods Wavsyn with so much data it won't work right. If you see weird behavior or just no response, zero the MOD Wheel and try again.

Mirage OS

The Wavsyn Editor will not work unless the Mirage Advanced Sampling Operating System (MASOS V2) is loaded in the Mirage.

Disk Errors

If you cannot save to a floppy and the Mirage display says 'pd', that means the disk is protected.

Values not reflecting what is on Mirage

This can happen if you make changes on the Mirage while using Wavsyn. In this case, save your work on the Mirage, then reload a sound into Wavysn to get everything back in sync. For parameter changes covered by Wavsyn, just make changes using Wavsyn or it will get out of sync again.

HFE batch conversion

In order for hfe conversion to work, the HXCFloppy Emulator must be installed AND the hxcfe executable must be on your path environment variable (you need to add it yourself). To test if this is set up correctly, open a command window and type 'hxcfe'. If on the path, this will cause usage instructions to be displayed. The hxcfe.exe file is in the folder where the software is installed (like \HxCFloppyEmulator_soft\HxCFloppyEmulator_Software\Windows).

Logs

Running a process creates logs. These show up in the UI, but are also logged automatically using the electron-log node module. It logs to:

• on Linux: ~/.config/{app name}/logs/{process type}.log
• on macOS: ~/Library/Logs/{app name}/{process type}.log
• on Windows: %USERPROFILE%\AppData\Roaming{app name}\logs{process type}.log

For example, on Windows my main process log is here: C:\Users\eizde\AppData\Roaming\wavsyn\logs\main.log. Each run of a process appends to the log and will will start with a line that looks like this: [2021-06-29 09:27:09.440] [info] (user)