Folks, lots of changes have affected my once relatively stable Kodi world of 9 various systems on different platforms (Win, Android, Linux).
* 17.1 changes the skin ( ...uugh.)
* 17.1 seems to have broken profiles and skins don't seem to convey (likely will be resolved)
* Pivos (small box media player company) seems to have abandoned my Xios DX platform, recommending Emby as a way to keep various versions of Kodi platforms in sync (16.1 will be their last)
* I currently use MySQL to sync my devices (which requires all versions to be the same to share the MySQL DB)
* The MySQL server is not coresident with a Kodi installation, but it is on my windows machine that is used as a media server that is nearly always on. It's remote, in a home office, so I don't want to have that be a Kodi install and share the Kodi DB.
So, Emby it is, for me.
I have seen the Kodi.wiki on Emby, but it assumes that you would be setting up Emby in an environment that is just running XBMC, not already running MySQL
It appears to me that part of the process is that Emby needs to copy the current Kodi DB information before it "takes over" the function of the DB.
Can anyone verify if this logic is correct:
1) Export my library to individual files on my Windows NAS and overwrite the existing files to ensure that I have the latest copies there on my NAS.
2) Copy my userdata subdirectory before making any changes
3) Remove the MySQL section in AdvancedSettings, start KODI
4) Allow Kodi to rescan the media and repopulate the local database
5) Once complete, proceed with standard Emby server install,
6) Load the Emby Add-in, and follow the process to have it copy the local database to the Emby server
7) Verify that this all worked, Uninstall MySQL, load Emby Add-in on my other systems
Have I got that right? Will I lose anything in the process?
Thanks for any feedback.