System restart, ticking or LOUD BUZZ when CPU hits 100%
-
- KVRist
- 209 posts since 25 Jun, 2004 from New England
I've been able to consistently reproduce a setup that crashes HARD! I'm trying my best to consider this system for live use but if any piece of gear would do live what Receptor did tonight, I'd demand my money back immediately.
THIS IS A SHOWSTOPPER!!!
Receptor:
version 1.3.20050627
1 Gig RAM
buffer = 64 samples
Plugin:
Kompakt
version 1.0.3.0006
DFD off
SSE Support enabled
Multipatch: Heaven Layer I
I press 2-3 note repetitively to cause the CPU meter to hit 100%. The system fails in one of three ways:
- the synth audio stops and is replaced by a ticking sound that lasts for about 1 minute. the synth sound comes back to normal (no restart).
- the system restarts and returns to normal
- there is a blazingly LOUD BUZZZZZZZZZZZZ!!!! coming from the speakers!!!!! if this were to happen at one of my gigs, it would level the room. imagine 500-600 people screaming in pain!!!! that's what i'd be responsible for. all because i configured receptor with a patch that caused the cpu to reach 100%.
i am so frustrated.
THIS IS A SHOWSTOPPER!!!
Receptor:
version 1.3.20050627
1 Gig RAM
buffer = 64 samples
Plugin:
Kompakt
version 1.0.3.0006
DFD off
SSE Support enabled
Multipatch: Heaven Layer I
I press 2-3 note repetitively to cause the CPU meter to hit 100%. The system fails in one of three ways:
- the synth audio stops and is replaced by a ticking sound that lasts for about 1 minute. the synth sound comes back to normal (no restart).
- the system restarts and returns to normal
- there is a blazingly LOUD BUZZZZZZZZZZZZ!!!! coming from the speakers!!!!! if this were to happen at one of my gigs, it would level the room. imagine 500-600 people screaming in pain!!!! that's what i'd be responsible for. all because i configured receptor with a patch that caused the cpu to reach 100%.
i am so frustrated.
-
- KVRAF
- 3971 posts since 19 Apr, 2005 from Brissie
Man, that's no good at all! Mind you, I've always HATED Kompakt/Kontakt, and found them extremely CPU hungry - love most of the other NI stuff! I want to love them, but they give me the irrits.
I must say, I'm using Receptor 2-4 nights a week at the moment, with no problems... but I'm not trying to play heavy samples through Kompakt (especially piano, which I'd love to do).
Therefore, it's still not the all-in-one solution I hoped for - not yet anyway. *sigh*
I must say, I'm using Receptor 2-4 nights a week at the moment, with no problems... but I'm not trying to play heavy samples through Kompakt (especially piano, which I'd love to do).
Therefore, it's still not the all-in-one solution I hoped for - not yet anyway. *sigh*
-
- KVRist
- 387 posts since 24 Aug, 2004
Try setting your sample buffer size to 128 - it should fix things. I'm not familiar with that patch, but you should also check out your settings for maximum voices in Kompakt.
I'm hoping that Kontakt behaves well on Receptor when it is ultimately available.
I am able to play piano live on receptor, although it is with a few comprimises.
I use the White Grand Jr. piano, which I batch converted to mono by splitting the samples and using the right side for the high notes and the left side of the low notes. This can be played with DFD off and is immpossible to crash. It also,
after some tweaking in Kompakt , is more expressive and sounds better than my Yamaha P200.
I'm also having good luck with the Scarbee libraries, providing everything is set just so.
I'm hoping that Kontakt behaves well on Receptor when it is ultimately available.
I am able to play piano live on receptor, although it is with a few comprimises.
I use the White Grand Jr. piano, which I batch converted to mono by splitting the samples and using the right side for the high notes and the left side of the low notes. This can be played with DFD off and is immpossible to crash. It also,
after some tweaking in Kompakt , is more expressive and sounds better than my Yamaha P200.
I'm also having good luck with the Scarbee libraries, providing everything is set just so.
-
- KVRist
- Topic Starter
- 209 posts since 25 Jun, 2004 from New England
thanks for the advice. unfortunately, trying to keep the CPU usage down is missing the point. prior to these nasty crashes, i had played successfully for hours using a simple piano, bass and strings multi that was consistently under 50% CPU usage. I was about to post a message on how happy i was with the stability of 1.3. the point of my posting is that there is nothing graceful about the way receptor handles a CPU hungry multi. blood will come out of the ears of your audience.
if this is not reproducible by anyone, i may have a defective unit. i'm sure that would be easier to resolve.
i'm waiting to hear back from muse to determine how i may remedy this problem.
i've also got a capable notebook setup that i will setup to push the CPU usage and check it's stability. brainspawn forte has a builtin stress test for exercising the setup for as long as you specify. it will send all sorts of midi to the plugins and log the results.
if this is not reproducible by anyone, i may have a defective unit. i'm sure that would be easier to resolve.
i'm waiting to hear back from muse to determine how i may remedy this problem.
i've also got a capable notebook setup that i will setup to push the CPU usage and check it's stability. brainspawn forte has a builtin stress test for exercising the setup for as long as you specify. it will send all sorts of midi to the plugins and log the results.
-
Rick@MuseResearch Rick@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=18273
- MUSEician
- 350 posts since 23 Mar, 2004
If you overload the CPU hard enough I can see how this can happen, samplers would be the most likely to do this. My recommendation would be to run the Receptor live at 44.1 / 128. As for the loud buzz we will work on duplicating this.
SoftJunkie wrote:thanks for the advice. unfortunately, trying to keep the CPU usage down is missing the point. prior to these nasty crashes, i had played successfully for hours using a simple piano, bass and strings multi that was consistently under 50% CPU usage. I was about to post a message on how happy i was with the stability of 1.3. the point of my posting is that there is nothing graceful about the way receptor handles a CPU hungry multi. blood will come out of the ears of your audience.
if this is not reproducible by anyone, i may have a defective unit. i'm sure that would be easier to resolve.
i'm waiting to hear back from muse to determine how i may remedy this problem.
i've also got a capable notebook setup that i will setup to push the CPU usage and check it's stability. brainspawn forte has a builtin stress test for exercising the setup for as long as you specify. it will send all sorts of midi to the plugins and log the results.
Rick
Muse Research
Muse Research
