[Milhouse]

If you export the old RPi2 library to separate files then it will write the artwork and nfo files alongside the movies, which should be on your network, and when you import everything back in to create the MySQL library the network paths of artwork and movies alike will be used and accessible to both clients.

There's no easy solution to fix your current MySQL database, you could use mktools.py, or SQL queries, but I think in your case it will be easier to export the old RPi2 library to separate files and then rescrape a new MySQL library.

For your watched statuses you can add an advancedsettings.xml option to import watched statuses from the exported nfo files:

Code:

    <importwatchedstate>false</importwatchedstate>  <!-- import previously exported playdate and playcount from .nfo files. Defaults to false -->
    <importresumepoint>false</importresumepoint>  <!-- import previously exported resume point from .nfo files. Defaults to false -->

or you can use the texturecache.py tool to backup the watched status and resume points from your old RPi2 library to a file, eg.

Code:

texturecache.py watched movies backup movies.dat

then later on restore the movies.dat file to your new MySQL library (doesn't matter which client you use when restoring):

Code:

texturecache.py watched movies restore movies.dat