INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: [Bug] Two issues with network related paths  (Read 2457 times)

)p(

  • Citizen of the Universe
  • *****
  • Posts: 579
[Bug] Two issues with network related paths
« on: January 04, 2012, 03:28:17 am »

Two possible network path related bugs:

1) Playing audio over upnp with network path set to x: from original local d: does not work
When MC sends a Play To command through upnp (Whitebear) for a track in my local library (d:) it sends the string a) below, but when it sends a Play To command for a track on my x: directory (one that does not play) it sends the string b) below:

Code:
a)  <CurrentURI>http://192.168.0.103:52100/Music/F2077920.flac</CurrentURI>

b)  <CurrentURI>http://192.168.0.103:52100/Music/F2357059.</CurrentURI>

It misses the extension.


2) This was mentioned before but still exists in mc 17.0.62.
When using a network path like //Server/etc. jrmc does not find the cover art with the quick find in folder option. It does when you assign it a drive letter.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13940
Re: [Bug] Two issues with network related paths
« Reply #1 on: January 05, 2012, 10:26:03 am »

Two possible network path related bugs:

1) Playing audio over upnp with network path set to x: from original local d: does not work
When MC sends a Play To command through upnp (Whitebear) for a track in my local library (d:) it sends the string a) below, but when it sends a Play To command for a track on my x: directory (one that does not play) it sends the string b) below:

Code:
a)  <CurrentURI>http://192.168.0.103:52100/Music/F2077920.flac</CurrentURI>

b)  <CurrentURI>http://192.168.0.103:52100/Music/F2357059.</CurrentURI>

It misses the extension.
What is the file that "does not play" in example b? Are you saying that the file won't play in Media Center?
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: [Bug] Two issues with network related paths
« Reply #2 on: January 05, 2012, 10:35:50 am »

Bob,

I'm chiming in as I happened to have been following the thread over at the Logitech/Slimdevices forums:

   http://forums.slimdevices.com/showthread.php?t=90842&highlight=whitebear&page=11

The file is a .flac file.  Under one usage scenario (b), the file suffix is omitted.  See the thread above, and posts just prior.
Logged
The opinions I express represent my own folly.

)p(

  • Citizen of the Universe
  • *****
  • Posts: 579
Re: [Bug] Two issues with network related paths
« Reply #3 on: January 05, 2012, 11:48:57 am »

What is the file that "does not play" in example b? Are you saying that the file won't play in Media Center?

It does not play on the upnp renderer/client because the extension is missing.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13940
Re: [Bug] Two issues with network related paths
« Reply #4 on: January 05, 2012, 01:56:54 pm »

Bob,

I'm chiming in as I happened to have been following the thread over at the Logitech/Slimdevices forums:

   http://forums.slimdevices.com/showthread.php?t=90842&highlight=whitebear&page=11

The file is a .flac file.  Under one usage scenario (b), the file suffix is omitted.  See the thread above, and posts just prior.

Thanks for the extra info. I tried duplicating there here without success, perhaps I'm not getting all of the information straight.
I created a file on my linux samba share with a UNC path not mapped to a drive:

\\linux\tmp\ftest\The Beatles - Carry That Weight.flac

Imported \\linux\tmp\ftest into MC, it found my one file.

Plays in MC and I can push the song to the Whitebear server without trouble. When I look at the wireshark dump, all of the file references have the extension in them.
Logged

)p(

  • Citizen of the Universe
  • *****
  • Posts: 579
Re: [Bug] Two issues with network related paths
« Reply #5 on: January 05, 2012, 02:10:10 pm »

Thanks for the extra info. I tried duplicating there here without success, perhaps I'm not getting all of the information straight.
I created a file on my linux samba share with a UNC path not mapped to a drive:

\\linux\tmp\ftest\The Beatles - Carry That Weight.flac

Imported \\linux\tmp\ftest into MC, it found my one file.

Plays in MC and I can push the song to the Whitebear server without trouble. When I look at the wireshark dump, all of the file references have the extension in them.

That is correct. It works with //Server etc. It only happens as I mentioned above when you map the network path to a drive letter. In my example x: and that is how its imported in the jrmc library.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13940
Re: [Bug] Two issues with network related paths
« Reply #6 on: January 05, 2012, 02:28:12 pm »

That is correct. It works with //Server etc. It only happens as I mentioned above when you map the network path to a drive letter. In my example x: and that is how its imported in the MC library.
Still can't reproduce it.
My file is now:
S:\media\samples\FLAC\ftest\The Beatles - Golden Slumbers.flac
which is on the same samba server with a different share mapped to a drive and that's the way it shows up in MC's db (with the s: path).
Works without a hitch.
What's the "file type" in MC's database for the file you are having trouble with?
Logged

Alex B

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 10121
  • The Cosmic Bird
Re: [Bug] Two issues with network related paths
« Reply #7 on: January 05, 2012, 04:04:33 pm »

I can't reproduce this either. I don't have Whitebear, but I tried the foobar2000 UPNP renderer (MC as a DLNA server & controller).

A file from \\192.168.100.1\volume1\Media\Audio\...  (from the NAS server in my router box) played fine directly from the network share and also from R:\Media\Audio\... after mapping the drive letter.

foobar2000 got the correct address & filename in both cases ( e.g. http://192.168.100.55:52100/Music/F24947894.flac )
Logged
The Cosmic Bird - a triple merger of galaxies: http://eso.org/public/news/eso0755

)p(

  • Citizen of the Universe
  • *****
  • Posts: 579
Re: [Bug] Two issues with network related paths
« Reply #8 on: January 05, 2012, 04:16:06 pm »

I can't reproduce this either. I don't have Whitebear, but I tried the foobar2000 UPNP renderer (MC as a DLNA server & controller).

A file from \\192.168.100.1\volume1\Media\Audio\...  (from the NAS server in my router box) played fine directly from the network share and also from R:\Media\Audio\... after mapping the drive letter.

foobar2000 got the correct address & filename in both cases ( e.g. http://192.168.100.55:52100/Music/F24947894.flac )

Ok that definitely rules out a problem with MC. Must be something weird on my end. I'll just rescan my library using //Server paths. Those work for me.
Thanks for taking time to test this :)
Logged

Alex B

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 10121
  • The Cosmic Bird
Re: [Bug] Two issues with network related paths
« Reply #9 on: January 05, 2012, 04:26:10 pm »

If you really want/need to change the file paths you don't need to re-import (and lose your playback statistics and "date imported" values). The Rename, Move, & Copy Files tool can do the task.

In my example case, I would set it to "Find What: R:\" and "Replace With: \\192.168.100.1\volume1\" and apply the changes only to the database, i.e. select the "Update database to point to new location (no file rename, move, or copy)" option from the tool's drop-down menu.
Logged
The Cosmic Bird - a triple merger of galaxies: http://eso.org/public/news/eso0755
Pages: [1]   Go Up