Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[blafarm]

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.

[blafarm]

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.

[JimH]

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"?

[blafarm]

Thanks for your response, JimH.

Yes, there are some circumstances where RMCF can work for me.  It is an elegant solution because it facilitates the "Move" function, as well as keeping the database updated.  And the ability to creat Presets in that tool is helpful.  I do have a couple comments that I hope will be viewed as constructive suggestions:

1.  I think the RMCF tool's UI could be cleaner, and clearer, regarding the Move function.  As it is currently structured, the Move function is not a standalone option, but rather a fallback behavior if there is a directory change.  I think it would be clearer to have a dedicated radio button, or pulldown menu option, that allowed the user to understand, without ambiguity, that they are just moving files.

2.  As mentioned, the Preset options are very helpful.  I do wish I could invoke them using a keyboard combination.  Yes, F6 gets you to the tool, but it would be nice to give the user the ability to define a keyboard shortcut option which invoked a RMCF Preset without menu diving.

3.  Sorry, yes I meant Auto Import in my previous message -- not Auto Update.  It's kind of a backwards way of accomplishing a database update, but I have found it doesn't really work reliably, as it sometimes must be run repeatedly before deleting references to files that no longer exist in a particular folder.  Coming from a world that uses professional media management tools, I've grown accustomed to common functions like "Refresh Media Database".  Something like that would be a nice function to add to MC.

4.  I also wish I could assign a keyboard shortcut for "Update Tags (from library)".  If there is a way to do that, please let me know.

5.  Lastly, the reasons why using the OS to facilitate certain file management functions are too lengthy to describe here, but the workflow is time tested and can't be easily replicated within MC.