Jump to content

Some movies cannot be played when using webdav in direct mode


wxg1015
 Share

Go to solution Solved by wxg1015,

Recommended Posts

wxg1015

I recently used emby for kodi direct mode webdav and found a problem, when there are spaces in the link, it will not play. For example, http://192.168.0.10/movie/jo jo/1.mkv or http://192.168.0.10/movie/1/jo jo.mkv. I compared other videos and found that only those with spaces in the path cannot be played. Checked the log and found that the error code is http 400.
In addition, I tried to add webdav directly with kodi. I found that movies with spaces in the path can be played normally, so the problem should be the plug-in.
Nfs does not seem to have this problem, only webdav. 

Link to comment
Share on other sites

wxg1015
It seems that this problem exists in all versions of the plug-in, from 4.x to the latest 6.0.9。
Link to comment
Share on other sites

wxg1015

When kodi directly accesses the webdav link without plugin, it will automatically replace the space with %20, so it can be played normally. I guess, emby for kodi may not do this step?

photo_2021-09-20_09-56-01.jpg

Edited by wxg1015
Link to comment
Share on other sites

wxg1015

Sorry, I used the translation software to translate it. There may be errors... Let me briefly talk about it

1.native mode

2.webdav

3. There are spaces in the name of the movie

When the above three conditions are met, the video will not be played and an error will be reported

Edited by wxg1015
Link to comment
Share on other sites

quickmic
On 9/20/2021 at 3:56 AM, wxg1015 said:

When kodi directly accesses the webdav link without plugin, it will automatically replace the space with %20, so it can be played normally. I guess, emby for kodi may not do this step?

photo_2021-09-20_09-56-01.jpg

 

Let me try to understand... You use native mode to sync content to Kodi. The native content is actually a "http://" link, correct?

If so, I'll test it. I could imagine, what's going wrong here.

Have you also tried addon-mode? It might work...

Link to comment
Share on other sites

wxg1015
1 hour ago, quickmic said:

 

Let me try to understand... You use native mode to sync content to Kodi. The native content is actually a "http://" link, correct?

If so, I'll test it. I could imagine, what's going wrong here.

Have you also tried addon-mode? It might work...

Yes, you are completely correct.  It is "http://". This problem does not exist in the addon-mode, only occurs in the native-mode.  

Link to comment
Share on other sites

quickmic
35 minutes ago, wxg1015 said:

Yes, you are completely correct.  It is "http://". This problem does not exist in the addon-mode, only occurs in the native-mode.  

ok, thanks for confirmation. The problem is "http://" URLs don't allow spaces. I can write a workaround but actually the core issue is somewhere else.

This native "http://" path is coming from Emby server. Not sure which content you use, anyway. Even Emby server should not have an "invalid" http:// path in it's database.

I assume, the http pathes are generated with a 3rd party plugin/tool whatever. It should never have generated invalid http pathes. The problem will not only be related to spaces. There are many more "forbidden" charecters in URLs.

in your example:

"http://192.168.0.10/movie/jo jo/1.mkv" has been generated by some tool or you did it manually.

if you drop "http://192.168.0.10/movie/jo jo/1.mkv" into a browser it will autmatically "fix" the URL to: "http://192.168.0.10/movie/jo%20jo/1.mkv"

But actually, this should not even happen. The URLs should be valid in the first place.

Anyway, as mentioned. I think I can write a workaround.

 

Edited by quickmic
Link to comment
Share on other sites

wxg1015
10 minutes ago, quickmic said:

ok, thanks for confirmation. The problem is "http://" URLs don't allow spaces. I can write a workaround but actually the core issue is somewhere else.

This native "http://" path is coming from Emby server. Not sure which content you use, anyway. Even Emby server should not have an "invalid" http:// path in it's database.

I assume, the http pathes are generated with a 3rd party plugin/tool whatever. It should never have generated invalid http pathes. The problem will not only be related to spaces. There are many more "forbidden" charecters in URLs.

in your example:

"http://192.168.0.10/movie/jo jo/1.mkv" has been generated by some tool or you did it manually.

