Need help troubleshooting log file for playback issues on AFTV2

[jkasanic 12]

Ok, so I'm fairly new to Kodi (Jarvis 16.1) as well as the AFTV2. I have everything working well with Internet streams but I can't seem to get local file playback from my UnRAID server to work. I've finally figured out how to get a url of my log file:

 

https://paste.ubuntu.com/23132662/

 

As I didn't realize the email server wasn't working in Log Uploader.

 

Anyway, I scanned the log file and think I'm having issues getting my advancedsettings.xml file to load. I created this file because I thought the root cause of my playback issue was related to buffering/timeout issues?! I was getting can't play next item and file failed to play errors.

 

Looking for some detailed guidance to get Kodi with emby add-on playing my local files. Please let me know if I've forgotten any important details.

[hoppel118 37]

"Can't find next item to play" can be a problem with your network credentials. Is your network share reachable from within kodi?

 

Show us the content of your advancedsettings.xml.

Edited September 4, 2016 by hoppel118

[jkasanic 12]

"Can't find next item to play" can be a problem with your network credentials. Is your network share reachable from within kodi?

 

Show us the content of your advancedsettings.xml.

Contents of special://profile/advancedsettings.xml are...                                            <!-- Created using Easy Advanced Settings addon -->                                            <advancedsettings>                                              <network>                                                <buffermode>1</buffermode>                                                <cachemembuffersize>104857600</cachemembuffersize>                                                <curlclienttimeout>10</curlclienttimeout>                                                <curllowspeedtime>15</curllowspeedtime>                                                <readbufferfactor>10</readbufferfactor>                                              </network>                                              <measurerefreshrate>true</measurerefreshrate>                                              <skiploopfilter>0</skiploopfilter>                                            </advancedsettings>

I pulled this from the log file link. i'm not sure if these settings are even being applied though based on log errors?!

 

Edit: Just wanted to note that I have Emby for iOS app working fine with my setup so I don't think it's a server permissions issue.

Edited September 4, 2016 by jkasanic

[hoppel118 37]

For my odroid c2 I figured out that the following buffer settings work fine:

<advancedsettings>  <network>    <buffermode>1</buffermode>    <cachemembuffersize>157286400</cachemembuffersize>    <readbufferfactor>20</readbufferfactor>  </network>  <pvr>    <minvideocachelevel>20</minvideocachelevel>    <minaudiocachelevel>20</minaudiocachelevel>  </pvr></advancedsettings>

The odroid c2 has 2gb of ram.

 

But I don't think that wrong buffer settings have something to do with the error message "Can't find next item to play".

 

Did you try this? http://emby.media/community/index.php?/topic/38097-error-playlist-cant-find-a-next-item-to-play/?p=357258

 

Do you use path substitutions with hostnames? Try the IP instead of the hostname: http://emby.media/community/index.php?/topic/36681-emby-for-kodi-network-credentials-and-ip-path-substitution-needed-under-libreelec-to-play-mp3s/

Edited September 4, 2016 by hoppel118

[jkasanic 12]

I don't believe I'm using path substitutions but will confirm.  in the meantime, I also captured part of the Emby Addon log that I think is pertinent to my issue. Seems like the port 6357 might be causing an issue?

 

Edit: I forgot to include these lines where 192.168.1.108 is the local ip of my AFTV2:

 

http://192.168.1.71:8096/dlna/cc949481b15362ce240c6817952ec927/connectionmanager/events

2016-09-04 00:10:06.5610 Info HttpClient: HttpClientManager GET: http://192.168.1.108:6357/

2016-09-04 00:10:06.5780 Error HttpClient: Error getting response from http://192.168.1.108:6357/

emby.rtf

Edited September 4, 2016 by jkasanic

[Angelblue05 4130]

Your issue is plain and simple. You need to convert your local paths to network paths using Emby path substitution, so that every device within your network can access your storage.

 

Did you search the forums; we answer this question a few times a week...

 

Check the wiki: https://github.com/MediaBrowser/Wiki/wiki/Path%20Substitution

 

Otherwise, just enable under the emby add-on settings > playback tab > play from http

This will bypass any path issues since the server will then be providing the file to Kodi.

 

Sent from my iPhone using Tapatalk

Edited September 4, 2016 by Angelblue05

[jkasanic 12]

Ok, I'll take a look at the links you provided when I get home. As far as setting up the paths vs http, is there any downside? My AFTV2 can't direct play my mkv files as far as I can tell, but if I have other devices that can (WDTV live plus, PCH A-400 etc), is there any difference? Thanks for your post.

[Angelblue05 4130]

I have been using playback from HTTP for about two weeks now, and I can tell you I don't see differences between the two. You may need to adjust advancedsettings in Kodi to get perfect playback without any buffering. The file being played is the same, except it's just provided to the client via HTTP rather than Kodi accessing the file via a network protocol.

 

Give it a try, let me know how it performs on your device.

Edited September 4, 2016 by Angelblue05

[jkasanic 12]

Your issue is plain and simple. You need to convert your local paths to network paths using Emby path substitution, so that every device within your network can access your storage.

 

Did you search the forums; we answer this question a few times a week...

 

Check the wiki: https://github.com/MediaBrowser/Wiki/wiki/Path%20Substitution

 

Otherwise, just enable under the emby add-on settings > playback tab > play from http

This will bypass any path issues since the server will then be providing the file to Kodi.

 

Sent from my iPhone using Tapatalk

 

So I took a look at path substitution. I'm not sure how I would use this in my setup since I'm basically using a linux distro (UnRAID in my case) to feed media to Kodi.  My network paths are predefined in the docker container for emby (e.g. /config is mapped to /mnt/cache/appdata/emby/ and /mnt is mapped to /mnt/user/Media which is the location of my Media files).

 

The examples shown for path substitution don't really make sense since I'm not using any mapped drives?! Perhaps I'm missing something or maybe I should post my issue over in the emby docker support thread on the UnRAID forum?

 

FWIW, enabling http as you suggested worked for my high bitrate mkv's and the dashboard reports "direct playing" is enabled on the stream?!

Edited September 5, 2016 by jkasanic

[Angelblue05 4130]

Yeah it's the exact same file when you play from HTTP as when you play from network protocol. The only difference is how the file is accessed.

Edit: I forgot to mention it also uses very little cpu on your Emby server.

 

Your path should look like:

From: /mnt/
To: \\{ipaddress}\

Then your paths would look like: smb://{ipaddress}/mnt/user/Media

 

If you use nfs instead then

From: /mnt/
To: nfs://{ipaddress}/

You need to make sure the end path is actually valid.

Edited September 5, 2016 by Angelblue05

[jkasanic 12]

Ok, cool. For some reason I just assumed http would force a transcode. I'll play around with the paths tomorrow and report back. Thanks for all the help!

[Angelblue05 4130]

To force transcode, you need to reduce the video quality. It will kick in when we compare the bitrate values.

[jkasanic 12]

so adding the /mnt to \\serverip\Media path substitution worked as well.  No discernible differences on my 50" LCD but I'll experiment with my projector as well.  i even deleted my advancedsettings.xml and it streams perfectly.  I haven't tried any Atmos or DTS:X titles yet. Those give my PCH A-400 fits sometimes. Will be nice to compare now!  Thanks again!