Jump to content

Search the Community

Showing results for tags 'unable to direct play'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 1 result

  1. Currently running Emby Version 3.0.5675.1 on my Windows 8.1 machine, and the Emby for Kodi addon version 1.1.17 on my Amazon Fire TV within my home network. I also like to access my library remotely to stream via my mobile devices. When trying to play from my Video Library while within my network, I receive the message that I am unable to direct play, and whether I want to stream via HTTP or HTTPS. I believe my issue has to do with my path substitution being set up incorrectly. I have my share permissions set up correctly for NFS, but think my syntax is wrong in my Emby Server for path substitution. For example, my current path substitution is set up like: From To "G:\TV" "nfs://192.168.0.10/G/TV/" "H:\Kid Movies" "nfs://192.168.0.10/H/Kid Movies/" It's my understanding that NFS does not require a username/password to access the Windows shares, versus if I were using SMB I would need to configure the setting within the Emby for Kodi add-on with the credentials. The above are a couple of examples, for which I thought were working correctly up until a few days ago when Emby for Kodi or my Emby Server were updated (I was out of town and something auto-updated). Now I receive the HTTP message and 'Warning: Unable to direct play'. I'd like to direct play my library from within my network, while still accessing media outside of my LAN. My examples above include the quotation marks because I am not aware of how Emby will process paths that contain spaces, so that's how I originally entered them. With borrowing from my above examples, what would be the official syntax to use for my NFS shares? For those paths that contain spaces, do I use quotes? Am I able to use the IP Address, or is Emby looking for the server name? For those paths that DO NOT contain 'spaces', would I use: Option A) nfs://192.168.0.10/TV Option B ) nfs://192.168.0.10/TV/ Option C) nfs://ServerName/TV Option D) nfs://ServerName/TV/ Option E) None of the Above (please provide a better suggestion) For those paths that DO contain 'spaces', would I use: Option A) nfs://192.168.0.10/Kid Movies Option B ) nfs://192.168.0.10/Kid Movies/ Option C) "nfs://192.168.0.10/Kid Movies" Option D) "nfs://192.168.0.10/Kid Movies/" Option E) nfs://ServerName/Kid Movies Option F) nfs://ServerName/Kid Movies/ Option G) "nfs://ServerName/Kid Movies" Option H) "nfs://ServerName/Kid Movies/" Option FML) None of the Above (please provide a better suggestion) Lots of play above with IP Address vs Server Name, quotes vs no quotes, slashes vs no slashes.... As you can see, just a little lost looking for some help. Thanks
×
×
  • Create New...