Mixvibes Dj Community old forum

It's pretty simple really. The industry at large is NOT interested in establishing any standards.

Personally I feel that all information added in DJ software belongs with the track. So expanding the tag fields with a number of DJ specific tags could solve so many problems. Since this is not the case, we are stuck.

What remains is beatgridding as the beatgridding engines are specific developments by the respective companies, who - understandably - want to keep that one close to their chest.

Tools are being developed by third parties, but are only as good as the current version of the software/database that they read and migrate data to and from. It's a stop gap solution, but if it works for you ...

I suspect it will take a long time, if ever, before we will see some kind of transparant standard linked to the track file for storing user generated information (cue points, loops, starting beat, etc.)

I'd like to add my name to this list of frustrated users please...

Having the same issue with rekordbox import - no beatgrid data is included. The option is definitely ticked for the XML export in RB. I've tried deleting the MV settings file and it's still an issue.

I can live with the lack of dynamic analysis, even if most of the music I play would be better suited to this. I'm I'm going to play 30 tunes I don't mind going through them slowly with a beer to make sure the grids are perfect.

RB is definitely easier to edit grids with, so I'd like that process to either be as easy in MV or for MV to properly sync with RB.

you could check if the rb export xml file has the info.

By this it can be narrowed down to an import issue.

Not sure if it will work, but maybe if you reimport the same file against the same collection it may be handled slightly different.

Cross store tracks by unique file location/filename so you shouldn't get duplicates.

RoJeC wrote:you could check if the rb export xml file has the info.

Thanks. How do I check that?

I was having a couple other issues so I deleted the settings file and started from scratch and the lack of grids is still an issue with the RB import.

The mixvibes.settingsfile is a file that holds program preferences. It's not useful to delete this unless you have a problem running Cross.

For tracks you have the collection(s) and the analysis files.

For reading XML you have various XML readers. Alternative can be Notepad++, excel, a browser.

I've pretty much spent the whole day trying to make this program work for me, but no luck, so I'm off. There's just too many issues with it unless you're playing perfectly quantised, computer generated music. Shame.

MrJL wrote:I've pretty much spent the whole day trying to make this program work for me, but no luck, so I'm off. There's just too many issues with it unless you're playing perfectly quantised, computer generated music. Shame.

I set multiple beat grids for songs that have fluctuating rhythm (funk, disco, rock, reggae, any old school material). It is workable.

Dynamic analysis is pretty new feature.
So the recent decades(!) required manual intervention in all DJ software.
No doubt one day it will be in Cross.

discopex wrote:I set multiple beat grids for songs that have fluctuating rhythm (funk, disco, rock, reggae, any old school material). It is workable.

Yeah I think i was just bummed out yesterday after spending most of a day trying to get stuff to work and getting nowhere. I think I need to get over RB being better to edit grids in and just suck up MV being more difficult whilst keeping my fingers crossed for future improvements