INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Update Database Misunderstanding  (Read 125 times)

blafarm

  • Regular Member
  • World Citizen
  • ***
  • Posts: 101
Update Database Misunderstanding
« on: Yesterday at 12:00:23 pm »

Introduction

I have read about this option in a number of posts, and I have found the RMCF option called:  "Update database to point to a new location".

I'm probably using this function incorrectly, but it does not seem to address my goals.

Goals

I frequently need to use Windows/Linux to move both album folders and individual tracks between several folders on a single M.2 storage drive.

For example, I need constantly move these files between folders that are named "Selects Takes" or "Out Takes", and I need to move them using the host operating system -- not MC.

After doing that, I simply want to force MC to update all of its databases to reflect the file location changes, but I have not found a way to do that.

What I've Tested

I have run a number of simple tests using "Update database..." and I can't get MC to even acknowledge that album folders and individual tracks that have been moved out of a specific folder -- are no longer there.

For the record, I am not wanting to "point to new location" -- I only want MC to update all of its databases to reflect where the media files are currently located.

And by update, I am seeking for MC to not only add newly moved files to the database, but to also delete files in the database that are no longer in an existing folder.

Any assistance would be greatly appreciated.
Logged

blafarm

  • Regular Member
  • World Citizen
  • ***
  • Posts: 101
Re: Update Database Misunderstanding
« Reply #1 on: Yesterday at 02:06:47 pm »

Well, it is clear that using the RMCF tool is the preferred way to manage moving files.
And I can easily see how it would work well for a fairly static media library requiring only infrequent changes.
However, it won't work for my use case.

I have found a workaround using Auto Update, but it comes with some peril -- not the least of which is its inconsistent performance.
But it does represent a fallback if one must use the host operating system to manage files locations.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 73292
  • Where did I put my teeth?
Re: Update Database Misunderstanding
« Reply #2 on: Today at 01:32:30 am »

The wiki describes how Rename, Move & Copy works.  You can use it to move your files.  Using the OS to do that is unnecessary,  Is there a reason?

You might also consider using file tags to separate the two categories of files.  You could then leave the files in one location, but set up two views to see them separately.

When you say "Auto Update", do you mean "Auto Import"?
Logged
Pages: [1]   Go Up