All Activity

I have a Terramaster F4-210 NAS running TOS 4.2.41- on a Realtek RTD1296 @ 1.4Ghz ARM Cortex-A53 x 4 CPU. The version of Emby in the applications store to install is 4.8.8.0 which I tried but it kept stopping after I started it, so I uninstalled/reinstalled it and it started but I cannot open the Wizard, when I click Open I get: So I uninstalled Emby and restarted the NAS and did a manual install of Version 4.9.5.0 (emby_TOS_APP_4.9.5.0_aarch64) from the Emby website, but I get the same result as above, and strangely in applications it gives me an update option which then takes it back to 4.8.8.0 Any ideas? I want to give Emby a try now the Alexa skill for Plex (which I have working on the Terramaster) has been removed Cheers

I got tailscale installed on my nas and my android phone. However when I try to connect with emby out of my network it can't connect.Tailscale shows both my devices. Am I missing something?

OK it looks like you setup a redirect somewhere. Something is causing your login requests to get sent to Emby Server as a GET rather than a POST. Could be you setup a redirect, vpn, etc.

Log sent: ~16:15, user: TMC Started playing the show listed below; audio set to AC3 stereo; tried to change the speed twice, but it stayed at normal. (speed control does work if I switch to AAC stereo, but not all my media has this)

