Sign In:     


Forum: Wishes and new features

Topic: make the tag editor save data to your music file and not in the software only,
add this kind of id3 tag editor for those who have brought paid for the full version of virtual dj.
the id3 tag editor should be able to write tags to your mp3's wave files or whatever file your using,
like a normal id3 tag editor, including your cue points that's stay on the file, instead of just editing it for virtual dj.

now for instance yesterday my computer cut off when it came back on all my cue point had disappear all bpm had gone, had to scan my hard drive again and still scanning it.

and had to start going through my tracks again one by one adding cue points again.

if the id3 tag editor had saved the data to the mp3 instead then the data would always be there on your mp3.
 

Posted 4 days ago @ 3:10 pm
Ruthless Chris wrote :
had to scan my hard drive again

No, you could have just restored from a backup.
 

TRIED THAT BUT IT DIDN'T WORK , VIRTUAL DJ HAD JUST UPDATED
 

The Tag Editor already can be set to save standard tag fields on the tracks.

That being said, application specific data (like hotcues) are not, nor they are going to be.
There are several reasons for this, data access speed and data integrity being the most important.

VirtualDJ uses a very simple way to store it's data. A simple XML file that you can backup, copy, edit, e.t.c.
There are only 3 ways for VirtualDJ to loose "cue points data"
  1. Locked fdatabase ile after a crash.
    This is the most common (and rare) reason. If VirtualDj crashes, there are some rare ocassions that the thread that handles the database file stays in memory. This means that when you try to start VirtualDJ again, it cannot access it's database and every single song appears as a new entry.
    The way to solve this is to close VirtualDJ and kill any virtualdj.exe instances remaining on task manager, OR reboot your system.
  2. The database file got corrupted. It's a quite rare case and usually it implies that either your hdd is going bad, or something went horibly wrong with it. Usually VirtualDJ will display a message that the database is corrupted and ask if you want to attempt a fix.
    This case needs a lot of attention because even if you repair the database or restore it from a backup, you could still loose everything if the hdd is damaged.
  3. The database file is missing completely. Usually due to user accidental deletion or move


Finally VirtualDJ has an automatic backup feature. You can set it up to take backups at frequent intervals.
Even with large databases, the size of the backup file is quite small (like 30 to 40MB or similar) which also makes keeping multiple backup files easy.