Mobile Zombie
Regarding the settings file.
I store a few builds that I feel confident in locally, in case I need to quickly change.
Sometimes when I've had to change I notice some settings are also changed, even if I choose 'not to delete settings' during installation.
My question is:
Is it good practice to also keep a backup of the settingfile related to each build that I use and just replace after installation ?
Or will this corrupt something?
I store a few builds that I feel confident in locally, in case I need to quickly change.
Sometimes when I've had to change I notice some settings are also changed, even if I choose 'not to delete settings' during installation.
My question is:
Is it good practice to also keep a backup of the settingfile related to each build that I use and just replace after installation ?
Or will this corrupt something?
Posté Mon 28 Aug 17 @ 7:13 am
PhantomDeejay
1) IMHO it's better to store / backup the actual virtualdj.exe executable file instead of the full installation:
In C:\Program Files (x86)\VirtualDj you can have multiple files like virtualdj (3798).exe, virtualdj (3780).exe, virtualdj (3752).exe, virtualdj.exe
2) The default settings of VirtualDj itself rarely change. Last time a default setting was changed was from 8.1 to 8.2 transition.
3) What can change between various builds is the addition of some new settings:
Older builds that read new settings that don't know will ignore them.
Newer builds that read an old settings file without the new settings will automatically create the new settings entries and will use the default values for them.
Therefore I don't see any practical gain from keeping a backup of settings.xml file per build...
In C:\Program Files (x86)\VirtualDj you can have multiple files like virtualdj (3798).exe, virtualdj (3780).exe, virtualdj (3752).exe, virtualdj.exe
2) The default settings of VirtualDj itself rarely change. Last time a default setting was changed was from 8.1 to 8.2 transition.
3) What can change between various builds is the addition of some new settings:
Older builds that read new settings that don't know will ignore them.
Newer builds that read an old settings file without the new settings will automatically create the new settings entries and will use the default values for them.
Therefore I don't see any practical gain from keeping a backup of settings.xml file per build...
Posté Mon 28 Aug 17 @ 7:49 am
Mobile Zombie
Aha, that was good info.
I thought the installation required to be done byh setupfile in order to write registrydata and whatsoever.
OK, so I can keep only EXE files then. Good.
One setting that seems to change is for example 'max preload' I think it's called.
I thought the installation required to be done byh setupfile in order to write registrydata and whatsoever.
OK, so I can keep only EXE files then. Good.
One setting that seems to change is for example 'max preload' I think it's called.
Posté Mon 28 Aug 17 @ 7:54 am
PhantomDeejay
VirtualDj 8 doesn't use your registry to store any info.
The ONLY info stored in registry is the location of VirtualDJ's home path (typically C:\Users\Username\Documents\VirtualDj)
ALL the other settings are kept inside settings.xml file.
Also maxpreload will change only if you keep it in automatic (which is the default and recommended value). Depending on your computer specs it may take different values, especially if you use two different machines. Other than that if you set it on a logical fixed value (let's say 15 mins) it will stick.
The ONLY info stored in registry is the location of VirtualDJ's home path (typically C:\Users\Username\Documents\VirtualDj)
ALL the other settings are kept inside settings.xml file.
Also maxpreload will change only if you keep it in automatic (which is the default and recommended value). Depending on your computer specs it may take different values, especially if you use two different machines. Other than that if you set it on a logical fixed value (let's say 15 mins) it will stick.
Posté Mon 28 Aug 17 @ 8:09 am
Mobile Zombie
Great! I've learned more today :)
It's kind of fantastic to recieve answers to tech questions within minutes. Great work!
It's kind of fantastic to recieve answers to tech questions within minutes. Great work!
Posté Mon 28 Aug 17 @ 10:07 am