TSP2 sux, yeah I said it!

OKay, so I have been a loyal user for a long time... all the way back to the first Traktor Skratch....even further for those who remember N2It...then stanton etc...

So I am really upset about the new TSP2 using audio8.

Can't use scratch control on deck c and d like TSP1.
The sync is all weird and warps the pitch when going from one deck to the other from internal mode to scratch control. Pitch control locked when in scratch control mode.

I'm too frustrated to elaborate or even describe the issues further... but why is it that if I want vinyl control on c and d I have to change the input setting for c to a... so dumb.
also I used to use input c on the audio 8 as my record in, but with the new way I can't do that.

Sample decks...bah... I'm going back to tsp1

You suck NI....are you trying to force me to serato....Come on... why change things that worked flawless....

ughhh

If any one cares, please respond....or did you just rob me of 50 bucks.....
this free 2.5 upgrade better be solid and functional like the rock solid tsp1

 

This is the reason I am still using TSP rather than TSP2. Because I have heard countless of complaints about it not being stable, problems here and there from other different forums and local users here. 1.2.7 is quite very stable to me and besides, I still have 3 pairs of timecode vinyl in different colors that have yet to be used. If I make the upgrade now, my time code vinyl will be wasted and won't work with TSP2 especially 2.5. So I'd rather wait for a really stable version until I make the upgrade. Who knows probably TSP3 next year? Hahaha! :lol:

 

stick with what works for you... at the end of the day stability is the MOST important thing for everyone..!
Are you listening NI..!

 

As far as I am aware your old timecode vinyls will still work. Do a search there a loads of threads explaining it.

You don't need to buy an A10 the A8 will still work fine. Unless I have missed something?

I have found TSP2 to be very stable but I am just using two decks.

You don't have to use the sample decks or remix decks.

 

ok mate, then there's no sense in opening a thread.

you either put down your language and write down what your issues are so everybody can help you work'em out or you stop it right here.

p.s.: TSP2 working rock solid on my 4yrs old laptop. 2 track decks, 1 sample deck, with key lock, FX etc pp.

p.p.s.: dk22 is allowed to elaborate his issues in this thread although he violated some forums rules by the rudeness of his initial posting. everyone who cant help: go tell your hairdresser.

 

from day 1 i was able to use time codes on 4 decks with the audio 8, check your inputs are routed properly, you can route 2 turntables to use 4 decks and it works, now ya i believe you that in 2.1.2 the sync with time codes is all messed up, i tried to address this issue but no one responded. So I use 2.0.3 and can't complain.

 

Tsp 2 doesn't work as well as tsp 1 when using 4decks and vinyl control. I got 4 decks to control my 2 turntables to work but the way you have to put the I inputs is silly and not as functional as tsp1.
And hey. I paid 50 bucks for sub par software upgrade. Sorry if I don't feel like writing a novel to help someone try and figure out what I spent countless hours tryin to figure out. I'm not dumb with this stuff and the solutions are not good to get stuff working.
Solution. Back to tsp 1. End of story. And yes tsp2. Is a sub par 50 rip off. Sorry moderator..
I will however try the suggestion of versions posted by mastermc. Thank you for your response. Sounds like you may have a solution. I find it funny that in a way this proves the software upgrade is bad. When you have to resort to legacy versions. . I'll give 2.0.3 a go. But after that. Relying on tsp1.

 

can you elaborate? didnt use that function for a while so what changed?

well, but you felt like writing a novel with a rant with ...uhm... questionable language. aha.

i keep it open here for a moment to give you the chance to explain your issue so i can either forward it or help you.

 

Questionable language? Huh? The truth? What?

I'll wait until the 2.5 upgrade and see if they've recognized the problem.
Like i said earlier. Solution: continue to use tsp1. A solid piece of work that NI developers should be proud of.

 

ok, since you refuse to explain what your issue is, this thread is now:
*closed*