Jump to content

Search the Community

Showing results for tags 'web player'.

  • 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
    • Non-Emby 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 5 results

  1. Hi, With 71.0 comes a new picture in picture feature for Windows 10. I can see the small blue icon on the right hand side, I can hover it and the text reveals nothing happens when I press it. Here's mozilla's blog post about it: https://blog.mozilla.org/blog/2019/12/03/news-from-firefox-on-mobile-private-network-and-desktop/#PiP
  2. bluesaxman

    Question about browser decoders

    Hello, I didn't see a post about this, so I thought I would ask. I'm pretty sure this has something to do with fedora, because the webplayer works fine at home on chrome/firefix/qutebrowser on arch (client side), however I'm currently on a fresh install of fedora (client side) and when I try to play a move in chrome or firefox, it hangs and in the js console I get a message about websocket problems. I added a few things to my apache config to try and fix this, but I went from a 404, to a 500 and then to a "Invalid Socket response" message. I'm wondering if I just forgot to install some library on the client side that is causing the browsers not to run the web player correctly. I checked the emby server logs and everything on the server end seems to be in order, emby even thinks the transaction was successful and shows the movie currently being played even though the web player stalled out in the browser. Nothing is showing up in the apache logs ether, so the proxypass I have set up is working fine. So my question is, could I be missing some libraries that chrome/firefox needs in order to properly talk over a webshell? I will be happy to provide the logs I mentions if you would like, but I don't know that it will be necessary as both (emby server and apache error logs) are clean.
  3. I was testing a test movie file, and the web client crashes at around 32 minutes of play back. It doesn't matter if I skip through the video or watch it to the point, the video crashes. I've attached my three logs relating to playback, and it seems that FFmpeg is throwing an exception somewhere. Any tips? A little bit of extra information, it crashes in the web player AND on Chromecast. I've tried the video straight in VLC (just the video file, not DLNA) and it plays the section just fine. remux-c8cb89d2-a6f3-44a7-9364-73b75a9e4e70.txt remux-c990a73f-5972-4ea5-9633-76da4e1bc127.txt server-63598778350.txt
  4. jime1051

    Google Chrome

    Web page player in Google Chrome Browser 35.0.1916.17 dev-m not playing videos. Operating system win 8.1 Pro. IE 10, IE 11, Firefox work fine - just not Chrome. Replicated on (2) separate systems with same OS and Chrome numbers. Both computers MB3 works fine from other Browsers. Thought at first MB# was broken as Chrome is my default browser, but loaded localhost to check other browsers and they work fine. Not complaining - just for everyones information in case they use Chrome by default.
  5. As the title states in the new web player the status bar at the bottom always stays on. Running win 7 64 bit in chrome 33.0.1750.154 Let me know if there is anything I can check on my end.
×
×
  • Create New...