CPU overload

Comments

• pgill

  January 2009 edited 4:10PM

  Hi, I've played for decades with hardware synths and Mr T and the Trumpet are my first softsynths so you might get better advice.
  
  
  
  When I first used the softaware, every 30 seconds or so I got a dropout, I don't know if this is the same as you are experiencing.
  
  
  
  On the windcontroller forum Jason suggested using "DPC LATENCY CHECKER", which is free, you'll have to google it.
  
  
  
  I noted the culprit which was a background device/s on my laptop that were acting badly. Once isolated they could then be turned off in "Device manager".
  
  
  
  Regards Pete.
• Phil999

  January 2009 edited 4:10PM

  I also think it must be some background service that is the culprit. With your DAW, you should be able to play nicely with 128k or even 64k buffer. I don't know Mac, so I can't say more.
  
  
  
  Hope you find the solution soon.
• webbiedave

  January 2009 edited 4:10PM

  I am experiencing similar behavior.
  
  
  
  After playing The Trumpet for 5 or 10 minutes I experience a lot of popping and clicking (every few notes). I then reload kontakt and it will work fine for 5 or 10 minutes before the popping and clicking returns.
  
  
  
  I have a 3.0Ghz Intel with 2GB RAM running Windows XP with the Kontakt buffers set very high. I am using it with my sequencer and it is the only instrument loaded. I don't have other programs in the OS running other than necessary drivers.
  
  
  
  Any ideas to get rid of the popping and clicking?
  
  
  
  (My guess is a much faster computer because if I set the ASIO buffer latency very high i.e., 100ms, the popping and clicking goes away)
  
  
  
  Thanks.
• Stevie

  January 2009 edited 4:10PM

  I have a similar problem. Although the time is longer. It takes about an hour until it starts to crackle. I got a
  
  Q9950 quadcore. So CPU shouldn't be an issue. When I reload the project and the sequencer the problem disappears for another hour.
  
  
  
  
  
  Best,
  
  
  
  Stevie
• Firebird

  January 2009 edited January 2009

  Dartane wrote: Hello to all. Would first like to congratulate and thank the creators of these amazing products.
  
  I am an EWI 4000s player using IMac 2.4 dual core, latest leopard OS, Logic Pro, and Motu Ultalite interface.
  
  The only problem I have been experiencing thus far is CPU overload with prolonged playing (more than 5 minutes) of the Trumpet either stand alone or within Logic (no other tracks playing). My settings are 512k buffer, 44100khz, 18ms. The program plays flawless for the first 5 minutes with the CPU meter well below maximum range, than starts to crash. At that point I must reload the instrument and start over. Is anyone experiencing the same problem and can anyone offer an explanation and/or possible solution.
  
  Thanks dave
  
  Dave,
  
  I am using a macbook pro, 2.5 Ghz Intel Core 2 Duo. I think this may be less powerful as your computer :?: I do not experience this problems. I use a FastTrack Pro audio interface, putting the sample rate at maximum (96000). In Mr. Sax T I choose "Match to audiocard" and I put the buffer to 64samples. For me this is working even if I have some other software instrument loaded at the same time.
  
  I can not think about a possible solution for you right now, but there must be one. How much RAM do you have installed. Did you check the apple Activity Monitor? Maybe by looking at this you could find out what is wrong.
  
  Firebird
• Giorgio Tommasini

  January 2009 edited 4:10PM

  Dartane and others,
  
  
  
  I was finally able to reproduce the problem on my quad core duo system. I played a sequence in Cubase, and set it to be played in a continuous loop. In the basal state, CPU load was approximately 5%. After about 10 min, the CPU load approximately doubled. After 30 min, I got CPU peaks up to 100%. Mr. Sax T. does not exhibit this behaviour, nor (apparently) The Trumpet vers. 1.01.
  
  Note events and controllers events are apparently unchanged.
  
  
  
  We are working on this. An effective temporary workaround is to click on Engine -> restart engine, which resets the instrument CPU load to the basal state.
  
  
  
  The next update will hopefully fix the bug.
  
  
  
  Giorgio
• Stevie

  January 2009 edited 4:10PM

  Hey Giorgio!
  
  
  
  That's great. Looking forward to it
  
  
  
  Best,
  
  
  
  Stevie
• Perry

  January 2009 edited 4:10PM

  That is great news!
• bobhunt

  January 2009 edited 4:10PM

  That is definitely good news that the problem is being addressed. I have had the same problem. Thank you for letting us know!
• Giorgio Tommasini

  January 2009 edited 4:10PM

  We could eventually identify the bug, and fix it.
  
  
  
  The next release will be definitely free of this bug, even though many new bugs will undoubtedly be introduced.
  
  
  
  Best,
  
  
  
  Giorgio
• bobhunt

  January 2009 edited 4:10PM

  The next release will be definitely free of this bug, even though many new bugs will undoubtedly be introduced.
  
  So Mr. Tommasini are you saying your programs are prone to being buggy?
• bobhunt

  January 2009 edited 4:10PM

  On a positive note the tip about resetting the engine helps tremendously in saving from restarting the program.
  
  I have found that I get somewhere around 20-30 minutes using Asio4all instead of the Creative Asio. And of course if the Engine is reset once every few minutes there isn't a problem.
• valouz

  January 2009 edited 4:10PM

  So Mr. Tommasini are you saying your programs are prone to being buggy?
  
  
  
  it is humour of developer
  
  
  
  I do not know If you know a little bit software's world : we always say that for one bug corrected, two or three will appear.
  
  
  
  But it is only valid for the bad developers also that does not apply to the samplemodeling team
• Perry

  January 2009 edited 4:10PM

  I think the new bug introduced will be a subliminal message to buy more Sample Modeled instruments. 8-) I have attached a subliminal message to create more. :twisted:
• LHall

  January 2009 edited 4:10PM

  So glad you found the bug. Looking forward to the fix as this is afflicting me as well.
  
  
  
  Big thanks.