cr0okedl
This must have happened to me about 20 times already ....
out of nowhere when i open Vdj an error msg comes up and it says 'Internal Database Currupt' or something along those lines
... when this happens all my cue points and songs that i've analysed are gone and its basicly like starting all over from square one having to set new cue points for all my songs which is a big pain because i use mp3s (over 50,000 of them) and i get bout 100+ new songs every week (mainly play dancehall/reggae ... new riddims every week)
what i started to do to help with this problem is copy the VirtualDJ Database xml document every few days and keep it in another folder .... so if the database becomes corrupt again, i can just replace it with the copy so i wont have to start over from scratch like the other times ... but, ide still loose the cues that were put in after the last save
is there anyway of knowing what is causing this? or any input on the matter from more experience PC Tech people would be nice
out of nowhere when i open Vdj an error msg comes up and it says 'Internal Database Currupt' or something along those lines
... when this happens all my cue points and songs that i've analysed are gone and its basicly like starting all over from square one having to set new cue points for all my songs which is a big pain because i use mp3s (over 50,000 of them) and i get bout 100+ new songs every week (mainly play dancehall/reggae ... new riddims every week)
what i started to do to help with this problem is copy the VirtualDJ Database xml document every few days and keep it in another folder .... so if the database becomes corrupt again, i can just replace it with the copy so i wont have to start over from scratch like the other times ... but, ide still loose the cues that were put in after the last save
is there anyway of knowing what is causing this? or any input on the matter from more experience PC Tech people would be nice
Posted Tue 22 Aug 06 @ 5:38 am
DJ-ALF
If you don't shut down your VDJ properly or power loss this can happen. Always shut down your VDJ before you shut down Windows or your database might be lost.
Posted Tue 22 Aug 06 @ 8:52 am
cr0okedl
DJ-ALF wrote :
If you don't shut down your VDJ properly or power loss this can happen. Always shut down your VDJ before you shut down Windows or your database might be lost.
trust me i do ....
thats not the problem
Posted Tue 22 Aug 06 @ 9:27 am
DJ-ALF
Than your problem is something else. It can be defective Ram modules, try to find some software to check them out. It never corrupted to me on 3 machines.
Posted Wed 23 Aug 06 @ 8:55 am
cstoll
How large is your XML database file? - is it over 25Mb?
If yes, then when V4 comes out your problems will be solved. During beta testing of V4 an XML limitation bug was discovered and has been corrected.
Please be have patience until V4 releases - soon, I hope.
cstoll
If yes, then when V4 comes out your problems will be solved. During beta testing of V4 an XML limitation bug was discovered and has been corrected.
Please be have patience until V4 releases - soon, I hope.
cstoll
Posted Thu 24 Aug 06 @ 5:42 am
mackbolan1
I had the same thing happen to me as well, i play the same music you do and like you i add about 50-100 songs to my database per week, what you need to do is go into programs file,go to virtualdj and remove the currupt database and analyse your whole music collection again, i just install 4.0 on my laptop and had to analyse 200gig of music.
Posted Mon 25 Sep 06 @ 5:31 am
DJ-ALF
As I said many times, have a several backups of your database, that way you will at least have something scanned and you have less scanning to do if database is been corrupted. I have 3 different copies by date, every weekend I make one. Just to be sure ;)
Posted Mon 25 Sep 06 @ 6:47 am
sbangs
very wise , its like with all work , you should back it up
Posted Mon 25 Sep 06 @ 10:27 am
djsynystr
has anyone figured this out? i have been having this problem ever since upgrading to VDJ 6. i shut down properly and NEVER unplug until all is powered down? i had a thread going before and it basically got swept under the carpet and never got answered.
Posted Fri 06 Jan 12 @ 2:53 pm
Moderation staff
This is an ancient topic from 2006 and the problems described here have most likely been long since fixed.
If you are not running the latest version of the software, please upgrade. There have been bugs in older versions that can cause problems like this that have been fixed.
If the problem still persists in the latest version, please open a new topic.
[Very old topic closed]
If you are not running the latest version of the software, please upgrade. There have been bugs in older versions that can cause problems like this that have been fixed.
If the problem still persists in the latest version, please open a new topic.
[Very old topic closed]
Posted Fri 06 Jan 12 @ 3:54 pm