provbank " files that I made from the SysEx dumps. And there appears to be no way to get that synth again functioning again, even though I already own it! I do have a bootable clone of an older version of my boot drive, and I'm going to check and see if it contains a version of Prophet-V that is old enough to import SysEx or at least read those ". provbank " but those don't import into the current ProphetVS-V.Īnd ya know what's truly fucked? The older Prophet-V3 (the one with the dual engines from the previous version V-Collection) is now DEAUTHORIZED on my rig. I still have the Prophet-V banks created from that SysEx, in a format with the suffix ". At one point I had all of my old VS patches in Prophet-V, and I sure as hell didn't delete them. Not like I really give a shit, because I have two hardware Prophet VS units, and I can manually rebuild the five patches that matter in a half hour, but if I ever see those French fuckers in person at some NAMM show, I'll give 'em an earful.
Vi control arturia update#
They never warned us that this would happen, they just quietly removed the feature in some update of Prophet-V, and that patch format became incompatible. Also I can't really remember which version of Prophet-V could import SysEx, and at which version it stopped being able to do so.
Vi control arturia install#
I suppose I could attempt to install that on a spare machine and see if I can get the patches back, but I can imagine that it's phone-home-ware and won't install anymore. I even have the original CD-ROMs of the very first version of Prophet-V. provbank " files won't read in the current ProphetVS-V. And there appears to be no way to get that synth functioning again, even though I already own it! I do have a bootable clone of an older version of my boot drive, and I'm going to check and see if it contains a version of Prophet-V that is old enough to import SysEx or at least read those ".
0 kommentar(er)