if you drop "http://192.168.0.10/movie/jo jo/1.mkv" into a browser it will autmatically "fix" the URL to: "http://192.168.0.10/movie/jo%20jo/1.mkv"

But actually, this should not even happen. The URLs should be valid in the first place.

Anyway, as mentioned. I think I can write a workaround.

 

The content I filled in on the emby server is shown in the figure.  In addition, as I said before, kodi directly adding webdav will not cause this problem.  Because kodi will automatically add %20.  as the picture shows

Screenshot_20210922_152612.jpg

IMG_20210919_105942_374.jpg

  • Like 1
Link to comment
Share on other sites

wxg1015
1.txt1.txt
16 minutes ago, wxg1015 said:

我在emby服务器上填写的内容如图。另外,我之前说过,kodi直接加入webdav不会造成这个问题。因为 kodi 会自动添加 %20。如图所示

截图_20210922_152612.jpg

IMG_20210919_105942_374.jpg

Videos without spaces in the name can be played normally. I checked the log. You can take a look.

1.txt

 

2.txt

Edited by wxg1015
Link to comment
Share on other sites

quickmic

Please test this url with a webbrowser:

http://2501.jinyu.top:5005/movie/Marriage Story 2019 BluRay 1080p DTS-HD MA 5.1 x264-MTeam/Marriage.Story.2019.BluRay.1080p.DTS-HD.MA.5.1.x264-MTeam.mkv

Does it work?

 

The (not working) url:

"http://2501.jinyu.top:5005/movie/Marriage Story 2019 BluRay 1080p DTS-HD MA 5.1 x264-MTeam/Marriage.Story.2019.BluRay.1080p.DTS-HD.MA.5.1.x264-MTeam.mkv"

...compared with (working) URL...

"http://2501.jinyu.top:5005/movie/Shao.Lin.Si.Zhi.De.Bao.Chuan.Qi.2021.2160p.WEB-DL.H265.DV.DDP5.1-PTerWEB.mp4"

..has also a "subdirectory" included in the path:

Syntax of not working URL:

"http://2501.jinyu.top:5005/movie/SUBDIRECTORY/Marriage.Story.2019.BluRay.1080p.DTS-HD.MA.5.1.x264-MTeam.mkv"

The SUBDIRECTORY has the spaces in the name. I need to know, if replacing the spaces is enough to fix it or if the URL is completly wrong.

Edited by quickmic
Link to comment
Share on other sites

wxg1015
2 minutes ago, quickmic said:

请使用网络浏览器测试此网址:

http://2501.jinyu.top:5005/movie/Marriage Story 2019 蓝光 1080p DTS-HD MA 5.1 x264-MTeam/Marriage.Story.2019.BluRay.1080p.DTS-HD.MA.5.1.x264-MTeam. MKV

它有效吗?

 

(不工作)网址:

" http://2501.jinyu.top:5005/movie/Marriage Story 2019 蓝光 1080p DTS-HD MA 5.1 x264-MTeam/Marriage.Story.2019.BluRay.1080p.DTS-HD.MA.5.1.x264-MTeam .mkv”

...与(工作)网址相比...

"http://2501.jinyu.top:5005/movie/Shao.Lin.Si.Zhi.De.Bao.Chuan.Qi.2021.2160p.WEB-DL.H265.DV.DDP5.1-PTerWEB.mp4"

..还有一个包含在路径中的“子目录”:

无效 URL 的语法:

http://2501.jinyu.top:5005/movie/SUBDIRECTORY/Marriage.Story.2019.BluRay.1080p.DTS-HD.MA.5.1.x264-MTeam.mkv

SUBDIRECTORY 在名称中有空格。我需要知道,如果替换空格就足以修复它,或者 URL 是否完全错误。

As mentioned earlier, if you use kodi and webdav directly, all movies can be played normally, regardless of whether there are spaces in the path. Including the use of mx player or web browser. According to my test, an error will be reported if there is a space in the path, and an error will be reported if there is a space in the subdirectory name or movie name, not just the movie name. In my opinion, movies that do not contain spaces in the subdirectory name and movie name can be played normally. The problem lies in the spaces. "There are spaces in the url" causes the movies to not be played.

