All Activity

Is it a regular view or a widget on Kodi's homescreen?

Did you set it to look in the correct folders?

https://github.com/Amanade3/Emby-Expiry-Manager The project is completely free to use. If you'd like to support the development, I've added a voluntary support link: Support the project: http://buymeacoffee.com/amanade3

New Release v1.3.8.0

Already checked on but with no luck

Hi, Here are my version details: Android App: 3.5.55 Emby Server: 4.9.5.0 (Running the portable version on Windows 11) Thanks!

Thanks. I think I may see the issue. Ear Wax requires your Emby User ID, not your Emby username/display name. On the Ear Wax setup page, this is the field labeled Emby User ID, with the instruction to enter the ID rather than the display name. Can you confirm whether you entered your actual Emby User ID in that field, or your Emby username? If you entered the username, please replace it with the User ID and try the connection again. If you already entered the User ID and are still getting HTTP 500, let me know and I'll investigate the validation failure further.

Doing meta refresh, missing information and replace images indeed does set it to the highest resolution, but that in turn also changes it for HD-Only users. My method means 4K for 4K+HD and HD for HD only.

You might benefit from posting your issue in the thread dedicated to the plugin itself

Thanks! You can enable “Show YouTube root folders at Emby’s top level”.

I'm sure there's stuff happening, but the testing area for Apple TV is pretty dry. Not really telling what is being worked on.

I haven't tracked down any issue. If it is a huge problem for you, you can use the standard app.

question for understanding. I have set a schedule for the plugin to run for 18 hours every day (as it needs to get through my whole library which will take a while). The schedule screen shows the plugin ran correctly, but only for ~40 mins (1st screenshot). When I run it manually, it states it needs ~450 hrs to complete (2nd screenshot). Why is the scheduled task not running for the full 18 hours?

Thanx dev for this great plugin could have the channels inside youtube category on home screen instead of being one youtube icon like in ss

New Emby server Beta release, v4.10.0.30.

Hey Guys Just installed the introDB plugin and went to scan for intro markers but the scan is only going to 0.3% before it stops completely. Any idea what could be wrong. I whitelisted all my tv shows (About 2600 shows) and it seems the scan stops within 3 minutes of starting it. Attached is my log maybe someone could help Thanks Mook embyserver.txt

Tv guide issue is still the same is there an updated beta for the amazon tv app? Also not sure if its the amazon tv app or server as I usually mostly use the amazon app but recordings are starting late around 5-6 mind and the popup for "now playing" also has the same delay

Why aren’t you answering my question? Have I hit a sore spot?

We are looking into the issue of this showing as 1080p. It is an edge case due to the cropped resolution so we will have to account for that. Thanks.

Because it’s really just a stopgap solution. @Luke Were you actually counting on me forgetting your empty promise, or are you just mocking me?

PS: I don't mark any answer as an solution, when I don't see any solution. I will call it a "work around".

That's understandable Same experience, but then the waf factor is gone. Have to take that discussion Thanks and done

OK we are looking into it. Thanks.

4.10.0.30 fixes the tail for me. Thank you. This is the recipe I gave in the post with the sample: seek to about 35 seconds from the end and let it play out. Emby Web on Safari, the same synthetic sample I attached, a clean disposable container for each build, nothing carried over from my server. 4.10.0.29 — 500, and the picture freezes on the last frame: 05:55:22.209 GET .../hls1/main/220.ts -> 200 (2 ms) 05:55:22.215 GET .../hls1/main/221.ts 05:55:22.216 Starting transcoding because currentTranscodingIndex=null 05:55:22.220 StreamTranscode 06922e ... -ss 00:22:06.000 -noaccurate_seek ... SegmentComplete=video:0 Index=221 ... Frames=32 filename=D7DD1C_221.ts FfRunException: Error starting ffmpeg 05:55:22.276 Response 500. Time: 60ms 05:56:22.222 PlaySession has gone idle while playing. Position: 1325390 ms. IsPaused: False 4.10.0.30 — 200, and the session ends by itself: 05:06:15.809 GET .../hls1/main/220.ts -> 200 (2 ms) 05:06:15.818 GET .../hls1/main/221.ts 05:06:15.819 Starting transcoding because currentTranscodingIndex=null 05:06:15.830 StreamTranscode 0155ad ... -ss 00:22:06.000 -noaccurate_seek ... 05:06:15.863 Process exited with code 0 05:06:15.885 Response 200. Time: 67ms 05:06:34.522 POST Sessions/Playing/Stopped It is the same ffmpeg command, and it writes the same line it wrote before: SegmentComplete=video:0 Index=221 Start=0.000000 End=1325.370000 ... Frames=32 ..._221.ts Same run, same 32 frames, same announcement. The only thing that changed is how the exit is classified — which is exactly what your changelog line says. In your own log, across everything each container did: 4.10.0.29 4.10.0.30 "Error starting ffmpeg" 18 0 FfRunException 18 0 "Starting transcoding because" 38 36 "Process exited with code 0" 46 44 That is the case I opened this thread about, and on the ts path it is served now. One thing left over, and I want to be careful about how much weight I put on it: with fMP4 segments a script asking for the last segment still gets no response at all on this build, where 4.10.0.29 returned 500. I have not reproduced that with a real player — neither Emby Web nor my own tvOS app requests fMP4 from this build — so I am not going to call it a live defect until one does. I will report back if I get there. And a correction I owe you. In #comment-1536600 I wrote that the restarts themselves weren't the problem, because segments 106 and 210 went through the same restart path and returned 200. That was too strong. The fast-clean-exit classification was a real and separate defect — it is the one this build removes — and my original wording in #comment-1536596, "a clean exit is read as 'Error starting ffmpeg'", was right. I withdrew more than I should have.