{"id":526,"date":"1999-05-19T00:00:00","date_gmt":"1999-05-19T00:00:00","guid":{"rendered":"http:\/\/www.sweetwater.com\/sweetcare\/?p=526"},"modified":"2007-04-27T00:00:00","modified_gmt":"2007-04-27T00:00:00","slug":"those-extra-patches-old-proteus-modules-sequencer","status":"publish","type":"articles","link":"https:\/\/www.sweetwater.com\/sweetcare\/articles\/those-extra-patches-old-proteus-modules-sequencer\/","title":{"rendered":"Getting to those extra patches in old Proteus modules from your sequencer."},"content":{"rendered":"

Old EMU modules had tons of great patches in them, and they defined what have since become many of the standard features in multi-timbral modules. But there have also been recent developments that make us wish for more when we use them. For example, they never had bank select commands as this inSync reader is finding out: “I want to automate patch select on an old EMU Proteus Vintage Keys module using Opcode Studio Vision Pro. It only lets you access patches 0-127 and there are over 300 sounds. There is a patch map, but to access anything above 127 you have to stuff anything between 128-300 into one of the other positions from 0-127. Is there a way to automate this or to get to all the patches at will?”The old Proteus modules do not support Bank Select messages so you will be limited to 128 patches using the Patch Maps. You could set up per MIDI channel on the module the program, volume, and panning for that channel and then transmit it via Sysex to your sequencer. When you send this back to the module it will reconfigure it. This is a far cry from being truly automated, but it does at least allow you a way to call up specific sounds for each sequence without having to intervene and build a new patch map each time.<\/p>\n","protected":false},"featured_media":0,"template":"","categories":[],"tags":[34253,34793],"storecat":[],"itemids":[],"manufacturers":[],"acf":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n