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
Printable View
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
Same problem here - I think it might have something to do with not being on mountain lion.
50% CPU utilization without any tracks being played at all - no key lock, nothing. I think NI overlooked testing 2.6 on previous OSX versions.
Yes, I am not on mountain lion and not upgrading on this computer.
Worried about my gig on Saturday night!
Use 2.5 if you have a gig. I went back to 2.5 until I can find a solution to my issue. Its in the "Backup" folder Applications -> Native Instruments -> Traktor -> Backup.
I've started on 2.6 and whenever i load one of the new fx in. It jumps.
Won't be using 2.6 out for a while! Not until the CPU load chills out a bit.
I don't want to upgrade to Mountain Lion either, can't be bothered arsing around with the USB 3.0 to USB 2.0 crap again.
No problems at all. Running Traktor 2.6.0 on a Macbook Air 13" (Late 2011 model). CPU Load for the kernel is at 4.5% and user mode is 7% when doing nothing at all. When playing two decks, running 3 samples in the remix deck and applying effect 1 and 2 the user mode has 14% CPU load.
Haven't got it on my macbook yet but on Windows there's no difference.
Must be a Mountain Lion problem?
i'm on an older mbp running lion, haven't upgraded to mountain. traktor idles around 33% cpu, but i have noticed that simply putting the new macro fx into the fx slots is enough to make the cpu jump into the red.
it doesn't matter if the fx is being used or not, just having it in a slot is enough to get cpu spiking crazy :(
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.
wouldn't that mean it IS a ML issue? ¯\(°_o)/¯Quote:
Originally Posted by GeekGod
dude i had huge spikes after the update myself and im on a windows (won't get a mac yet)
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.
Sorry that might have come across wrong - I have snow leopard on my mac. Friend has ML. Originally I thought the problem was due to not having ML but that theory is kaboshed.Quote:
Originally Posted by NoizeuNit
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?
Absolutely but in my case when the CPU jumps too much the audio cuts out which is not very appealing.
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.
Quote:
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
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
I had issues the other day just out of the blue. I rolled the audio drivers back for my A10 and that solved it.
Im not running mountain lion. Played 2.6 out last night for about 3 and half hours. Not a single pop glitch crackle and cpu was running normal.
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 think that it was that traktor was waiting for some timecode input on decks 3 and 4, and so was using more cpu....maybe.
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.
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.
I am struggeling with this in the same way (at least i think 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 forums) 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.:cursing:
Will defenitely call NI now to get their advise...
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.
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 ... :sneaky2:
Hah! Good luck!Quote:
Originally Posted by Rudi-J
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...
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
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.
@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.
Doesn't surprise me one little bit. After two years as a NI customer I've learned not to waste my time with NI support. Acknowledging something might be wrong with a product is just not part of their brief. They have sent me on ridiculous wild goose chases, wasted my time and money to buy items they claimed would fix my problem but did nothing.Quote:
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%).
Good for you it improved with the new hardware....Quote:
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?
I've tried this and nothing...Quote:
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
So the PC is on 2.6 and the CPU load display of traktor remains in green (not talking about the task manager)Quote:
Originally Posted by Nicky H
Yes mate, no problems at all...
Sorry for bad screenshot:
Attachment 13950
p.s yes that is 2 Unlimited in deck a :)
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)
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....
Weird...
Even weirder that it affects some machines and not others..
Some mac, and some pc..
Has to be a Traktor bug surely?
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.