INTERACT FORUM

Please login or register.

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

Author Topic: Changing the Platform.jmd File Causes Auto-Import Problem  (Read 155 times)

Shasta Mike

  • World Citizen
  • ***
  • Posts: 247
Changing the Platform.jmd File Causes Auto-Import Problem
« on: December 18, 2024, 12:39:27 am »

Moving my external drive and library from a Linux Id to a Windows 11 PC caused a problem when importing new files for the slashes to show as forward in the Tag.  Changing the platform.jmd file from Linux to Windows fixed that. 

However, when I did a new auto-import thousands of folders imported that shouldn't have.  For some reason Import writes over the folders there and will show a (Varies) value on the tag for Import Date.  Then in some cases there are two listings for the same song of an album.

For now, I went back to a Library backup made before this change. Could having the Fix Broken Kinks checked on the Import config cause this?  Is there some other way to config Auto-Import to solve this?  All I want auto-import to do at this point is add folders added to the music library from a few days ago and ignore everything prior.  I cannot figure out a way to use a date to config the auto-import function.   
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5239
  • "Linux Merit Badge" Recipient
Re: Changing the Platform.jmd File Causes Auto-Import Problem
« Reply #1 on: December 18, 2024, 08:37:36 am »

The issues you're seeing are probably a result of old auto-import rules not working correctly after the migration.  Specifically, try:

1) Export Linux/Id Library and Import the library on Windows
2) Quickly turn off auto-import in the background under options
3) Use the "rename, move, copy" tool with the Update Path option to fix the file paths and direction of the slashes.  Specifically replace the root of the Linux filesystem with your drive letter (C: or D:, etc.) and check the box to reverse the direction of slashes.  Try a few files to test, then you can do the rest all at once.
4) Write down your auto import rules (if you need to), and then delete all your old auto import rules
5) Re-create the auto-import rules with the correct paths
6) Close JRiver and check the Platform.jmd file under your JRiver library directory to make sure that it says Windows rather than Linux (do not skip as a library restore may have undone this step!)
7) Restart JRiver
8 ) Turn auto import back on.

If you follow these steps correctly, you'll have all the same library info as you used to have and there should be no phantom auto-import problems.

This is based on reversing the steps for a successful migration from Windows To Linux from here: https://yabb.jriver.com/interact/index.php/topic,128397.msg890849.html#msg890849
Logged

Shasta Mike

  • World Citizen
  • ***
  • Posts: 247
Re: Changing the Platform.jmd File Causes Auto-Import Problem
« Reply #2 on: December 18, 2024, 12:05:37 pm »

The issues you're seeing are probably a result of old auto-import rules not working correctly after the migration.  Specifically, try:


If you follow these steps correctly, you'll have all the same library info as you used to have and there should be no phantom auto-import problems.

This is based on reversing the steps for a successful migration from Windows To Linux from here: https://yabb.jriver.com/interact/index.php/topic,128397.msg890849.html#msg890849
  Maybe I am already too far along with the migration to go back to zero and follow your rec 100%.  I used the Change Media Location when I migrated which worked wonderfully except the slash issue in the Tag.  Following along somewhat to your rec and then configuring auto-import not to update for External Changes and limiting import to FLAC files only, added about 50 folders and I could manually deal with that OK. 

Things seem to be working OK.  I'll know for sure when adding some more new music.  Thx!

Edit: just imported one new folder and nothing old came along. And, the cover art came through automatically OK as well.   

What are the downsides besides the obvious for checking No for updating broken links?   I think that was triggering other phantom importing.
Logged
Pages: [1]   Go Up