1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

CPU Overload Crashing Application

Discussion in 'REAKTOR' started by Joseph Green, Oct 14, 2019.

  1. Joseph Green

    Joseph Green New Member

    Messages:
    5
    Hi guys, time to get straight to the point. I'm currently running Reaktor on a (not-so-great) Windows 10 Laptop that I'm using lieu of my computer since it's going to be stuck half-way across the US for the rest of the year. While I've obviously stayed away from CPU-intensive Ensembles for good reason, this laptop sometimes can't handle even some more basic ensembles, and will Overload and make me switch to Factor 1/4 at the worst. As of late however, when I try to load an ensemble that overloads it, Reaktor freezes and doesn't respond, making me force it to close. I can't think of any reasoning for this as of late other than a Windows Update that my laptop went through a week or so ago.

    Thanks for your time, hope your days are going well.
     
  2. colB

    colB NI Product Owner

    Messages:
    3,969
    How long are you waiting?

    Some core modules take a long time to compile - a few seconds on a powerful machine, but potentially quite a bit longer on a low end laptop. Maybe try to give it a minute or two and see if that helps?
     
    • Like Like x 1
  3. Joseph Green

    Joseph Green New Member

    Messages:
    5
    It's almost immediate- I'll click on the ensemble in Reaktor's sidebar to load it, it'll think about it for a couple of seconds and then freeze the application, leading me to have to force close it. When I say think about it, I mean literally to the point where if I'm using one ensemble and switch to another; it will stop the current one, and before it can load the UI of the other, it's frozen. Additionally, if I load an ensemble from a blank one with nothing in it, it will load the UI, show it running, I'll go to play notes and it will read that MIDI is being transmitted, but no sounds come out. I've checklisted everything beforehand (MIDI channel configuration, Reaktor knowing that my keyboard exists in the first place); in this same moment, if I try to even touch the menu bar, it freezes and I have to close it.

    I would also like to stress that some of the Ensembles I'm using aren't that CPU intensive (at least from memory of what this laptop could do) and even when they were it always just displayed the Overload error. For example- Paule's Prophet 5 simulation used to run fine on this laptop, with no need to change the sample rate at all (though it did get very close from what I remember). Now when I try to load it, nothing sounds and it freezes.

    Another issue that seems to plague a lot of Ensembles (and I genuinely have no idea if this is a User problem or something on Reaktor's end) but most ensembles will load at the Host/System speed of whatever your computer is able to handle; for example, my main computer can load ensembles at 192000 Hz, which is well above any rate that most ensembles need, so I'll tone it down after I load one so I'm not overworking my computer every time I load Reaktor. I know that you can tell your computer to automatically do that but that's a different point and I've forgotten over time how to do it. On the opposite end, my laptop automatically defaults to 48000 Hz, which is fine for most basic ensembles and has a very decent audio quality to my ears for what this laptop is (a $300 laptop). However, if I'm loading in a relatively complex ensemble, it defaults to that sample rate when I load it, which previously would most of the time overload the CPU and cause it to automatically load the error message and turn itself off, at which point I could lower the sample rate and use it with some success.

    My problem with this lies in the fact that if I know an ensemble is complex, and I tell Reaktor to use a lower sample rate before loading, it overrides that command when I load it, because it always tries to load at the host/system default, which leads it to overload or as of late, just freeze the application.

    I apologize not explaining further about this problem in my first post, I didn't know as much about it as I do writing this now. If a concrete solution already exists to this problem, I'm all ears. If not, I don't personally need an immediate fix as this setup is temporary, I just thought I'd bring up this issue as not everyone who uses this program has computers with high sample rates and good CPU's.