MIXVIBES Dj Community old forum

this is what happens after analysis and trying to quite Cross.
took about 4 minutes to close Cross.

the monitor pic is after analysis was finished for one hour.


also song load seems to be wrong somewhere with cpu-spikes of over 60-70% when heavy scratching and fx only need 25-30%.

Ok after 24hours here is what I have :
- select all (89k tracks)
- right click 'Analyze all'

I've got the same thing as you :
- color wheel
- cpu spike to 150%- Cross doesn't respond bla bla bla...

I can't do anything in Cross, but in fact Cross is working because i can see the number of files increasing into the peak folders.

After a few minutes, Cross release the pressure and give me back control over it.
Same things happened at the end, while writing/saving covers/database.
Not very comfortable but the application still hang on strongly and doesn't crash.

The cpu spikes can only be viewed while into these states. If I open a new session with the same huge mediabase (already analysed with full covers) and I can't reproduce this.
So I guess only preparing collection can be painful, performance shouldn't be down once done and in a fresh session.

These issues are still the same about the collection performances while or after building/writing.

that´s correct, i was just surprised how long it keeps writing, but no crash, so basically that´s ok, but even in a longer session (with all analyzed) when lots of artworks are being cached the cpu-spkes on song load come back for me.

I set the buffer-latency so that there´s no glitch when scratching one deck, browsing the dock/lists and applying a long brake-fx on the second deck.
For me that´s 64 Samples, but for security I use 96 Samples and after a while it starts glitching on songload but on nothing else.

Support@MixVibes wrote:Cross doesn't respond bla bla bla...

btw love that line

We know where is the flaw into the database management, just need some time to fix this.