Jump to content

fail to play ISO and BDMV in emby for kodi next gen


bcqingfeng
Go to solution Solved by quickmic,

Recommended Posts

bcqingfeng

I installed kodi-20.1-Nexus-arm64-v8a and kodi nextgen v8.2.8 on a S905 tv box but it failed to playback ISO and BDMV movies. 

Tried to debug on a win10 PC with Kodi 19.5 and kodi nextgen v8.2.8. The same thing happens.

Tried:

for ISO: 

1. kodi 19.5 with embynexgen 8.2.8, play ISO, failed;

2. kodi 19.5 with embynexgen 8.2.8, play MKV, successed;

3. emby theater 3.0.15 for win, play ISO, partly successed (can play but stays at the menu,need to drag the progress bar);

4. emby 3.2.32 for android phone, play ISO, partly successed (can play but stays at the menu,need to drag the progress bar);

5. emby v2.0.83 for android TV , play ISO, partly successed (can play but stays at the menu,need to drag the progress bar);

6. kodi 19.5, add video source with webdav mounted, play ISO, successed.

 

for BDMV:

7. emby theater 3.0.15 for win, play BDMV, successed  --image3

8. kodi 19.5 with embynexgen 8.2.8, play BDMV, failed  --image1

9. kodi 19.5, add video source with webdav mounted, play BDMV (index.bdmv), successed; --image2

the logs of 1, 2, 3, 6, 7, 8, 9 are copied to attached log txt. (sorry for possible inconvenience, please let me know if need to be seprated files)

 

Looks like the nexgen add-on is getting native path from server when play ISO and BDMV,  while the emby native apps get the right path.  How can i figure this?

image.png

image.png

image.png

LOGS.txt

Edited by bcqingfeng
Link to comment
Share on other sites

quickmic

I only reviewed the log, no tests performed yet, but question:

Is this path correct and accessible by Kodi? Have you mounted the drive?

2023-06-27 10:25:07.367 T:20904    INFO <general>: VideoPlayer::OpenFile: /volume2/mnt/CloudDrive/189cloud/mount/189BD/鬼子来了 (2000)/Devils.on.the.Doorstep.2000.DVD.480i.MPEG-2.Dolby.Digital.5.1.ISO
2023-06-27 10:25:07.369 T:29152    INFO <general>: Creating InputStream
2023-06-27 10:25:07.369 T:29152   ERROR <general>: XFILE::CDirectory::GetDirectory - Error getting /volume2/mnt/CloudDrive/189cloud/mount/189BD/鬼子来了 (2000)/
2023-06-27 10:25:07.391 T:29152   ERROR <general>: Skipped 1 duplicate messages..

-> "/volume2/mnt/CloudDrive/189cloud/mount/189BD/鬼子来了 (2000)/Devils.on.the.Doorstep.2000.DVD.480i.MPEG-2.Dolby.Digital.5.1.ISO"

Link to comment
Share on other sites

quickmic
2 minutes ago, quickmic said:

I only reviewed the log, no tests performed yet, but question:

Is this path correct and accessible by Kodi? Have you mounted the drive?

2023-06-27 10:25:07.367 T:20904    INFO <general>: VideoPlayer::OpenFile: /volume2/mnt/CloudDrive/189cloud/mount/189BD/鬼子来了 (2000)/Devils.on.the.Doorstep.2000.DVD.480i.MPEG-2.Dolby.Digital.5.1.ISO
2023-06-27 10:25:07.369 T:29152    INFO <general>: Creating InputStream
2023-06-27 10:25:07.369 T:29152   ERROR <general>: XFILE::CDirectory::GetDirectory - Error getting /volume2/mnt/CloudDrive/189cloud/mount/189BD/鬼子来了 (2000)/
2023-06-27 10:25:07.391 T:29152   ERROR <general>: Skipped 1 duplicate messages..

-> "/volume2/mnt/CloudDrive/189cloud/mount/189BD/鬼子来了 (2000)/Devils.on.the.Doorstep.2000.DVD.480i.MPEG-2.Dolby.Digital.5.1.ISO"

Can you please also perform a test on a Windows PC with. Maybe you Box is not capable to open the file. (I had that on some devices).

2023-06-27 10:25:34.368 T:32036 WARNING <general>: could not find codec parameters for Z:\mnt\CloudDrive\189cloud\mount\189BD\鬼子来了 (2000)\Devils.on.the.Doorstep.2000.DVD.480i.MPEG-2.Dolby.Digital.5.1.ISO

 

Link to comment
Share on other sites

bcqingfeng
1 hour ago, quickmic said:

