Search the Community
Showing results for tags 'blank'.
After upgrading to Emby Server 126.96.36.199 my music library no longer displays graphics. Every MP3 song of every album in my collection contains an embedded album image. Each folder includes a folder.jpg. I also did a new library scan after the upgrade. So I don't know why the views are all blank now. - How can I fix this or is this a problem of the Emby server release?
Hi all, I have run into a rather weird issue this evening after reviewing my hardware encoder options. After seeing a remote user connecting and playing a media file that needed to be transcoded due to global bit rate limitations, I noticed that it was streaming at a rather low bitrate of ~900kbps when the global limit was set to 2.5mbps. My upload speed is more than capable of achieving this and has done so without issue in the past. I hopped onto DSM to see what was up and found my CPU usage was spiking to 99-100%, which was causing the slow down. This has never happened before and I would typically only see CPU usage of 10-20% while transcoding any file, so I thought to check my hardware acceleration options, as per the wiki suggests, to ensure nothing was switched off. I found that I still had hardware acceleration set to 'Advanced', but weirdly enough, no options appeared under 'Preferred Hardware Encoders' as they had just a week ago. See the screenshot. It is almost as though it no longer recognizes any of the hardware options for hardware acceleration on my NAS. I am stumped as to what has caused this sudden switch. My only inclination would be that it has to do with my recent upgrade from Synology DSM firmware 6.2.3-25426 Update 3 to version 6.2.4-25554 last evening. That upgrade went smoothly and nothing indicated there was an error, but this is the only major change from last week to today. I have confirmed that this occurs both for remote users and myself while local. This issue occurs on a variety of different platforms including Amazon Fire TV devices, Firefox, etc. I also confirm that the spikes completely subside once I stop playing/transcoding of media files. Direct play files are seemingly not causing spikes of this nature. My Emby Premiere license also appears to be correctly input and resolving fine. I am also running the official package, not within Docker. Any help would be appreciated so I can adjust my hardware acceleration options to not cause spikes. Included is the server, hardware, and transcoding log of a problem file. Thank you. Server Specifications: Synology 920+ 8GB Memory Firmware: 6.2.4-25554 Emby: 188.8.131.52
Emby is not seeing the network shares, when I go to add media it shows the local drives and networking (networking is blank) but if I try to use IP or network name the info is blank, I can access the shares from windows. Details: So I had emby setup and working for about a month or 2, all the media added and accessible, went and finally paid for the lifetime subscription and went to go log in and so some test, when I couldn't see any media, Started troubleshooting, found out that if I tried to add new media or modify the existing, that emby could not see the network essentially. Tried adding drive as mapped networking drive, ensured I could see the network shares, checked permissions for username ( which has full writes to the drives) checked networking settings across the board. I even went as far as to completely wipe it and re-install fresh, and tried it on a different pc and the pc that has the data, still cant see the network path. I work in IT tier2/tier3 so I know my way around and how to troubleshoot, but this issue has me perplexed. Error is "There was an error adding the media path. Please ensure the path is valid and the Emby Server process has access to that location." when adding media to the library.
Does this happen to anyone else... When I open Media Browser (current version) through Windows Media Center, I will get a blank library. I will have to open or close it a few times or even rescan the library even though I know it has just finished... I opened it on the Web a moment ago and had the same thing happen. I have gotten this on multiple machines and have tried various forms of the current Server (3.0.5582.4 / 3.0.5588.0). Attached are the most current logs...