How to kill someones ears with TP 1.1.2

Since there was no response to my post about beatgrid/noise issue in tech section,
http://www.native-instruments.com/forum/showthread.php?t=92006
I am posting my new "discovery".
It happens only in 1.1.2 not any earlier version.
1. Load new track, which TP couldnt auto analise = reads BPM 0.00, if you dont have such tune, just type/ enter 0.00, the effect will be same.
Hit monitor/cue button.
I had this beep/noise issue right on day one of release of 1.1.2 but since there seemed to be no explanation also support couldnt figure it out I just moved back to 1.0.2 without investigating more .
I upgraded recently to 1.1.2 to be able to test daScratch and then noticed that mysterious noise problem. It happens only on cue out not on main and is obviously click related. I noticed it that when you perfectly align the grid that obnoxious noise rings, today found out that it is instant on 0.00 BPM tunes and just now while writing tested the rewriting BPM of any tune to 0.00 gives same result.
I tested on 2 computers, XP and Vista have no access to Mac at the moment.
Would be great if somebody could check it on OSX.
Warning, set the volume low, or off before you try, that beep is extremely loud.

 

That nasty beep comes if Traktor is playing a track with 0 bpm and you have the CLICK option turned on in the master section AND you have the headphone/cue button selected. Basically trying to do a tick but instead of twice per second or whatever according to a set bpm, it's trying to do an infinite number of clicks because it's a 0 bpm. I've had this since the very first beta of Traktor (Scratch) Pro.

 

So it is on any OS. Your explanation makes sense, at least to me. However it does not happen on 1.0.2 and I dont think it was on 1.1.1 either
Did you try what I described in other thread- same conditions but with defined BPM (not 0.00) , vinyl mode, track playing and you try to nail the beat. Closer you get to the ideal spot the same buzz happens and once you nail it exactly it will/can -if you hold it there- buzz ad infinitum. It means that in all practicality you cannot correctly beatgrid unless drive yorself nuts with that buzz.
I did today around 100 songs, real pain because have to stop, or off the cue button. My problem is that now got taste of good things of 1.1.2 over 1.0.2 so I am not keen to roll back.
Any more info from you, and anyone else will be very valuable since I will talk to NI on Monday and more info I can pass to support, easier to fix that thing before next version release.

 

Maybe it was only on OSX on 1.0.2 cause I know I bug-reported it a while back then figured it out along with a couple of other users.

And yes, what you described is a perfect way to get the buzz. Basically I have to analyze first OR turn off the tick until after I've placed the grid and tapped/manually entered the tempo.

This only seems to happen to me when it's an acapella that Traktor has problems mapping the tempo on, or if the track has a huge intro/outro that screws up the tempo reading so bad that I have to manually correct it. With the number of tracks I have I'm glad I don't see this often.

If you think this is bad, try accidentally leaving the ticker on with vinyl timecode control and scratching back and forth across a beat marker cueing up the track....with a pair of Yorkvilles blaring. I think I actually made someone's head explode a few weddings back....we'll miss you, drunk uncle Jim.

 

No sh... it really happened? That was the reason I panicked right after few hours of using 1.1.2 and rolled back to 1.0.2 cause any individual or group would have right to kill me or worse for exposing them to that noise.
Isn't it only happening on monitor/headphone out ? It is not much of consolation but it means only DJs are potential victims not the public.
I am curious what NI will tell me tomorrow.

 

If you're using external mixer mode and you've got the headphone/cue button selected for that particular deck AND you've got the deck CLICK on, you will get this.

I bet I know what NI will tell you (same thing I would)....

Turn off the track click, otherwise even if you don't hear the beep/buzz, you'll hear the click click click on each beat.

 

Started the week with good deed. Called NI, explained, the bug was reproduced and forwarded to developers to fix it.

 

Awesome....my bug never did get resolved I think I closed it on my own. Well done aviray. Next step, Aviray-branded Traktor thongs.