MIXVIBES Dj Community old forum

Hello.

I just fired up Cross last night. I am using a Windows XP laptop, Numark Mixtrack, and Native Instruments Audio 2 DJ interface in ASIO mode.

Hopefully I can explain this right. Let's say I have a track loaded and not playing. If I have the Mixtrack in scratch mode (scratch button illuminated) obviously I can move the jogwheel back and forth and hear the track scratching.

If i turn off the scratch button then the jog wheel is set to change the pitch. If I move the job wheel with a track that isn't playing, I get a horrible long buffer error, glitched out modem sound. This only happens with a track that isn't playing. If a press play first and then use the jogwheel, the song makes tempo adjustments just fine with no glitching.

I raised my latency up to the slowest limit and it made no difference. This continued to happen.

Does anyone have any ideas about this?

Thanks.

can you monitor the ram/cpu usage when this occures ,, curious as to the spec of the computer you are running any other info to help us figure out what going on will help

Windows XP Home

Intel Core 2 Duo T5270 1.4GHZ
2GB Ram

Yeah, not very powerful, but I usually never have any problems with it on any DJ software or music
making program. I also did a long list of the usual XP perormance tweaks for music use.

I will try to do the CPU test when I get home.

Maybe I can provide an audio example also.

the more info the better if you can get the oppunity to try the same setup on a bigger spec computer and see if the same occurs i am using a slightly bigger system,on vista and barly keeps up with Cross and all the new features,, lets us know

If i turn off the scratch button then the jog wheel is set to change the pitch. If I move the job wheel with a track that isn't playing, I get a horrible long buffer error, glitched out modem sound. This only happens with a track that isn't playing.

This is a normal behavior called cd mode (try on a cd player).
The artefact your are reffering too are probably because you're not in speed or hybrid mode and the master tempo is trying to kept the key.

I had kind of thought it could be normal and became aware of the hybrid and speed that you mentioned just last night while testing.

have you testedit using the proper settings,,(something i didnt know) if works as wanted then will close this as solved

Well it seemed to still glitch out like that when I changed speed or hybrid, but that may be because I had key lock on

But yeah, I guess you can go ahead and consider it solved.