Receptor Lockups
-
- KVRist
- Topic Starter
- 209 posts since 25 Jun, 2004 from New England
I have been able to lockup the Receptor multiple times by generating agressive MIDI data and having multiple VSTi instruments running. Have there been any reports of this or have you seen this in your own experience? Are there workarounds or guidelines to avoid this behavior?
-
Rick@MuseResearch Rick@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=18273
- MUSEician
- 350 posts since 23 Mar, 2004
If the CPU gets overloaded I know it can crash. Adding addtional RAM really does a fine job of improving performance. Also try running at 44.1 Sample Rate and a Buffer Size of 256.
SoftJunkie wrote:I have been able to lockup the Receptor multiple times by generating agressive MIDI data and having multiple VSTi instruments running. Have there been any reports of this or have you seen this in your own experience? Are there workarounds or guidelines to avoid this behavior?
Rick
Muse Research
Muse Research
-
- KVRist
- Topic Starter
- 209 posts since 25 Jun, 2004 from New England
Those are my configurations. For obvious reasons, an occasional CPU overload is tolerable but a lockup/crash is not. Playing to a room of 300/600/1000 people and having the keys or bass dropout is not pretty. It's usually followed by a band meeting and an intervention to stop using the gear in question!
I may start another thread but I should mention that the CPU overload is 'spiky' in behavior. I'll be running steady at 20-30% and all of a sudded it will jump to >100% for a split second and they settle back to the 20-30%. This may indicate that background tasks are interfering (polling enet, usb, ...). I no nothing of the workings of the software but i wanted to make you aware of the behavior I am seeing.
I may start another thread but I should mention that the CPU overload is 'spiky' in behavior. I'll be running steady at 20-30% and all of a sudded it will jump to >100% for a split second and they settle back to the 20-30%. This may indicate that background tasks are interfering (polling enet, usb, ...). I no nothing of the workings of the software but i wanted to make you aware of the behavior I am seeing.
-
- KVRist
- 112 posts since 24 Jun, 2004 from Austin, TX / France / Germany / Luxembourg
Yes, I have this same problem. And the problem comes surely of USB request ...SoftJunkie wrote:I may start another thread but I should mention that the CPU overload is 'spiky' in behavior. I'll be running steady at 20-30% and all of a sudded it will jump to >100% for a split second and they settle back to the 20-30%. This may indicate that background tasks are interfering (polling enet, usb, ...).
Bye
Spid
-
- KVRist
- Topic Starter
- 209 posts since 25 Jun, 2004 from New England
Why do you suspect USB? If so, i've always gained stability in my PC recording setups by disabling various USB ports in the BIOS. I wouldn't dare mess with the Receptor BIOS unless suggested by MUSE but if that improves stability/performance, I'm all for it.
-
- KVRer
- 21 posts since 25 Aug, 2004
Just out of curiosity, do you think the issues that you mention (Receptor lockups, CPU spiking) be fixed with eventual software upgrades or might this suggest a deeper problem?
I received my Receptor today and I'm worried about even opening it. I hope it doesn't turn out to be another Coleco ADAM...I am still very amenable to taking the plunge and setting it up this week, but I need some reassurance. I am hoping to use the Receptor in an October gig with only one or two VST instruments open at a time.
Ben
I received my Receptor today and I'm worried about even opening it. I hope it doesn't turn out to be another Coleco ADAM...I am still very amenable to taking the plunge and setting it up this week, but I need some reassurance. I am hoping to use the Receptor in an October gig with only one or two VST instruments open at a time.
Ben
-
- KVRist
- Topic Starter
- 209 posts since 25 Jun, 2004 from New England
I don't wish to discourage anyone with this info. I beleive this is a future part of my live rig. But I am also going to have a backup system just in case.
October is probably when I'll ready to take this thing live as well.
October is probably when I'll ready to take this thing live as well.
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
We do not recommend that you change the BIOS settings. Turning off USB on Receptor is not a good idea.SoftJunkie wrote:Why do you suspect USB? If so, i've always gained stability in my PC recording setups by disabling various USB ports in the BIOS. I wouldn't dare mess with the Receptor BIOS unless suggested by MUSE but if that improves stability/performance, I'm all for it.
We will investigate, but I seriously doubt that it has anything to do with USB. If you insert your iLok, or any other USB device, there wiill be some USB activity that will involve the CPU. It should not spike, though.
But, as long as you don't have any USB device connected, USB should not affect performance at all. We will look into it again to make absolutely sure that indeed performance is not affected by USB.
Dan
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
- KVRAF
- 35263 posts since 14 Sep, 2002 from In teh net
Don't you need the iLock in all the time if you are using premium instruments? I find USB always eats CPU cycles unnecessarily on my PC but that's USB 1 - doesn't Receptor use the USB 2 standard (it should surely)?
-
- KVRist
- 76 posts since 17 Jun, 2004
Receptor does indeed support USB 2.0aMUSEd wrote:doesn't Receptor use the USB 2 standard (it should surely)?
-
- KVRer
- 21 posts since 25 Aug, 2004
Thanks for the encouragement and information. I'm planning to take a day off on Friday and install it then.
Ben
Ben
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
Theoretically, you need the iLok only when you instantiate a premium plug-in. Practically, you are not going to put the iLok in and out constantly during live performance as you change multi or single patches.aMUSEd wrote:Don't you need the iLock in all the time if you are using premium instruments? I find USB always eats CPU cycles unnecessarily on my PC but that's USB 1 - doesn't Receptor use the USB 2 standard (it should surely)?
When you put the iLok in or take it out, there will be some CPU activity, but it should not spike. After a while, things settle down. Even with the iLok inserted, there should be practically zero USB activity until you instantiate a plug-in, take the iLok out, or put it back in.
Yes, Receptor uses USB 2.0
Dan
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
-
- KVRist
- 112 posts since 24 Jun, 2004 from Austin, TX / France / Germany / Luxembourg
When I start Receptor, and load the first MULTI, it is arround 20-30%.
It peak to 100% for just a little moment, and come back to 20-30%... for 10 seconds, and peak again, etc...
It's something with usb_uhci error repport.
Bye
Spid
It peak to 100% for just a little moment, and come back to 20-30%... for 10 seconds, and peak again, etc...
It's something with usb_uhci error repport.
Bye
Spid