Receptor 2 crash on stage!! Anyone had this happen??

[Rick@MuseResearch]

Ron,

What is your support ticket number?

Rick

[reinski]

It's 4596

[OpenDoerr]

Thanks Rick. Just so you know, the crashes didn't occur during patch changes. It's always when I'm playing Ivory in the middle of a tune. It's not a CPU overload issue either, being I'm never over 20 or 25%. The weird thing is that the GEQ-7 isn't a part of the patches that have crashed. I just bought and registered my GEQ-7 last night so maybe that'll fix the problem. Could you tell me how to send my System Log to Plugorama? I selected it from my Receptor drive to include in my support ticket to Plugorama, but it won't let me do it. Like I mentioned, I browsed through the log a little and did see mention of the missing GEQ-7 a few times around when it went down.
Thanks,
Ron

Whenever I've had a Receptor crash (version 1.7). It's been related to sample based patches that are very large (e.g. Kontakt 3 using multiiple VSL intruments to create a full string section) that is sharing resources with other plugs in a Multi. The CPU meter may only be hovering around 40-50 when it's idle, but try laying your arm on the keys and watch the Receptor go to it's knees. You really have to put your patches through heavy testing before taking them live. Try to break them at home first. Things might seem cool at home when you're setting up, but if you get to a spot in your live set where your polyphony is going up (bigger chords, faster runs, sustain pedal down for a while) you could easily choke the throughput from the hard disk to the RAM.
It may not be CPU overload, but with samples, it's about RAM and Hard Disk activity.

I haven't used Ivory personally, but from what I've heard, all that amazing realism comes at a heavy resource price. I would suggest structuring your Multi's and patches such that you can have a Multi dedicated to one instance of Ivory alone. Use another Multi for your other plugs. Once you feel like you've achieved stability with an Ivory-only Multi, then start adding back other plugs until you hit a breaking point. Again, make sure to put the Multi through the ringer each time you add a plug. Don't be nice to it. Lay your arm on the keys, hold the pedal down while doing a gliss. Obviously this isn't stuff you would do live, but hey, that's why car manufacturers do all these ridiculous stress-tests on their cars before they put them on the road with people in them.

This is one of the reasons why software instruments can progress faster that hardware instruments. Hardware manufacturers are forced to limit the capabilities of their instruments to the lowest common denominator of what they can guarantee will work every time. That puts a lower ceiling on creative potential, but it also limits the stress of wondering if your instrument is going to quit the gig in the middle of a song.

Receptor is a great tool, but it puts a level of responsibility back on us. We don't have an instrument with a 'governor' programmed in. We get to choose what to do with it. Choose wisely.

OD

[reinski]

Thanks for your insight OD. Just so you know, when my crashes occurred I was using only playing one plug in - Ivory. I did however have 2 more Ivory instantiations on the snapshot which were bypassed, so they weren't taxing the CPU. At least it doesn't appear to. I also had 5 or 6 instantiations of B4 II on this snapshot, which are all bypassed as well. I only use one plug in at a time. My CPU meter never goes above 25%. Also, when the crashes occurred I wasn't banging a lot of notes out or playing much at all. It's looking more and more like some kind of bug that occurs with multiple plug in instantiations. I appreciate your suggestion about limiting my snapshot to a single Ivory instance, but when I play live I definitely need instant access to different plugins. Everything I'd read about Receptor implied it was set up for the live musician as well as for studio.
Thanks again,
RR

[Rick@MuseResearch]

Ron,

Just a note that we are helping you resolve this through your support ticket.

[gustavokch]

Thanks for your insight OD. Just so you know, when my crashes occurred I was using only playing one plug in - Ivory. I did however have 2 more Ivory instantiations on the snapshot which were bypassed, so they weren't taxing the CPU. At least it doesn't appear to. I also had 5 or 6 instantiations of B4 II on this snapshot, which are all bypassed as well. I only use one plug in at a time. My CPU meter never goes above 25%. Also, when the crashes occurred I wasn't banging a lot of notes out or playing much at all. It's looking more and more like some kind of bug that occurs with multiple plug in instantiations. I appreciate your suggestion about limiting my snapshot to a single Ivory instance, but when I play live I definitely need instant access to different plugins. Everything I'd read about Receptor implied it was set up for the live musician as well as for studio.
Thanks again,
RR

I don't own Receptor or Ivory for a matter of fact, but if you had 2 bypassed instances of Ivory loaded, my guess would be that they are eating up your memory.