Jump to content

Search the Community

Showing results for tags ''.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Emby Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 6 results

  1. Real time monitoring has been working fine on, but has stopped working. Have to manually scan or wait for scheduled scan to detect new files. I have disabled and re-enabled real time monitoring in each library several times, rebooted the NAS with no effect. Log is attached, but I did remove the NAS IP address as I do not feel comfortable posting my NAS IP on a public forum. Any help would be appreciated.
  2. Hi, I am in the process of a full library scan, and I see the following errors appear in the server logs repeatedly. System.Exception: ffprobe failed for file... streams and format are both null and [matroska,webm @ 0xebdc00] Format matroska,webm detected only with low score of 1, misdetection possible! [matroska,webm @ 0xebdc00] EBML header parsing failed : Invalid data found when processing input embyserver.txt
  3. Netfool

    Samba Configuration

    I abandoned Emby Server on the Nvidia Shield and moved the server to 3.4 GHz Core i7 machine with 32GB of RAM running MacOS 10.14.6. All of the library files are on the same Linux box used by former Shield Emby Server. Live TV is fed by an HDHR box and programs can be viewed live from the MacOS Emby Server. Everything works fine except that the DVR will not record. Files in the Recordings library put there by the Shield Emby Server play fine. The MacOS server acknowledges my Emby Premiere key. Any suggestions?
  4. Good morning, Emby Server has been updated automatically and now the images contained in the monitored folders are no longer visible regardless of the type of library chosen (personal photos and videos - mixed content, etc.). I have already tried to shut down the server and delete the contents of the programdata\cache folder. Do you have solutions?
  5. Using the Colibri browser, I logged into Emby using the remote (wan) access and am ported to the Theater session with the very nice Theater visual screen however, when I open Music, the list of options I get are: Suggestions Albums Album Artists Artists Playlists Genres Although my session is considered Emby Theater, I'm using Linux Mint 20, Colibri browser. If I use Chomium or Firefox from the same system and remotely log into Emby, I get ported to the same Theater session, however I do see the "Songs" option however I also get the same visual theme (Dark theme) that I get when logging in locally, not the Theater visual I get using Colibri. Server log attached. embyserver.txt
  6. Running The Nvidia Shield Emby Server on a 2019 Nvidia Shield Pro. Attempting to use the Nvidia GPU to do hardware trans-codes has never worked for me. Ever hopeful, I wanted to test under and discovered a completely different problem. I attempted to transode a file from H264 to HVEC. That first conversion failed as before. I also tried to convert the file to a 4MB/sec version. Hardware trans-coding of that failed as well. I did the same for 3 additional files to test whether or not it was a problem with that specific file. All failed to used the hardware encoder. However, when I went back and examined the logs, in all cases Emby attempted to convert the first file, NOT the file I asked it to convert. Conversions were started from the Movie page in some cases and from the library thumbnail for the movie in others. A screenshot of the Logs page and relevant logs are attached. (The screenhot to establish the order of the transcode logs). The Remux log came from playing the last movie to confirm its was not originally shot in 16 by 9 (it was however released letter-boxed) and mostly in monochrome. It's possible that the initial problem was caused by cancelling the first conversion from the dashboard. Allowing it to complete software a software trans-code in all cases would have tens of hours. embyserver.txt ffmpeg-remux-3b027453-a1da-4a8a-811f-c14d291c3ebe_1.txt ffmpeg-transcode-3cb5e847-7345-4bb5-b335-9a1e7e88e3c6_1.txt ffmpeg-transcode-8db60443-f8f7-4cc2-851e-aa53df25e619_1.txt ffmpeg-transcode-bd201aa7-eece-4a32-ae0c-3fe8ae75076a_1.txt ffmpeg-transcode-cc0c53cb-384f-47a0-92d2-8172e76f6c30_1.txt ffmpeg-transcode-d13fff65-36f7-48c7-b57a-9e29c7b38769_1.txt ffmpeg-transcode-d715900d-b7ae-4f42-8d84-a4a8d04c4ca2_1.txt ffmpeg-transcode-da1997bb-81b1-412e-ab21-10b73c21c3a5_1.txt
  • Create New...