MIXVIBES Dj Community old forum

Good morning:

I am using version 3.2! Why is it that in the "analysis status" column I have a ? and a check mark on two different songs that were played during the same set? I have 7000 songs in my collection and swear that I analyzed every one but now I have 5000 songs that have ? in that particular column? Does this mean I have to reanalyze and will this mess up any grids that I have redone manually? Or anything else for that matter? I guess maybe I don't understand the four columns in the "preference" section?

Thx
DDJJ

ddjj wrote:Good morning:

I am using version 3.2! Why is it that in the "analysis status" column I have a ? and a check mark on two different songs that were played during the same set? I have 7000 songs in my collection and swear that I analyzed every one but now I have 5000 songs that have ? in that particular column? Does this mean I have to reanalyze and will this mess up any grids that I have redone manually? Or anything else for that matter? I guess maybe I don't understand the four columns in the "preference" section?

Thx
DDJJ

Did you analyzed all with 3.2?
I ask because if you analyzed with a 2.x version and then upgraded to a 3.x version the track will be analyzed for peaks only upon loading. This peak analysis contains the infor mation for waveform color.

You can select all track that have the "?" and analyze for peak only. All your locators, grids, and loops will be retained.

just a wild guess, this may not be your problem but I thought I mention it just in case.

FigDJ:

I think that is maybe what I did, but does that mean that the ? means that "all" has not been analyzed for 3.2?...If I analyzed all in 2.6, would there not be any ? marks in 2.6? Also Ive noticed shifts in the grid in some songs from 2.6 to 3.2...?
I have my preference set to Gain only in 3.2....wouldn't that have taken care of ? on one of the two songs played on the same set?
damn IM confused?

DDJJ

In 3 the beatgrid has been redesigned. This requires new analysis. Also key analysis was introduced around that version.

If ever analysis was completed it is marked ok. Your set preference only applies when using right click menu. It is not restricting analysis that are required for use of Cross.

ddjj wrote:FigDJ:

I think that is maybe what I did, but does that mean that the ? means that "all" has not been analyzed for 3.2?...If I analyzed all in 2.6, would there not be any ? marks in 2.6? Also Ive noticed shifts in the grid in some songs from 2.6 to 3.2...?
I have my preference set to Gain only in 3.2....wouldn't that have taken care of ? on one of the two songs played on the same set?
damn IM confused?

DDJJ

Alright we can take this as a step by step process to resolve the issues but 1st I got a few questions to help me device a course of action.

Did you retained 2.6 as an installed program?
If so then you should have the following:
under
user\appdata\roaming\mixvibes\analyses\

these are all the analyses performed under any 3.x version.

then under
user\appdata\roaming\mixvibes\Cross\peaks\

these are all the analyses performed under a 2.x version

let me know if you still have the last one available.

Good morning!

Just to let u know what I am doing!
I have crashes in 3.2 therefore I am using the 2.6 version currently:
I have two collection files named 3.2 and 2.6!

I use 3.2 to update my collection, and analyze the tracks under 3.2.
Then I resave the file to 2.6 and use Cross 2.6 for giging!

I have both directories that u say above but I use my own directory to save the peak files that have been now been all analyzed using 3.2 (C:\Users\jim\Music\MixVibes\Peak)....

the "peak" directory is empty and the analyses has only 291 files out of 9000 tracks that I have....hope this make sense!

DDJJ

ddjj wrote:Good morning!

Just to let u know what I am doing!
I have crashes in 3.2 therefore I am using the 2.6 version currently:
I have two collection files named 3.2 and 2.6!

I use 3.2 to update my collection, and analyze the tracks under 3.2.
Then I resave the file to 2.6 and use Cross 2.6 for giging!

I have both directories that u say above but I use my own directory to save the peak files that have been now been all analyzed using 3.2 (C:\Users\jim\Music\MixVibes\Peak)....

the "peak" directory is empty and the analyses has only 291 files out of 9000 tracks that I have....hope this make sense!

DDJJ

OK, so that is backward of what I do.
I gig primarily with 2.6 and use 3.2 for MIDI research.
I don't like the smaller waveforms in 3.2 and the broken beatmatcher.

Not suggesting that this is what you should do, this is what worked for me in my workflow. (you probably not going to like this)

I analyzed, cued, and looped all my track in in 2.6. By default that would save the files in
Mixvibes\Cross\peaks\

Then I sort the directory by date created.
The newly created peak files will be obvious to your view.
Copy the new peak files (the 1st time was an all file dump) to the
Mixvibes\Analyses
This is were versions 3.x store the peak files.

Open Cross 3.2 and set the analyses for peak only.

then you can analyze the new tracks or analyzed all if you want (it won't hurt the files already there as long as it is for peak only)

your new 3.2 compatible peak files will retain all the cue, locator, beatgrid, and loop information that was already generated in 2.6 and the grid will match perfectly between the deck waveforms and the beatmatcher.

I only keep one collection and it work perfectly for both versions.

The way FigDJ describes works but backwards compatability is not guaranteed.
The more detailed use of track info in version 3 could be the cause of your crashes. If specific files or files from specific sources cause it then it is recommended to make them available to the devteam. By this they might catch the event and avoid crashing.
In the end staying at 2 is not a solution, unless like FigDJ you prefer some functionality that changed.

Hello:

My crashes are in 3.2, not 2.6....so all my work is done in 3.2 with the hopes that someday I can use it, then I rename it to 2.6 and use it in 2.6, I have never had a crash...The current 3.2 was initially a 2.6 file (again without a crash)...and was renamed to 3.0, 3.1 and then to 3.2...reflecting the new trax that I have obtained! Maybe I should have a directory for 2.6 and a separate one for 3.2? My crashes have started since 3.0, and have reported such....always when I am track loading!

DDJJ

Quite some things have changed that are used in the track loading phase. in 3.0 the new beatmatcher and equalizers that needed more detailed analyses to use it the new way. in 3.2 some things changed to have more efficient loading.

As FigDJ mentioned there basically would be no need to use a different (copied) collection or copied analyses files for these version. you can just use one collection and start the program you want to use. (as mentioned before no guarantees for this compatibility; works for these versions).

Loading issues can be caused by delays in your environment. Typical causes would be hdd and/or USB hubs in powersave mode and/or antivirus (/spam/malware) software.

Make sure your hdd has no powersave on (or make it > like 4 hours). USB powersave best be disabled (when using USB devices) in the hardware settings for each internal hub.
Also make sure your CPU is running max (not on saving mode).

For the AV you should exclude several folders
- peak/analyses
- collection
- program files/mixvibes
Especially the first 2 are important. As Cross is constant reading and writing the AV can cause significant delays (in computer time).

Could you indicate what your crash frequency is; like nr times/hour; nr of times per tracks (1 of 10) or so. And is it always the same tracks, so easy to duplicate or somewhat random.

I have had the experience in 3.0.0 of frequent crashes, but after that it has become rare, and ran several test for both Beta's as RC's leaving Cross run in autoplay over the weekend without any hickup as appeared on Monday morning.

And just to be sure, is there anything you do with your files (e.g. with other program) before or after loading into Cross collection.