Official Traktor Pro / Traktor Scratch Pro questions thread

will the trakor pro work with the behringer bcd3000?

 

Yes

 

Ahh fond memories of gigging in Thailand are flooding back to me now. The beaches, the tan, the strangely butch hookers......... hang on.......those aren't real women are they? WTF!

Ah the laughs I had watching those blokes who'd had a few too many not realising that which was plain to see!

Adams apple anyone?

 

Will it be possible to install both Traktor Pro and Traktor 3 at the same time? In case I dont like pro as much I can just remove it again.

 

I think isnt problem.. Traktor 3 using own directory to install and own directory for settings.

 

My first post on this forum and my question is :

I want to buy tractor scratch to do my job.
You suggest to buy the new product or just buy the old and make the upgrades?

How much it will coast to take the old wt t3 and make the update free on web and how much is the original price of the new?

What y suggest?

 

Not more thongs. If I eat another thong, I’ll end up looking like one.




Oh hang on, that’s not right….

 

really good point, I'd like to still have traktor 3 installed just in case before I move across fully to Pro....Can I Moderator confirm that Pro won't ovewrite the existing install of Traktor 3?

 

Its already been confirmed that you can install and remove pro separately, see phil's post about backing up you music collection first though.
http://www.native-instruments.com/forum/showthread.php?t=72760

 

"TRAKTOR PRO is completely flexible. You can use your mouse and keyboard or a MIDI controller—all major controller brands now feature pre-mapped yet fully customizable MIDI assignments for TRAKTOR PRO."

** Ok - I keep asking this - and I have read this (haven't found any other information elsewhere yet)....

Will the Denon HS5500 platter spin with this new release of Traktor Pro?

When it says "all major controller brands" does that mean Traktor Pro will work with the Vestax VCI-300 - as this is what it sounds like, but just want to confirm.

Thanks!

 

Midi

I Spoke to someone about this the other day. I Have a M-Audio Xponent Controller. And asked if the new version of Traktor Pro will nativley support it. Instead of messing around with TKS files that someone else has managed to get working with other Traktor program. His responce was No there was no native support for this controller and that you would have to map the controller yourself i asked why? other DJ Products support the controller without any problems. This software is quite expencive and some time should have been spent on mapping these controllers so that they will work when using Traktor Pro.

 

I agree 100% on this if they are supporting the vci's,bcd and others. Why not Xponent?
But something tells me we will be happy come nov.1 we will see.

PS I remember reading the the dennon HS5500 will be supported in what is now late 2008.

 

There is no mention of support for Xponent. There is support for the Dennon HC4500. I do not know for sure that the displays are supported but I think _maybe_ not. I've asked for the support message to be updated several times.

Phil

 

Xponent

If The Xponent Is not supported in Traktor Pro Will The TKS Files made by someone who does not work for Traktor work with the Pro version. If you cannot support this hardware then i will not buy and stick with Virtual DJ as the controller is fully operational . Why Why cannot Traktor Team get this to work when other DJ Softwares can? this is getting really annoying

 

Why is it NI's responsibility to develop and test a competitiors product support?

TKS files are not supported by Traktor Pro .TSI files are what is supported.


Phil

 

Yeah, I can see what you mean about the Xponent - since that is more connected with Torq and yes, Torq is the competitor. Hopefully that is not the though with the VCI-300 because it works with Serato's Itch : )

You see - Vestax (I think it was them, might have been NI folks or Ean for all I know) made such a NICE .tks file for the VCI-100, it sort of spoiled people I think. The expectation is there for native support on all these new controllers and there are a lot of them. I am just hoping for VCI-300 utilization similar to how well the 100 works with Traktor with the .tks.

Anyway - I think I might have read something on DJ Tech Tools that said there will be full support to make the VCI-300 able to work - not sure about if there will be any midi-programming already done...or if I will have to do that from scratch....

As for the 5500's -- I just would love seeing them spin natively....meaning not having to use Traktor Scratch and a dvs system because it is just sort of silly, and it would be nicer to be able to use Traktor PRO (no DVS concerns) and all midi spinning support...

 

Xponent

So why are Traktor Pro's Website saying that All major Midi Controllers are fully supported when in reality they are not. This excerpt is from Traktor Pro's website MIDI mapping of all major controllers on the market. What they should be saying is what controllers are supported and which ones are not. The TKS file that some person made for Traktor 3.4 is working with Xponent Will this not work in Traktor Pro? Why should i buy this software and spend another 300 to 400 pounds on a controller when i have a very expencive piece of hardware here.

 

If the displays still stay dark this will be the status quo.

 

Use your noggin for more than just beating up walls :S
Traktor = NI, Xponent = M-Audio , Products = Competiive, Answer = Obvious!
Buy it or don't its your choice, or Make your own .TSI file. forget TKS thats so Traktor 3. Its not rocket science, hell even I can do it that means you are a shoe in then.

 

I don't want this to end up in a forum fight. Yes i am a complete novice when it comes to making Midi files i leave that to the professionals or to people who know what they are doing. I just expect a company as well established as NI to think about what controllers are going to be supported and not to lead customers into buying something that may not work for them. This is all i'm going to say on this matter.