All Activity

And that is not what you showed, you showed the partition being mounted to a path like /media/cooltwou/Media, so that doesn't align with your library folders. Please provide your /etc/fstab, and ls -la /mnt/wwn-0x5000c500e90d708c-part2

Yeah you would think so. I had to go to a 3rd party player in order to get Trakt to work for now until Emby figures it out.

A library category just for multichannel music. And support for SACD and .iso.

Hi, can you please show a screenshot example? Thanks.

Hi, every time when? Doing what?

it is looking at that hard drive because I named the hard drive media and I looked though the path for libraries and every one is still pointing to this hard drive: /mnt/wwn-0x5000c500e90d708c-part2

I figure it is a chicken or egg situation. Nobody is going to use Emby for Audiobooks if there is no way to get metadata and Emby isn't going to support Audiobook development if nobody is using Emby for Audiobooks. This was a way to keep my Emby Audiobook test library in sync with ABS so I could monitor the current state of audiobooks in Emby. If Emby were to add a few basic audiobook QOL features I'd consider making an Audnexus metadata plugin to grab audiobook metadata directly. As it currently stands there is no point developing audiobook metadata plugins since Emby does not have the required fields to store it. Really Emby needs to drop treating audiobooks as albums.

Well done! Although I'm asking myself why the heck anyone wants to use Emby for Audiobooks if he ever tried ABS Pretty happy with it in combination with Audra on mobiles.

Logged on to emby serever, library thumbnails appear, everything looks normal, select library and blank screen

Tried today .55 update. Nothing changes. Still crashes every time. I change nothing on the iPad from version .52 and older. Those 2 iPad only have emby app installed and do nothing than this every evening. Please try again, I'm a premiere user, I don't wanna change emby

What error does it give after installing?

I can't do that anymore because after installing, it gives an error. I uninstall and reinstall version 2.2.8, which is the one I use. I don't know what the problem is, since it only happens with later versions. Version 2.2.8 works, but the newer ones give an error.

Testing is complete, and it works for BOTH, ALL, as in, ZERO issues. So I'm guessing 3.8.5 might have solved it, and the logs were just misleading, but I can say updated on Kodi - works, updated on Emby - works. Watched 2 episodes on Kodi, did the sync task, and it reflected it properly. Watchted 2 on Emby, it updated Trakt, and Subsequently Kodi was all set too. And bonus, V: The Final Battle is correctly marked as watched on V, in Emby. We have liftoff. Thanks for your updates. I'll close this bad boy out.

The Ver from Sept 2025 work well

Hi. This is still the status:

I’m following up on this topic, which has now been open for two and a half years. Is it possible to get a solution or at least an update on the progress?

Hi, not currently, but we can add an option to control this. Thanks.

hi @flashls82are you still having an issue with this?

Hi, can you give it another try?

Hi, we are working on improving this. Thanks.

OK we are looking into this .Thanks.

HI, are you still having an issue with this?

The provided server log ends at 17:14 but this ffmpeg log is from 21:58, so they don't align. I don't see any issues in the transcode log, playback was on a Roku which you haven't mentioned any issues with.

Well, this probably won't be a surprise to anyone. But I did eventually see a memory usage spike using Beta 4.10.0.11 when running a manual scan first thing in the morning after the NAS sat idle overnight. It took seven days to happen. But happen it did. It did not result in Emby shutting down due to an OOM event. The memory was released within 30minutes. FYI, the prior automatic scan had happened 10hours earlier. I suspect that this has been happening for a while (maybe forever). But it only ended up on my radar after Emby shutdown mid-June after running out of memory. That led me to checking memory usage in Resource Monitor daily to see what was going on. And I saw a spike in memory usage every few days during the morning scan. A couple of times there were OOM events. But there were just as many spikes where the system recovered. In the past I wouldn't have noticed them unless Emby shutdown. So much for my theory that this only began happening post Beta 4.10.0.15. I have updated to 4.10.0.20 and will continue to monitor.

Luke, thats interesting. Same bug I experienced with Entrapment Bluray and @softworkzautorefresh code. The refresh rate is double the fps, not matching. This only seems to happen with Mpeg2. Softworkz, any idea why this happens? You were going to revist your code.