YAMJ / yamj-v2

Yet Another Movie Jukebox (YAMJ) v2
GNU General Public License v3.0
28 stars 11 forks source link

MediaInfo-rar doesn't scan IP format paths #2444

Closed Omertron closed 8 years ago

Omertron commented 9 years ago

Original issue 2445 created by Omertron on 2012-07-01T08:39:49.000Z:

What steps will reproduce the problem?

  1. Add 2 different media paths
  2. Run YAMJ with mediainfo-rar enabled
  3. BD ISOs on the 2nd media path have no mediainfo. BD ISOs on the 1st media path have mediainfo. Normal mediainfo (DVD ISO, MKVs) work on both media paths.

What is the expected output? What do you see instead? Mediainfo-rar should work on both media paths, just like media info does.

What version/revision of YAMJ are you using? On what operating system? R3142

What skin are you using? Eversion

What device are you using YAMJ on? Networked Media Tank, PlayonHD, Other? A300, A200

Please provide any additional information below. Mediainfo-rar: http://www.lundman.net/wiki/index.php/Mediainfo-rar

Omertron commented 9 years ago

Comment #1 originally posted by Omertron on 2012-07-02T10:56:37.000Z:

After further testing it is not related to how many libraries you have, but rather how you set up a library.

Mediainfo-rar work:

Y:/
<playerpath>smb://[nobody=a]192.168.0.101/Media/</playerpath>

Mediainfo-rar doesn't work:

\\192.168.0.101\Media
<playerpath>smb://[nobody=a]192.168.0.101/Media/</playerpath>

It seems you can not set the path to "\XXX.XXX.X.XXX\" without it breaking Mediainfo-rar. The GUI generates My_Library with \. Editing it to \ and YAMJ won't run. With \, all my media is scanned and plays correctly but mediainfo-rar gets no results.

Looks like I will need to use a mapped drive, but it is a bug regardless.

Omertron commented 9 years ago

Comment #2 originally posted by Omertron on 2012-07-02T12:14:23.000Z:

I think the difference is not the number of "\" in the path, but rather that the path is served via a HTTP server (at least to the scanner's perspective)

Thanks for continuing to look into it. I'll have a look at the MI scanner code and see what can be done to it.