Vanguard on Receptor

Locked New Topic
RELATED
PRODUCTS

Post

Anybody here sucessfully using reFX Vanguard on Receptor? I'm finding the implementation poor at best. I can rarely use it on more than one channel at a time and any attempts to instanciate more than one will often result in no sound coming from any of the Vanguards. Rebuilding the plugin chance has no effect on this.

I really like this plug and have lots of banks for it so it's a shame the functionality doesn't appear to be up to scratch on Receptor.

Post

Hi Simon,

I use Vanguard all the time and although it is a resource hog it works fine on my Receptor. How much RAM does your Receptor have? Are you running other plug-ins at the same time?

Best
Chris

Post

I have the latest Receptor Pro (2Gb RAM) - surely more than enough! The problems only occur when I have Vanguard on channel one and then try to insert on two or higher: the second instance won't receive any MIDI or make any sound and, in some cases, also stops the channel one VG from working. As soon as I insert another instrument on the second channel (instead of VG) then I get MIDI reception (channel light flashes) and the instrument sounds so the problem appears to be with Vanguard's reaction to Receptor. I've tried re-installing but the problem persists.

Post

Hi boomboyz, the receptor patch that you are using with vanguard, is it loaded from boot up? If it is, try loading a blank patch and then reloading the patch with vanguard inserted. I have had a similar problem with piano sounds on Kontakt 2.2. The problem only happens when I boot up the box with the receptor patch that has the kontakt 2.2 piano sound. I normally have to load a different receptor patch and then reload the patch. It works after this.

Post

Thanks philosorhymes, that's certainly helped. I found that if I shut down Receptor with an empty multi (so that it booted up with a blank canvass) I could insert multiple Vanguards. Problem solved!

Post

Glad that helped boomboyz, I've had this problem for a while now, perhaps you could report it to muse as well. Looks like there will not be a fix for this kind of problem until the new software version is released.

Post

The word from Muse is that it will be fixed in v1.6 (due May).

Post

Well untill then I guess we'll just have to grit our teeth and bare it. It has caused me quite some headache, I always use this particular setup of mine and normally I shut down in a hurry or Receptor crashes and shuts down. This means the patch I was last using will load on next boot up, which is the patch with the piano sound. So I wait for that to load then unload it and then load it again. Not great eh! It's a hot issue for me. I need to probably find something else to use for my pianos.

Post

boomboyz wrote:The word from Muse is that it will be fixed in v1.6 (due May).
I have experienced similar 'non-start' issues with plug-ins. I have noticed that my problems are only related to plug-ins I have purchased [that were originally pre-installed demos that I liked], namely Z3ta+ and Beast. It has put me off buying any more plug-ins in the meantime.

When you say the problems will be fixed in v1.6, do you mean this start problem with plug-ins generally, or just Vanguard?
Rudy G

Post

I can't answer for Muse, but it appears thazt it corrects a number of small issues (not small to us users, but small compared to the whole box crashing, or accepting Synchrosoft dongles...) Should be out real soon.
Dasher
The Soundsmith
It's all about the music. I keep telling myself that...

Post

Since loading v1.6 most of my problems with plug-ins not starting have gone...except reFX plug-ins, namely Beast and Claw. These often fail to emit any sound as part of a bunch of patches I have in each 'song' on Receptor. I had not notied this earlier but returning to som older song patches, the problem is still there with my reFX plug-ins.
Rudy G

Locked

Return to “Muse Research and Development”