Leaderboard

Not everyone will and they are very clunky to operate.

Simple request that the Android app have the ability to blacklist a song. Lots of features available when the three . . . are touched next to a song. I would like an option to 'blacklist or skip permanently a song. As opposed to deleting the song which than breaks of the completeness of the music album.

@Luke Any updates? Been a couple months.

This is a great idea, which has been requested in several different threads here.

I'm having exact same issue and can confirm as of iOS 26.4 no audio on any video no matter the format. I switched from auto player to native but that is buggy locking up after pausing a video or randomly the app locks up at the end of shorter tv shows for no reason. I have since gone back to auto and turned off "Continuous Audio Connection" and the problems went away.

New Emby Beta server v4.10.0.8.

Hi, there's already an open request for this or something functionally equivalent. Please join in and contribute to the existing discussion at:

Nice theme, it looks good, I just installed it. I'll try it out for a while. I'll keep an eye on any improvements you make.

+1 vote for the Alternate/Joined order option

I am already to ask for deepseek, they said the question on th EMBY.so I just ask some question in here.

That did the trick! Thanks

Try the one just uploaded to Github.

Dynamic DNS is what you want. My ISP routinely renews my IP, typically at least once a day. So I currently use No-Ip (www.noip), but have used other services such as changeip in the past (www.changeip.com), but there are many others, some free, some paid. You enter your preferred name and choose your a ddns domain name from a list provided by the dynamic dns provider. As an example say its *.ddns.info, and you choose it to be mendocinotim.ddns.info You have to then update that ddns record so it points to your current ip address where your emby server is, this is usually done via your router, but can be done with other hardware or software as well. Best to check which ddns your router supports to see what options are available to you. I have some posts that previously I made in relation to ddns for my emby server running on a qnap nas device, including generating ssl certs for the emby server so that users can connect securely to (using the same example as above): https://mendocinotim.ddns.info:8920, which is then connected to your ip address of the emby server running at your home. Edit: You may be able to use your existing domain name you already have, to be dynamically updated with the server ip, same as the ddns - but I dont have a domain name, so I have no experience of that myself, maybe someone else will be able to confirm if that is the case. Hope that helps.

