Compromised Pathes

Compromised Pathes
« on: September 15, 2021, 05:40:53 AM »
Hello everyone today something really unfortunate happened with my Prophet 10. I state that yesterday I installed the 2.0 os. I created and saved some patches with stacks and splits and everything went well but this morning as soon as I tried to save another one, some strange and horrible sounds came out and it compromised all the patches I previously created. I tried to do a global reset, a tuning and I reinstalled the os for safety but nothing to do. hours work was lost. has anyone had similar experiences? Thank you

LPF83

  • ***
  • 1437
Re: Compromised Pathes
« Reply #1 on: September 15, 2021, 07:50:30 AM »
Hello everyone today something really unfortunate happened with my Prophet 10. I state that yesterday I installed the 2.0 os. I created and saved some patches with stacks and splits and everything went well but this morning as soon as I tried to save another one, some strange and horrible sounds came out and it compromised all the patches I previously created. I tried to do a global reset, a tuning and I reinstalled the os for safety but nothing to do. hours work was lost. has anyone had similar experiences? Thank you

Do you mean it compromised all patches you created under 1.5.2?  If so, try going back to the old OS to see if it helps.

If you mean you spent hours of work on stack/split patches, I'd recommend holding off on large time investments until the OS stabilizes.  It introduced a lot, especially for a release that had no beta period, has known issues and fixes are coming.
Prophet 10, OB-X8m, Prophet 6, OB-6, 3rd Wave, Prophet 12m, Prophet Rev2-16, Toraiz AS-1, Pro 2, Virus TI2, Moog SlimPhatty, Hydrasynth desktop, Korg Minilogue XDm, Roland JP-8080, Roland System-8, Roland SPD-SX SE / Octapad, Maschine, Cubase/Ableton/Akai MPC

Re: Compromised Pathes
« Reply #2 on: September 15, 2021, 08:13:47 AM »
yes, unfortunately I also compromise the old patches that I had previously created with 1.5.2 not all fortunately but randomly among the various presets banks. While all the programs saved in stacked mode and in split mode have disappeared. Too bad, something nice came out of me. Tonight I try to reload the 1.5.2

Re: Compromised Pathes
« Reply #3 on: September 15, 2021, 08:39:56 AM »
And of course you made a backup before upgrade to 2.0.0.   :o

Cheers !
1976 MiniKORG700s // 1979 Prophet-5 rev.2 // 1981 KORG CX-3 // 1984 DX7 // 2020 Prophet-10 rev.4 // MoPho Box // 2 Creamware MiniMax // Creamware Pro-12 // 2 EMU-Proteus 2000 // EMU-Vintage Keys  // Casio VZ-10M // Roland VK-8M // Fatar SL 880 // Roland JUPITER-X

Re: Compromised Pathes
« Reply #4 on: September 15, 2021, 08:56:09 AM »
And of course you made a backup before upgrade to 2.0.0.   :o

Cheers !
in part, I had not saved the last things 😭 i'm thinking about buying the software editor to make it easier, you say it's worth it? will it be compatible with 2.0?

Re: Compromised Pathes
« Reply #5 on: September 15, 2021, 11:09:59 AM »
I donīt know ... I do my backups on computer (Mac) with free program "SysEx Librarian"
which also handels the upgrades perfectly.  Easy enough    :)

Cheers !
1976 MiniKORG700s // 1979 Prophet-5 rev.2 // 1981 KORG CX-3 // 1984 DX7 // 2020 Prophet-10 rev.4 // MoPho Box // 2 Creamware MiniMax // Creamware Pro-12 // 2 EMU-Proteus 2000 // EMU-Vintage Keys  // Casio VZ-10M // Roland VK-8M // Fatar SL 880 // Roland JUPITER-X

Tomasn

Re: Compromised Pathes
« Reply #6 on: November 28, 2021, 09:23:37 AM »
Hi. This happened to me just now. It happened when I replaced (recorded) a stack patch with a single patch. Can that action cause this error? Have recreated must of what was lost, and everything seems normal again.