All Activity

yes.

Probably: Files yes, directories no. See my longer answer above. In its current state, this is a severe security issue. Users get access to entries they are explicitly not allowed to see.

Do you mean the 4.10.0.10 beta?

Thanks to @Lessajfor the hint on the path. My question now is, does this setting also apply to plugins using ffmpeg or ffdetect or does it exclusively only apply to real transcoding happening? If not, where would I maybe have to set up another path to use for plugins' cache/temporary files except for the plugin settings themselves?

I don’t really use transcode, all streams are direct play because I don’t have too much ram

Good to know thank you. I also found another topic in here talking about the transcode path and it defaulting to the RAM if not set up as a path on the drive: I also created a mount for a local folder and use it as the transcode path in emby now.

Yep same discussion here.

It is too much, some changes was made in the DB and if you don’t have enough RAM this will be consumed with a couple of user’s when the app start

I even had 512 in there lol Thank you, changed it to 64, let's see how it goes.

Try to set 64MB instead of 128mb on the DB settings and do a server reboot, let me know if this helped you

Hi, I have a similar issue and posted in the Docker topic about it: I also had the problem on 4.9.3.0 and it still persists on the newest beta. I really want to avoid reinstalling everything since I have a pretty big library and already had to reset my database a few weeks ago due to a problem caused by a power outage. But even before that I had these problems of emby server crashing. Maybe there would be another fix? Would be nice to learn where to look for crash logs to see what causes the crashes.

Emby for android unified app, on Amazon its called only "Emby". Well i dont know whats happening but on google playstore .28 is the latest version i could install, while on Amazon is lottery.

I'm on Emby 4.9.3.0 & Trailers Plugin 1.4.0.0. I only have 3 trailers from 2026 and 2027.

Mostly everything is accurate in original topic. I bought lifetime Emby and I have to say that despite the text being clearly ai generated, but I have to admit that it's true unfortunately. Emby has nice gui, but hw transcoding in jellyfin is way richer and more optimised. Ok, if you run it on intel quicksync, but on my rk3588 jellyfin hw transcodes 4k to 4k HEVC at 4.8x. Emby won't even let me do this on rk3588... Which is ok I guess. Until you realise that jellyfin doesn't need ANY subscription.

Thank you so much for this plugin version, you are a true legend , I loaded this and it picked up in my plugins folder on my Emby. I am running Kometa now to see if it will apply the overlays. I must say a massive thanks for this.

@yocker Any plans to release this plugin in the emby plugin store? This way we dont have to care about manual updates.

yes, the search does begin as soon as you start selecting letters. But while I can see how thats useful, I don't want that - my server is not always on the same lan, and I have a large library - sending a query on every letter is not ideal. but why are you seeing this on an Android tv box? what is the search you see in other streaming apps, or in the play store, or browser? do you not have onscreen keyboard? this looks like something custom implemented by Emby and I don't see why

@hatharry YES... F'ING YES.. it works!! happy happy joy joy Thank you Merci Beaucoup

Hi, what you could try to do is remove the playlists library from emby library setup. That will kick off a library scan, so once that finishes, then create a new playlist manually and that will recreate it. See if that brings everything back.

Hi, what guide data are you using? What you could try to do instead of recreating the series is just refresh the guide data in the server.

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

Try this one, i changed the pathing slightly. EmbyCredits.dll

I am using a reverse proxy with "/emby". When navigating to the port directly, the page loads and plugin appears to function. Version 2.4.2 thru 2.4.9 all show this in the browser console when failing under the reverse proxy. I don't believe I changed anything on the reverse proxy, so not sure why it has quit working. Obviously, returning a 404 will break the page, and it looks like the plugin is not including "/emby". Attached is a console history of me clicking on EmbyCredits on the plugin page. embycredits.log

The updated is now available please try again