@yockerYou might want to do some testing for "subdirectory" type reverse proxy entries (ex: https://www.domain.com/emby/) as your plugin bombs on loading content in that manner. I have mine setup both as a subdomain (https://emby.domain.com/) and the former, and only now did I observe the issue:

I appreciate the support. Sadly, that's exactly what happens after I downgrade the plugin, and restart the server. As I mentioned above, downgrading the plugin + restarting makes it seem like I did not, and so if I had copied the log before restarting, it would've most likely mentioned that the downgrade was successful. I will send you a fresh debug log after the downgrade, and one after a restart, then. Thanks. I appreciate it. I did realize that, and so I invalidated those tokens within minutes of the incident. Also, I tried to remove the log, but no matter how many times I tried editing my reply, the log would multiply, and deleting the reply completely isn't possible, unfortunately. In other words, I couldn't fix my mistake even if I wanted to, which is kinda embarrassing for someone who's been tinkering with all kinds of IT stuff since 2006. Will do. Cheers, I did read that before posting that reply, but I missed the note written in italic ("rookie" mistake, I guess), hence the unsanitized log incident. I can easily locate stuff on the log, but when I read that the whole log had to be included, I decided to just follow those instructions. Speaking of locating relevant stuff on the log, I just noticed that the Emby app from MS Store (for some friends and family) throws this error `Playback error: there was an error processing the request....` while it works fine on my PC. I tried to update dependencies manually by getting them from what I call the Adguard Store (Microsoft Store - Generation Project), but to no avail. Firefox triggers a "No compatible streams are currently available", while Chromium-based browsers like Brave, Chrome, and even the UnGoogled Chromium work great. I also am not sure if this is relevant in terms of performance, but I have 128GB of DDR4 RAM (3200 MT/s CL16) (managed to grab another 64GB kit for $170 days before the current scary situation, which felt like I had foresight ), and metadata + transcode cache is stored on my Samsung 970 Pro (1TB). I figured the more the merrier, and if you could please explain in technical details why 128MB (default) would be more optimal, I would appreciate it. It's just that I have a "traumatizing" experience with Jellyfin when it comes to the loading animation, and that's the main reason I switched to Emby in hopes that the latter handles database operations better. So far so good.

Installed version 4.10.0.7 beta just to see if the sqlite updates would help, sadly searching is still sporadically unreliable. Still looking forward to a fix, hopefully soon.

Indeed it does. I would assume that plugin would never get approved for the Catalogue.

Which is what makes it dangerous and opens us up to store policy scrutiny.

I found that disabling the new setting introduced in TVos 26.4 called "Continuous Audio Connection" resolves this issue.

Hi. I don't think we could ever do this. It would be incredibly dangerous from a security standpoint and I don't think we could ever get through store policies without a ton of risk there as well.

Hello i have an Gemini AI sub but when i set my API ket and test, i have this error. What's wrong? Connection failed: models/text-embedding-004 is not found for API version v1beta, or is not supported for embedContent. Call ListModels to see the list of available models and their supported methods

I'll absolutely necro-post this; Just got emby with hw acceleration working on FreeBSD 15.0. What a journey... I followed this guide as close as possible, however the tar for the fake /sys is offline in the meantime, so a bit of trial and error was key. For everyone trying to replicate here is my working one: sys/ sys/bus sys/bus/pci sys/bus/pci/devices sys/bus/pci/devices/pci0000:00 sys/bus/pci/devices/pci0000:00/boot_vga => 1 sys/bus/pci/devices/pci0000:00/vendor => 0x10de sys/bus/pci/devices/pci0000:00/device => 0x1ff2 sys/bus/pci/devices/pci0000:00/drm sys/bus/pci/devices/pci0000:00/drm/render0 => link to /dev/dri/render0 sys/bus/pci/devices/pci0000:00/class => 0x030000 sys/bus/pci/devices/pci0000:00/subsystem_vendor => 0x17aa sys/bus/pci/devices/pci0000:00/subsystem_device => 0x1613 sys/bus/pci/devices/pci0000:00/enable => 1 This gets ffdetect to a point where it tries to use the card. Next hurdle is vaapi... for an nvidia card you need libva-nvidia-driver, that however is a bit special itself. its not enough to hand it /dev/dri and /dev/drm, it also wants /dev/nvidiactl and /dev/nvidia0 (yes, nvidia0; thats hard-coded; my host always creates nvidia1, so symlink that). for good measure I also put /dev/nvidia-modeset into the jail even though it might not be needed. Next this little beast also needs CUDA... this made me pull my hair and have me install half a linux in /compat, more precise the libc6-shim package. With that you get the nv-sglrun ruby script that somehow (don't ask me how, I stopped digging deeper at that point) makes CUDA available. Bare with me, we're almost there... just one little wrapper around the ff* binaries in /usr/local/lib/emby-server/bin and we're there. So rename the original binaries to _real and for each put a wrapper like this in: #!/bin/sh export PATH=$PATH:/usr/local/bin /usr/local/bin/nv-sglrun /usr/local/lib/emby-server/bin/ffdetect_real $@ And will you believe it, it freaking works. All this crazy setup just to find out that libva-nvidia-driver only implements hardware decoding, no encoding (╯°□°）╯︵ ┻━┻ Well, its better that nothing i guess. And maybe some day claude will be good enough in generating code to close that gap; the humans don't seem very interested in implementing it. DISCLAIMER: This is a very striped down version of my pain, i faced lots of missing symbols, version mismatches and spontaneous reboots on the way. I might have missed some steps but I'm happy to help anyone brave enough to try. FINAL RANT: Is this really the way to go? This seems unnecessary complicated, doesn't it? Can we not just have nice things, please?!? /cheers

This is a matter of privacy rather than security - your whole machine isn't compromised by an image being downloadable. Sure, it matters - but it's not always the most important thing. Also, I believe that there is more than one Emby developer, so the fact that one person may be actively working on the images issue doesn't mean that the work of another cannot be presented in a beta. Paul

Just in case anyone else get this, here is what worked for me. I just had this exact same issue on my FireTV. Licensing error and then uninstall Emby App and then try to reinstall and it said "App not found" - just like above. It turns out that it was the personal DNS server I'm using. I use Pi-Hole on a Raspberry Pi for my DNS which will block ads and any other block list you add to it. I just needed to disable the Pi-Hole filters for 5 minutes and then it found the app and is working now. I imaging that the Licensing error is some Amazon licensing on all apps through their appstore and my filtered DNS was blocking it. I probably didn't need to uninstall first, just disable the filter and launch Emby again. I'll try that if it happens again.

This is why I've dumped Emby for the time being - they're not listening to the use base IMO.

Hello As audio is going to be fully driven by tags in the upcoming Emby Server versions, I‘m wondering which tag to choose for the reader(s) from audiobooks...? So which tag Emby is going to use when audiobooks section will be more polished and Emby will introduce a reader database field? Mp3tag doesn’t even provide a “reader” tag or similar, so I’m unsure. I want to make my files future proof for the upcoming releases of Emby server...

Thank you, this worked.

try switching prefered player from auto to native. had a family member with eac3 and no sound, this fixed it.

I’m really happy to see an official staff member respond so actively. It shows that the developers are actually listening to user feedback, which is great (even though this suggestion is already five years old). Keep it up!