I just quadrupled the power of my Receptor!

Locked New Topic
RELATED
PRODUCTS

Post

Brian was kind enough to demonstrate the snapshot feature at the Namm show to me. The feature allows one to use 16 plugins with no load time between patches.

If you're not familiar with this feature, here's a brief overview:

Using snapshots allows you to load all 16 slots with plug-ins and create 128 patches that selectively turn each plug-in on and off. So patch one could have Ivory, Scarbee Rhodes, B4, Absynth Strings layered on a couple different keyboards, and then patch two could have Ivory, Atmosphere, Absynth, Pro-53, Chameleon 5000 in a massively stacked layer. Any combination of plugins can be enabled for the remaining 126 snapshots, as long as the 16 plug-ins remain in their respective slots, and there is no plug-in loading time.

I had been using Ivory, Scarbee Rhodes, two instances of Zebra, Pro-53, Chameleon, Atmosphere, and Kontakt strings on different midi channels and would layer or place them on different midi channels. Now I can leave that setting, with another eight plugs loaded but in standby mode (I forgot the muse lingo for not using processor power), switch to patch 2 through 128 and I have a brand new configuration. With different plug patches and plugins activated, I can have configurations for different songs and styles of music without waiting.

Maybe quadruple isn't the correct technical term for the increased power, but I feel like I have significantly increased the usefulness of my Receptor! This was worth the price of my Namm ticket alone.

Hopefully Muse can find some time to add this feature to the video tutorials, if it is not there already.

Thanks again, Bryan.

—Will

Post

This is not a new feature. Unfortunately, you cannot change programs within each plugin while using this feature. Therefore for example, you are stuck with the same Atmosphere patch for all of your 128 programs. In reality you have diminished the power of the Receptor by the permutation of (16 times 128). This is a very very big number!

Post

Hmmm. This is not the way it was explained to me. I understand it is not a new feature, but one new to me, and it seemed to me that you are able to change patches for each plug.

Perhaps Bryan can explain further for us.




PhilMuller wrote:This is not a new feature. Unfortunately, you cannot change programs within each plugin while using this feature. Therefore for example, you are stuck with the same Atmosphere patch for all of your 128 programs. In reality you have diminished the power of the Receptor by the permutation of (16 times 128). This is a very very big number!

Post

[quote="musiklov3r"]Hmmm. This is not the way it was explained to me. I understand it is not a new feature, but one new to me, and it seemed to me that you are able to change patches for each plug.

Perhaps Bryan can explain further for us.





[quote="PhilMuller"]This is not a new feature. Unfortunately, you cannot change programs within each plugin while using this feature. Therefore for example, you are stuck with the same Atmosphere patch for all of your 128 programs. In reality you have diminished the power of the Receptor by the permutation of (16 times 128). This is a very very big number![/quote][/quote]

Hi guys

Well, you're both right. Will says that you can change patches of plug-ins in a snapshot, and that is true (it was a new feature added in 1.6). But Phil is also right that you are, from a preset perspective, limited to the plug-in presets you used when you created the snapshot bank. Ideally, snapshots would have arbitrarily savable presets so that you could have, say B4II loaded into a snapshot, and each of the 128 presets in the Snapshot would be unique in the sense that you could select different source presets for B4II for each of the snapshot presets. That feature is coming in a future software update.

In the meantime, you CAN send a plug-in a preset change on any channel OTHER than the one you are using to select the Snapshot preset, which is what Will is talking about. So you could have a bunch of plug-ins loaded, and you can send program changes to each of those plug-ins individually as long as you don't send them on the channel that you have designated to receive the snapshot preset change information. So with a little programming of your controller keyboard and willingness to deal with program changes over multiple MIDI channels, you can indeed do what Will is describing. Or you can just wait for our update that has this feature, which is currently planned for the third update down the road (Direct Install, announced at NAMM, is next up for release, followed by a major update coming in late spring or early summer depending on whether we let the engineers go home and see their families over the next few months... just kidding).

One thing is true that Will points out. A LOT of people don't know about snapshots, and truth be told it is my favorite feature on Receptor. I even had the MD for Kelly Clarkson call up the week before NAMM and tell me that his Receptor was broken because the other keyboardist's Receptor is able to have a bunch of plugins loaded and he can switch between them without having to reload samples, but the MD can't do the same thing on his Receptor. That's because he was using a regular MULTI instead of a SNAPSHOT multi, so it was reloading the plug-ins (samples included) whenever the unit receives a patch change. A couple of minutes on the phone to tell him how to create a snapshot, and voila, instant access to all the plug-ins he has loaded with no switching or reloading time!

So... controversy resolved hopefully with a happy ending for all.

Cheers

Groovology

Post

So if I understand correctly, I can have:

128 snapshot patches
with a total of 16 different plugins (always on the same channel strip)
wherein each of the snapshot patches can have a different combination of active vs inactive plugins
but for each plugin all of the 128 snapshots can only have the same plugin preset

I can send preset change commands to the plugin after the snapshot loads to change presets.

Is this correct?

Thanks for the clarifications, Bryan.

—Will

Post

delete this post.

Locked

Return to “Muse Research and Development”