All Activity

Good morning, I had a similar problems yrs ago, it's because you need to use the following for your m3u: http://<IP ADDRESS of HLS-Proxy>/restream That should do it! Have a great day

An hour or so and it should be ready if everything goes to plan.

Already done! "Save Debug Logs to File" is enabled and ready to go. Just let me know whenever the new build is up, and I'll run it right away to grab the isolated logs!

Doesn't look to be stalled, there's just a lot of noise in the log from another plugin (TMDB api lookups). FFmpeg did cause an error at one point, i'm working on adding a guard againts that but other than that i don't really see a problem in the log. When that version is done can i get you to make the plugin save individual logs? That will remove all the noise.

After loading the app and connecting to the server the screen attached pops up. No matter what I am choosing from there it directly returns to the same screen. Also there is no possibility to uninstall the app or reenter anything else either.

Hi @yocker, To answer your question: it definitely stalled mid-detection rather than finishing early or skipping files. Out of roughly 62,000 episodes in my library, only around 3,000 have been processed so far. The remaining ~59,000 are untouched and do not have any credit markers or previous timestamps. Looking closely at the log, the batch processing kicked off for Les Griffin Season 5 at 00:15:20.395, and then the plugin stopped logging completely while server-side TMDB queries were running. The scheduled task just hung right there. I'm ready to test your upcoming build as soon as it's available. Thanks for looking into it!

@fbourgDoes the plugin act like it was done or has it stalled mid detections? Looks like a lot of episodes was added to the queue that already had time stamps or failed and the plugin skipped them. If you look purely on the ETA then the time left can be very deceptive and can fluctuate A LOT. You add items to queue. It start detections on episodes and the ETA goes up to lets say 2 hours. Then 80% of the files suddenly doesn't have to have detections run anyway and the ETA can seem to be wrong because most of the work suddenly disappeared. That said, looking in the logs i might have found a problem. I will have a version ready for you to try soon.

https://titlovi.com/

This has suddenly started working again on all firesticks. The only thing I did was to turn off automatic subtitle downloading and upgraded Emby server to 4.10.0.40 Thanks for your help @ebr

You guys still don't want to add the biggest subtitle website in the Balkans region, titlovi.com? Why?? Opensubtitles is terrible, terrible! 90% of subtitles there are Google translated.

Install the ms store first don’t use winget. Once the store is installed install emby from there.

Hi I have been using using HLS-Proxy sucessfully to stablise the streams into emby for several months, but am running into an annoying situation where if emby starts a new stream and it exceeds the steam limit i have set in HLS-Proxy, the oldest stream is kicked off. What I would like to see is that the new stream is blocked rather than the roll over behaviour. My searches have not yielded a solution to this except to confirm that this is the default behaviour of HLS-Proxy I dont want Emby to restrict the steams because i use the restreaming feature, so ideally this would be enforced from HLS-Proxy. Any ideas on how to do this or are there parameters for HLS-Proxy that are not availbable from the Web config that can be set in the Local.Json file?

Perhaps I don't I understand exactly how your fix works I entered "wsreset -i" in an elevated powershell before installing EMBY Theater (using the Winget command) and afterwards but I get the same error. I have posted a screen shot. Please explain if I have installed incorrectly or used the wsrest command wrongly. Thanks.

New Emby server Beta release v4.11.0.3.

I'll look into it! Tbh I didn't know these type of list existed on MDBList. Shouldn't be any bigger problem As a sidenote, I want to give a heads up and recommend using TMDB and their API feature: https://developer.themoviedb.org/reference/getting-started Feels like this has flown under the radar a bit within this plugin. This gives some rally nice lists as well.

its new version 2.9.0.1 ?

Hi. I have 3 firesticks exhibiting the same problem. The one I'm testing now is fire TV stick hd (1st gen) running fire os 7.7.1.6 The emby version on the firestick is 2.1.54a It's not just this particular episode that is causing issues. Alot of the x265 encoded episodes are having this problem recently

The plugin stopped again overnight. Here are the files. Version 2.9 embyserver-63925725666.txt embyserver.txt

Hi, yes we are looking into it. Thanks.

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

Yes, of course; in fact, if I try to create the user on another server, it works fine. But on this one, that error appears. I'm not sure if the issue lies with my server or with a corrupted installation file.

Yeah, it's been there forever but it's somewhat easy to overlook. Logically, it is placed where it should be (Readers>Downloaders>Savers), but maybe practically it should be moved up, below Readers, so both NFO-related settings are kinda grouped.

I finally got around to creating a video showing the bug. Let me know how you want me to file this. Nothing shows in the logs at all bug in user settings.mkv

So here the main reason I stick with Emby for Android... I can press the home button on the onn remote and it kills any app. I am able to go back into any app and it starts over. No third party software, no remote mapping. Just using the developer mode., but the home button doesn't kill Emby for Android TV. Petty I know.

Are all the bugs being tracked by the development team? Is there an estimated timeline for fixing this issue? This issue is still present in version 4.10.0.40 (Emby Android 3.5.55). The only workaround I found is using Emby for web on the TV.