With it set to YES, MC silently removes all of the files it can not locate! This is a VERY bad thing for drives that are intermittently inaccessible. So if files on the E: drive are not accessible, this tells MC what to do. That setting tells MC what to do when it thinks a file is no longer in the library that *used* to be. Anytime I need to dismount a drive or restart a computer, JRiver is always closed first. The drives never become disconnected or anything while JRiver is running. All drives are on RAID 1 controllers and encrypted using VeraCrypt. The files are hosted on a combination of Windows Server 2008 R2 SMB shares and local drives. I've been using the same library since I first got JRiver in 2011. My library has about 43K audio files and about 6K video which total to about 16TB. I also have a client connected to the same library running on another machine in my living room that's also running Win 10 that's only run when I'm using JRiver in my living room. However this issue has persisted across a few versions and even a couple OS upgrades (from Win 7 on both machines). This is problematic as it erases lots of other crucial library fields.Ĭurrently, I'm running MC 23 圆4 on Win 10 as my main library that runs 24/7. I've only seen this issue on audio files so far. Sometimes this requires me to try 3 or 4 different backups until I end up on one that doesn't re-import older files that were previously in the library. The only way I've found to "resolve" this is by restoring an older library backup and import again. This is quite annoying as one of my main views sorts by date added. Upon a manual run of auto-import, it will import 1000s of "missing" files that were previously in the library. I've been having an intermittent issue with my library for quite some time (over the last 2 or 3 major versions).įiles will be missing from my library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |