2.0.2 ? Anyone upgrade yet? Thoughts? Impressions?

update does not fix the master tempo effect trick or the beatslicer problem, no mass load for sample decks, still got that disappearing wave form. update fail! lol

 

That's why it was advertised as a hotfix and not an update. It was really only designed to go after the showstoppers like the CPU issue with timecode. I'm sure an update will be released in due course that addresses some of the bugs.

 

This used to happen to me on my pc. Agree with lethal, its probably your graphics processor. I had to roll back my driver to the previous version to make it stop. Before that though, you could try bumping up your latency to see if that helps any.

 

hotfix 2.0.2 is working nearly perfect here.
now i am able to control traktors 4 decks with one timecode cd player with no pops and clicks.

even at very low latency settings 64/128 i don't have any buffer underruns even with everything filter effects timestreching etc. on.

the only underruns i get is when switching through my default layout via a midi knob of my mc6000? any ideas? also even with higher lat setting 1024, i get underruns when switching layouts via knob.

cheers
chill

 

Could be your GFX card speedstepping

 

sony vaio onboard graphics no options to adjust anything.

never had any issues when switching layouts before 2.0.2, in all other previous verions.

cheers
chill

 

Need some clarification here. Does the problem occur on when switching layouts with a knob or does it occur with Midi buttons too? Does the problem occur if you map a keyboard key? Is it only when switching to or from the default layout or just moving between any two layouts? What about if you go from a 2 deck to 4 deck layout?

Phil

 

i am working with 6 different saved layouts.
to switch in between these layouts i am using a knob. no matter if you switch between 2 or 4 decks, or any saved ayout, or simply from one layout to an other, sometimes i can hear clicks and pops doing so. before version 2.0.2 i never had any issues when switching layouts, in every release before the latest i was even possible to switch and cycle in between all layouts with no problems at all.

?

i have not tried changing via buttons though.

cheers
chill

 

Do you mean you use a knob and every time you move it, it changes layout like every step of the knob goes to a new layout ?

I have mapped this function of my x session pro midi controller and i have no issues. If you map it to another knob or map it to the keyboard, do you have issues ?

 

Anyone found the midi/controller icon at the top does not light up when you have a vestax vci100 attached? used to light up with 2.0.1

 

you mean the "ctrl" light ?

does the controller work even without the light ?

 

tested the following today...
even when cycling through the layouts via mouse, sometimes there occur bufferunderruns and you hear clicks and pops.
?

strange, on the one side i have to admit that i never had any better results with dvs than with the actual combo 2.0.2 + 3.0.0 audio driver.
it is even working very good with 1 ms buffer size 32 samples @44khz.

on the other side there are pops and clicks when changing layouts.

recognized the following even with 512 samles, which is similar in result to lower samplerates but just a bit lower cpu meter values...
during playback of a track (no matter if via timeode, or even just the audio 10 connected and no use of timecode or any midi controller) the cpu meter in traktor is inbetween about 10 to 20 percent. sometimes when changing layouts via mouse the cpu meter peaks into red zone and that is the reason for the pops clicks and buffer underruns.

done further testing please try the following, i guess that is the main reason the described problem, tested on 3 different pc systems....

128 and 256 sampes simply load a mix at least 60 minutes, press play via mouse no filter no effect no eqs, no timestretching, do nothing simply watch the bufferunder counter and the cpu meter, after several minutes, coud take up to 20, can't precisely tell the time cause it varies, the cpu meter starts kind of peaking every few seconds into red and therefor the bufferunderrun counter equals a kind of seconds counter. pressing play and restart playback or replay from cue, is bringing back normal behaviour to the cpu meter, probably start with lower sample values to see what i mean in a more obvious way. but it also happens at higher sample values.
?
tried the same thing with a regular track and a 1 bar loop. after a special kind of time the cpu meter starts peaking every few seconds to red. i guess that something after a little while is driving the cpu meter crazy.

just to let u know.... my pc is completely plain, just one prog installed, all optimizations done. almost everything is deactivated less than 20 running processes.
also reinstalled traktor and audio driver after playback of optimized image, same result as described above.
1.5ms with audio8 and 1.2.7 on same laptop.
---
can anyone confirm the same?

any solutions?

cheers
chill

 

what do you mean after a special kind of time ? and did you try the old drivers, to be honest i don't trust the latest drivers ?

 

tested with 3.0.0 and 2.9.8 beta and audio 10.
did not test with audio8 yet cause i have sold my old one will try also with audio8 from a friend.

after a special kind of time .... means that i can't tell the time, simply test yourself.... start traktor set 128 samples or lower, load a 1h mix, go have a meal, come back half an hour later and check the cpu meter and the buffer underrun counter.

cheers
chill

 

ok i have just loaded a 60+ mix in wav format and i am testing. Do you get glitches right away ? because i don't have any glitches at the moment ?

 

i am just using 320kbps mp3.
the cpu behaves normal in the beginning of a track, after several minutes, i would say check each ten, it starts jumping to red every few seconds.

looking forwrd for your report....

cheers
chill

 

Ok just for safe measure i always use 528 samples to get best results with no hiccpups and i am using the old audio 8 drivers 2.0.15. I am just playing it from time codes and then switching it to internal mode while track is still playing with no issues what so ever. The cpu fluctuates a little to maximum 25 percent i'd say and i am like 15 minutes into the track. As i mentioned my mix is in Wav format but my next test will be in mp3 format

@chill
I would like you to try it exactly like i have stated and please report back your results

 

can not test with audio 8 until next week.

simply test with 128 latest 3.0.0 no timecode and no midicontroller.
simply load a 60 minutes track press pay via mouse and do noting more just watch.

cheers
chill

 

yes i understand but i have not tried the new drivers and i think it could be a bad idea to use the new drivers since the old ones are stable and i have had problems with the newer drivers. Also 128 samples I believe are to low since I can only use a powered usb hub with my audio 8 since my usb ports or pc can not handle the audio 8 without a powered usb hub. I have spent weeks last year trying to figure out why my audio 8 would stop playing after a while, then someone at my local shop recommended a powered usb hub which cured the problem permanently so 128 samples is a no go for me. I hope you can understand that doing the exact same test as you did is actually not a good idea on my end but i can tell you that i am satisfied with the audio performance even if the latency is high and it does not affect my mixing one bit. Actually i am 30 min in my mix and no issues what so ever. This is why i hope eventually you can test it the same way as i have.

 

I had a similar thing. 2.0.2 was working fine while I was just jamming, but I came to record a mix and 10 minutes in Traktor crashed. NEVER had that happen to me before.

Reopened it and started off again, this time 5 mins in I had the loop thing. It was odd, no real glitching or dropouts, just like it was running a 2 beat loop and moving it forwards a bit every now and again. Controls weren't completely unresponsive, but only worked on and off. Switched back to 2.0.1 with the exact same settings and no problems.