Cross 1.71 Random single glitch while mixing, ruins a mix

[Hannes]

I think he means there´s some issue with the buffering, so the tracks gets corrupted frames on load.

[ldorio]

I think he means there´s some issue with the buffering, so the tracks gets corrupted frames on load.

Yeah, that's what I mean

Funny thing is, this has happened over the span of numerous different versions. I always hope that a new version means that the problem has been corrected, but no luck so far.

[Hannes]

That´s really crazy

[Support@MixVibes]

Really strange in fact because it happen on whatever computer you own and with all version of Cross.
Do you use any memory scanner, booster, analyzer ?
What is the basic package of application you install for your use ?

[BennyB]

Really strange in fact because it happen on whatever computer you own and with all version of Cross.
Do you use any memory scanner, booster, analyzer ?
What is the basic package of application you install for your use ?

I think I have an idea:

How do you set Cross's memory usage? Is there enough allocated ram space?
go to Preferences/general, and on the buttom you'll see "Audio Cache (% RAM)".
If it low, maybe it can cause certain tracks to not load complitely into memory, and this might couse the glitch.

Defaultly Cross sets a certain amount of memory space... maybe it causes the problem...

Try this:

set the pagefile size smaller in windows, and try to allocate more RAM space for Cross

Or: Allocate less RAM, because some part of the cache might be in the virtual memory of windows, and as we know virtual memory is on the HDD, which has low access time.
If Cross can't access those parts quicly, it might cause Cross to restart the track... and since the place of the loaded track is constant in the RAM (also in the virtual memory), it is not moved, so the problem can be reproduced.

And as I see, Cross is designed to read directly from RAM, but it has no controll what windows does with the cache once it is set.