Traktor 2.6 Hogging CPU!
Traktor 2.6 Hogging CPU! Posted on: 29.10.2012 by Rosita Jesch Hi All,I just started 2.6 up for the first time and my load is 20% or so with empty decks and it fluctuates for no reason. Is this only the first time it starts up? A bug? OSX 10.7.5 Fores | |
Lisette Ruben 29.11.2012 |
Originally Posted by Nicky H
|
Janyce Henningson 29.11.2012 | Yes mate, no problems at all... Sorry for bad screenshot: ss.jpg p.s yes that is 2 Unlimited in deck a |
Chun Douthat 29.11.2012 |
Originally Posted by Nicky H
|
Janyce Henningson 29.11.2012 |
Originally Posted by Rudi-J
My pc is a few years old now; intel i5 2.8 8gig ram 4 decks with macro fx on is about 9% in task manager macbook still on 2.5, haven't updated because of all the problems listed in here but pc seems ok |
Chun Douthat 29.11.2012 |
Originally Posted by Scaper7
Please do me a favour and check what happens to your TP2.6 CPU load control display when you raplid twist the knob/encoder adjusting loop length or if you rapidly press hot-cue buttons? |
Emanuel Kepics 29.11.2012 |
Originally Posted by GeekGod
With regards CPU hogging, I've just bitten the bullet and bought a new quadcore i7 laptop (Win7) so I can just get on with using Traktor, despite CPU load issues. My Core2Duo was glitching occasionally with 2.5/2.6 but not on the new i7 system. 0-1% CPU load with Traktor sitting idle (FX on, Keylocks on) ... even with 2 tracks running, load is negligible (still only around 1% registering in task manager/performance tab, occasionally climbing to around 10% briefly, then back 0-1%). |
Chun Douthat 03.12.2012 | Toevening some wonder magic happened on my PC (ACER Aspire X3900) I was booting with WLAN enabled to catch the latest MS WIN 7 64bit updates. It said "one important update" so I confirmed download and installation without further notice. I then started up Traktor to import, beat grid and set cue points for some new tracks.... When I suddenly noticed that the ERROR COMPLETELY DISAPPEARED: I was suddenly again able to twist the loop length encoder and move the loop (PLOOPING) without any hassles. CPU load in Traktor remained stable unchanged at about 20% No problems clicks or pops also when doing it on multiple decks at the same time using effects, beat juggle with cue point as far as I could etc. etc. all now even with a setting of 256 sampling rate on the VCI-400SE with "low latency" setting resulting in 5.8ms processing and 2.0ms output (7.8ms overall) in TRAKTOR. What happened? I found out the last update I just installed was a "Nvidia Graphics Adapter WDDM1.1, Graphics AdapterWDDM1.2' Other Hardware - NVIDIA GeForce GT 320" Hence, In the device manager, a new Graphics card driver manager Dated 02.10.12, Version 9.18.13.697 from NVIDIA got installed. If I disabled this driver again - the bug immediately returned. A few days before I just deinstalled all NVIDIA stuff and downloaded and installed the latest drivers from their WEB site with no effect at all. Can't fully understand what actually happened here, but anyway. So happy it got disappeared ! That's the way - aha aha - I like it ! |
Lisette Ruben 29.11.2012 |
Originally Posted by Nicky H
|
Rosina Steinkuehler 29.11.2012 | That would be my guess. I sent over screen shot "proof" that the problem exists and NI is now trying to get the programmers to understand there is an issue. The way I see it is a tug of war between support and the developer in berlin. For some strange reason I get the feeling the programmers have their head up their anus and don't want to believe anything support says. |
Janyce Henningson 29.11.2012 | Weird... Even weirder that it affects some machines and not others.. Some mac, and some pc.. Has to be a Traktor bug surely? |
Chun Douthat 29.11.2012 | Just made another interesting observation: Twisting loop length encoder will push up CPU load no matter what decks, but if deck c for instance is set to remix deck (and of course also when it is set to "live in") the CPU load remains stable. If the remix deck is thus loaded with 4 samples then the loop on deck c will play fine, can also be rapidly adjusted in length and position by encoders without clicks and pops and all this with CPU load in traktor display not exceeding 50%. So the bug eats up CPU time only for track decks.... |
Chun Douthat 29.11.2012 | Thanks for double checking Nicky, I am now in contact with NI service - hope they have an idea (at first they wanted me to unload Macro FX and release the FX link to the decks, but this seems to have nothing to do with it) |
Janyce Henningson 29.11.2012 | Yes mate, no problems at all... Sorry for bad screenshot: ss.jpg p.s yes that is 2 Unlimited in deck a |
Chun Douthat 29.11.2012 |
Originally Posted by Nicky H
|
Janyce Henningson 29.11.2012 |
Originally Posted by Rudi-J
My pc is a few years old now; intel i5 2.8 8gig ram 4 decks with macro fx on is about 9% in task manager macbook still on 2.5, haven't updated because of all the problems listed in here but pc seems ok |
Chun Douthat 29.11.2012 |
Originally Posted by Scaper7
Please do me a favour and check what happens to your TP2.6 CPU load control display when you raplid twist the knob/encoder adjusting loop length or if you rapidly press hot-cue buttons? |
Emanuel Kepics 29.11.2012 |
Originally Posted by GeekGod
With regards CPU hogging, I've just bitten the bullet and bought a new quadcore i7 laptop (Win7) so I can just get on with using Traktor, despite CPU load issues. My Core2Duo was glitching occasionally with 2.5/2.6 but not on the new i7 system. 0-1% CPU load with Traktor sitting idle (FX on, Keylocks on) ... even with 2 tracks running, load is negligible (still only around 1% registering in task manager/performance tab, occasionally climbing to around 10% briefly, then back 0-1%). |
Meg Reinoehl 28.11.2012 | @GeekGod... interesting you say that... because I've worked with developers before and they always ask for screenshots or screencasts of certain reported issues. In some cases it makes sense, because if you're making something happen it'll show in whatever workflow you're doing, but it's stupid/rude/disrespectful to ask for it as "proof" of it actually happening. |
Rosina Steinkuehler 29.11.2012 | Glad you where able to resolve your issues. I have a Core i7 Mac Book Pro that I completely formatted and reinstalled from the ground up. Out of the box the latency on Traktor is close to 50% with a FRESH INSTALL. Something is not right here. EDIT: for kicks I performed the steps in the above article and it made the latency 500* worse. |
Neville Blackinton 29.11.2012 | I had a similar issue but my problem was the system and not Traktor. This fixed my CPU spikes while idle and thus Traktor - http://www.rdoxenham.com/?p=259 |
Chun Douthat 28.11.2012 | OK - in the meantime I calmed down and decided to go "the official way" first by issuing a ticket describing the issue. I asked them to come back to me on the phone - let's see what happens next... |
Rosina Steinkuehler 28.11.2012 |
Originally Posted by Rudi-J
|
Chun Douthat 28.11.2012 | Gonna approach them in German maybe they feel it's more of an issue if they figure out there is a guy out there in the mood to kill somebody but within striking distance ... |
Rosina Steinkuehler 28.11.2012 | What's really funny is NI wants me to prove this with a video. They do not believe their own customers. Apparently the developers in 'berlin' are really hard to get along with from the bits and pieces that I can gather from USA support and require 'proof' of issues. Silly. Sucks we are caught in the middle but I cannot be bothered to 'prove' there is an issue with their software. |
Chun Douthat 28.11.2012 | I am struggeling with this in the same way (at least i believe so) on a Win 7 64bit with VCI-400SE (and with or without maschine, F1, BCR connected). The problem emerged unnoticed as i worked hard to complety my TSI in ther recent weeks. Have you guys encoders on your controllers that allow to adjust the loop length? To my expereience just rapidly twisting these encoders alone (even with no tracks loaded) lets the CPU load easily enter the red zone. Setting the ASIO sample rate to 4096 (!) avoids this issue but has of course unacceptabel other downsides... First I thought it's caused by the VCI-400SE (new firmware and stuff), then i thought it was Win 7, some graphic card driver, some usbdriver bug issues etc. (analyzed my system with latency software, deinstalled/deactivated literally all unused stuff not mandatory for running traktor using latest dricers etc. etc. etc.) then i thought (referring to postings also listed elsewhere in the community s) on a MAC this is all no problem, but now I just learned otherwise, am totally confused, but more and more my "feelings" are also that the TP 2.6 update is the real cause for this mess nomatter if MAC or PC. I am really uncertain how to progress: Going back to Wing XP 32?, Going back to TP 2.? (N.B. i read elsewhere that Win 8 is even more a mess when it comes to DCP latency...) After many years of using Windows I would even be ready to switch to a MAC just if somebody would guarantee this would fix that dammed issue. Will defenitely call NI now to get their advise... |
Rosina Steinkuehler 25.11.2012 | Ticked opened with NI. If anyone else is having these issues you should give them a call - they claim nobody has reported any CPU issues whatsoever. |
Tonia Denor 23.11.2012 | any updates on this? I am running over 100% cpu on idle 10.7.5 with 2.6 I dont know what to do, as soon as I open maschine it causes so much lag. |
Bertie Metro 03.11.2012 | On my 15'' 2006 1,83 core duo mbp w/ 2gb ram and osx 10.6.8 (yes i know, old...) i had glitches and pop and stuff at 41000 and 128 buffer. Then i rolled back the audio8 drivers, unchecked multicore. It was better, but still pop and crackles. So i went in and "disconnected" the audio inputs for deck 3 and 4, for the fx send, for the aux in, and put deck 3 and 4 in internal in the timecode options, rechecked the multicore option, and now it's fine, 2 decks and 4 fx bank, even with the new macro fx. I believe that it was that traktor was waiting for some timecode input on decks 3 and 4, and so was using more cpu....maybe. |
Ned Somerset 02.11.2012 | Im not running mountain lion. Played 2.6 out last evening for about 3 and half hours. Not a single pop glitch crackle and cpu was running normal. |
Leeanna Ayla 02.11.2012 | I had issues the other day just out of the blue. I rolled the audio drivers back for my A10 and that solved it. |
Rosita Jesch 02.11.2012 | I am on 10.7.5 - not mountain lion. But here's the bad part. I just tried 2.5.1 as another user suggested - in the backup folder - and am still getting the CPU jumps in that program! Fores |
Armando Chrystal 30.10.2012 |
Originally Posted by trux
yup have the same problem once I unloaded the new FX cpu was fine again...the new FX slam my CPU meter |
Fatimah Czuprynski 30.10.2012 | oh okay thats s**ks of course. Maybe for the moment if you want to try the new effects you should put the latency up so the CPU doesn't jumps that much. |
Rosina Steinkuehler 30.10.2012 | Absolutely but in my case when the CPU jumps too much the audio cuts out which is not very appealing. |
Fatimah Czuprynski 30.10.2012 | Same here. But it was stable. i took the risk and played two and a half hours last sat. with it and i allowed the dj after me to use my mac. CPU was jumpin' all the time but traktor still was stable. thats the most important thing, isn't it? |
Rosina Steinkuehler 30.10.2012 |
Originally Posted by NoizeuNit
|
Alberta Oberti 30.10.2012 | Forgot to mention. I'm running Mountain Lion with latest updates on my Macbook Air 13". But I did a clean install after some other problems after the upgrade from Lion. Never had any problems since. |
Ciara Cuttill 30.10.2012 | dude i had huge spikes after the update myself and im on a windows (won't get a mac yet) |
Kasandra Kreindler 30.10.2012 |
Originally Posted by GeekGod
|
Rosina Steinkuehler 30.10.2012 | I thought it originally was a ML problem but a friend of mine had identical issues and he has ML. Back to the drawing board on the cause.... I might break down and just reinstall the entire machine to see if it helps. |
<< Back to General DiscussionReply