All Activity

it is Emby for Android 3.4.74

Hi @Luke, yes it is 100% reproducible for me. I am assuming its 100% reproducible for everyone. I can't find the pattern as to why. "ask m.b home play the song house" is treated differently* to "ask m.b home play the song Jurassic park" *i am making the assumption the emby log is indicative and representative for both equally, both result in a single search statement in the emby log. *I am assuming the content in the library and wether there is indeed such song content present is not important...the incorrect search call to the api i am assuming is representive of the core of the issue (not the librarys actual content) i had a play with number of words in the song title and number of syllables in title word 1,2,3...and havent found the pattern yet. But for a given song title the outcome is 100% consistent..Some titles search 'properly' some don't it seems. i am speaking in english with southern english accent. I get a low sucess rate on Emby hearing the skill name properly...and have to really labour it out....."Em"..."Bee"...HOME...I dont think that is relevant here because the alexa history and the search shows i was heard properly...but it perhaps just 'goes to' a weak success rate in the voice recognition of skill name / command structure [at least for my accent]. FWIW When the skill recognition goes wrong Alexa has heard "ask home play the song Jurassic park"..."m.b home" has a weak recognition rate in my accent /language...I wonder if a more certain skill name is possible.

Sinon: https://emby.media/support/articles/TV-Naming.html Je pose juste là

