2.1 status

wish id have never downloaded this update

using timecode is hopeless cpu is in red all the time so drops out every sec pathetic!

im using traktor scratch pro on a late 2010 macbook pro 13, 2.4 core duo, 4gb ddr ram

on 2.0.3 i had 4 decks running timecode with everything on and it never ever failed me once

im not happy at all

 

Check your latency settings, perhaps turn off multi-core.

If all else fails, run 2.0.3 which is still present and correct on your computer.

 

ive checked latency i have it 1.3ms thts why i bought a macbook pro was perfect before, ive turned multicore off still same

i shouldnt have to lower the latency tho strange how its was perfect before this update cant be tht much difference can there really

 

Far too low.
---

A lot more potential keylocking going on.
---

Raise the latency

 

ive never had any problems with it this low before tho

had 4 timecodes runnin at the same time and cpu never moved

wots the recommended latency?

it seems to be runnin fine on 2.7, im used to having it at 1.3 is there a difference?

 

To be honest I'm amazed you've been running 4 decks with timecode at 1.3ms.

Most people can't tell the difference at 10ms of latency, some turntablists will tell you differently. 2.7ms is still really low. It take it you're running your soundcard at 96khz?

 

no im running at 48000khz

just tryed it on 96 and cpu goes mental untill i lower latency to 2.7

you can really tell a difference when you use timecode and lower the latency spesh when scratching thts why ive always had it at 1.3

 

Would you class this update as essential? Bit dubious as to go for it now after readin this ha

 

...because it'll still be there

 

I would. No problems for me at all.

 

Hey guys! Was hoping those of you who have updated could fill me in on the specifics of these listed fixes -

* GUI tempo fader decoupled from Scratch and Tempo Bend
* Cueing accuracy of CD timecode fixed

Thanks for any info!

 

Just downloaded it and Im getting pops and crackles on windows 7.
Great!

 

As per the readme file on your hard drive, Windows users with pops and crackles should try disabling multicore

 

Yeah! 1.3 ms, is way too low. like lethal_pizzle said, I can't belief youve been running 4 timecodes! I usually have mine at 10.7 ms.

 

thanks, I'll check it out.

 

Had it at 1.3 since I bought my MacBook pro and it's never droped a beat till this update

 

Thanks for the info LP.

I don't know why the track etc audio can't be completely loaded into cache just like in T3?

It just seemed to be such a stable situation all round.

So stable in fact the once you saw the track had finish caching, you could unplug the media it was playing from and it would all continue to play no problem.

Peace.