Hi everyone, I'd like to introduce JellyWatch for Android TV, a third-party media player built from scratch for Android TV, Google TV and Fire TV. It connects to both Emby and Jellyfin servers. The server type is detected automatically when you enter your URL, so there is nothing to configure manually. JellyWatch is built natively with Jetpack Compose for TV and designed entirely around the D-pad remote. No phone UI stretched to fit a television. Every screen, every animation, every interaction is made for the big screen. The app was first published in June 2026 and has already crossed 10,000 downloads on Google Play in just a few months. Website: https://jellywatch.app/android-tv Google Play: https://play.google.com/store/apps/details?id=com.jellywatch.tv Amazon Appstore: https://www.amazon.fr/dp/B0H6F1KLQ4 Emby support JellyWatch works with Emby servers out of the box. When you type your server URL on the login screen, the app probes the endpoint and detects whether it is Jellyfin or Emby automatically. Emby accounts get full access to: All libraries (movies, series, music, books) Continue Watching and Recently Added Live TV channels and recording timers Full playback with Direct Play and transcoding fallback Admin dashboard with active streams and library statistics Jellyfin-only features (Skip Intro, Trickplay thumbnails, SyncPlay, remote subtitle search, theme songs) are gracefully hidden when connected to an Emby server, so the interface stays clean and relevant. Playback engine The player is where JellyWatch really shines. It uses an intelligent 3-level fallback system: Direct Play passthrough -- your file plays as-is, no transcoding, no quality loss Local FFmpeg decode -- if a codec is not supported by the device hardware, the app decodes it locally with FFmpeg before hitting the server Server transcoding -- only as a last resort Supported formats and features: 4K, HDR10, HDR10+, Dolby Vision H.264, HEVC, AV1 (with libdav1d software fallback), VP9 Dolby TrueHD Atmos and DTS:X passthrough with force mode DTS-HD MA, FLAC, Opus Multichannel FLAC surround (5.1/7.1) delivered as Dolby Digital Plus over HDMI ARC/eARC automatically Two playback engines: ExoPlayer and MPV Playback speed from 0.5x to 2x Live quality switching (Original, 4K, 1080p, 720p, 480p, 360p) mid-stream without interruption Display rate switching to match video frame rate (24p, 25p, 30p, 60p) for judder-free playback Audio Night Mode for dynamic range compression (quiet dialog boost, loud peak reduction) Stats for Nerds overlay: codec, resolution, bitrate, HDR type, frame rate, dropped frames, buffer health, network bandwidth, display mode Subtitles SRT, ASS/SSA with full styling (rendered locally with libass), PGS bitmap subtitles Server-side burn-in option when needed Online subtitle search during playback via OpenSubtitles (requires a subtitle provider plugin on your server). Results are sorted by rating and download count. Downloaded subtitles are saved permanently on the server and available for all users. Home screen and navigation Resume right where you left off (Continue Watching) Next Up so you never lose track of a series Recently Added, organized by library Direct access to all your libraries Home Screen Channels: Continue Watching and Recently Added appear directly on the Android TV launcher, so you can resume without opening the app Fast search with content type filtering High-resolution artwork, smooth GPU-optimized animations Cinematic screensaver to protect OLED displays Exclusive features These are features that, to my knowledge, no other Emby or Jellyfin Android TV client currently offers: Kids Profile A dedicated kids mode with a custom home screen, large poster cards, hero banner, the Fredoka rounded font, colorful animated backgrounds, and three color themes. A parental PIN locks all exits from Kids mode and blocks access to Settings and adult profiles. Content filtering is managed by your server user policy. Linked Profiles (multiple servers, one home screen) Have accounts on two different servers? Link them from the "Who's watching?" screen. Continue Watching, Next Up and Recently Added merge into a single unified home screen. No more switching between servers. Each profile keeps its own watch history and preferences. Home Assistant Cinema Mode Connect your Home Assistant instance with a Long-Lived Access Token. Assign a script, scene or service call to play, pause and stop events. Press Play and your lights dim. Pause and they come back. Stop and everything returns to normal. Fully local, no cloud, no polling. Supports scripts, scenes, and direct service calls. Configure in Settings > Home Assistant. Multichannel FLAC Surround FLAC 5.1 and 7.1 files play in full surround on ARC/eARC soundbars and receivers. The app detects multichannel tracks and delivers Dolby Digital Plus over HDMI with no server configuration needed. Local Trailer Autoplay Place a Movie-trailer.mkv or Movie-trailer.mp4 next to your film on the server. JellyWatch plays it muted on loop as the backdrop on detail pages. No YouTube, no internet, no API key required. Additional features Theme songs: ambient background music plays automatically on movie and series detail pages, like a cinema lobby. Volume configurable (Off, Low, Medium, High). Trickplay thumbnails: scrub the timeline and see a live preview of the scene at the target position (requires Jellyfin 10.9+). Skip Intro and Credits: configurable per segment type (Off, Auto-skip, or Button). Supports intro, credits, recap, preview, and commercials. Smart coexistence with the Up Next overlay (requires Jellyfin 10.9+). SyncPlay: watch any movie or series in perfect sync with friends and family. Create or join a group, play/pause/seek together in real time. Automatic pause when someone is buffering (Jellyfin only). Admin Dashboard: real-time server monitoring on your TV. Active streams with backdrop artwork and transcode info, library statistics, connected devices grouped by user, library scan trigger, running task progress, server info and update alerts. Visible only for admin accounts. Seerr/Jellyseerr integration: search, discover trending content, and request movies or TV shows directly from the remote. Multi-account: switch between multiple accounts on the same device with avatar and quick switch. TV Quick Login: sign in with a short code on your phone, no TV keyboard needed. Picture in Picture: press Home during playback and the video continues in a floating window. Music player: browse albums, artists, genres and playlists. Persistent mini-player for background browsing. 10-band parametric equalizer with real-time presets. EPUB reader: browse your book library and read ebooks on your TV with dark, light and sepia themes, adjustable font size and D-pad page turning. Are you still watching?: after a configurable number of consecutive episodes (2-5), a dialog asks if you're still there. Prevents all-night playback. Can be disabled. Image cache management and optional animated backgrounds. Supported devices JellyWatch runs on all Android TV devices: NVIDIA Shield Chromecast with Google TV Amazon Fire TV (Stick 4K, Cube, Fire TV Stick) Xiaomi Mi Box Sony Bravia Mecool and other Android TV boxes Any device running Android TV 8.0 or above Requirements Android TV 8.0+ A Jellyfin Server 10.8+ or an Emby Server Local or remote network connection Trickplay thumbnails and theme songs require Jellyfin 10.9+ Download Google Play: https://play.google.com/store/apps/details?id=com.jellywatch.tv Amazon Appstore: https://www.amazon.fr/dp/B0H6F1KLQ4 Website: https://jellywatch.app/android-tv Mobile companion app JellyWatch also has a separate mobile app for server monitoring and management (not a player). Real-time session tracking, watch analytics, user management, Seerr/Jellyseerr/Radarr/Sonarr integration, and more. Available on Google Play: https://play.google.com/store/apps/details?id=com.jellywatch.app Disclaimer: JellyWatch is an independent third-party client. It is not affiliated with, endorsed by, or sponsored by Emby LLC or the Jellyfin project. "Emby" and "Jellyfin" are referenced for compatibility purposes only. Happy to answer any questions or take feedback. If you run into any issues with your Emby server, feel free to reach out here or on our Discord.

