mid files into ProphetVS-V - it can only import WAV files, truncated to 128 samples of 12-bit words. While you can dump the User Waves from the hardware via MIDI, there is no way to import those. So if you have patches that use waves 0-31, they will not sound correct when imported into ProphetVS-V. syx files created by dumping patches from the hardware, it DOES NOT manage dependencies between those patches and the User Waves in the VS hardware. syx files using the trusty and crusty SysExLibrarian software, which is freeware, runs on Monterey, and is available here:Īlthough ProphetVS-V does import. syx " and fortunately I never throw away a file, so I had those files right at hand. You MUST have the dumps from the hardware in a file with the suffix ". Or however far back the versions on my Yosemite boot drive clone were.īut. Other than using an ancient boot drive of course. ![]() ![]() And since Prophet-V (the old dual-engine version) has now been deprecated and is no longer for sale, there's no way to get those old banks to play. prox " exported banks do not import into the current ProphetVS-V. provbank " were Prophet-V banks from an even earlier version? Dunno.Īnd guess what? Yup. ![]() prox", so maybe those other files with the suffix ". I tried using Export Bank for those, and it created files with the suffix ". They sounded like they're supposed to (which is to say, basically correct but nowhere near as lively and juicy as the hardware). I was able to launch that version of Prophet-V and lo and behold - there were all my NIN patches converted from the SysEx files I had dumped from my hardware units. I kinda don't think that they would care what I think.Īnyway, I just tried booting from my older Yosemite boot drive clone, and it had Logic v10.2.4 and Prophet-V v3.3.1 on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |