I have a couple of different takes on snapshots; one on preparing for a show and one for jobbing dates.
In loading up a complete set of samples and patches for a show that is performed the same way each performance Snapshots are great. One you get the hang of it you can prepare patches rather quickly. With all of the samples in RAM changes are almost instantaneous.
When preparing for a jobbing date where you must change sounds several times in the midst of a set, Snapshots (ver1.6) gets you halfway there.
It is great to be able to change patches and therefore mixer settings on an independant MIDI channel but when you access the plug-ins directly (on any other MIDI channel), you can only access the factory patches. Yikes! Most of them are unusable for jobbing.
So if the ability to access user edits of plug-in patches is about 3 releases down the road (from what I gleaned from other posts) it looks like we are in for a rather long wait. Too bad because this would go a long way to making the Receptor a viable jobbing module.
It still means a lot of programming from your keyboard controller, control face or synth. I use a Kurzweil PC2X and that allow more MIDI manipulation than most. Can't imagine doing it on some of the toys that are passed off as Master Controllers today.
The Good Doctor
Snapshots (ver1.6 style)
-
The Good Doctor The Good Doctor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=103791
- KVRer
- 15 posts since 5 Apr, 2006
-
- KVRist
- 82 posts since 15 Apr, 2007
While I agree it would be great to be able to do this through the Muse operating system, it is possible to do what you want with some plug-ins now.
First, it seems to me that what you want to do is load a vst instrument as part of a snapshot and then change patches on that individual vst, and be able to select your own edited patches rather than the factory presets. I have been doing this with several VSTis. However I have been sticking to those that don't rely on samples so that there is no issue with sample loading time. (This is important because I have found that sending a patch change to Receptor while Kontakt is loading a sample can cause a crash.)
The way to do this is to set the Receptor to receive program change messages on only one channel, and then set it to send patch changes on other channels directly to the VSTi. Once you do this, you can change patches on any VSTi that responds to midi patch change messages. This works great with some VSTis like B4II and Pro53. It doesn't seem to work at all with others, like Atmosphere or Minimonsta.(If I'm wrong on this, somebody please correct me.)
Of course, what you want is to access your own user patches, not the factory patches. To do this, you must make your edited sound bank the default patch bank that the VSTi accesses. How to do this will be specific to the VSTi you are using. The Pro53 automatically loads the bank called "def.p5a" in the presets directory, while the B4II loads the bank called "def.b4a" in its presets directory. So, for these synths, after you have edited a sound bank, you just save it to the presets directory with this name. (You may want to save the original factory presets with a different name first.)
While I don't think Minimonsta can receive patch change messages, you can work around this by storing up to 12 patches you want to use as Melohman morphs. I haven't yet gotten to puzzling out other synths like Massive, Absynth, FM8, Z3ta, etc., so if anybody knows how to do this on these or other synths, please help us out.
K.
First, it seems to me that what you want to do is load a vst instrument as part of a snapshot and then change patches on that individual vst, and be able to select your own edited patches rather than the factory presets. I have been doing this with several VSTis. However I have been sticking to those that don't rely on samples so that there is no issue with sample loading time. (This is important because I have found that sending a patch change to Receptor while Kontakt is loading a sample can cause a crash.)
The way to do this is to set the Receptor to receive program change messages on only one channel, and then set it to send patch changes on other channels directly to the VSTi. Once you do this, you can change patches on any VSTi that responds to midi patch change messages. This works great with some VSTis like B4II and Pro53. It doesn't seem to work at all with others, like Atmosphere or Minimonsta.(If I'm wrong on this, somebody please correct me.)
Of course, what you want is to access your own user patches, not the factory patches. To do this, you must make your edited sound bank the default patch bank that the VSTi accesses. How to do this will be specific to the VSTi you are using. The Pro53 automatically loads the bank called "def.p5a" in the presets directory, while the B4II loads the bank called "def.b4a" in its presets directory. So, for these synths, after you have edited a sound bank, you just save it to the presets directory with this name. (You may want to save the original factory presets with a different name first.)
While I don't think Minimonsta can receive patch change messages, you can work around this by storing up to 12 patches you want to use as Melohman morphs. I haven't yet gotten to puzzling out other synths like Massive, Absynth, FM8, Z3ta, etc., so if anybody knows how to do this on these or other synths, please help us out.
K.