doubts before install

hi,

it may sound as an obvious question but, is it still possible to install this version while keeping an earlier one functional?

won't it overwrite the current S4 or other NI device's drivers with 64bit versions and make these unusable with 32 bit traktor versions?

another doubt is regarding the multicore "hack". it is specified to create the txt in the "home" folder. does that mean the folder where traktor.exe (win) or traktor.app (mac) are?

thanks

 

good questions.... i happy this is out but my confidence with NI is at an all time low.... i downloaded the update file and than..instead running it really had to think this out. This is a beta.

Maybe we should wait until Carl Cox is using it.. Bottom line back up and proceed with caution.

 

haha exactly... i have the downloaded file too, and i'm really curious to see what improvements this switch to 64 bit represents.

searching/loading the collection/itunes should be faster, i guess.

but also because this version seems a quite big step forward, i'd like to be sure there are no loose ends and i can test it safely without putting in jeopardy the "production" setup... i just have one computer

 

well, you're right and thanks for your suggestion.

however, the questions regarding backwards compatibility and ability to run several versions side by side, will be still valid when the next release of not-beta traktor 64 bit comes out.

i guess i'll have to leave it to somebody else to verify.

 

Hi, you can install the public beta and still use the old version from the Backup folder.

 

Hi @Sander @ NI , thanks for your reply.

Does your answer apply both to windows and osx?

 

Yep..

 

great, thanks!

 

another question regarding side by side install of this beta. does it mess with my library when analyzing/gridding tracks under 2.7.4 and im using 2.6.8 for productive use?

 

Hi,

We didn't update the collection.nml so the answer to that question is no but since its a beta its of course at your own risk. When you start 2.7.4 and choose to import the previous collection it will copy all files to a new folder.

Best
Sander

 

so that means, tracks that i analyze/grid/etc under 2.7.4 do work under 2.6.8. means it's downwards compatible?

 

When you add new track in 2.7.4 and then load it in 2.6.8 as a new track you have to analyse it again since the analysis information is stored in the traktor user folder and is version specific.

 

Cue points and other meta data stored in the tags of the track are being recalled.

 

Then why does it create a new file and an outdated collection file when you use 2.7.4 with a collection file from 2.7.3 ?