MIXVIBES Dj Community old forum

Hi,

Since using version 3.0 of Cross I have issues with manual loops.
I use timecode CD's in absolute mode and often create manual loops.
When doing larger loops, like 2 or more beats, it often happens that these are no longer seamless.
You will then hear a small silence at the end of the loop, it does not happen with every loop so it is unclear what causes this but it is fairly easy to trigger.
Smaller loops, like 1 beat, work without issues.
This same behaviour also occur in the latest RC.
2.6 does not have this issue so my cd players and the cds are fine.

Regards,
tb0ne

Hello,

This is a typical audio buffering issue: when Cross can't decode the whole track in memory, it streams it from the disk, and the decoder is not always fast enough to fulfill long jump requests.

Cross can't decode in memory either because the audio cache setting is not set to max, or the file is really really too big.

Then, set this setting to max (don't try in-between values, they are basically useless) and let us know.

One more things, the buffering issue is emphasized by the use of Master Tempo. If you switch to Speed mode, you'll hardly ever hear it again, whatever the audio cache setting.

Cheers,

Hi SylMV,

Thanks for the feedback, i will retry with the setting on MAX and see what the effect of the pitch setting is.
However, why does this never happen with 2.6 and why is the cache setting there if its useless?

Cheers,
tb0ne

The behavior was the same in 2.6 but probably either you changed the settings by mistake or there were a bug while migrating settings from 2.6 to 3.0.

The cache setting is not useless, but it could be a "on/off" instead of a continuous value (inherited from older Cross versions).

Right, the audio setting was set to 2%, both in 2.6 and 3.0, my machine has 4GB RAM.
I tested with these settings, 2.6 does not have the issue while 3.0 has.
Cranking it up fixes it in 3.0 however.
Is 3.0 more latency sensitive because of the new features and have I balanced on the good side with 2.6?

let us know how it goes and if you get the time /oppunity to ring out the r c version 3.1 , this will futher the performance of the software updates , and the software as a whole