All Activity

Hello franklin24723, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team

.

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 prior. 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.

Hi, we are looking into this. Thanks.

ffmpeg-transcode-35112d61-56bb-4efb-9bfe-cab3601ed9aa_1.txt

The first log is when i asked her to try and play a movie just to catch the log file

There one guaranteed way to fix that where there is no laggy or choppy videos.

Thanks @Luke and yes, the NUC has proven to be a good option as I evaluate which way to go (grab a Shield or use my current NUC). All the great advice from the likes of you, @FrostByteand others to help my understanding on the many configuration issues / pitfalls to get the NUC firing TrueHD audio has been very helpful (and thank you). I can't say I understand the ranting and raving from @RanmaCanadaover using other sources or information (like ChaptGPT) along with community advice to assist with configuration help (like BIOS bugs / driver bugs) but that user might have their own issues. Thanks again all who contributed positively. I'm excited that I got my HW-Q990c sounding awesome.

MPV shut it down start back up and it works

Well, I've been doing this for many, many years and now I always add the year in parentheses. As for putting "The" after a comma on the name, that has never been a problem before and I tried it as "The Future (2011) to see if that would fix it, but it didn't. I now know how to rig it to fix the problem after the fact, and, to my knowledge, this problem has been rare. I'm just worried that there might be stragglers in my large library that I have missed over the years. With this current problem, the movie wasn't showing up in 'Latest Movies' or in the Library under 'The Future' or 'Future, The' which makes me think that it was not even in the library. Once I changed it to something innocuous like 'The Future is Fun', it showed up in library and 'Latest Movies'. Then I fixed it through 'Identify' and 'Edit Metadata'. Now it's as if there was never a problem. AI thought it was a corrupted metadata entry. Now, I just want to find an easy way to compare the files on the disk with the library to see if there are missing entries.

How can I stop it

The server is transcoding it so that it can be deinterlaced properly.