Jump to content

1.0.15 Playlist issue


Dan64

Recommended Posts

Dan64

After installing the version 1.0.15 my playlists do not works on Kodi 14.2. I have performed the reset of local Kodi DB. But the playlists that I'm using still are not working.

 

Here an example of playlist:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="movies">
    <name>Films-Azione</name>
    <match>all</match>
    <rule field="path" operator="contains">
        <value>Movies/Films/Azione</value>
    </rule>
</smartplaylist>

the full path is the following

 

\\192.168.0.11\Emby\Movies\Films\Avventura\

 

Before the upgrade all the movies inside the folder "Avventura" were selected now none is found.

 

 

   

Link to comment
Share on other sites

Dan64

I'm using network paths. The Kodi client is running on Windows 8.1 and the directories are fully accessible by windows apps.

Before the upgrade I was using the emby for kodi version 0.33 (or 0.32 I don't remember).

There is a storage where are downloaded the addons that I can use to recover the old version ? the rollback feature seems to be disabled.

Edited by Dan64
Link to comment
Share on other sites

Angelblue05

Err yeah, you will need to reset and rescan your library in, then hopefully your smart playlist will pick up on the content. There's too much that changed in between, a clean slate for your database is required. :)

If you want to remain on 0.32: https://github.com/MediaBrowser/Emby.Kodi/releases/tag/plugin.video.emby-0.0.32

This is why it's best to do a backup of your userdata folder, then you can easily revert back. Now there's no guarantee that even going back things will work. 

 

But I will say that the initial scan speed has greatly improved since. So it might be easier/faster to just start from scratch in your situation. :wacko:

Edited by Angelblue05
Link to comment
Share on other sites

Dan64

I have already performed a "Reset of local Kodi DB" and performed a rescan, but the problem still persist. For the moment I will try to revert back to 0.32.

Thanks for the zip file. I discovered that the size of my package directory was above the limit allowed to have rollback enabled.

Link to comment
Share on other sites

Angelblue05

The reason I asked for the paths is because this is not a valid path for Kodi (with the IP). I think you'd need to set your path in Emby as nfs://IP/path/to/content

 

You'd need to troubleshoot this more, because I have playlists working just fine in Kodi with v1.0.15. Anyway, if one day you change your mind, we are here to help as much as we can.

Edited by Angelblue05
Link to comment
Share on other sites

Dan64

But I don't understand why was working on 0.0.32 and on 0.1.3 (I have discovered that I was running this version).

The problem is that I'm using path substitution on server side and this path is valid for windows since I'm also using Emby for Windows.

I don't think that the problem is related on paths because I have also an Android client (using the old xbmc3 addon) that is working fine.

Link to comment
Share on other sites

Angelblue05

If you launch Emby for Kodi - do you see your Emby user views? If so, are they populated by your Emby content (like in the web client). First we need to validate that the content was actually scanned in correctly. We will start from there to make sure everything is working.

Edited by Angelblue05
Link to comment
Share on other sites

Dan64

I have decided to use path substitution in Kodi do fix the problem of path (if any). I'm using this advanced settings file:

<advancedsettings>
    <packagefoldersize>9000</packagefoldersize>
    <pathsubstitution>
       <substitute>
         <from>\\192.168.0.11\</from>
         <to>SMB://192.168.0.11/</to>
       </substitute>
    </pathsubstitution>
</advancedsettings>

Actually I'm using SMB since my network server is a Linux server using samba for sharing.

Link to comment
Share on other sites

Angelblue05

Ok. It is indeed if any, since you didn't have any problem previously. Just have a look when you playback. However back to your actual problem, is your content not populated or it's just the smart playlist that's not working? Let us know, you can you verify following my previous post. Thanks :)

Edited by Angelblue05
Link to comment
Share on other sites

Dan64

I seems that the problem is on Server Side. Previously the client was working because were available a working db. After the db reset the server is unable to populate the db. Here the related kodi log

12:47:45 T:2612  NOTICE: EMBY Service -> logMsg : Starting Monitor
12:47:45 T:2612  NOTICE: EMBY Service -> logMsg : ======== START EMBY ========
12:47:45 T:2612  NOTICE: EMBY Service -> logMsg : KODI Version: 14.2 Git:20150326-7cc53a9
12:47:45 T:2612  NOTICE: EMBY Service -> logMsg : EMBY Version: 0.0.32
12:47:45 T:2612  NOTICE: EMBY ConnectionManager -> logMsg : Connection Manager Called
12:47:45 T:2612  NOTICE: EMBY ConnectionManager -> logMsg : Server already set
12:47:45 T:2612  NOTICE: emby 1 -> __init__ : emby Service -> starting playback monitor service
12:47:45 T:2612  NOTICE: emby WebSocketThread -> Log Level:2
12:47:46 T:2612  NOTICE: Not authenticated yet
12:47:46 T:7772  NOTICE: EMBY UserClient -> logMsg : |---- Starting UserClient ----|
12:47:46 T:7772  NOTICE: EMBY UserClient -> logMsg : Returning accessToken from SETTINGS for username: Test accessToken: f7cdd38008ff48ab986a564f819f616b
12:47:46 T:7772  NOTICE: EMBY UserClient -> logMsg : Returning userId from SETTINGS for username: Test userId: 8ad9331b05ce4aada4467c29a4d271f3
12:47:46 T:7772  NOTICE: EMBY UserClient -> logMsg : Returning accessToken from WINDOW for username: Test accessToken: f7cdd38008ff48ab986a564f819f616b
12:47:46 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Set username: Test
12:47:46 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Set userId: 8ad9331b05ce4aada4467c29a4d271f3
12:47:46 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Set server: http://192.168.0.11:8096
12:47:46 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Set token: f7cdd38008ff48ab986a564f819f616b
12:47:46 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Verify SSL host certificate: False
12:47:46 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : SSL client side certificate: None
12:47:47 T:7772  NOTICE: File_Lock_On C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\machine_guid.lock obtained
12:47:47 T:7772  NOTICE: EMBY ClientInformation -> logMsg : ClientId saved to WINDOW: 4A84F9CDF0C24DDB9C2F5AF4A659CC2E
12:47:47 T:7772  NOTICE: File_Lock_On C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\machine_guid.lock released
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Header: {'Accept-Charset': 'UTF-8,*', 'Accept-encoding': 'gzip', 'Authorization': 'MediaBrowser UserId="8ad9331b05ce4aada4467c29a4d271f3", Client="Kodi", Device="Kodi", DeviceId="4A84F9CDF0C24DDB9C2F5AF4A659CC2E", Version="0.0.32"', 'X-MediaBrowser-Token': 'f7cdd38008ff48ab986a564f819f616b'}
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Requests session started on: http://192.168.0.11:8096
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Sessions?DeviceId=4A84F9CDF0C24DDB9C2F5AF4A659CC2E&format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : ====== 200 Success ======
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Session result: [{u'UserName': u'Test', u'DeviceName': u'Kodi', u'ApplicationVersion': u'0.0.32', u'QueueableMediaTypes': [], u'LastActivityDate': u'2015-06-28T10:48:31.6610960Z', u'UserId': u'8ad9331b05ce4aada4467c29a4d271f3', u'SupportsRemoteControl': False, u'Client': u'Kodi', u'SupportedCommands': [u'Play', u'Playstate', u'SendString', u'DisplayMessage', u'PlayNext'], u'AdditionalUsers': [], u'PlayableMediaTypes': [u'Audio', u'Video'], u'PlayState': {u'CanSeek': False, u'IsMuted': False, u'IsPaused': False}, u'Id': u'36070c7f22a7c6858e5457b7936ac46f', u'DeviceId': u'4A84F9CDF0C24DDB9C2F5AF4A659CC2E'}]
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Capabilities URL: {server}/mediabrowser/Sessions/Capabilities?Id=36070c7f22a7c6858e5457b7936ac46f&PlayableMediaTypes=Audio,Video&SupportedCommands=Play,Playstate,SendString,DisplayMessage,PlayNext&SupportsMediaControl=True
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : PostData: {}
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Sessions/Capabilities?Id=36070c7f22a7c6858e5457b7936ac46f&PlayableMediaTypes=Audio,Video&SupportedCommands=Play,Playstate,SendString,DisplayMessage,PlayNext&SupportsMediaControl=True&api_key=f7cdd38008ff48ab986a564f819f616b
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : ====== 204 Success ======
12:47:47 T:7772  NOTICE: EMBY DownloadUtils -> logMsg : Posted capabilities to sessionId: 36070c7f22a7c6858e5457b7936ac46f
12:47:47 T:7772  NOTICE: EMBY UserClient -> logMsg : Current user: Test
12:47:47 T:7772  NOTICE: EMBY UserClient -> logMsg : Current userId: 8ad9331b05ce4aada4467c29a4d271f3
12:47:47 T:7772  NOTICE: EMBY UserClient -> logMsg : Current accessToken: f7cdd38008ff48ab986a564f819f616b
12:47:47 T:2612  NOTICE: Doing_Db_Sync: syncDatabase (Started)
12:47:47 T:6208  NOTICE: emby WebSocketThread -> WebSocket URL : ws://192.168.0.11:8096/mediabrowser
12:47:47 T:6208  NOTICE: emby WebSocketThread -> Client Starting
12:47:47 T:6208   ERROR: --- request header ---
12:47:47 T:6208  NOTICE: .
12:47:47 T:6208   ERROR: GET /mediabrowser HTTP/1.1

                                            Upgrade: websocket

                                            Connection: Upgrade

                                            Host: 192.168.0.11:8096

                                            Origin: http://192.168.0.11:8096

                                            Sec-WebSocket-Key: DA5QOZ+GStaDkgt0CgfqgQ==

                                            Sec-WebSocket-Version: 13
12:47:47 T:6208  NOTICE: .
12:47:47 T:6208   ERROR: -----------------------
12:47:47 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: --- response header ---
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: HTTP/1.1 101 Switching Protocols
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: Server: websocket-sharp/1.0
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: Upgrade: websocket
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: Connection: Upgrade
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: Sec-WebSocket-Accept: ujQiZtmskfGmL55hA3fzuES6BgU=
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208   ERROR: -----------------------
12:47:48 T:6208  NOTICE: .
12:47:48 T:6208  NOTICE: emby WebSocketThread -> Opened : {"Data": "Kodi|4A84F9CDF0C24DDB9C2F5AF4A659CC2E|0.0.32|Kodi", "MessageType": "Identity"}
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:48 T:6208   ERROR: send: '\x81\xd8?!j7D\x03.VK@H\r\x1f\x03!X[H\x16\x03~\x19^q\x06b.q\x0fbX\x03{e(\x0e|\x13,\x02~g^v\t\x14St|\x13/K\x0f\x0fZ\x19\x0c\x13\x16|PE\x03\x15\x13\x01HzZR\x19VXD>NODH\r\x1f\x03#SZO\x1e^KXHJ'
12:47:48 T:6208  NOTICE: .
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/Items/Root?format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : ====== 200 Success ======
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/items?ParentId=e9d5075a555c1cbc394eec4cef295274&Sortby=SortName&format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : ====== 200 Success ======
12:47:48 T:2612  NOTICE: Sync Episodes -> TvShowsSync : Finished 0:0
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/Items/Root?format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : ====== 200 Success ======
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:48 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/items?ParentId=e9d5075a555c1cbc394eec4cef295274&Sortby=SortName&format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:47:49 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : ====== 200 Success ======
12:47:49 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:47:49 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/items?ParentId=c8ca023cdbb96c78e4de5fcb477df512&SortBy=SortName&Fields=Path,Genres,SortName,Studios,Writer,ProductionYear,Taglines,CommunityRating,OfficialRating,CumulativeRunTimeTicks,Metascore,AirTime,DateCreated,MediaStreams,People,Overview&Recursive=true&SortOrder=Descending&IncludeItemTypes=Movie&CollapseBoxSetItems=false&format=json&ImageTypeLimit=1&api_key=f7cdd38008ff48ab986a564f819f616b
12:48:02 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : ====== 200 Success ======
12:48:03 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : === ENTER downloadUrl ===
12:48:03 T:2612  NOTICE: EMBY DownloadUtils -> logMsg : URL: http://192.168.0.11:8096/mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/Items/8fd112373478a90f87f3431e26f53c17/LocalTrailers?format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:48:33 T:2612   ERROR: Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPConnectionPool(host='192.168.0.11', port=8096): Read timed out. (read timeout=30)",)': /mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/Items/8fd112373478a90f87f3431e26f53c17/LocalTrailers?format=json&api_key=f7cdd38008ff48ab986a564f819f616b
12:48:33 T:2612  NOTICE: .
12:48:44 T:1564  NOTICE: Thread JobWorker start, auto delete: true
12:49:03 T:2612  NOTICE: Sync DB -> syncDatabase : syncDatabase Exiting
12:49:03 T:2612   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <class 'requests.exceptions.ConnectionError'>
                                            Error Contents: HTTPConnectionPool(host='192.168.0.11', port=8096): Max retries exceeded with url: /mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/Items/8fd112373478a90f87f3431e26f53c17/LocalTrailers?format=json&api_key=f7cdd38008ff48ab986a564f819f616b (Caused by ReadTimeoutError("HTTPConnectionPool(host='192.168.0.11', port=8096): Read timed out. (read timeout=30)",))
                                            Traceback (most recent call last):
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\service.py", line 151, in <module>
                                                Service().ServiceEntryPoint()
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\service.py", line 117, in ServiceEntryPoint
                                                libSync = librarySync.syncDatabase()
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\LibrarySync.py", line 53, in syncDatabase
                                                completed = completed and self.MoviesSync(connection, cursor,True, True)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\LibrarySync.py", line 137, in MoviesSync
                                                WriteKodiDB().addMovieToKodiLibrary(item,connection, cursor)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\WriteKodiDB.py", line 675, in addMovieToKodiLibrary
                                                jsonData = downloadUtils.downloadUrl(itemTrailerUrl)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\DownloadUtils.py", line 167, in downloadUrl
                                                r = s.get(url, params=postBody, timeout=timeout)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\sessions.py", line 476, in get
                                                return self.request('GET', url, **kwargs)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\sessions.py", line 464, in request
                                                resp = self.send(prep, **send_kwargs)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\sessions.py", line 576, in send
                                                r = adapter.send(request, **kwargs)
                                              File "C:\Users\MediaCenter\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\adapters.py", line 424, in send
                                                raise ConnectionError(e, request=request)
                                            ConnectionError: HTTPConnectionPool(host='192.168.0.11', port=8096): Max retries exceeded with url: /mediabrowser/Users/8ad9331b05ce4aada4467c29a4d271f3/Items/8fd112373478a90f87f3431e26f53c17/LocalTrailers?format=json&api_key=f7cdd38008ff48ab986a564f819f616b (Caused by ReadTimeoutError("HTTPConnectionPool(host='192.168.0.11', port=8096): Read timed out. (read timeout=30)",))
                                            -->End of Python script error report<--
12:49:16 T:5492  NOTICE: Thread JobWorker start, auto delete: true

The problem is on server side but I don't know how to fix it.

Link to comment
Share on other sites

Angelblue05

Yeah I think you must have been on a later version (0.0.33), after we removed the api key from the query url. This is what's causing the server to fail to answer... However, there were no version drafted for 0.0.33 so I can't give it to you....  I think at this point, you have no choice but to use the latest beta version (1.0.15) and we'll start from there.

 

Steps to follow: Update to the latest Emby for Kodi version, then do a reset database like you did previously. This time however, if you are able to go into %appdata/Roaming/Kodi/userdata/database and delete myvideosxx.db. Start Kodi and let the content sync up. Then your Emby content should show up in Kodi. 

 

Edit: I'm sorry you are having this difficulties :( I will try to help as much as possible...but I have to go soon.

Edited by Angelblue05
Link to comment
Share on other sites

Dan64

I will try to use the last version 1.0.15. I will inform you about the results of my tests as soon as will be completed.

Link to comment
Share on other sites

Angelblue05

Thanks null_pointer :) Yes that must be it! I wasn't sure if it was just playlist not working or content also not showing. 