Should be fixed in v1.0.8.5! @Mookdogalso check if this fixed it for you please!

OK thanks I'll mess with it and let you know, thanks for all the help

Hey Guys Just installed the introDB plugin and went to scan for intro markers but the scan is only going to 0.3% before it stops completely. Any idea what could be wrong. I whitelisted all my tv shows (About 2600 shows) and it seems the scan stops within 3 minutes of starting it. Attached is my log maybe someone could help Thanks Mook embyserver.txt

No

Just to throw this out there, my current Emby install sits on a Netgear ReadyNAS but those systems are EOL'd and unsupported, so I wanted to migrate over to a more resilient setup. That said, the ReadyNAS still works fine, so I'm not in a rush. (Also, datacenter SAS storage isn't the cheapest thing right now so it will be a bit of time before I can migrate my whole library across...) Any advice you do have is greatly appreciated, I just want to prove the viability of this solution before I go broke on storage.

Do you use a reverse proxy?

I'm sure the features will get richer as time goes on. @softworkz This one is just a little trickier because you're in a different context.

embyserver.txt

I'm considering making an automatic resume if a failure happens.. Problem will be having it working well together with Embys time limit setting.

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

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

Yes, here's the OS details: Edition Windows Server 2025 Standard Version 24H2 Installed on 8/13/2026 OS build 26100.33296 Experience Windows Feature Experience Pack 1000.26100.275.0 Also since this is a server OS, Desktop Experience is installed, as well as the DX runtimes. Plan was to use the nVidia Tesla A2 (Driver v610.88) for transcoding. (I originally planned to use Docker, but it seems on a Windows OS that's a bit of excessive overhead just for the convenience of containerization...but I admit I'm fairly new to the hosting side of Docker. That's why I'm just going to install direct.)

Yes — and it turns out that comparison is the answer. Your web client builds the same URL for the same endpoint: getAudioStreamUrl() in modules/emby-apiclient/apiclient.js hits Audio/{Id}/universal with the same parameter names I was using, and it fills TranscodingContainer from the Container of whichever transcoding profile was matched. The difference is which value ends up there. In modules/browserdeviceprofile.js the audio HLS transcoding profile declares Container "ts" on Chromium and "aac" everywhere else, Safari included — never "mp4". The video HLS profile in the same file does push m4s. So the web app never takes the audio fMP4 path at all, which is why nothing shows up there. Measured against the same track, the same server and the same session, changing only that one parameter: TranscodingContainer=ts playlist 200, segment 0 -> 200, 91,556 bytes TranscodingContainer=aac playlist 200, segment 0 -> 200, 91,556 bytes TranscodingContainer=mp4 playlist 200, init.mp4 -> 500, every segment -> 500 The two values your own web app uses both work. Only mp4 fails, with the null reference at TranscodingCommandBuilder.HlsGetCommandLineArguments and no ffmpeg process ever started. I'm asking for mp4 because I want fMP4 audio segments for Apple's native player, the same way the video path already offers m4s. Happy to test a build whenever you have one.

I will try and uninstall and reinstall official release .54 and see if it fixes

No those were created by Emby.

That's strange. There is nothing that should stop it then other than some settings in Emby. This is the schedule task in Emby. See if the time limit is set as that will stop it. Edit: I mean if it is set incorrectly. Also are these enabled in the plugin?

Following up on my own 4.10.0.30 post: I found why the tail still hangs, and this time I can show it with your own app. The last segments are the same file. Byte for byte. On the 21-minute episode from the top of this thread: my own tvOS app, 6-second segments Emby for Apple TV 2.0.9, 3-second segments md5(segment 220) = d57aadc9... md5(segment 440) = d57aadc9... md5(segment 221) = d57aadc9... md5(segment 441) = d57aadc9... md5(segment 442) = d57aadc9... 2 identical, 2,646,476 B each 3 identical, 2,646,476 B each Both go through the same path — HLS with .ts and the video copied — and both stop in the same place. Every one of those requests returns 200, so from the server's side nothing looks wrong. Why it happens, from your own command lines. You restart ffmpeg per segment and seek to the nominal segment boundary, with the video copied: -ss 00:22:00.000 -f segment -c:v copy -> segment 220 -ss 00:22:06.000 -f segment -c:v copy -> segment 221 With -c:v copy ffmpeg cannot start anywhere except a keyframe. In this episode the last keyframe is at 1319.693 s and there is none after it, so every run whose -ss lands past it rewinds to that same keyframe and emits the same frames. That also predicts the count, and the prediction holds: the number of duplicated tail segments is the number of segment boundaries that fall after the last keyframe. With 6-second segments there are two (1320.000, 1326.000) and I get two identical segments; with 3-second segments there are three (1320.000, 1323.000, 1326.000) and I get three. I isolated the condition with four synthetic files that share the exact same arithmetic — 1326.336 s declared, 222 segments at 6 s, the last starting at 1326.000 — and differ only in where the last keyframe falls: last keyframe segment 220 vs 221 playback 1324.000 different (528,092 / 138,180 plays to the end 1320.000 different (907,664 / 351,372 plays to the end 1319.720 IDENTICAL, 366,788 B hangs at the end 1319.693 (real) IDENTICAL, 2,646,476 B hangs at the end 280 milliseconds of keyframe placement is the whole difference. If the last keyframe sits exactly on a segment boundary, or if there is another keyframe after it, the tail is fine. The synthetic that reproduces it, if you would rather build your own than take mine: ffmpeg -f lavfi -i "testsrc=size=1920x1080:rate=25" -frames:v 33150 \ -c:v libx264 -preset ultrafast -crf 32 -pix_fmt yuv420p -profile:v high \ -force_key_frames "expr:gte(t,9.693+n_forced*10)" -sc_threshold 0 video.mkv ffmpeg -f lavfi -i "sine=frequency=440:sample_rate=48000" -ac 2 -t 1326.336 \ -c:a ac3 -b:a 192k audio.mka ffmpeg -i video.mkv -i audio.mka -map 0:v:0 -map 1:a:0 -c copy sample.mkv That puts the last keyframe at 1319.720 with none after it. Play it, seek to about 20:00, and let it run out. It reproduces on both apps, and the segment md5s match the same way. One thing worth knowing, because it explains why this is hard to reproduce on demand: Emby Web on Safari swallows the duplicate and ends cleanly. So "it works for me" and "it hangs every time" can both be true on the same build, the same file and the same server. If the restart seeked to the keyframe that actually precedes the requested segment, and a segment were dropped when it cannot advance past the previous one, I believe this tail would end. Happy to run anything against this setup, I have it ready.

I guess compare to a web app url for that endpoint?

I am using the new Windows client. This problem started a couple months ago. When tuning in a TV station (tuner channel), the audio does not play properly - cutting in and out for approximately 30 seconds. Eventually it rights itself and sounds fine. This does not happen when I play a recorded TV show, for example. I am bitstreaming / passing through all audio through hdmi to a receiver. Audio being bitstreamed is typically dolby digital 5.0.