Bernie V 7 Posted February 7, 2016 Share Posted February 7, 2016 My media is on a Synology NAS. In Kodi I can play movies (direct stream) and play music (also direct stream). In my setup it isn't possible to play songs on my receiver trough DLNA Kodi. Browsing just works but not playing. I checked the Kodi log and saw this: EMBY Items -> Processing userdata: {u'Audio': [u'eecfa9a3ccf7eb96b53b85c5dd395866'], u'MusicAlbum': [u'522ded9f3ce788fe5ac17d1146535ca1']}07:02:48 31731.585938 T:1733293088 NOTICE: Using Image Cache Thread Count: 0 -> 107:02:49 31732.451172 T:1733293088 NOTICE: Previous line repeats 1 times.07:02:49 31732.451172 T:1733293088 NOTICE: EMBY Music -> Update playstate for song: The Sound Of Silence07:02:49 31732.451172 T:1733293088 WARNING: CreateLoader - unsupported protocol(/nfs) in /nfs://192.168.1.101/volume1/music/Unmixed Compilations/Various/30 Stars - Acoustic/Simon & Garfunkel - The Sound Of Silence.mp307:02:49 31732.451172 T:1733293088 NOTICE: Emby musictools -> File does not exist! These are my path subsitutions for my music, in this order: mnt/music -> nfs://192.168.1.101/volume1/musicmnt/music -> \\192.168.1.101\musicmnt/music -> \\vandernas\music In the Kodi addon my settings are direct stream and paths through the Emby addon In the album.nfo file that Emby creates: <?xml version="1.0" encoding="utf-8" standalone="yes"?><album> <review /> <outline /> <lockdata>false</lockdata> <dateadded>2016-02-03 16:24:54</dateadded> <title>30 Stars - Acoustic</title> <originaltitle>30 Stars - Acoustic</originaltitle> <year>2015</year> <genre>Ballad</genre> <art> <poster>/nfs://192.168.1.101/volume1/music/Unmixed Compilations/Various/30 Stars - Acoustic/folder.jpg</poster> For all my media Emby creates /nfo:// in the nfo files. Is this correct? Because Kodi doesn't seem to find the media when I use DLNA. Play music and movies in Kodi itself is working. What do I have to change in my setup to play songs on my receiver trough DLNA Kodi? Link to comment Share on other sites More sharing options...
Luke 36999 Posted February 7, 2016 Share Posted February 7, 2016 dlna doesn't use path substitution so the problem is likely something else. are you able to play video? can you find the exact error in kodi? i don't think the above directly relates to it. Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 7, 2016 Share Posted February 7, 2016 (edited) DLNA has nothing to do with the emby for kodi add-on settings. Edited February 7, 2016 by Angelblue05 Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 7, 2016 Author Share Posted February 7, 2016 Yes playing video works in the Kodi GUI. For music I don't use the Kodi GUI, but the display on my receiver with the remote control of my receiver. For music I use the remote controle of my receiver and navigate to the Kodi DLNA server. At that moment I can browse the music. When I want to play music I see on the display of my receiver: "Cannot Play Music". I have checked the logs of Emby and this is what I see: 2016-02-08 00:06:20.3370 Info App: /usr/bin/ffmpeg -i file:"/mnt/music/Unmixed Compilations/00s/Hitbox 2000 Volume 4/Ricky Martin ft. Meja - Private Emotion.mp3" -threads 0 -vn -id3v2_version 3 -write_id3v1 1 -y "/var/lib/emby-server/transcoding-temp/f7fa9151e0c3750a142f2229fa3742a7.mp3"2016-02-08 00:06:22.8385 Error App: Error streaming media. The client has most likely disconnected or transcoding has failed.2016-02-08 00:06:23.0016 Error HttpServer: Error in HttpListenerResponseWrapper: Write failure *** Error Report *** Version: 3.0.5818.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.4.0.1 Processor count: 4 64-Bit OS: False 64-Bit Process: False Program data path: /var/lib/emby-server Mono: 4.2.2 (Stable 4.2.2.30/996df3c Fri Jan 22 00:48:14 UTC 2016) Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe Write failure System.IO.IOException at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x6e0bad28 + 0x00114> in <filename unknown>:0 at SocketHttpListener.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) <0x6e0bab98 + 0x0008b> in <filename unknown>:0 at SocketHttpListener.Net.ResponseStream.Close () <0x6e0bc670 + 0x00197> in <filename unknown>:0 at MediaBrowser.Server.Implementations.HttpServer.SocketSharp.Extensions.CloseOutputStream (SocketHttpListener.Net.HttpListenerResponse response, ILogger logger) <0x6e0bb968 + 0x00053> in <filename unknown>:0 InnerException: System.Net.Sockets.SocketException The socket has been shut down at System.Net.Sockets.Socket.Send (System.Byte[] buffer, Int32 offset, Int32 size, SocketFlags flags) <0x6e0bb288 + 0x000c8> in <filename unknown>:0 at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x6e0bad28 + 0x000a3> in <filename unknown>:0 2016-02-08 00:06:23.0338 Error HttpAsyncTaskHandler: Error occured while Processing Request: Write failure *** Error Report *** Version: 3.0.5818.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.4.0.1 Processor count: 4 64-Bit OS: False 64-Bit Process: False Program data path: /var/lib/emby-server Mono: 4.2.2 (Stable 4.2.2.30/996df3c Fri Jan 22 00:48:14 UTC 2016) Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe Write failure System.IO.IOException at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x6e0bad28 + 0x00114> in <filename unknown>:0 at SocketHttpListener.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) <0x6e0bab98 + 0x0008b> in <filename unknown>:0 at SocketHttpListener.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) <0x6e0b65e8 + 0x0024b> in <filename unknown>:0 at ServiceStack.Formats.HtmlFormat.SerializeToStream (IRequest request, System.Object response, IResponse httpRes) <0x6a924f48 + 0x00b97> in <filename unknown>:0 at ServiceStack.HttpResponseExtensionsInternal.WriteErrorToResponse (IResponse httpRes, IRequest httpReq, System.String contentType, System.String operationName, System.String errorMessage, System.Exception ex, Int32 statusCode) <0x6a93e6f8 + 0x0027b> in <filename unknown>:0 at ServiceStack.ServiceStackHost.OnUncaughtException (IRequest httpReq, IResponse httpRes, System.String operationName, System.Exception ex) <0x6a93cda8 + 0x0028b> in <filename unknown>:0 at ServiceStack.HostContext.RaiseUncaughtException (IRequest httpReq, IResponse httpRes, System.String operationName, System.Exception ex) <0x6a937e60 + 0x0004b> in <filename unknown>:0 at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse (IResponse response, System.Object result, ServiceStack.Web.ResponseSerializerDelegate defaultAction, IRequest request, System.Byte[] bodyPrefix, System.Byte[] bodySuffix) <0x6e0b0000 + 0x0109b> in <filename unknown>:0 at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse (IResponse httpRes, IRequest httpReq, System.Object result, System.Byte[] bodyPrefix, System.Byte[] bodySuffix) <0x6e0cccb8 + 0x0030f> in <filename unknown>:0 at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse (IResponse httpRes, IRequest httpReq, System.Object result) <0x6e0cbe68 + 0x00033> in <filename unknown>:0 at ServiceStack.Host.RestHandler+<>c__DisplayClass5.<ProcessRequestAsync>b__0 (System.Object response) <0x6e0c5678 + 0x00207> in <filename unknown>:0 at ServiceStack.Host.Handlers.ServiceStackHandlerBase.HandleResponse (System.Object response, System.Func`2 callback, System.Func`2 errorCallback) <0x6e0c50d0 + 0x001d3> in <filename unknown>:0 InnerException: System.Net.Sockets.SocketException The socket has been shut down at System.Net.Sockets.Socket.Send (System.Byte[] buffer, Int32 offset, Int32 size, SocketFlags flags) <0x6e0bb288 + 0x000c8> in <filename unknown>:0 at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x6e0bad28 + 0x000a3> in <filename unknown>:0 2016-02-08 00:06:23.0352 Info HttpServer: HTTP Response 500 to 192.168.1.103. Time: 2818ms (slow). http://192.168.1.103:8096/emby/Audio/d9172048194fe70a3853b233fff6fcc8/stream.mp32016-02-08 00:06:23.7532 Info MediaEncoder: Killing ffmpeg process2016-02-08 00:06:23.8485 Info App: Killing ffmpeg process for /var/lib/emby-server/transcoding-temp/f7fa9151e0c3750a142f2229fa3742a7.mp32016-02-08 00:06:24.1536 Info App: FFMpeg exited with code 02016-02-08 00:06:24.1536 Info App: Deleting partial stream file(s) /var/lib/emby-server/transcoding-temp/f7fa9151e0c3750a142f2229fa3742a7.mp3 Am I right that the transcoding-temp folder need to have read/write permissions (0777) to everyone? Link to comment Share on other sites More sharing options...
Luke 36999 Posted February 8, 2016 Share Posted February 8, 2016 that doesnt really look right because the kodi dlna profile is built to direct stream everything without transcoding. i wonder if the wrong profile was chosen. in any event, please always provide complete log files. Link to comment Share on other sites More sharing options...
xnappo 1593 Posted February 8, 2016 Share Posted February 8, 2016 Wait, are you using the Emby DLNA server or are you trying to use the Kodi one? Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 8, 2016 Author Share Posted February 8, 2016 Wait, are you using the Emby DLNA server or are you trying to use the Kodi one? I use the Kodi DLNA, not the Emby DLNA, not the Emby webclient to play music to my receiver and not the Kodi GUI. Just the remote control of my receiver to play music with DLNA Kodi on my receiver. For more logs: I will send some when I'm back home. Link to comment Share on other sites More sharing options...
xnappo 1593 Posted February 8, 2016 Share Posted February 8, 2016 (edited) @@Angelblue05 @@Luke - so Kodi *itself* can be a DLNA server. So he is going Receiver->Kodi DLNA->Emby_provided_path . @@Bernie V - why not just use the Emby DLNA sever instead? Edited February 8, 2016 by xnappo Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 8, 2016 Author Share Posted February 8, 2016 @Angelblue05 @Luke - so Kodi *itself* can be a DLNA server. So he is going Receiver->Kodi DLNA->Emby_provided_path . => Correct, In Kodi I enabled DLNA and can browse in the Kodi music DLNA folders and files of Kodi (Genres, artists, last added albums, playlists, ...). When I try to play music => see the error in my first post. Al my music in Kodi is provided by the Emby add-on. @Bernie V - why not just use the Emby DLNA sever instead? => 1) The Emby DLNA in my setup is disabled (generated to much overload) 2) Playlist management for music is better in Kodi 3) Kodi is my frontend for music and movies, Emby is my backend Link to comment Share on other sites More sharing options...
xnappo 1593 Posted February 8, 2016 Share Posted February 8, 2016 (edited) Ok - yes I agree playlists are better in Kodi. Hopefully @@Angelblue05 or @@marcelveldt can figure out what is different between us creating the DB entry and the native scraper. Why do you like browsing music from your receiver though? Is it in a different room? Just curious. Edited February 8, 2016 by xnappo Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 8, 2016 Author Share Posted February 8, 2016 Ok - yes I agree playlists are better in Kodi. Hopefully @@Angelblue05 or @@marcelveldt can figure out what is different between us creating the DB entry and the native scraper. Why do you like browsing music from your receiver though? Is it in a different room? Just curious. Yes, I have a multiroom systeem. Link to comment Share on other sites More sharing options...
xnappo 1593 Posted February 8, 2016 Share Posted February 8, 2016 It looks like your music DB is set up with HTTP paths. That is probably the problem. You need to set it up with direct paths. Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 8, 2016 Author Share Posted February 8, 2016 It looks like your music DB is set up with HTTP paths. That is probably the problem. You need to set it up with direct paths. Yes, I use don't use direct paths. I will change this en give it a try. Thx! Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 9, 2016 Share Posted February 9, 2016 I've tested with direct paths and it works correctly. 1 Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 9, 2016 Author Share Posted February 9, 2016 I've tested with direct paths and it works correctly. Happy that this is possible! I changed it yesterday but the Kodi sync wasn't completed when I went working. Another thing: Just found that my path substitution in Emby had a typo: mnt/music -> nfs://x.x.x.x/volume1/music has to be /mnt/music -> nfs://x.x.x.x/volume1/music (I forget a /) This was causing the error unsupported protocol(/nfs) in /nfs://192.168.1.101/volume1/music/Unmixed Compilations/Various/30 Stars - Acoustic/Simon & Garfunkel - The Sound Of Silence.mp3 Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 13, 2016 Author Share Posted February 13, 2016 I can confirm DLNA playing is working now with direct paths from my receiver. I only see that the played songs aren't showed up in the history of played songs in Emby. I there a way to do this without starting the songs directly from Kodi? Link to comment Share on other sites More sharing options...
Luke 36999 Posted February 13, 2016 Share Posted February 13, 2016 Well done Link to comment Share on other sites More sharing options...
xnappo 1593 Posted February 13, 2016 Share Posted February 13, 2016 (edited) Sounds like Kodi doesn't send an OnPlaybackStarted event when playback starts from DLNA. Nothing we can do on our side, you would have to ask the Kodi devs. Edited February 13, 2016 by xnappo Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 13, 2016 Author Share Posted February 13, 2016 Sounds like Kodi doesn't send an OnPlaybackStarted event when playback starts from DLNA. Nothing we can do on our side, you would have to ask the Kodi devs. I tried the same with Emby DLNA enabled and played a song on my receiver with Emby DLNA -> also no history in Emby of the played songs. Link to comment Share on other sites More sharing options...
Vidman 589 Posted February 13, 2016 Share Posted February 13, 2016 I believe that is by design for emby dlna Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 14, 2016 Share Posted February 14, 2016 When you play via dlna in Kodi, it doesn't report the item the same way. We could do a manual search with the title, but I honestly have no plan on implementing this any time soon, if ever. Via dlna, Kodi returns this: Method: Player.OnPlay Data: {"item":{"album":"The Best Damn Thing","artist":["Avril Lavigne"],"title":"Girlfriend","track":1,"type":"song"},"player":{"playerid":0,"speed":1}} When you play on the same device, this is what Kodi returns (this works): Method: Player.OnPlay Data: {"item":{"id":11,"type":"song"},"player":{"playerid":0,"speed":1}} Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 14, 2016 Author Share Posted February 14, 2016 (edited) When you play via dlna in Kodi, it doesn't report the item the same way. We could do a manual search with the title, but I honestly have no plan on implementing this any time soon, if ever. That's a pitty. At this moment music playlists based on "the last played time" of a track are useless when the music is played over DLNA. Or are there other options where I don't know about to play "not recently played music" over DLNA? Edited February 14, 2016 by Bernie V Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 14, 2016 Share Posted February 14, 2016 Actually testing it again, it would not be possible for us to fix this. Kodi doesn't report anything on the main Kodi device where the emby add-on is, if I play something via dlna. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
xnappo 1593 Posted February 14, 2016 Share Posted February 14, 2016 Right - like I said - need to request that from the Kodi team. 1 Link to comment Share on other sites More sharing options...
Bernie V 7 Posted February 14, 2016 Author Share Posted February 14, 2016 (edited) Right - like I said - need to request that from the Kodi team. In meantime I asked it in the Kodi feature request forum Edited February 14, 2016 by Bernie V 1 Link to comment Share on other sites More sharing options...
Recommended Posts