Search the Community
Showing results for tags 'system requirements'.
Found 4 results
Posting this in case it helps someone avoid the issue I had. Emby Server for MacOS 4.3.x requires MacOS 10.13 -- this is a change from Emby Server 4.2.x which could run on MacOS 10.12. The release notes don't mention this (https://emby.media/community/index.php?/blog/1/entry-477-emby-server-43-released/) Even worse, the Wiki lists the requirement as MacOS 10.6.3 (https://github.com/MediaBrowser/Wiki/wiki/System-requirements) This is disappointing as I'm not the first person to point this out but the release notes and Wiki haven't been updated. Consider this a friendly nudge to update the documentation accordingly.
MikeTech posted a topic in Live TVWorking on proof-of-concept testbed using available hardware at hand. Decades of pro IT experience, but total noob with Emby for home use. Emby Server is running on a Mac mini (Mid 2010), 2.4G Core 2 Duo, 16GB RAM, its stock internal HDD (320GB 5400 RPM), with an external drive to house recorded media. Recorded mp4 (m4v) media streams perfectly on all devices, no worries there. Added HDHR Connect to experiment with streaming Live TV, it set up very smoothly and displays 32 available local OTA channels. SD channels and subchannels stream just fine with default settings, using ffmpeg transcoding, on both wired and wifi connections (and on the server machine itself). But, it seems that 720p and above HD channels are simply too much for ffmpeg to handle with this CPU, and I have to manually change settings on the remote app (iOS is all I have played with so far) down to 480p/420k for those HD streams to keep CPU load for ffmpeg below 100% and get the HD channels to stream at all. Same result with the Roku app. This Mini has the Nvidia GeForce 320M 256 MB GPU, but there is apparently no support for that, and it probably wouldn't be much help anyway. Grateful for any wisdom on the recommended system requirements to support live HDTV transcoding from the HDHR Connect, since clearly this is not enough! Or, maybe I need to get the Extend with built-in transcoding to h.264...(?)
I have been using Emby Server for a few weeks now, installed on my Win 8.1 machine (AMD Phenom II X4 955 quad core 3.20 GHz, 4 GB RAM), currently with about 515 movies, 125 TV Shows, and about 45,000 songs. I've noticed that since I migrated from a MySQL implementation and began using Emby Server to share to my two Kodi devices and multiple mobile devices, that Emby Server consumes a good deal of my system's RAM, upwards to 1 GB when it appears idle and I'm not streaming. I know I may not have the most current or beefy system, but things are no longer snappy and quick to open/process with Emby Server running. I'm sure an upgrade in RAM would not hurt I've read the system requirements on the Emby Wiki (https://github.com/MediaBrowser/Wiki/wiki/System%20requirements), which state Minimum Requirements — no transcodingIntel Core 2 Duo processor 1.6 GHz or better At least 1GB RAM for Windows/Mac OS X Recommended Configuration — transcoding HD Content:Intel Core 2 Duo processor 2.4 GHz or better If transcoding for multiple devices, a faster CPU may be required At least 2GB RAM So are these specs listed for minimal system requirements, or the requirements that Emby Server will consume? I've tried searching the community for any related threads, and read that it may be an idea to remove Music from the Emby library may help the situation. Does anyone have any other suggestions aside for the RAM boost? Thanks