Traktor 2.5

[rotebass]

:shrug: I just really don't get the whole "its a public 1st release so don't use it" defence of TP2.5. I don't really care that much TBH, I'll wait til the next release and once the remix deck mapping is opened up.

I'm not saying it's right, I'm just saying that it is just the way it is.

I'm not sure I even care about the remix decks TBH, still considering a Launchpad and Ableton, it's on the list behind a dozen other gear purchases ATM.

[scamo]

I'm going to have to join the "oh shit, it has real issues" group. But thankfully, I don't do gigs....yet.

My first impressions of 2.5 are very reserved (especially since I don't have an F1 either). I am sort of noticing performance improvements in some areas, but then have some issues in others like glitchy sound, when starting and stopping samples in the Mix Decks. This is a no-go for me and my Windows i3 setup. I can't imagine someone with a Core-Duo system even thinking about working with the Mix Decks and effects. I am going to play with my settings to see if I can get rid of the glitches, but if I can't, it would be a terrible step backwards for me.

And the sync issue is a total no-go. 15 minutes into a mix and finding there is no real sync on a track with several beat markers is like, "Oh my god! No way dudes! Are you making me go back to having to beat match on purpose?" LOL! Another step backwards.

So yes. This is a public beta and NI would be smart to start doing true public betas instead of releasing gold versions with serious problems. It would help their reputation quite a bit IMHO! As the saying goes, two steps back to make one giant leap forward. It is always that way, you just have to call it a proper name. The steps back are fine, if you aren't calling them the giant leap forward and NI seems to get this wrong every time.

There is also a new Windows driver for the S4, 3.0.2, which doesn't automatically get installed with 2.5. The 2.5 performance totally sucks with the older 3.0.0 driver, so don't forget to install the new driver too, as I found it improves the performance considerably. There are just still some issues in other areas that need attention.

I will continue testing.....as it is not a gold version and hope NI will release 2.5.1 very, very soon.

scamo

[DJWORX]

I have no pity for anyone that installs a major update before a gig, software 101...

Well said. Using a landmark release in any mission critical scenario is DJ russian roulette. As we should know by now, newer does not mean more stable, especially with a whole new workflow shoehorned into the mix. Software companies release things with the best will in the world, but they cannot replicate every scenario with just a relative handful of beta testers.

Sandbox that new release for home use only for at least a week, maybe even a month. Hammer it into submission while keeping an eye out for bugs, especially in the online community. Then and only then should you consider using it for playing out.

With software, assume it's buggy until proven otherwise, especially if your mortgage depends on it.

[oliosky]

wow there is some management speak in that post Gizmo

I'm just gonna focus group and brainstorm my situation to determine whether my market location with this landmark release is, or is not, mission critical and if I have the capacity and resources to effectively sandbox the current release at this present time without affecting project objectives and quality of outcomes... Should we conference call again a week?

[DJWORX]

Actually, there was more tech speak than management speak in that. But the last line does rather sum it up succinctly.

[rotebass]

A drum buddy of mine summed it up pretty well, it would be like switching from Remo to Evans heads and then playing a show that same night, not a good idea

[JesC]

Dang! were not worthy...Gizmo came across the web to comment.

personally im still having issues with my setup, anyone else using the DVS?

[djlotus]

I'm using DVS JesC and I have encountered a few strange issues.

I am having this issue where I will get random acceleration in the speed of a track which lasts only a second or two. It sounds like I am speeding up the record. I can't for the life of me reproduce it purposely.

I also have random switching between absolute to relative when I pull the needle off the deck.

Also, when scratching, it will randomly skip ahead in the track without the needle jumping.

Good news is my MK1 vinyl still works.

[hola amigos]

trying to roll back to version 2.1.2 anybody know how on a mac? I clicked on the 2.1.2 folder and started to open more folders and ended up copying my files for roll back, now how do i access the roll back? For some reason its saying my "Sample tracks" that come with traktor pro 2 are corrupted or missing files. And i like to use the sample tracks so i need to roll back to 2.1.2 so i can actually use my sample tracks.

[JesC]

I'm using DVS JesC and I have encountered a few strange issues.

I am having this issue where I will get random acceleration in the speed of a track which lasts only a second or two. It sounds like I am speeding up the record. I can't for the life of me reproduce it purposely.


I also have random switching between absolute to relative when I pull the needle off the deck.

Also, when scratching, it will randomly skip ahead in the track without the needle jumping.

Good news is my MK1 vinyl still works.

Thanks man, I'm having the same issues as you. Are you getting a LOW input on the timecodes cause mine is under 1/4 of the VU meter, and Im using the MK1 timecodes, mine switches from REL/INT rapidly. Im tried setting my mixer on phono/line and changed the input on my audio 8 to phono/line/timecode. Also it reads my time codes on Side A with a 15min run time & SIDE B with a 10 min. Plus my calibration is going nuts. What Im getting is the timecodes jumping from 33/45 speed and i need to hit calibrate to get it back to 33 rpms