INTERACT FORUM
More => Old Versions => JRiver Media Center 27 for Linux => Topic started by: danrien on January 25, 2021, 10:50:34 pm
-
Any experience with migrating a library cleanly from Windows to Linux? I did a search and only found a post from a few years ago, any recent successes or guides that I could look to?
-
I would not recommend exporting a library from Windows to linux as all file paths will differ.
As windows goes like d:\folder\subfolder and linux /mountingpoint/folder/subfolder. If you have a clean library you can run an import without any issues in linux.
-
Any experience with migrating a library cleanly from Windows to Linux? I did a search and only found a post from a few years ago, any recent successes or guides that I could look to?
I did it last year, and a number of folks have done it recently. It takes a little work but is absolutely doable and is worth it if you've had your library a while to keep all the library only metadata (like last played and date imported, etc.). Here's a recent thread with some discussion:
https://yabb.jriver.com/interact/index.php/topic,127962.0.html
and a few more:
https://yabb.jriver.com/interact/index.php/topic,123748.msg857087.html#msg857087
https://yabb.jriver.com/interact/index.php/topic,117593
The basic steps are:
1) Export Windows Library and Import the library on Linux
2) Quickly turn off auto-import
3) Use the "rename, move, copy" tool with the Update Path option to fix the file paths and direction of the slashes. Try a few to test, then you can do the rest all at once.
4) Delete all your old auto import rules
5) Re-create the auto-import rules with the correct paths
6) Close JRiver and edit the Platform.jmd file under your JRiver library directory so that it says Linux rather than Windows (this one is important and can lead to mysterious problems if ignored)
7) Restart JRiver
8 ) Turn auto import back on.
-
When I tried to convert a library it repeatedly failed, crashing partway through the process and corrupting the library. Gave up after multiple attempts with ever smaller library sections, but still crashing and corrupting the library.
My work round is to use the portable library feature. It seems to work and has the advantage that I can use my old process of ripping/library maintenance on a different (Windows) machine from the server.
-
I did it last year, and a number of folks have done it recently. It takes a little work but is absolutely doable and is worth it if you've had your library a while to keep all the library only metadata (like last played and date imported, etc.). Here's a recent thread with some discussion:
https://yabb.jriver.com/interact/index.php/topic,127962.0.html
and a few more:
https://yabb.jriver.com/interact/index.php/topic,123748.msg857087.html#msg857087
https://yabb.jriver.com/interact/index.php/topic,117593
The basic steps are:
1) Export Windows Library and Import the library on Linux
2) Quickly turn off auto-import
3) Use the "rename, move, copy" tool with the Update Path option to fix the file paths and direction of the slashes. Try a few to test, then you can do the rest all at once.
4) Delete all your old auto import rules
5) Re-create the auto-import rules with the correct paths
6) Close JRiver and edit the Platform.jmd file under your JRiver library directory so that it says Linux rather than Windows (this one is important and can lead to mysterious problems if ignored)
7) Restart JRiver
8 ) Turn auto import back on.
Thanks! I'll give this a shot :-\
-
This worked like a charm, thanks mwillems!