All Activity

Hello I've the same problem, do u have an issue ?

Hey all, running into an issue here that's completely crippled Emby on my side. I stored all my Emby content (movies and shows) on a 2tb external hard drive, to avoid them cluttering up my computer. The drive was listed as the F: drive on my computer, so all the files were accessed via F. I recently came into possession of a relative's old laptop (Win10 from 2021) and decided to make it devoted to running Emby 24/7. So I moved the external drive and plugged it into the laptop (now the E drive), then moved the programdata folder over from my appdata folder on the original computer, and moved it to the laptop as well, to the same location. Now I can access Emby on the laptop browser (Firefox, same as my desktop PC) and can see my content listed, all the movies and shows, but they're all giving the same playback error when I try to watch them. I've tested it on various movies and shows, none of them are working, all giving the same error every time, and if memory serves this actually started before I even made the move. I've checked the files are being accessed from the correct place, I updated the library to access both the E and F drives, then just the E drive on the laptop to simplify things, and it still isn't working. I'm running into the playback error message on my desktop PC and my TV, when both used to work perfectly fine, as well as the laptop itself. I use a VPN on my desktop PC, I didn't intend to use it on my laptop, but I downloaded it again anyway just to see if it worked, but even with it enabled, the issue is still here. Let me know what logs are required and I'll attach them in a reply, I just want to get this fixed because as it stands, the entire system is down for me now. TLDR: I've encountered the above error on my TV and two separate computers, it cropped up prior to moving the files, but seems to still be appearing even now

Hi, I tested with the standard Emby for Android app on the same test device/BlueStacks. Result is the same as with Emby for Android TV. When entering the server as a bare hostname: emby.example.com login fails with: Access token is invalid or expired The proxy log shows the login request as a GET: GET /emby/Users/authenticatebyname?X-Emby-Client=Emby+for+Android&X-Emby-Device-Name=SM-S908E&X-Emby-Device-Id=[redacted]&X-Emby-Client-Version=3.5.36&X-Emby-Language=en-us HTTP/2.0" 401 When entering the server explicitly as: https://emby.example.com login succeeds. The proxy log then shows the correct POST request: POST /emby/Users/authenticatebyname?X-Emby-Client=Emby+for+Android&X-Emby-Device-Name=SM-S908E&X-Emby-Device-Id=[redacted]&X-Emby-Client-Version=3.5.36&X-Emby-Language=en-us HTTP/2.0" 200 So it is not only Emby for Android TV. The standard Emby for Android app behaves the same where bare hostname fails, explicit "https://" works.

The issue is fixed for me with the latest update, thanks a bunch. tested on iPad 11 Air and iPhone 13 Pro (both with ios 26.5) Codecs tested: HEVC/hvc1, 4K/hvc1, H264/avc1, Subs (SRT) on and off.

Use Backup & Restore plugin with "Include metadata subfolders" options ticked. No, unless NFOs/artwork saved with media.

You can follow related discussion here: Doesn't appear so, more likely that the beta will be pushed as stable soon(ish).

My apologies if this isn't the correct place to post this... Using Firefox on Windows with Windows Emby Server version 4.9.5 When switching my movie library between Date Added order and Title order, the switch doesn't apply. The drop-down at the top lists it as being in title order, but I don't get the alphabetical list on the right. If I go back and select Title order again, the list appears and everything is fine. It was definitely more reliable under 4.9.3. I'll add it's not ALL the time, but probably about 1/3 of the time, I have that problem.

I see beta build 4.10.0.16-beta got a security update for FFMPEG under entry of Update ffmpeg build to disable magicyuv decoder The vulnerability is called “PixelSmash” (tracked as CVE-2026-8461), a critical heap out-of-bounds write in FFmpeg’s MagicYUV decoder. Are there plans to release just a security update for 4.9.5 customers? I don't run beta on production server and the beta going GA is probably some way off still. Thanks

note that the server version is 4.9.5.

The issue that i noticed is that some audio like atmos unbale to detect by Emby server. Please check and fix this issue. Audio info in Emby (ios/ android TV/ chrome web browser) Title Hindi EAC3 5.1 (Default) Embedded Title Dolby Atmos 5.1 Language Hindi Codec EAC3 Layout 5.1 Channels 6 ch Bitrate 768 kbps Sample Rate 48,000 Hz Default Yes Audio info with Mediainfo: Audio ID : 2 Format : E-AC-3 JOC Format/Info : Enhanced AC-3 with Joint Object Coding Commercial name : Dolby Digital Plus with Dolby Atmos Codec ID : A_EAC3 Duration : 1 h 59 min Bit rate mode : Constant Bit rate : 768 kb/s Channel(s) : 6 channels Channel layout : L R C LFE Ls Rs Sampling rate : 48.0 kHz Frame rate : 31.250 FPS (1536 SPF) Compression mode : Lossy Stream size : 657 MiB (10%) Title : Dolby Atmos 5.1 Language : Hindi Service kind : Complete Main Default : Yes Forced : No

Yup working again.. cheers

Hi, yes that is fine. No problem.

Hi. Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares? Thanks.

I will definitely check this out and see what I can find.. that thought did come across my mind and I thought I'd checked my settings and everything but I'll review Thank you

Isn't all of this covered in the UI on the external player setup screen?

Can you give it another try?

Looks like you set the content type of the library to music. It would need to be music videos, or any of the other video types.

Hello, I would like to move all files in my media library to another subfolder, for example, from /video/movie/film1 to /video/movie/UHD/film1 How should I proceed to ensure the metadata and watch history for the media in this library are retained? I want to avoid having to re-scrape the metadata after the move. Can I simply move the files directly and then rescan the library?

I increased the watcher per your suggestion and rebooted my NAS. Will keep an eye on this and see if this helps

Every file and folder in your library uses a watch. A movie can be 50+ watches depending on how many pictures and stuff you like to keep. An instance is the number of changes since the last scan. Every actual watched file (not what you set it at) uses about 1K of memory.

Hi again, Have you tried changing the Album Artist field to "Soundtrack". Not the Artist field, just the Album Artist field. This will not affect the individual Artists on the individual Songs. Your "Soundtrack" Albums willl then appear under the one "Soundtrack" Album Artist and the Albums should then also be present in the "Albums as Contributing Artist" row on the respective individual Artist pages. As per my previous example, here is this view (e.g.) the main Album Artist page is "Larkin Poe" and the Bad Monkey "Soundtrack" Album on which they contribute only one Song also is shown on the row below their main Albums: The relevvant Song will also be in the Larkin Poe Songs list/page/etc. Of course, that's just my method of doing it. Whatever you wish to have as Album Artist should also work. If you still can't get it sorted out nicely, perhaps post your own specific example to help get to a resolution. Cheers!

Thank you for the quick reply and the help. I'm pretty sure I did setup spotlight collection with or within your plugin I'm not sure if I did it correctly so I will double check that. I will now work on the MDBLis instead of the ACdb and I'll report back

so what does "1148576" actually do? I remember few years ago where I posted about this, created the task, etc and fixed the issue. Never was certain about the number Thank You for your help!

Hi Luke, thanks for the suggestion but I'm using 4.9.3.0. again because I couldn't resolve the issues in 4.9.5.0. Version 4.9.3.0. works perfect for me. I just wait until the next update maybe then the bugs are fixed.

If you're going to add a bunch more files still, I would just change it to 1148576. Or, if you want to go up in smaller amounts just keep adding 10,000 until the error goes away.