J-Snip
Ran into a snag ...
My VDJ database on my external "J" Drive is not being seen on VDJ Win 7. All my files have no bpm's, etc but on XP it reads it just fine.
Any clue has to resolve this? I don't know much about Win 7.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I really need to continue tinkering with things before opening my big mouth. LOL
It was a security/permission issue on the database file. Had to give it more access with the "user" account.
My VDJ database on my external "J" Drive is not being seen on VDJ Win 7. All my files have no bpm's, etc but on XP it reads it just fine.
Any clue has to resolve this? I don't know much about Win 7.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I really need to continue tinkering with things before opening my big mouth. LOL
It was a security/permission issue on the database file. Had to give it more access with the "user" account.
Mensajes Thu 11 Oct 12 @ 9:49 pm
sum.zero
the vdj db uses links like"J:\track_directory\track.mp3". if you use an external drive you need to make sure windows is recognizing and mounting it using the same drive letter [eg F: or G: or J:] each time or vdj will not be able to associate your cues with your tracks. try using windows disk management tools to set the external drive to use the correct drive letter. you can examine your db.xml file in a text editor if you are unsure of which drive that is.
hope that helps.
hope that helps.
Mensajes Fri 12 Oct 12 @ 10:48 am
djdad
No, that is not true. The database on external HDs is irrelevant to the Drive letter. So no matter how the Drive is recognized in Windows, the database will still work.
Make sure you have full access to the HD, as it may carry some Proprties from yoru other computer/OS. Rightclick on the HD (in Windows Explorer)-->Properties-->Security tab and make sure your account name (username) has full access to that HD.
Then in VirtualDJ Browser, expand "MyComputer" Rightclick on that HD, choose Add to SearchDB. Goto Config->Browser tab, choose the Ext Drive from the list, and do a Check, Clean Fix.
It is a common sense to always keep the database file as a backuip copy before doing anything of the above (just in case).
Make sure you have full access to the HD, as it may carry some Proprties from yoru other computer/OS. Rightclick on the HD (in Windows Explorer)-->Properties-->Security tab and make sure your account name (username) has full access to that HD.
Then in VirtualDJ Browser, expand "MyComputer" Rightclick on that HD, choose Add to SearchDB. Goto Config->Browser tab, choose the Ext Drive from the list, and do a Check, Clean Fix.
It is a common sense to always keep the database file as a backuip copy before doing anything of the above (just in case).
Mensajes Fri 12 Oct 12 @ 11:15 am
sum.zero
that has not been my experience when the user has two db files [one in root of vdj install directory, one in the root of the external hdd] and using files off both drives. i'm not lying about it. my db started as vdj6. maybe that has something to do with it. i've experienced this using the same db files on two different laptops.
here is a line from the db file in my root directory pointing a file in my external hdd:
<Song FilePath="F:\_music\_a.set\03 naked lunch excerpts - dinner conversation.mp3" FileSize="10469755">
absolute path. if this drive is mounted as g: in windows it will not match the file to the entry.
here is a line from the db on the external hdd:
<Song FilePath="F:\mp3\c\cocteau twins - victorialand\03 throughout the dark months of april and may.mp3" FileSize="4443612">
again the path is absolute. in my case, changing the drive letter using windows drive management tools solves the problem quickly and easily...
edit: and does not require db edits via the check/fix tools
here is a line from the db file in my root directory pointing a file in my external hdd:
<Song FilePath="F:\_music\_a.set\03 naked lunch excerpts - dinner conversation.mp3" FileSize="10469755">
absolute path. if this drive is mounted as g: in windows it will not match the file to the entry.
here is a line from the db on the external hdd:
<Song FilePath="F:\mp3\c\cocteau twins - victorialand\03 throughout the dark months of april and may.mp3" FileSize="4443612">
again the path is absolute. in my case, changing the drive letter using windows drive management tools solves the problem quickly and easily...
edit: and does not require db edits via the check/fix tools
Mensajes Fri 12 Oct 12 @ 1:46 pm
cstoll
For the CORE Database that is found in the /My Documents/VirtualDJ folder - the drive letter is ABSOLUTE in it's reference. That is why if you try and switch computer system and use ALL INTERNALLY STORED files (typically on the C) it is VERY VERY critical that not only internal drive letters match but the path as well.
For the EXTERNAL DRIVE VirtualDJ Databases AND DEDICATED INTERNAL DRIVES (other than C) - the DRIVE LETTER means absolutely NOTHING. It is a place holder. That is why you are able to hot swap between systems and platforms (PC / Mac) and always have your cue points, etc. available.
The ONLY THING critical is the PATH that follows the drive letter indicator ( A: ) - so that way VirtualDJ knows how to drill down from the ROOT of the drive to the file location.
So - if you are using EXTERNAL DRIVES OR DEDICATED Internal Drives that you can move between system - there is nothing to worry about.
Mensajes Fri 12 Oct 12 @ 2:05 pm
sum.zero
ok, thank you for the clarification. i'd experienced issues with files and absolute paths on my primary hdd and had assumed the issues would apply to the external as well due to the absolute path entries in the db.
i have manually changed my drive letter and confirmed the files are still visible in my virtual folders and have retained cue information when loaded. good stuff. only downside is that things like the song links in the history section are broken. i don't use playlists so i can't comment on that section.
switching back and sticking with the philosophy of maintaining a standardized drive letter for my external hdd.
have a great day.
i have manually changed my drive letter and confirmed the files are still visible in my virtual folders and have retained cue information when loaded. good stuff. only downside is that things like the song links in the history section are broken. i don't use playlists so i can't comment on that section.
switching back and sticking with the philosophy of maintaining a standardized drive letter for my external hdd.
have a great day.
Mensajes Fri 12 Oct 12 @ 3:02 pm