While working on my project, I noticed some strange behavior — certain pipelines disappeared or were displaced without any action on my part. It felt almost like the effect of a virus or some form of corruption. To be on the
D04_m7ths extra_7.5.25.mhp (2.6 KB)
safe side, I saved the project immediately. However, when I tried to reopen it later, it failed to open entirely. Unfortunately, I’ve now lost access to the project completely.
Attached the corrupted project. I’m running th latest Editor update.
Why would this happen??
This is a significant issue, and I’d appreciate any help in recovering the project or identifying what might have caused this.
Hi, it’s difficult to say what went wrong, seems like something extraordinary. We haven’t had any reports of a similar issue for a very long time.
I can make sense of the first 12 pipeline rows in your preset, the rest of them stop making logical sense.
Do you have any previous backups of your preset, or have it stored in the device memory?
Can you recall what were your last modifications in the preset before the issue occurred or did you manipulate some mapped parameters on some particular pipes?
Hi,
thanks for getting back. Yes, they stop making sense the moment the editor started to malfunction. Some pipelines got changed into others and displaced automatically. No, I didn’t have a backup of the very project I was working on. It happened while working, so even before I could make a backup or store it. It happened several times before, only now I thought I should flag.
I am not sure what actions I was doing specifically, other than changing some parameters on an LFO via laptop keyboard. There were some mapped pipelines in the same row I was working on, yes.
Is there any way to open the project after getting the error message? Or is it lost for good?
Hi, this is what I was able to recover:
D04_m7ths extra_7.5.25_fix.mhp (2.6 KB)
The 13th line is the most suspicious one, but hopefully it’s not far from what you had before.
To fix the issue for good, as you seem to be able to reproduce it relatively often, please be very mindful of what are the steps you are doing, and immediately write that down with as much details as possible to your notes (together with any background info that could be relevant, like if you had MIDI CCs or other messages flowing through Midihub at the time that are mapped to some params, and which ones) and share with us, we’re very interested in getting such extreme issues properly fixed.
Also, whenever such corruption issue occurs, always do a ‘save as’ and write to a new file, don’t overwrite what you had previously saved.
2 Likes
