Quiet in here ....

Seems very quiet here for a beta program - does this mean no-one is finding bugs or is it more that no-one is testing things? The Serato equivalent is really busy with updates pretty much every week

Mike

 

2.7.4 is running without issues for me, tested it on desktop and laptop extensively. Only thing is the multicore support on desktop and the blurry waveform on my laptop(running fine on 4 cores)

 

it looks quiet indeed, but what we don't know is how many people is actually trying the beta, just NI knows how many downloads it has had. in my case i've tried it for a few hours and had no surprises either, nor good ones neither bad ones. i kind of expected an improvement on speed on certain tasks, for example loading the itunes node, but it doesn't seem to be faster.

one issue that i find important to address is the overwriting of key text, it drives me nuts. until the final version is released or NI states that it has been looked at and asks us to test this specific issue, i won't be able to see if this has been solved. another thing i would like to see implemented is to completely separate the key analysis from the standard analysis routine, and this hasn't been mentioned either.

at least this testing has raised attention for an issue that could potentially hang traktor, and that's good.

 

analyzing seems faster but consitency check is still slow as hell . It's seems that n.i. is starting really slow with their 64 bit version .

 

I am also in the serato beta.. My guess is that serato has much more users than Traktor. Also i hate to say this but serato has much more interaction with the users on the their forum and releases than traktor. Hence you see a much more information on that beta vs this one.

I deleted the beta after find the explorer crash but i also notice consistency was slow. The Key issue also needs to be addressed. Was it fixed in the any of the 2.7 releases? I totally forgot the check and test that.

 

Since you guys mention the consistency check... it's one of those things I find rather vital, but the implementation (speed) and the workflow of updating DB/file inconsistencies (file rename, new location, etc) gets my blood boiling every time I have to use it in Traktor.
Is that still the same in 2.7.4 ? As in:
- you get a Windows explorer pop up in which you can paste a path (which is good), but only if you select a single file (and this is bad, imagine going through 100s of files this way...).
- but with multiple files, the windows explorer pop up does not have an address bar, and always resets to /user/documents/... both of which are major annoyances for me.
- selections & task triggering in the Inconsistency report are awkward to say the least (no re-sorting, no filtering, no shift+ selections and a few other things)...

Has any of the above been addressed ?
If always feels to me like the consistency-check was implemented on the first release of Traktor, and left in a half-arsed, 'barely working' state ever since, just going by how annoying it is to actually use it as a tool... (this is just my opinion...)

Churs.
c.

 

I'm testing right now......and yes.....the sound quality was ok in the beginning.....but after an hour.........it's degrading,.....or my ears don't function properly......listen for yourself.....

https://beatbravo.com/heinrich-von-s/live Is it me? Or do you also hear it? I'm curious....

 

The volume is constantly changing......sometimes it spikes in the red...without adjusting from my side...

 

i have always thought that the consistency check is helping halfway. it tells you about problems you have but doesn't help you much to solve them, besides analysing missing stripes or non analysed tracks.

it would be great to have it isolate the reported tracks you want to work with, in playlists.

i agree that its functionality should have evolved from its initial implementation.

regarding your question, alec.tron, there have been no changes in the consistency check in this beta version.

 

maybe it'd be better to open a new thread for what you describe, it's an issue nobody had reported previously.

 

Exactly, it is helping and it's a fundamental functionality...but it is half-way implemented only... which is better than not at all
Yet, I would have tools or python scripts to feed it direct paths for finding inconsistent files as well (as you can't just give it the library root path.. as I found out when Traktor constantly locked up trying to locate 100 files inside of a 40k+ library...), yet, I have no way to get there quickly as there's no API, and when doing it painstakingly by hand (we are on a computer after all... so automating tedious tasks is what they're actually really good at... ) it restarts in /user/documents/ everytime and does not have an address bar, so I am forced to hand-navigate to the desired location. Utterly silly this.
c.

 

this may be because serato had much more things to implement to be up to par with traktor. it seems they've commited seriously to this task seeing the last two years evolution of both software implementation and hardware partnerships.

if things don't change here, the day could arrive that traktor is no longer the best dj software.

btw, no, overwriting of key text has not been addressed in any 2.7.x release yet.

 

I haven't installed it as it doesn't fix the file compatibility issues introduced in 2.7.x. I'll be sticking with 2.6.8 until such time.

 

installed crashed two times, wrote email to the support. Expect no answer, hope they can work something out from the log.

 

I have only been able to test on my Mk1 S4 on 64bit, still waiting for 64bit drivers for Pioneer DJM-T1, Denon X1700, Numark 4TRAK ....

The 32 bit version hasn't improved anything as far as I can see, the multicore bug is still there, slow consistency checks and track loading time has increased for some files, it won't even play others (2.6.8 is working fine).

 

Has anyone tested on Mac ?

 

yes i have, my experience with it is explained in an earlier post.

 

Thanks did see that u had a mac till now , anyhow I also had the problem of traktor overwriting keys and I fixed it by changing musical key settings in analyse options to Open key as the display option and written to file tags key text ect.

 

I think the Serato beta gets more responses because the company interacts more, I don't think it's just cos they have more catching up to do. Have to admit I was really surprised to see NI implement 64bit in such a minor release rather than 2.8 or even 3.0 - I expect the marketing people aren't happy as "hey - we've gone to 64 bit" would be a major selling point

Mike

 

I've been playing around with the 2.7.4 beta for a few hrs (about 6 total over the past few days).

The audio does sound much better. My CPU load is way down . I can also enable muticore support with no issues (acually lowers my CPU meter by another 10%).

The only issue I have is when I try to load the software without my Audio 10 connected. The program crashes on loading - looks like it's as issue with ASIO4ALL driver (I have a second OS that I use for prepping tracks/messing around that I don't normally use when I'm actually spinning - ASIO4ALL is good for this).

All in all I'm loving the 64! (I have 8gb of RAM)