Nicotux
This time, simply choosing a karaoke skin with a karaoke file playing but not in karaoke mode
Destructions:
- All the databases in external and internal hdd
- the favorite folders
- some of the config, not everything
what was keept:
- the selected skins, custom buttons and some other settings
- the filters
- the pads
- the history
apparently most of what is on hdd
it recovers and starts to rescan everything ... let's wait for 2 or 3 hours to recreate the basic database
pretty sure all cues and tags and other are lost
This version b4918 seems to crash/recover really too often and stall otherwhise
Destructions:
- All the databases in external and internal hdd
- the favorite folders
- some of the config, not everything
what was keept:
- the selected skins, custom buttons and some other settings
- the filters
- the pads
- the history
apparently most of what is on hdd
it recovers and starts to rescan everything ... let's wait for 2 or 3 hours to recreate the basic database
pretty sure all cues and tags and other are lost
This version b4918 seems to crash/recover really too often and stall otherwhise
Inviato Sun 19 May 19 @ 10:07 pm
Nicotux
Addon to destroy list:
Attached covers
karaoke tags
all infos for file types not supporting tag
all custum infos for other files types
First seen date
......
Attached covers
karaoke tags
all infos for file types not supporting tag
all custum infos for other files types
First seen date
......
Inviato Sun 19 May 19 @ 10:41 pm
Nicotux
It took finally 3hours as expected
Now ready compare both the new created databases and the previously backuped ones
Now ready compare both the new created databases and the previously backuped ones
Inviato Mon 20 May 19 @ 1:09 am
Nicotux
Here is the first result:
In this situation VDJ recovered in a sort of secured virtual environment without anything but the running config so that it think there is no database and started to create one
In this virtual recovering environment, the actual databases seems not to be accessible to VDJ however they still exist physically on disk and won't be overwritten
There is no alteration in any way to the original databases, simply VDJ seems unusable for hours rescanning the system
At this point you get a fake ram database in a VDJ running in a virtual environment without any informations, no poi, no cues no favorits, no bpm, no cover ... and creating a backup will save this fake database
A BIG thank for the feature preserving the databases.
simply exit and kill not responding VDJ background thread... stall network io ? or infinite crash report
restart VDJ and you'll got everything back
i found it usefull to describe to prevent some big fright to those which experiment such crash during gig
In this situation VDJ recovered in a sort of secured virtual environment without anything but the running config so that it think there is no database and started to create one
In this virtual recovering environment, the actual databases seems not to be accessible to VDJ however they still exist physically on disk and won't be overwritten
There is no alteration in any way to the original databases, simply VDJ seems unusable for hours rescanning the system
At this point you get a fake ram database in a VDJ running in a virtual environment without any informations, no poi, no cues no favorits, no bpm, no cover ... and creating a backup will save this fake database
A BIG thank for the feature preserving the databases.
simply exit and kill not responding VDJ background thread... stall network io ? or infinite crash report
restart VDJ and you'll got everything back
i found it usefull to describe to prevent some big fright to those which experiment such crash during gig
Inviato Mon 20 May 19 @ 2:24 am
Adion
If the other vdj instance didn't close correctly it is indeed possible that the vdj database is not closed yet, so a new instance can't open it.
If this happens you should get a warning message at startup though telling you that the database couldn't be opened.
Making sure all instances are closed and then starting vdj again would indeed fix that.
Unfortunately it appears you did not login to vdj so there is no crash report logged.
I will try it I can reproduce the crash
If this happens you should get a warning message at startup though telling you that the database couldn't be opened.
Making sure all instances are closed and then starting vdj again would indeed fix that.
Unfortunately it appears you did not login to vdj so there is no crash report logged.
I will try it I can reproduce the crash
Inviato Mon 20 May 19 @ 5:04 am