Can you please also perform a test on a Windows PC with. Maybe you Box is not capable to open the file. (I had that on some devices).

2023-06-27 10:25:34.368 T:32036 WARNING <general>: could not find codec parameters for Z:\mnt\CloudDrive\189cloud\mount\189BD\鬼子来了 (2000)\Devils.on.the.Doorstep.2000.DVD.480i.MPEG-2.Dolby.Digital.5.1.ISO

 

Hi Quickmic, thanks for your reply!

For the first point you mentioned "Is this path correct and accessible by Kodi? Have you mounted the drive?"  The answer is NO.

As mentioned I think this is the exact problem, Kodi with emby nexgen addon is getting the streaming path from server for MKV, so that is a success.

but for ISO and BDMV the server gave direct file path ,which is not mounted on KODI, so the playback failed. 

Further more, I dont think this path can be mounted on KODI since it is on the server's host.

 

Supplementary: Never set "Shared network folder" in the emby library;     emby nexgen works under default addon mode. 

Interestingly for "native" EMBY apps, they are getting correct path for ISO and BDMV.

 

For the test on windows PC, yes, all the tests except 4 and 5 are performed on win10 PC (Kodi 19.5 with embynexgen; emby theater). (test 4 and 5 were performed on android phone and TV, not so easy to get the log and they act the same as in PC, so i did not include the logs.) The codec warning you noticed is not a problem, it went on playing smoothly.

 

image.thumb.png.3c8651494ca88dce93a564f023f49184.png

image.thumb.png.2753f1880e180cfbc669caf3c6d66fb2.png

 

image.thumb.png.b9241d4b0e13711e175d38a5a4481571.png

image.thumb.png.f28e535e10192eada82dbdded0037969.png

 

Please tell me if i am missing something.

Link to comment
Share on other sites

quickmic
Quote

For the first point you mentioned "Is this path correct and accessible by Kodi? Have you mounted the drive?"  The answer is NO.

As mentioned I think this is the exact problem, Kodi with emby nexgen addon is getting the streaming path from server for MKV, so that is a success.

but for ISO and BDMV the server gave direct file path ,which is not mounted on KODI, so the playback failed. 

Further more, I dont think this path can be mounted on KODI since it is on the server's host.

Well yes, Kodi plugin uses native access to filesystem when playing ISO or bdmv. In the past, Emby server was not capable to play such content directly. Seems the situation has changed @Luke

Currently you need native access for the plugin but I'll review if improvement is possible.

Link to comment
Share on other sites

bcqingfeng
22 hours ago, quickmic said:

Well yes, Kodi plugin uses native access to filesystem when playing ISO or bdmv. In the past, Emby server was not capable to play such content directly. Seems the situation has changed @Luke

Currently you need native access for the plugin but I'll review if improvement is possible.

Thanks for your explanation! Do you mean reset the plugin to native access mode instead of addon mode?

Link to comment
Share on other sites

quickmic
55 minutes ago, bcqingfeng said:

Thanks for your explanation! Do you mean reset the plugin to native access mode instead of addon mode?

No, you can keep addon mode.

Addon mode automatically falls back to native mode when playing iso, but it needs file access.

Edited by quickmic
Link to comment
Share on other sites

bcqingfeng
22 hours ago, quickmic said:

No, you can keep addon mode.

Addon mode automatically falls back to native mode when playing iso, but it needs file access.

thanks! so i need to fill file address at the emby library "Shared network folder", and make that accessible to KOI, like "nfs://192.168.0.108/volume2/mnt/CloudDrive/189cloud/mount/189BD", right?

Link to comment
Share on other sites

  • Solution
quickmic
6 minutes ago, bcqingfeng said:

thanks! so i need to fill file address at the emby library "Shared network folder", and make that accessible to KOI, like "nfs://192.168.0.108/volume2/mnt/CloudDrive/189cloud/mount/189BD", right?

Depends, but probably yes. Native access configuration is highly dependent on your network specifications. E.g. I use native mode on OS level bases means the os itself mounts the drives. Anyway that's my config and seems not to be an option for your setup (Emby server on Windows).

You need to set "Shared network folder" on nfs:// or smb:// on Emby server side. Also Kodi needs that folder to be mounted (credentials). -> Testting via Kodi's filebrowser, it needs access to the mounts.

Edited by quickmic
Link to comment
Share on other sites

quickmic

Edit:

I think the smb prefix is not even neccessary. only "\\192.168.0.205\storage2\emby-test\subtitle2-smb4" as shared path. (at least for smb)

Edited by quickmic
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...