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

Locked New Topic
RELATED
PRODUCTS

Post

Last night during a my first live show with my brand new Receptor 2 it crashed and rebooted on the second song. Real drag! I was set up REALLY close to the drummer, and I was wondering if vibrations from the drums (he hits hard) could have caused the crash. Incidentally I was using CPU-hungry Ivory 1.7 when it happened. Anybody had a similar experience?? It really took the proverbial wind out of my sails....
Top

Post

Reinski,

Crashes do sometimes happen, but in my experience it is pretty easy to track down the cause and take steps to prevent it from happening again. With that being said, think you could let us know what other plugins where running at the time? DId it just do the software Reset and then get back up and running, or did it take more work than that to get things running again?
Top

Post

Thanks for your prompt response. I was playing Ivory when it happened, but the snapshot I was using contained 2 more bypassed instances of Ivory plus 6 or 7 bypassed instances of B4 II. Not sure if that matters or not. It immediately rebooted by itself and I was up in running in under a minute - which unfortunately is an eternity during a song. This was the first crash I've experienced, so do you think the close proximity to drums and super loud boomy stage (subs nearby) could be the problem?? I was also about a foot or 2 from a monitor wedge. I sure hope I can get to the root of the problem - I have to have a 100% stable rig on stage. Thanks again for your help.....
Top

Post

Hard to know what happened, check that the Receptor buffer size is back to what you want it set to. An over loaded CPU can be a cause of a crash, if possible bump up the buffer. Also you may want to try running your set with program changes from a sequencer and just run it in a loop. This is good way to see if the programed show remains stable.
Rick
Muse Research
Top

Post

Thanks Rick, but I'm not sure what you mean by running my set with a sequencer. I'm not using sequences. I'm sending patch (snapshot) changes from my controller keyboard. If I set the buffer higher, the increased latency will be noticeable, which is why I recently lowered it. I'll give it a try though. So no chance of vibrations affecting the unit??
Thanks.....
Top

Post

Reinski,

I think the key here is going to be looking at where the system resources are when your using this setup. When you get a moment you may want to load up that snapshot patch again. It'll be important to look at the 'setup' page in Receptor viewer. In the lower right hand corner is information about the amount of RAM available for your patch. The further this gets below 30% available the more stability issues you can expect, especially if you are using sampled plugins. Additionally look for the Z-load option next to it and make sure that is turned off as it will be just an un-needed strain on your RAM.

If this happened right when you did a patch change it could be that one of the plugins isn't responding well to the 'bypass'. Try cycling through the patches until you see it reset, and then when you find the one that causes a reset try just 'muting' it instead of bypassing.

There may be some details about the crash in your system log as well. This is located on Receptor's drive in the 'reports' folder. If you open a support ticket at http://www.plugorama.com/hd.php and upload the system log Technical support should be able to dig through and find some more details about what caused the crash.

I think what Rick is suggesting is connecting Receptor to a MIDI sequencer that is setup to play through the program changes in your show. This way you can let it sit there and run through all your patches for hours. If it keeps getting stuck in the same place that can provide a clue.

I do not think any of the environmental factors you mention caused the crash...I think most people put their Receptors through more than a loud drummer!


- Kevin
Top

Post

Thanks a lot Kevin. When I get back home I'll investigate your suggestions...
RR
Top

Post

reinski wrote:Last night during a my first live show with my brand new Receptor 2 it crashed and rebooted on the second song. Real drag! I was set up REALLY close to the drummer, and I was wondering if vibrations from the drums (he hits hard) could have caused the crash. Incidentally I was using CPU-hungry Ivory 1.7 when it happened. Anybody had a similar experience?? It really took the proverbial wind out of my sails....
I'll put a beer on it being a loose power cable... especially if you are on a stage that is wobbly at all, and if you're next to the drums which is going to cause your rig to wobble around... You really need to make sure that power cable is nice and snug... it just takes the tiniest interruption in that feed to cause a crash exactly like what you explain. If all you were doing was playing along and boom, it would be very strange for the system to do that... my guess is that it was power related.

Bryan
Top

Post

Thanks Bryan. I'm really hoping that's all it was. I'll double-check the power cable is snug...
Ron
Top

Post

Slightly off topic, but I sure like seeing the increased Muse presence in this and several other threads in this Receptor forum recently! Keep it up, guys! :tu:

Now back to regular programming...
Top

Post

batgab wrote:Slightly off topic, but I sure like seeing the increased Muse presence in this and several other threads in this Receptor forum recently! Keep it up, guys! :tu:

Now back to regular programming...
Isn't it funny that Muse has an increased presence in the Receptor forum after Receptor 1 users have recently stopped talking about the 1.8 update for Rev. C Receptors ...
Top

Post

Kevin@MuseResearch wrote:Reinski,

I think the key here is going to be looking at where the system resources are when your using this setup. When you get a moment you may want to load up that snapshot patch again. It'll be important to look at the 'setup' page in Receptor viewer. In the lower right hand corner is information about the amount of RAM available for your patch. The further this gets below 30% available the more stability issues you can expect, especially if you are using sampled plugins. Additionally look for the Z-load option next to it and make sure that is turned off as it will be just an un-needed strain on your RAM.

If this happened right when you did a patch change it could be that one of the plugins isn't responding well to the 'bypass'. Try cycling through the patches until you see it reset, and then when you find the one that causes a reset try just 'muting' it instead of bypassing.

There may be some details about the crash in your system log as well. This is located on Receptor's drive in the 'reports' folder. If you open a support ticket at http://www.plugorama.com/hd.php and upload the system log Technical support should be able to dig through and find some more details about what caused the crash.

I think what Rick is suggesting is connecting Receptor to a MIDI sequencer that is setup to play through the program changes in your show. This way you can let it sit there and run through all your patches for hours. If it keeps getting stuck in the same place that can provide a clue.

I do not think any of the environmental factors you mention caused the crash...I think most people put their Receptors through more than a loud drummer!


- Kevin
Hi again Kevin,
When I got back home (after 2 more crashes during my shows!! FUN!!) I noticed that my GEQ parametric effect on my B4 patches was gone. I assume that was because the demo period had elapsed. Think that could be causing the crashes? Also, on all five of the crashes, I was playing Ivory. Today I plan to try to get it to crash, plus do the system log thing you suggested. Once again I appreciate all your help....
RR
Top

Post

Hey again Kevin -
Regarding my Receptor crashing, do you think it could have something to do with the expiring GEQ-7 Parametric? I think it expired on the same day of the first crash. I remember noticing that my B3s were duller and missing some EQ. Could it be that the Receptor was constantly searching for the plug-in which wasn't there, and that caused it to freak out? I saw on my System Log where the missing GEQ-7 is mentioned several times. I'll try sending the log over to Plugorama....
Thanks
Top

Post

Receptor should ignore the timed out plugin (GEQ-7) but it's possible that was a cause. Remove that plugin from your patches or get an ilok licenes for it from plugorama.com. As for my previous post about testing your patches. If you own a sequencer then use it to send MIDI to Receptor. In other words the sequencer acts as robot just sending notes and program changes over and over. MIDI from any source such as MIDI drums, controllers, foot pedals, sequencers etc is still MIDI. If you do not have a sequencer then I recommend you use your controller to send notes and program changes, cycle through the patches several times.
Rick
Muse Research
Top

Post

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
Top
Locked

Return to “Muse Research and Development”