Tu peux faire tout ça de façon totalement automatique en utilisant Filebot (un super outil pour le renommage en série de fichiers média Pour les séries avec tmdb j'utilise ce filtre dans Filebot qui te donne directement le nommage parfait /monchemindaccès/{emby.tail} {"[tmdbid=$tmdbid]"}

2025-07-17 09:33:56.232 Debug LibraryService-0HNE3Q3I3LL58:00000001: http/1.1 GET http://‌192.168.0.207‌/emby/Items/75092/similar?api_key=‌XXXXXXX. Source Ip: ‌192.168.0.50‌, UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 2025-07-17 09:33:56.235 Debug SqliteItemRepository: GetitemById Movie 75092 /mnt/storage0/multimedia/movies/7/71 (2014)/71 (2014).mkv 2025-07-17 09:33:56.235 Error LibraryService-0HNE3Q3I3LL58:00000001: Error processing request *** Error Report *** Version: 4.9.1.7 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Linux version 6.8.12-11-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX OS/Process: x64/x64 Framework: .NET 8.0.11 Runtime: opt/emby-server/system/System.Private.CoreLib.dll Processor count: 38 Data path: /var/lib/emby Application path: /opt/emby-server/system System.NullReferenceException: System.NullReferenceException: Object reference not set to an instance of an object. at Emby.Api.Library.LibraryService.GetSimilarItemsResult(BaseGetSimilarItemsFromItem request, BaseItem item, User user, String[] includeItemTypes, Boolean enableGroupByMetadataKey, Boolean supportHidePlayed, Boolean groupBySeriesPresentationUniqueKey, CancellationToken cancellationToken) at Emby.Api.Library.LibraryService.Get(GetSimilarItems request) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost httpHost, IServerApplicationHost appHost, IRequest httpReq, IResponse httpRes, IStreamHelper streamHelper, RestPath restPath, String responseContentType, CancellationToken cancellationToken) Id is a movie Id

Nothing to do with Emby the software (this community site) You will need to contact the owner/administrator of that server and request help there.

Ok, I think i stumbled on a breakthough in this case. It has something to do with selected audiotrack when starting the playback. When I start File_1 with track1 (default, Ukrainian, AC3) it will play perfectly well, even if I change the track. If start it with the track2 (English, DTS 5.1) - it won't play even if I change the track back to default one. Similar results with File_2 - it starts well with track1 and track2 (which are Ukrainian AC3) and won't start with track3 (English, AAC). And again, changing track after start won't make a difference - it will play any track if already playing well, and it won't play if the "wrong" track was chosen at the start. File_1 was tested and both servers and the result is the same, FIle_2 - only on server_1 (the one I has issues with from the start). Logs are attached. I also tested some other files, and looks like the issue may be connected to some settings during ripping, because some other files that used AAC and DTS5.1 played fine if corresponding track were selected. But still, even these files with allegedly badly ripped tracks CAN play, if I chose different track instead at start and switch to the "bad" one later. And they CAN play normally on other devices with the "bad" track selected from the start. As for your questions: Attach the media info for the examples in attachment. if needed, I can share the very files. confirm if any files direct play, or is it just a few examples that have issues no, not all the files have issues. Some (I would say most) play perfectly well. Moreover, these problematic files play well on other devices from the same server, it's only LG TV client that has issues with them confirm it the server is local or remote on the TV I'm connected via LAN but remote was enabled on server_2 are you using a reverse proxy at the time of recent testing server_2 was forwarded to a remote proxy, but it was not used for local connection. Server_1 (the one that has more issues) is not using reverse proxy. are you trying to connect the app to the server using https Server_2 was forwarded to a remote proxy that had SSL certificates and HTTPS set up, but the connection was local. For now server_2 seems to work well, I am yet to find a file it cannot play. embyserver_1_file_1_audiotrack.txt embyserver_1_file_2_audiotrack.txt embyserver_2_file_1_audiotrack.txt

yes Luke. sorry thought that was closed long time ago. I'm not using the z9x pro anymore therefore I'm not using jellyfin anymore therefore all good I don't care which port emby uses and blocks fact was that in the installation process the port was not changeable and therefore I couldn't enter the settings menu to change the port... both emyb and jellyfin are suing the same initial port in installation process but now, all good!! best d

@lordairivisI had a similar way of "discovering" how to use multi-version files and found the following solution to be working best: /Movies/Godzilla Minus One (2023)/Godzilla Minus One (2023) - 1080p.mkv /Movies4K/Godzilla Minus One (2023)/Godzilla Minus One (2023) - 4K.mkv /MoviesAlt/Godzilla Minus One (2023)/Godzilla Minus One (2023) - 1080p - minus color.mkv My best best is that the special characters in the name cause the identification to fail. Additionally, I also found that using numbers in the parent folders causes issues. For example this (sometimes) doesn't working: /MoviesAlt/Godzilla Minus One (2023)/4K/Godzilla Minus One (2023) - 4k.mkv /MoviesAlt/Godzilla Minus One (2023)/1080p/Godzilla Minus One (2023) - 1080p.mkv But this does (replacing 4K and 1080p with UHD and HD, non-numeric): /MoviesAlt/Godzilla Minus One (2023)/UHD/Godzilla Minus One (2023) - 4k.mkv /MoviesAlt/Godzilla Minus One (2023)/HD/Godzilla Minus One (2023) - 1080p.mkv

On Windows 10 using Emby version 4.8.11.0 with the timezone set to UTC+1 I see that in my example the date for the episode Foundation s02e03 the Emby premieredate is the following: 2023-07-27T00:00:00.0000000Z. That matches with https://www.themoviedb.org/tv/93740-foundation/season/2/episode/3 but not with https://www.thetvdb.com/series/foundation-2021/episodes/9785494 and that's correct for my settings; TMDB is preferred over TVDB. In my case the date "27 jul 2023" is also displayed with this episode so that also seems correct. @Blue278does this issue affect all of your episodes or just some?

OK, je pourrai faire une vidéo ce soir. À noter que, pour être plus précis, via l'app Emby d'Android Auto, les pochettes n'apparaissent jamais. Par contre, c'est via le menu "Musiques" du véhicule que la pochette apparait puis disparait. En attendant, si jamais ça peut aider, voici un extrait des logs au moment de ce matin où j'ai eu le souci également: 2025-07-17 07:48:45.509 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:45.510 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress 2025-07-17 07:48:55.013 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing/Stopped. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:55.013 Info Server: http/1.1 GET http://**.**.**.**:8096/emby/Audio/133106/universal?UserId=a1c0cfb136a245e79ffa9033ad4d80e1&DeviceId=a7926e519561091f&MaxStreamingBitrate=200000000&TranscodingContainer=ts&TranscodingProtocol=hls&AudioCodec=aac&api_key=x_secret1_x&PlaySessionId=1752731150169&StartTimeTicks=0&EnableRedirection=true&EnableRemoteMedia=false. Source Ip: host1, Connection=keep-alive, Host=host2, User-Agent=Emby/3.4.74 (Linux;Android 11) AndroidXMedia3/1.5.1, Accept-Encoding=identity, Icy-MetaData=1 2025-07-17 07:48:55.013 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:55.013 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:55.014 Info Server: http/1.1 Response 200 to host1. Time: 20739ms. GET http://**.**.**.**:8096/emby/Audio/66569/universal?UserId=a1c0cfb136a245e79ffa9033ad4d80e1&DeviceId=a7926e519561091f&MaxStreamingBitrate=200000000&TranscodingContainer=ts&TranscodingProtocol=hls&AudioCodec=aac&api_key=x_secret1_x&PlaySessionId=1752731150137&StartTimeTicks=0&EnableRedirection=true&EnableRemoteMedia=false 2025-07-17 07:48:55.014 Info SessionManager: Playback stopped reported by app Emby for Android 3.4.74 on Tel Rémy playing Coldplay - O. Stopped at 19390 ms. PlaySessionId: 1752731150137 2025-07-17 07:48:55.014 Info SessionManager: Adding playSession 1752731150169 to session 7662ac105eeae920d509aeea174c927e 2025-07-17 07:48:55.014 Info App: User policy for MUSIQUE. EnableAudioPlaybackTranscoding: True 2025-07-17 07:48:55.014 Info SessionManager: Removed playSession 1752731150137 from session 7662ac105eeae920d509aeea174c927e 2025-07-17 07:48:55.014 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://**.**.**.**:8096/emby/Sessions/Playing/Stopped 2025-07-17 07:48:55.016 Info SessionManager: Playback start reported by app Emby for Android 3.4.74 on Tel Rémy playing Avril Lavigne - Losing Grip. Started at 0 ms. PlaySessionId: 1752731150169 2025-07-17 07:48:55.017 Info Server: http/1.1 Response 204 to host1. Time: 4ms. POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress 2025-07-17 07:48:55.019 Info Server: http/1.1 Response 204 to host1. Time: 6ms. POST http://**.**.**.**:8096/emby/Sessions/Playing 2025-07-17 07:48:58.784 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:58.809 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:58.809 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress 2025-07-17 07:48:58.998 Info SessionManager: Playback start reported by app Emby for Android 3.4.74 on Tel Rémy playing Avril Lavigne - Losing Grip. Started at 0 ms. PlaySessionId: 1752731150169 2025-07-17 07:48:58.999 Info Server: http/1.1 Response 204 to host1. Time: 214ms. POST http://**.**.**.**:8096/emby/Sessions/Playing 2025-07-17 07:48:59.702 Info Server: http/1.1 POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: okhttp/4.12.0 2025-07-17 07:48:59.703 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://**.**.**.**:8096/emby/Sessions/Playing/Progress

@ServerNoob005in this screenshot you have an extra "." in your file name. Also; doesn't this mean your "REAL" filename is "Redline (2009) {tmdbid=71883}..mkv.mkv"? Usually extensions are hidden and need to be "unhidden" manually by adding them to the "known extension" list. 1. Check the REAL filenames Your formatting comes close but I believe it doesn't actually match. You can confirm the filename using Powershell: Open Powershell Using `cd` and go to the correct drive and folder. For Example in my case: cd 'E:\Media\Movies\Redline (2009) {tmdbid=71883}\' Use the quotes above because the folder and filename contain spaces and special characters. When navigated to the folder, you can use the `ls` command and you should see something like this: PS E:\Media\Movies\Redline (2009) {tmdbid=71883}> ls Directory: E:\Media\Movies\Redline (2009) {tmdbid=71883} Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 17-7-2025 08:17 0 Redline (2009) {tmdbid=71883}.mkv That's how the file should look. If this is all the same, use the scan library method again to validate the item's existence. In my case I didn't even need to do that and the item popped up after a few seconds: 2. Validate Naming Convention Please also be sure your movies are DIRECTLY inside your library folder. If your "Movie library" has the following path: "C:\Media\Awesome Films". You should put films only directly inside: "C:\Media\Awesome Films\Redline (2009)". Don't do things like: "C:\Media\Awesome Films\anime_movies\Redline (2009)" because that doesn't fit the naming convention. Your parent folders also contain special characters, that might also cause issues. 3. Recreate a working scenario The best test in your case would be to create the following: "\\Network\Synology_1\Movies\Redline (2009)\Redline (2009).mkv" and create a new library in Emby configured to use "\\Network\Synology_1\Movies". This above example should absolutely work because it basically mirrors my working case. If it does not; something else is wrongly configured and the issue probably also lies somewhere else.

Apparently it was the setting under Audio "convert audio to dolby digital" seems to have fixed it.

So long story, about a couple months ago, some devices were experiencing a stuttering/laggy/choppy playback. This was mainly noticeable on the Android app, this was not present on Android TV app. Thing is, you could easily fix it, simply change the bitrate to another one. Any other bitrate would work. Even if it was higher than what it started on. The last was experienced on DirectPlay. I've seen a few threads about it here, but no answers were resulted in the posts. Fast forward, I'm setting up a new server, but now the problems are worse. New server, new storage, etc. I've tried switching the quality back and forward like I mentioned, and it works sometimes. But it's needing me to do it like 3/4 times for stable playback. I have log debug log files and DirectPlay log file as well attached. Additionally, I did a speed test of the storage. From the server that is hosting Emby, to the mounted storage that is hosting the files, I'm getting 367MiB/s read speed. Which I think should be sufficient enough for playback of a 2Mbps encoded video. This is now being seen across all devices, which makes me think it's a combination of the previous issue, and something new. The server is Arch Linux, using Docker compose for the Emby server, on the latest version. So any help would be appreciated. Here are the rotated log files. Edit: Should also mention that the host has 1GB up and down, so I doubt that is also the issue. ffmpeg-directstream-e25f0db8-302f-4f1a-a35d-13aec1ae0af3_1.txt embyserver.txt

The new version is up. Added: Support for videos in "Home Videos and Photos" type libraries. Clear icon cache button for when icons have changed in the icons folder - It should now work correctly, last time it didn't work when changing to a different image format, for example from jpg to png. Changed: Made the settings page preview dynamic and random, giving a better representation of the icons. Download here or at Github - EmbyIcons Edit: Forgot to say, the whole code is available on the Github. Do with it what you want, even make it your own, just please keep it open source! EmbyIcons.zip

I'm a brand new user of Emby, and signed up for an account. I was notified that I would get an email to confirm my account registration, but it's been 3 days, and nothing (yes, I checked my spam folder). I can't seem to get in touch with anyone on the Emby site either. I seem to be able to sign into my account, but I've not been able to confirm it; will this be an issue in the future?

@Lukewould it be possible for Emby to natively support the correct timezone? The fix is referring to FireFox. I use safari.

Good evening. @brothom @LukeAs I feared, it did not succeed. Even tried moving it to the normal generic "movies" folder on the off chance that would make a difference, and it gives the same result as below. I really don't know what to say at this point. It simply doesn't seem to care about the folder or mkv name at all. Unfortunately, I can't reasonably guess what has caused this as I said, I have hardly touched the settings. It doesn't matter how many times IU rescan the library- The result is always the same. I open to any further suggestions of where I should look next...

Me too Im using the server i used all the time Play.embyil.tv And suddenly it says name and password are wrong

With a movie or series, Try /items/id/similar From there the usual params that you're used to.

OK we'll take a look at it. Thanks !

root@emby:~ # pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.9.1.7/emby-server-freebsd13_4.9.1.7_amd64.pkg [emby] Fetching emby-server-freebsd13_4.9.1.7_amd64.pkg: 100% 98 MiB 17.1MB/s 00:06 [emby] Installing emby-server-4.9.1.7_1... package emby-server is already installed, forced install pkg: Missing dependency 'mbedtls2' Based on this: https://emby.media/freebsd-server.html If you look at the log messages in the commit history you'll see: 2025/01/02: security/mbedtls: Move to security/mbedtls2 2025/06/02: security/mbedtls2: Remove expired port My last package upgrade was since before the rename of mbedtls to mbedtls2, and now that the package is removed my version of mbedtls2 is named mbedtls and I fail the dependency check when I try to install the beta. I have mbedtls3 installed as per the dependency provided on your Emby Server for FreeBSD installation guide, but obviously the beta and stable channels are depending on mbedtls2 so I'm stuck on 4.9.0.30 from my last upgrade in 2024. That's my story, but anyone with a fresh FreeBSD 13 install would not be able to install Emby Server because the mbedtls2 port has been removed as of 06/02.

I did find this that might allow you to remove the port assignment manually: Does that help?

@eric.faes@gmail.comso with Docker all we do is list the ports that are needed and Docker takes care of the rest. It is responsible for deleting the port registrations, and it looks like people have this same issue on Synology with other software (not Emby). https://www.synoforum.com/threads/docker-local-port-conflicts-with-other-ports-used-by-other-services.10086/ Actually if you just google search there's a lot of hits about this.

@supermood?