To take advantage of the five dimensions of touch, all products use MPE – MIDI Polyphonic Expression. Modified on: Mon, 20 Mar, 2023 at 12:42 PMĪll products in the ROLI family - GRAND, RISE, BLOCKS, and LUMI - send standard MIDI messages and can be used with any software or hardware instrument that responds to these messages.
Now I'm scared to open past projects as I dont know if they will actually load correctly! I rely on patch recall for my work, and will often edit presets to fit my work but not actually resave them as new patches while I'm working as I'm unsure if they will be tweaked more, so if these come up as blank I will have no clue what patch was used, or what was tweaked!! Any help would be greatly appreciated.Solution home Using with Third Party Products General Compatible synths, DAWs and instruments But for sure a song I worked on last night and saved comes up blank today and I've lost all my loaded patches. I've tried both coupled and decoupled and I cant get it to consistently load up blank. I've tried running some tests but so far it doesn't seem to be consistent behavior.
Either way I ALWAYS save my VE pro metaframes, however even when I load these on their own, my latest Omnisphere instances are coming up blank. I have always run Omnisphere inside Vienna Ensemble Pro, and sometimes run it in coupled mode and sometimes run it decoupled. I recently updated Omni to v 2.3.2h(v) and now when I reload a song that had patches loaded in VE pro coupled to Cubase 8.5, my omnisphere instances are showing up completely blank! The multi says "empty" (not default as usual) and each omnisphere instance that had a patch is now completely blank!! Talk about frustrating! I thought having them coupled meant that this information is stored with my cubase project?! Before I updated omnisphere everything worked fine and patches were recalled no problem.
0 kommentar(er)
