Short lived 1.1.2 joy, back to 1.0.2

I was the one trying, till today, to calm pissed, disappointed users but now I am getting pissed. Yes I am patient but already so many months 4 updates and it is all ****ed up, that is truly pathetic.
Installed 1.1.2 today and thought "finally, they got it right, seems like now everything works smoothly". Till I have high pitched deafning, screaming beep coming out instead of music. First i thought something wrong with particular file, badly coded mp3 but when it happened on song that I knew is OK, took my performance notebook (still with 1.0.2) to check it and both files play OK.
I am not fanboy, betatester by passion, I pay for software that is suppose to be PRO, at least by name but this is not funny, this kind of **** happening when i work, be it club or bigger performance would be real disaster, damn public would have good reasons to sue me if someones ears would get damaged and such **** could really cause permanent damage.
This is real shame, such bug is no joke, it is not about some bloody effect not working or some noises or crackles. It is mega loud ear killing NOISE.
That is really ****ed up, dont know what to say more.

 

May i know ur computer spec?
Are use mac or pc?

I haven't try 1.12 yet...

 

lol... timecode cd?

 

Maybe. Depends if he is getting the high pitched 'beep' all the time or intermittently I guess.

 

sounds very much like the timecode vinyl or CD, lol

 

No, regular T. Pro on pc and I wont check it on mac, neither on xp, I dont even want to know what is exactly wrong with 1.1.2 since it is not my job, otherwise I could make software myself, I buy it so that I can focus on DJ work.
Somehow my NI patience is gone. One f...d update, two..... but 3 times ? Will use the 1.0.2 till something better, reliable comes be it Traktor Pro version that works or maybe Seraton Live.

 

I had this issue only once. It happened when I accidently unplugged my controller from my computer and plugged it back in. I tried numerous times to make it happen again but no luck.

To be a Pro in the digital realm you have to know how to troubleshoot your computer as well as being a Pro dj, that's just a fact of life right now. If you are unwilling to troubleshoot you setup I guess that's too bad for you. You'll still be p****d no matter what software you use.

 

if you dont want help great ..............if you trow us a bone

 

I have no trouble with my setup, TP 1.1.2 is the trouble.
I know how to make my sh... work even with the Traktor pseudo Pro - on 1.1.1 I spent several hours investigating, on the phone with support etc,etc. but now with 1.1.2, cut it short, " it is f...d so remove and use what works" 1.0.2 in this case.
It is just bloody 4 track playback software, nothing complex like Logic, Live or Protools, Final Cut or Photoshop. that they cannot get that together in so many updates surprises me.
I appraciate the enthusists who spend time betatesting NI, Ableton, Propellerheads and what not softwares, but I am musician not geek, it is not my thing.
When endorsing for some music instruments companies , they wouldnt ask me "how to solder better" ,or season the wood, my job would be to say how guitar and/or strings sound,feel and wear,not how much copper should be in alloy.
BTW. I dont think it is controller related, neither the soundcard- I did check it with different soundcards before reinstalling 1.0.2

 

@ Aviray,

All bickering aside, I would like to hear an audio clip of the aforementioned problem.

Also, please provide your system details in your signature or profile info.

 

Sorry to hear TP 1.1.2 is not working out for you.

I know some of us, at some point in time, felt the same way about Traktor like you're feeling right now.

Thanks for giving a bit more info.

 

I don't know if this is the same noise that I got during a broadcast at MixAddicts.com 20-03-2009.

It was very embarrassing!

Download (it's at the end of the sample) TSP Beep

For me I think it could be caused by two things:
1. I got MIDI Out selected for my A&H Xone:1D (I now only have MIDI In selected)
2. I used to use 256MB in cache size, then I read in this thread that it could cause crashes... :angry:

I'm using TC CD's and at the time of the beep I didn't touched the MIDI controller, it just happend in the middle of the mix...

I did a new broadcast today and everything seems to work OK

 

Yes sir, exactly that pitch. Only on some files (which would play normally, look normal and play without any problem in other audio app, mind you frm different albums there was nothing common that I would notice, no pattern as such). I could go without closing the application, to preferences and change to different soundcard and that beep would continue.
The reason I wrote is to warn/ inform fellow DJs, such thing can easily lead to getting beer mug or bottle landing on your head , I am glad I discovered it before going for job..
It is our responsibility/job that such sh... does not happen, how we do it it is our matter, we should know if we DJ for money, like I expect taxi driver to know if his brakes work. Since I did few hundred hours with 1.0.2 without issues then getting back to what works is obvious.,Even the previous version got me frozen GUI (keyboard and touchpad didnt react) once but I was able to continue set 1 and half hours more till the end using midi controller- this is still OK with me. Reason why I didnt use 1.1.1 was that it didnt read fades correctly ( NI support confirmed the bug, advised wait for net update) which is not "life threatning" but that beep thingy definitely is.

 

Yep I've hear this before.

It's a latency issue and it could very well be caused by the 256mb cache setting causing a memory leak in the application and then causing erratic latency problems.

It can happen when you enable keylock, invoke a looop, etc.

Please lower your cache setting to 128mb max and increase your latency slightly to see if the problem is cleared.

Also, please file support tickets and post your ticket numbers here.

 

By definition bickering is a petty argument.
I am always amused at the casual usage of this term on this forum.

This issue is everything BUT petty.

What kind of work-around is this?
Sounds like a programmer is sweeping his sloppy work under the rug by eliminating features.
Why implement 256MB in the first place?

Next up on the remove list will be Keylock, TimeCode or Cover Art?

 

No, I never had any soundcard on 256, it is 128 or less depending on the card, neither any keylock or loop on, it happens by simply playing some songs, which as I mentioned before , do not appear to have anything in common.
Nothing of that kind happened ever on 1.0.2 ( I tried same songs) on this or other notebook

 

No Lancellot,

It's a publicized bug, it's posted in the 1.1.2 notice because they want to fix the issue and inform users to prevent bad performance until the next major release.

 

That`s lovely but has nothing to do with the problem I described.

 

Is this a continuous problem or a random occurance?

 

No, I never had any soundcard on 256, it is 128 or less depending on the card, neither any keylock

quote



quartz refers to deck cashe size................................