1.PNG

2.PNG

3.PNG

4.PNG

Link to comment
Share on other sites

quickmic

I added a fix but note sure if it works. I have no test case. It depends how Emby server reports the "http" path via API. You can test it in next version (currently under development).

 

Link to comment
Share on other sites

wxg1015
6 hours ago, quickmic said:

I added a fix but note sure if it works. I have no test case. It depends how Emby server reports the "http" path via API. You can test it in next version (currently under development).

 

Okay, thank you, I will give you feedback after the test

Link to comment
Share on other sites

wxg1015
12 hours ago, quickmic said:

I added a fix but note sure if it works. I have no test case. It depends how Emby server reports the "http" path via API. You can test it in next version (currently under development).

 

Where will I find the updated plug-in? Is the public testing folder?

photo_2021-09-23_13-00-54.jpg

Link to comment
Share on other sites

quickmic
3 minutes ago, wxg1015 said:

Where will I find the updated plug-in? Is the public testing folder?

photo_2021-09-23_13-00-54.jpg

Not released yet, I'll send you a test version. A complete database resync will be required!

Link to comment
Share on other sites

wxg1015
3 hours ago, quickmic said:

Not released yet, I'll send you a test version. A complete database resync will be required!

great! It works well. But there is a small problem. As shown in the figure, the account password of webdav seems to be displayed in plain text. Does it need to be repaired at this time photo_2021-09-23_16-18-18.thumb.jpg.a430b2547dbd06030f6a3946feb22387.jpg

Link to comment
Share on other sites

wxg1015
4 hours ago, quickmic said:

Not released yet, I'll send you a test version. A complete database resync will be required!

Well, the account password is not displayed by default, only after I perform the operations as shown in the figure. I clicked the button in the picture, and the account password appeared on the movie information page that appeared. I don't remember if this happened in the previous version. Anyway, this should be considered wrong, right? before.thumb.jpg.c7ec11d2b418081f7da30760a41efc57.jpgbefore.thumb.jpg.c7ec11d2b418081f7da30760a41efc57.jpg

action.jpg

after.jpg

Link to comment
Share on other sites

wxg1015
4 hours ago, quickmic said:

Not released yet, I'll send you a test version. A complete database resync will be required!

Well, the previous version also had this problem...

Link to comment
Share on other sites

quickmic
6 hours ago, wxg1015 said:

Well, the previous version also had this problem...

This is not a problem of the plugin. That's "normal" in your use case. What you see (including the password) is indeed the "filename". This is what emby server reports as filepath and is quite understandable. I don't wanna bother you with technical details, anyway.

The only option is using the addon mode. Technically, I see no reason why it should not work. Please test again in addon mode, I'll also check.

Edited by quickmic
Link to comment
Share on other sites

wxg1015
3 hours ago, quickmic said:

这不是插件的问题。这在您的用例中是“正常的”。您看到的(包括密码)确实是“文件名”。这是 emby 服务器报告为文件路径的内容,并且非常容易理解。无论如何,我不想用技术细节来打扰你。

唯一的选择是使用插件模式。从技术上讲,我认为它没有理由不工作。请在插件模式下再次测试,我也会检查。

Got it, thanks

Link to comment
Share on other sites

  • 1 month later...
wxg1015
On 9/24/2021 at 12:25 AM, quickmic said:

This is not a problem of the plugin. That's "normal" in your use case. What you see (including the password) is indeed the "filename". This is what emby server reports as filepath and is quite understandable. I don't wanna bother you with technical details, anyway.

The only option is using the addon mode. Technically, I see no reason why it should not work. Please test again in addon mode, I'll also check.

Sorry for bothering you. But it seems that the plug-in does not work perfectly. For the "/bdmv" folder

1.jpg

2.jpg

3.jpg

4.jpg

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
 Share

×
×
  • Create New...