surge919

Members
  • Posts

    12
  • Joined

  • Last visited

surge919's Achievements

Noob

Noob (1/14)

1

Reputation

  1. i didn't migrate mine. I just let Emby rescan my library. you can try this and setup a separate Kodi on another machine and point that to the Emby server to see how it looks before scrapping the other method. I did this so I could manually sync up my watched and unwatched items.
  2. save yourself the headache and check out emby as your server and connect your clients to that.
  3. I gave up using the Kodi docker as a server. When it worked it worked ok but every once in a while something would happen and I'd have to troubleshoot the setup, recreate, the configs, etc. I still use Kodi for the client but I run a Emby docker for the server piece. With the Emby docker setup, you simply install the EmbyCon addon on the clients, supply the IP of the Emby docker and your done. I've been running this setup for about 8 months and haven't had any issues.
  4. Give Emby a try. I tried Jellyfin and noticed it was a little slower as well. I went with the Emby container and Embycon and so far it's been working very well.
  5. Here are the notes I have from my last install from scratch.. I may have missed a step but I'm pretty sure it's mostly accurate . YMMV Create a user on your DB server (MariaDB in my case so it's port 3307) Add the DB section in advanced.xml <videodatabase> <type>mysql</type> <host>10.0.0.20</host> <port>3307</port> <user>kodiuser</user> <pass>kodipassword</pass> </videodatabase> Change 10.0.0.20 to match your IP Address Change /volume1/data/kodi-headless-linuxserverio to match your path Run this from your NAS sudo docker create --name=kodi-headless-186 -v /volume1/data/kodi-headless-linuxserverio/:/config/.kodi -e PGID=0 -e PUID=0 -e TZ=America/New_York -p 8089:8080 -p 9777:9777/udp linuxserver/kodi-headless:186 Set to Always restart Start container Let database build up confirm login via http://10.0.0.20:8089/#settings/addons and ensure tvdb.com metadata.tvdb.com is installed and addon is enabled in stop container edit sources on kodi client to TV Shows / The TVDB (don’t refresh) edit sources on kodi client to Movies / Movie Database (don’t refresh) ensure path in db is set start container disable (debug) logging http://10.0.0.20:8089/#settings/kodi/system view logs run library scan curl --data-binary '{ "jsonrpc": "2.0", "method": "VideoLibrary.Scan", "id": "mybash"}' -H 'content-type:application/json;' http://kodi:[email protected]:8089/jsonrpc You should see the scan results in the logs tail -444f /volume1/data/kodi-headless-linuxserverio/temp/kodi.log
  6. Here's a link to the relevant issue and possible resolution https://github.com/linuxserver/docker-kodi-headless/issues/80
  7. Kodi (Leia RC5) is using the database MyVideos116 and the latest docker image of this is using MyVideos113 How can the version get updated (besides waiting for the docker image to be updated)?
  8. Has there been any progress on a version that works with Leia? I see a tag was added but it doesn't start. EDIT: Today I checked again and the tag showed it was updated a day ago. I deleted and re-added the docker image and it now loads up. I guess it was updated since I tried it last. It now seems to work. I'll post any issues I find. thanks
  9. The Media type information is stored in the Table called "path" I have a Library Scan working without first having to run the scan on a different machine. Here are the steps with everything wiped. First backing up the MySQL dbs (MyMusic* and MyVideos*) and then Dropping all tables.Removed all existing files from /userdata/Database Start up Kodi Headless docker so the DBs are created (MyMusic60 and MyVideos107) In PhpMyAdmin (or whatever your choose), go to the MyVideos107 DB and run the following SQL (replacing with the IP address and path of your files) kick off the Library Update http://10.0.0.20:8123/jsonrpc?request={%22jsonrpc%22:%222.0%22,%22method%22:%22VideoLibrary.Scan%22} I wiped everything and repeated this a few times and it worked everytime.. YMMV
  10. What do you mean about your comment about leaving a VM for background scanning? Once my initial scan is done will all future scans be handled correctly with just the headless running?
  11. Where is the Media type stored? I tried a media scan from a different machine and reverted it back to a fresh install.. Same method as above First backing up my MySQL db and then Dropping all tables.Removed all existing files from /userdata/Database I initiated a Library Scan but it didn't find anything. I then went to Library / Videos / TV / (Context Menu) / Edit Sources / "This directory contains" was blank so I set it to "TV Shows" I did the same for Movies. Now a Library Scan finds everything. thx
  12. I have a lot of old content which no longer exists on disk but a Library Scan shows the following errors http://10.0.0.20:8123/jsonrpc?request={%22jsonrpc%22:%222.0%22,%22method%22:%22VideoLibrary.Scan%22} A Library Clean doesn't remove them http://10.0.0.20:8123/jsonrpc?request={%22jsonrpc%22:%222.0%22,%22method%22:%22VideoLibrary.Clean%22} I tried to start from scratch by first backing up my MySQL db and then Dropping all tables. I already removed all existing files from /userdata/Database When I start the container, the tables get recreated but a Library Scan doesn't actually find anything new and the database shows nothing is added. Am I missing something or does this docker container require an initial library scan be done on a different machine? thanks.