Link to comment
Share on other sites

Dan64

Probably I have found the issue, the problem is that now the path stored is something like: plugin://plugin.video.emby/movies/e73b874b2a727ab07cbe4e....0cf

 

I'm able to play the file, but the information on the true path is completely hidden !

  • Like 1
Link to comment
Share on other sites

Angelblue05

Ok so in that case, you have the option to use direct path instead (add-on settings > sync options) - but it will require another sync (just perform local database reset, no need to delete the database file). However using direct paths doesn't give enough control to the add-on to control playback so you will lose out on some emby features like cinema experience, parental control, fall back methods for playback, etc.

 

Another option is to change the rules on your smart playlist to use other filters such as Genres or rating. You could also separate those folders individually in Emby and Kodi will follow suit and divide them for you, in different views. You have many options, so you can get the best out of this experience. It is up to you :) Glad at least, we have an answer, I'm sorry it took a bit to reach it.

Edited by Angelblue05
Link to comment
Share on other sites

  • 5 months later...
Bernie V

Probably I have found the issue, the problem is that now the path stored is something like: plugin://plugin.video.emby/movies/e73b874b2a727ab07cbe4e....0cf

 

I'm able to play the file, but the information on the true path is completely hidden !

Is there a way to find out what the exactly path is for a music file within Kodi using the Emby addon?

Link to comment
Share on other sites

Angelblue05

Music uses direct path. Either local (smb) or checking the add-on settings > sync option, if Music direct stream is enabled, then it's http.

Link to comment
Share on other sites

Bernie V

Music uses direct path. Either local (smb) or checking the add-on settings > sync option, if Music direct stream is enabled, then it's http.

Yes, I know but like the TS said it is not possible to create a smart music playlist based on the path in Kodi when using the Emby plugin.

 

Kodi log:

 

13:03:46 T:2676  NOTICE: EMBY Player -> ONPLAYBACK_STARTED: musicdb://songs/116.mp3 ITEMID: 04a1e5b6e86293380ec5a832a8ab1dba

 

The plugin uses musicdb://songs/ as path for the track and nothing from the original path where the music is stored on disk.

Link to comment
Share on other sites

Angelblue05

Music doesn't work the same way as the video library. The path are either smb or http. If you are not using direct stream for music then it is using direct paths to music.

 

The path you are seeing in log is an internal Kodi path. It's basically just used to find the right info in the database for the song to play.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...