Jump to content

ServerWMC: "local path detected" message... what to do?


LehighBri

Recommended Posts

LehighBri

I am using MB3 3.0.5309.26857 on Windows as ServerWMC 1.0.0.36 build and XBMB3C 0.9.517.

 

I normally watch my recorded media through XBMC's PVR capability, but today, I tried to use the "Play To" functionality within MB3's web UI to play a recorded file to an XBMC client, but I get the message below.

53cff42f5bdfa_xbmc1.png

 

Is there a reason I'm getting the message above when I did specify the UNC file path in the ServerWMC settings (see below).

 

53cff4398d872_wmc1.png

 

  Is the UNC file path setting in ServerWMC not being passed to MB3?  I would think that the setting should be shared so that any of my XBMC clients that I use MB3's "play to" feature would just work and I wouldn't get the XBMC message above.

 

Thoughts on this?  Is this a potential enhancement or is there some limitation here or something else I'm missing?  I definitely don't want to use the "Play from Stream" option in XBMB3C as I'm playing back on my local network.  The UNC path is really the way to go, so I would hope there's a way that ServerWMC could let MB3 know about it.

 

Note: Play To works great for imported TV shows.  The issue above is only related to actual recordings that I have from WMC.

Edited by LehighBri
Link to comment
Share on other sites

krustyreturns

To answer your question:  yes there is a reason and looks to be a problem with serverwmc and XBMB3C.  We use local paths when possible so that the user doesn't have to set up a network share unless they are ready to setup remote clients.  Using these by default has never been an issue - until now it seems.  We can add an option to the serverwmc settings to never use local paths and that should clear this up.  This should be easy to get into the next rev.

Link to comment
Share on other sites

LehighBri

To answer your question:  yes there is a reason and looks to be a problem with serverwmc and XBMB3C.  We use local paths when possible so that the user doesn't have to set up a network share unless they are ready to setup remote clients.  Using these by default has never been an issue - until now it seems.  We can add an option to the serverwmc settings to never use local paths and that should clear this up.  This should be easy to get into the next rev.

 

Great thanks.  Just to clarify one point.  The example above happened all on my one server machine that has WMC running, servermwc running, and my media, all local (on T:).  So I was a bit surprised to have that happen.

 

But yes, for other remote clients, they will definitely need to be able to use network shares so adding that support would be great.  That will definitely solve for the example here too, but I just wanted to clarify that there are examples where the client is the server (where I would think local paths could be allowed), and other examples where the client is not the server.

Link to comment
Share on other sites

krustyreturns

Actually I was thinking this was only a problem because everything was running on your server machine, I thought remote clients would likely not have this problem.  Have you verified this is a problem with remote clients too?

Link to comment
Share on other sites

LehighBri

Actually I was thinking this was only a problem because everything was running on your server machine, I thought remote clients would likely not have this problem.  Have you verified this is a problem with remote clients too?

 

I did.  I tested it on both my server and a remote rpi client and I get the same error message each time.  Even on the rpi, it seems to be trying to playback from T:\Recorded TV instead of playing back from the network share I specified in the serverwmc settings.

Link to comment
Share on other sites

krustyreturns

In each case though, I'm assuming mbs is on the same machine as wmc, right?

Link to comment
Share on other sites

mini__me

Can confirm I have seen the same using playto from the web client to send recorded/live tv to an XBMB3C remote client.

 

Though sending to the XBMC DLNA Client worked fine for recorded TV using direct play and transcoded for Live TV, hopefully the update you are planning will fix the sending to XBMB3C client remotely :)

Link to comment
Share on other sites

mini__me

Sure thing, always happy to help if I can :)

 

I won't be able to try it out today as I'm working away, however I'll have a few hours tomorrow night free before traveling again so I should be able to give any test builds a quick go :)

Link to comment
Share on other sites

krustyreturns

Sure thing, always happy to help if I can :)

 

I won't be able to try it out today as I'm working away, however I'll have a few hours tomorrow night free before traveling again so I should be able to give any test builds a quick go :)

 

 

I PM'd you and @lehightbri a test build, let me know if it works.

Link to comment
Share on other sites

MrWebsmith

krusty,

 

can i help with this problem if my wmc/swmc/tuner is on box 1 but my mbs is on box 2??... or only if they are the same machine does the problem come up..

 

(i havent specifically tried the 2 stream test on my setup)

 

 

if i can assist then ill take the test build.. if you think i wont have the issue, then ignore my babblings

-MWS

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...