MIXVIBES Dj Community old forum

I have the repeating problem that Cross crashes frequently while analyzing. The only constant I can see is that after the crash there is always a track with the status "corrupt".

The frequency would be like once every 25 to 100 tracks.
It happens in various circumstances, like tracks from hdd, tracks from local USB connected external hdd, local network connected hdd, remote connected hdd (max 3mb upload).

It happens while other applications are open, as well as when "no" application open. With Cross playing and without Cross playing.

I cannot find any problem with the tracks. The problem is not new to me, went over this with Charles in July (and have not reïnstalled my laptop yet as Cross is the only crashing application). I do have the latest drivers/firmware for the laptop/components installed.

The "corrupt" tracks are mostly imported from CD via iTunes (m4a), but also iTunes downloads. The only other format I have is mp3, but I do not know which

I couldn't find it to be a common problem in the posts, which indicates it might be hard(/firm)ware related.
However if you could make sure(/confirm) that corrupt tracks do not cause analyse crashes I might plan to reinstall my laptop from scratch.
The one thing that comes to mind is that upon installing a new version I always get the message that I am using a newer bonjour service.....

HI,

1: the track marked as corrupt after the crash, does it play/load correctly in Cross after restart?

2: can you check your ram-usage while analysis?

The tracks all play fine.

For the reply I re-analyzed a batch of 48 tracks which crashed this morning. All tracks downloaded from iTunes .

While analyzing Autoplay was on.

CPU usage before start at appx 7%. While analyzing appx 60% with moments upto 80%.

Memory before and during analyses between 350k and 360k. No peaks or drops outside this range.

audiocache setting = 43% of 2Gb =881mb

And ... no crash or corrupt track detected.

so, now it worked fine?
did you have anything else open the last time it crashed?

Yes it worked fine this time. At the time of the crash I had no other application open. (other than running in background).

Are there known applications/services suspected to interfere with Cross?
To reduce the chance of Cross crashing I did created a batchfile that stops several services and kills processes. So far it seems I did not find a process that causes the problem.

It gets some more confusing.
I had a batch of appx 200 tracks to analyze. Started this and left. Next morning Cross DJ had crashed, the Analyze counter still on 168. However after restart it appeared that all tracks are analyzed.... and no corrupt track.
Cross was the only application running.

Try with more little batch to spot the file crashing Cross then send it us.

Just sent 2 tracks by e-mail.
These are copies of the file that have the indicator "corrupt" after Cross crashed.
On re-analyze no problem occured. The track sounds fine to me.
Cross did continue analysing, but the application screen did not get refreshed nomore.
As a preperation I found on one the post information on how to get the best audio performance. So in this occurence there was the most restricted nummer of applications and services started, no "virtual file" for memory, no network (wireless nor fixed).

Have fun

Got them and now checking.
How do you launch the analyze : right click or button ?

I most use the button to analyze.