Who thinks we'll see Traktor Pro 3 soon?

[Glitchwerks]

Hmmm where do I start?
For me it's all the double handling.
If iTunes integrated directly it would be awesome.
But for example, if you "star" a track in Traktor it won't show up in your iTunes playlist without the use of a third party app ( I use "Trainspotter 2").

That's more to do with iTunes not having active monitoring of your folders. If I rate or edit a track in Traktor, it shows up immediately in Foobar (which does have active folder monitoring) unless the track is currently loaded in a deck. As soon as a new track is loaded, it will immediately update.

[Notanon]

Have you heard of Xone:K2? It has roughly the same ammount of buttons, knobs and encoders of this picture

Anyway, TSP 3 would be great if they spent some time thinking about how to make simple mixing better.
Ok, remix decks are cool and maschine is awesome, but:
- Elastic grids would be VERY useful.
- Tracks that cancel others would be good too (when you play one the other gets the "played" status), so you don't play the same vocals twice or more...
- More colors for hotcues, great for the ones who like to over-cue tracks hehehe

Yeah, have considered the K2, but a bit mixed on it, mainly the layout. Anyway, I just think in terms of modular units, NI could do a bit better in that regard. Not all of us particularly want a S2/S4/S8, particularly if we've already got a mixer or want a slightly more portable setup that doesn't require a mixer section if we're using a club mixer at a gig or wherever and there isn't enough width behind the booth for a S2/S4/S8 (which is a problem I see on a regular basis).

[Scalage]

I think hotcue naming would be a great addition. And, FWIW, I've always preferred Serato's UI.

I also think that it might be time to do a serious code audit. There's no reason why adding several mappings for controllers should make the settings window that that long to open.

Naming of hotcues has been around for much, much longer in Traktor than it has in Serato. I agree with the loading issue, it's really irritating to have to wait for the mappings if you just want to check your routing.

[Jester]

Merged (Same Topic)

[deathy]

Naming of hotcues has been around for much, much longer in Traktor than it has in Serato. I agree with the loading issue, it's really irritating to have to wait for the mappings if you just want to check your routing.

To be fair, though, the naming of hotcues in Traktor is almost completely useless. I'd like to see the names in the view.

[Karlos Santos]

Named Cue Point that appear on the waveform has been a requests for years and years and it's one that I have supported. It should be implemented.

However, the request to have custom colours for cue points will probably not happen. I know people wont like this but, NI dont like adding features that can confuse users. A Load Marker is Yellow - period. It's explained in the manual. If it was any colour you want then it could cause confusion. If you don't like that answer - tough. It's how it is. I cannot see NI changing this.
I think there should be 3 or 4 extra colours that people can chose for their own custom markers but all other standard cue points should remain the same colour as to comply with the manual descriptions.

AFAIK When you open the Preferences window Traktor reads the traktorsettings.tsi . If you have multiple tsi then Traktor takes longer to read the tsi and thus open the window. It's a pain. I've actually backed up my master tsi and deleted all the controllers I don't use regularly as it was taking forever to open preferences.

[Daniboy]

I think there should be 3 or 4 extra colours that people can chose for their own custom markers but all other standard cue points should remain the same colour as to comply with the manual descriptions..

That would be enough, at least for me. I keep using fade-in and fade-out markers for things that have nothing to do with fading.

[mostapha]

Yeah....opening my settings window with JUST the factory mapping for the ddj-sx is unbearable. As a result, I just don't use it....which means I keep Serato DJ around to spin that way.

....which is fine.

But making that process more efficient would be preferable.

[dj wo k]

(for those who want to route traktor into maschine it's simple and requires jack pilot ...)

[Tada Tadam]

64 modifiers and 4 condition slots.

I totally agree, or even better let them make it possible to use every functions state as "modifier states" in other functions
Like the deck A play = on but then for every button, in that case 8 modifiers would be plenty.

and very very please OSC data?