Maybe I should have mentioned this a long time ago when I first noticed, but wanted to experiment further to nail down the details. In short, while the factory presets supplied online can be transferred successfully into the Mono, user projects and also the working factory presets do not make the round trip from Mono to PC to Mono intact.
User projects saved on PC and then loaded into an empty project location appear to retain the patterns, but all the patches (sounds) are the same, possibly an init patch. The factory project doesn’t transfer with the recommended app; I get an “Invalid SysEx File” pop-up box with the error message, “F0 and F7 pairs not matched up.”
Further info: PC is a Windows 10 system, and the Mono has been on V1.2.3 for many months. To transfer to the Mono, the recommended MS MIDI SysEx File Transfer Utility can be used. Evidently, this app only functions unidirectionally, so for going the other direction I’ve had to use MIDI-Ox, and with that program, most, but not all, patterns from the factory set were transferred back to the Mono, but not accurately. Based on these behaviors, with the manufacturer supplied file being received OK, but not others, it seems there may be a problem with data being sent from the Mono, because even the same supplied preset file is affected then. Upon being received by the PC during the backup, using MIDI-Ox, no errors are displayed.
While it wouldn’t be a huge tragedy if my user patterns don’t survive an upgrade to the new firmware, there are some I’d like to retain if possible. Can anyone else comment on successes or failures backing up and restoring projects, and offer any suggestions? It would be good to know if this is down to user error, a defective unit or software, or if it’s a common thing.