Receptor Crash While In Use
-
- KVRer
- 4 posts since 8 Apr, 2015
Weird situation with my Receptor (pro max 2 running version 1.9xxxx, the last version before the 2.0 update). I haven't used it much due to lack of a good controller, but recently bought a Novation SL61mk2 which checks all the boxes I needed to put it into production use. I've been programming a lot of stuff for my Pink Floyd tribute band. Lots of synth leads, poly synth, string machines, etc. I did all of the programming with a standalone monitor and either no network connection or connected to my home network.
I finally racked it up in my road/gig rack and also put a wireless router in there to connect the Receptor via ethernet, and then use my laptop or tablet via wireless to make tweaks and adjustments to the sounds and levels at rehearsal, with the ultimate goal being to not need any of this once all the tweaks were done for live use.
The problem I ran into is the 1st time I took the Receptor to rehearsal, it crashed in mid use. It seems that when the laptop went into power save mode, it disrupted something network wise on the Receptor, and it crashed. By the time I realized it (I was playing on other boards at the time), the Receptor was at the "contact the factory" screen, and gave an option to enter into the diagnostic mode. I did that and let it run tests where it came back with a couple errors but I wasn't able to see exactly what was causing it. So I ran the tests one at a time, one that failed was the Updates- like the last update I installed was corrupted. Also there was a warning about the network using a 0.0.0.0 address which is weird because the router is serving up DHCP and it had worked fine previously. At rehearsal I finally got into expert mode, cleared the cache files and was able to get it restarted. I took the laptop off of power save mode so it didn't go to sleep. No more issues that night.
I got it home and last night powered it up and got a 2001 error. Ran a full disk check, ran the other tests individually, they all passed except for the updates one again. I disconnected the router, plugged the Receptor into my home network, and connected a standalone monitor and mouse/keyboard, like I had been doing while programming everything. Cleared the cache, and got it to boot. I let it run the auto update where it downloads the files from the internet, it took about 15 seconds to run so I don't think it did anything, but it booted fine after that. I've shut down and rebooted it a dozen times since last night and it comes up fine each time, all with the standalone monitor and either no network connection or connected to my home network.
I'm thinking something with the router I was using along with the laptop caused the problem and maybe corrupted some files with the dirty shutdown. The disk check did find errors that were corrected and clearing the cache was the one thing that let it boot for me.
I'm really concerned because the Receptor is now an integral part of the PF tribute project. It replaces a Moog Phatty with options to have whatever mono or poly sounds I need in whatever combos- a killer setup for this kind of music combined with the rest of my rig, which is a Roland FA08, Hammond SK1 73 and a Novation Ultranova. At this point I'm not sure I can trust it. If this kind of crash happened at a show where people are paying to see us and I have tech issues, it's not good.
Has anyone seen an issue like this? If not, I at least wanted people to be aware of what occurred. The only other issues I've had are a couple plugins cause the unit to hang and restart but it's not a full reboot when that happens, and the plugins are not ones that I really need, it was when I was auditioning stuff to look for a particular feature or sound.
I finally racked it up in my road/gig rack and also put a wireless router in there to connect the Receptor via ethernet, and then use my laptop or tablet via wireless to make tweaks and adjustments to the sounds and levels at rehearsal, with the ultimate goal being to not need any of this once all the tweaks were done for live use.
The problem I ran into is the 1st time I took the Receptor to rehearsal, it crashed in mid use. It seems that when the laptop went into power save mode, it disrupted something network wise on the Receptor, and it crashed. By the time I realized it (I was playing on other boards at the time), the Receptor was at the "contact the factory" screen, and gave an option to enter into the diagnostic mode. I did that and let it run tests where it came back with a couple errors but I wasn't able to see exactly what was causing it. So I ran the tests one at a time, one that failed was the Updates- like the last update I installed was corrupted. Also there was a warning about the network using a 0.0.0.0 address which is weird because the router is serving up DHCP and it had worked fine previously. At rehearsal I finally got into expert mode, cleared the cache files and was able to get it restarted. I took the laptop off of power save mode so it didn't go to sleep. No more issues that night.
I got it home and last night powered it up and got a 2001 error. Ran a full disk check, ran the other tests individually, they all passed except for the updates one again. I disconnected the router, plugged the Receptor into my home network, and connected a standalone monitor and mouse/keyboard, like I had been doing while programming everything. Cleared the cache, and got it to boot. I let it run the auto update where it downloads the files from the internet, it took about 15 seconds to run so I don't think it did anything, but it booted fine after that. I've shut down and rebooted it a dozen times since last night and it comes up fine each time, all with the standalone monitor and either no network connection or connected to my home network.
I'm thinking something with the router I was using along with the laptop caused the problem and maybe corrupted some files with the dirty shutdown. The disk check did find errors that were corrected and clearing the cache was the one thing that let it boot for me.
I'm really concerned because the Receptor is now an integral part of the PF tribute project. It replaces a Moog Phatty with options to have whatever mono or poly sounds I need in whatever combos- a killer setup for this kind of music combined with the rest of my rig, which is a Roland FA08, Hammond SK1 73 and a Novation Ultranova. At this point I'm not sure I can trust it. If this kind of crash happened at a show where people are paying to see us and I have tech issues, it's not good.
Has anyone seen an issue like this? If not, I at least wanted people to be aware of what occurred. The only other issues I've had are a couple plugins cause the unit to hang and restart but it's not a full reboot when that happens, and the plugins are not ones that I really need, it was when I was auditioning stuff to look for a particular feature or sound.
-
- KVRist
- 144 posts since 20 Feb, 2013
Hello
I use my pro Max allot for live gigs.
It has crashed a couple of times but ive always managed to recover with very little problem.Usually it was while there was a mouse and computer keyboard connected.
I figured that it was a USB problem.
I find it hard to believe that your router is the cause.
Once or twice I think it was a plugin that caused mine it to crash.
Usualy a plugin that is "unsupported".
Usually I just do a quick reset using the front panel power button and its fine.
I would recommend making a backup of your receptors hd once you have it set up properly.
There are a few posts on the forum on how to do it if you are a little computer savvy you wont find it difficult.
Or you could get the 2.0.1 upgrade there is a backup function included in this ,but personally I don't trust it.
All in all I find receptors to be very reliable (I have 3) I would estimate that I have had three or four minor crashes per 60 gigs.My bass player has had allot more problems LOL.
Good luck //Andy
I use my pro Max allot for live gigs.
It has crashed a couple of times but ive always managed to recover with very little problem.Usually it was while there was a mouse and computer keyboard connected.
I figured that it was a USB problem.
I find it hard to believe that your router is the cause.
Once or twice I think it was a plugin that caused mine it to crash.
Usualy a plugin that is "unsupported".
Usually I just do a quick reset using the front panel power button and its fine.
I would recommend making a backup of your receptors hd once you have it set up properly.
There are a few posts on the forum on how to do it if you are a little computer savvy you wont find it difficult.
Or you could get the 2.0.1 upgrade there is a backup function included in this ,but personally I don't trust it.
All in all I find receptors to be very reliable (I have 3) I would estimate that I have had three or four minor crashes per 60 gigs.My bass player has had allot more problems LOL.
Good luck //Andy
-
- KVRist
- 79 posts since 25 Apr, 2006 from Stockholm, Sweden
3-4 crashes in 60 gigs sounds like a lot to me... I've done over 100 gigs with mine this year with zero problems (except the ones I've caused myself by hitting the wrong button etc...). I also believe it can be a USB problem, make sure you're not using anything that needs special software.
-
- KVRer
- Topic Starter
- 4 posts since 8 Apr, 2015
I have 2 things plugged into the USB port, the Novation SL61 for power, and a mouse. Maybe it's the Novation? It needs a midi driver for windows and mac, but I'm not using USB for midi, only power.
I have it set up at home with the Novation connected and have rebooted it a bunch of times yesterday and also left it running for hours, and did a bunch of playing on it last night with no problems.
I have it set up at home with the Novation connected and have rebooted it a bunch of times yesterday and also left it running for hours, and did a bunch of playing on it last night with no problems.
