Default Recording Path - mapped drive vs network share

[benmoses 4]

In DVR | Default Recording Path, if I use a mapped drive to my NAS all is well, however if I use a share path such as //nas/network/RecordedTV, the "Recordings" library (that I understand is created when using Default Recording Path) is empty at all my clients including Emby Theater and Roku.  

 

Recordings do appear there when I navigate in Windows but Emby clients will not show them (and no error occurs)

 

I know the first thing to test is can I access the share in Windows using //nas/network/RecordedTV from my clients, and the answer is I can (at least from my Emby Theater machines).  

 

Am I missing something?  I'm ok using the mapped drive in this field for now, but I've read it is better to use the network share nomenclature as it allows the client to connect directly to the share.  Is this correct?

 

I know this topic has been visited before and I've seen those posts, but I have not been able to find a definitive answer yet.

 

Thank you!

Ben

[Luke 42085]

Hi, if you're on windows then you should be using unc path conventions, with \\ instead of /.

[benmoses 4]

BAH!  my bad.  I believe I was, but now I must double check.  I constantly get \ / mixed up going back and forth between Windows and linux.  It is all Windows systems though.

 

Yes, and UNC was the nomenclature/style I was referring to.

 

And yes, I should simply be able to substitute in the UNC path in place of the mapped network drive, correct?  I'll try again tonight.

 

thanks for getting back.

[Luke 42085]

Yes I would use the unc path rather than the mapped drive. thanks for the feedback.

[benmoses 4]

I think that was it.  // vs \\  LOL  <embarrased>

Thanks for your quick response.  

I'm loving emby so far, a few learning curves aside.

 

emby has been my migration away from dependance on Win7 / WMC / HDHomeRunPrime / Kodi / WMCServer (that's a lot of integrated software to juggle)