Snapshots vs Multis vs ???

[thesoundsmith]

The new snapshot feature is probably beneficial to some users, and the performance multi, once I understood it, gave us other conceptual options in setting up multiple synths for live use.

But with the eventual elimination of the Multi comes additional questions, especially as the who;e concept of the snapshot assumes you are only changing one instrument's patches during performance. I use two manuals, and will frequently change the lower to, for example, one of seven Rhodes/Wurli electric pianos, or if playing organ, change from lower to upper manual with midi channel change, then on upper manual, change presets - many times during the course of a song. If I change patch using the snapshot, it resets all of my other manual changes, which is totally unusable to work with the way I play.

So if anyone else has this issue, please reply here, that Muse can see the value of an old and trusted process... Or if you have a better idea? (I'm still waiting for the individual channel on/off and ccs on/off per slot, that would greatly facilitate some really complex setups. )

[JayVee]

Are you suggesting that Muse is eliminating, or planning to eliminate, their Multi system?

That would totally piss me off; I can't use their Snapshot method for the way I perform...

Please clarify

[Hybernation]

Are you suggesting that Muse is eliminating, or planning to eliminate, their Multi system?

From the Release Notes for 1.6:

Removed Feature:

* Performance Multis: Receptor v1.6 removes the Performance Multis feature, which has been made redundant by recent Receptor software advances. Prior to the implementation of Zload and Snapshot Banks, Receptor offered Performance Multis as a "work around" to slow patch loads whenever they required multiple plugin instantiations. In v1.6, some background coding that allowed this feature to work has been modified, greatly improving Receptor's plugin compatibility, performance and functionality. As a consequence, support for Performance Multis has been removed in v1.6 and, in reality, there is now no need for them, since their benefits have been completely superseded by the Zload feature (introduced in v1.2) and Snapshot Banks (introduced in v1.5).

I don't use Receptor live, though I do have some "multi's" I use as song templates. Presumably, I can use snapshots instead? I have NEVER messed with Snapshots at all...

Anyway, does THIS new feature help you live dudes? (Soundsmith?)

Send MIDI Program Changes Directly to Plugins: Receptor will now allow you to send MIDI program changes directly to Source plugins, completely bypassing Receptor's own, internal patch management feature. This is particularly useful, for example, when you load a plugin that does not yet contain any "Receptorized" patches-only its own, internal patches. By using this feature, you can tell Receptor to pass the MIDI program change information directly to the plugin rather than using Receptor's own methodology for managing Multi, Single, and Plugin patches.

Full release notes here

[JayVee]

O.M.G.
This changes everything.
I'll have to speak to someone at Muse.

: (

[thesoundsmith]

This changes little for me at the moment, Hn. It would have when I was first creating my Performance Multis and installing new VSTis, but not now. I need the Multi concept until the OS allows individual channel remapping (e.g., Lounge Lizard receives in ONE slot midi from channels 3, 4, 5 and 11 and sends to LL on ch 1, Colossus receives on channels 2,7,10 and 12 and sends its ccs and patch changes directly to those individual channels (like it is now with ALL and THRU selected, except also can refuse midi on some channels)

I constantly am working with controls, pedals, keys and patch changes on separate keyboards - I may start a Rhodes solo on a mellow patch, then switch to one with more bite, then add a flanger, then a high distortion barking Rhodes for the climax - while I'm accenting with Hammond on top, also changing patches at different times.

I have to add that I have now converted some of my most-used multis into a new Snapshot Bank, and so far, I'm not sure if it matters; as long as I don't switch presets on the Receptor control channel, what I do has not changed and the patches work as before. BUT the panel says MULTI, not SNAP as the docs led me to believe it would - the color is different, but the labeling still looks like MULTI - if this is normal, then I think I'm safe, but I don't know if this is a bug or my misunderstanding...

[JayVee]

The nature of my live work includes 5 different shows, with very few duplicate Multis...

I have a separate Bank for each show, and 25 to 35 different Multis in each Bank.
I never thought Snapshots would work for me, and I'm still wondering how they will.
I may have to totally change the way I operate.

Can anyone easily explain if, and or how, I'll make a smooth transition to 1.6?

[JayVee]

The nature of my live work includes 5 different shows, with very few duplicate Multis...

I have a separate Bank for each show, and 25 to 35 different Multis in each Bank.
I never thought Snapshots would work for me, and I'm still wondering how they will.
I may have to totally change the way I operate.

Can anyone easily explain if, and or how, I'll make a smooth transition to 1.6?

[c3boy]

I love Snapshot mode, but I use receptor to load up a snapshot bank of Scarbee Rhodes and Clavinet 16bit DFD (using Hybernations screen print settings) then I have at least 80 odd percent left on my memory! Works amazing. Whereas before I would run out of memory first rather than CPU load, but now I can bang more stuff into my snapshot, and mute the channels i don't need for that song. For me it's great, for me though, I realise others operate differently.

[JayVee]

Is there anyone here that uses their Receptor similar to how I've described I do?

[thesoundsmith]

Well, I just put in a ticket to Muse - I was setting up my rig to set the EQ and levels for a new set of live monitors, but when I went to lad a second, totally different snapshot, all I got was the same plugs in the same sockets - and this is TOTALLY different than the preset snapshot I had saved only minutes before. So while the internal part of the snapshot works fine for me, they will not load properly (or at least as I need them to.)

Stay tuned...

[thesoundsmith]

OK, here's what I got from Rick at Muse - converting a multi to a snapshot, EACH MULTI needs its own Bank, as any patch changes take place inside that bank. So:

Open a multi. Tell it to SAVE - create a new snapshot bank, name it like the patch. THEN save the snapshot INTO the bank. Then got back to your multis and load a different multi, save it to a DIFFERENT Snapshot bank. (Any patch changes done inside the snapshot are not being addressed by this post, I have to see if that will work....)

But I'm making slow progress in determining if this will be an issue.

And it still will be-I have a couple hundred multis, created according to several factors - some of which include which venue I'm playing, I have EQ adjusted for the specific room. Also according to which band or concept - R&B band, jaxx gig, rmx/groove session. ethnic orchestral setups, etc. Each of these has multiple patches (now to be snapshots) that previously were stored in a Bank (ok, R&B gig, this folder) that is now missing, the snapshot-single setup is the top layer. This needs to be addressed - and I don't yet know if I can issue a patch change on my upper manual B4 that won't revert back to the lower manual piano patch that was part of the initial setup but in the course of the song has changed several times.

[JayVee]

I too have a few hundred Multis.
I'm assuming I must convert everything to Snapshots, before moving to the 1.6 OS
(please confirm again)

I'm actually too busy to concern myself with this right now, but I anticipate this will be a significant problem; I don't recall exactly why Snapshots (when they were 1st introduced) wouldn't work for me...
I guess I'll find out in the near future

[thesoundsmith]

You don't need to convert if update (and at this point I don't know if you ACTUALLY need to do so now, my multis work fine under this build of 1.6 I didn't read the notice till after I had done a couple gigs with 1.6 and multis...

[gregh1]

My take on this is that they're eliminating Performance Multis ONLY - not Multis in general. Performance Multis are an optimization to provide quicker switching, which is what zload provides now. The 1.6 release notes are worth reading - several times...

And the new feature "Route All Other Channels to Source Plugin" will allow you to load your favorite collection of plugins as a multi, then switch patches inside each plugin with MIDI program changes on the matching channel. Combine that with snapshots to save CPU cycles for the inactive plugins. Changing snaphots (within the snaphot bank) will not reset the plugin states, it will only change the Receptor mixer settings, so each plugin will "remember" the last preset you requested via MIDI program change on its channel.

Example: on Receptor's SETUP page, select "Use Bank Select", "Use Channel: 16", and check "Route All Other Channels to Source Plugin". Now Receptor will respond to program changes on MIDI channel 16 to switch the entire state of Receptor. Use that to load a snapshot bank for the gig, and also to switch snapshot patches within the bank during the gig. Individual plugins will respond to MIDI program changes on MIDI channels 1 to 15. And you can still rely on the feature that only permits MIDI program changes to get through to the plugins if the MIDI channel matches Receptor's mixer channel number.

[orpheus69]

deleted post