All Activity

@leshkraven Thanks for the feedback. I would have been surprised when it was about out app, simply because it would have come up before, but I wasn't sure enough to blame it away, because my main machine crashes on sleep, so it's always disabled. Now, didn't you say that the one change on your side was a switch to a different display? With your recent results, my best theory would be that maybe a new display requires a "refresh" or fresh save of the power settings - but that's merely a guess.

I'm sure it was not emby. But now you got me thinking: a few years ago I was using a 3rd-party screen saver on the Chromecast. Maybe it was the one showing the track title, not Google's. Unfortunately it was discontinued so I have no way of verifying it.

OK try the latest build and see if that segment is severed now. Thanks

I have no issues with Dolby Vision profile 7.6 content on Emby for Android. Have you reported a media playback issue with an example? Otherwise you're just polluting someone else's topic.

Confirmed on 4.10.0.29 — thank you, that was fast. To keep this independent of my library and my server, I measured the beta on a fresh install in a disposable container, against a synthetic HDR10 HEVC MKV (AC-3 source track) made for the purpose. Same device profile as my earlier posts, transcoding forced; the only thing changing between rows is the audio codec list in the transcoding profile. What the manifest advertises, and what the media segment actually contains according to ffprobe: requested CODECS attribute segment audio aac "avc1.640029,mp4a.40.2" aac mp3 "avc1.640029,mp4a.40.34" mp3 ac3 "avc1.640029,ac-3" ac3 eac3 "avc1.640029,ec-3" eac3 opus "avc1.640029,opus" opus dts "avc1.640029,ac-3" ac3 flac "avc1.640029,fLaC" (transcode fails to start; below) alac attribute absent alac truehd attribute absent (transcode fails to start) (The video half is avc1 in these runs because the probe deliberately forces a transcode, tonemap included — the half under test here is the audio one.) And the row that matters most to me: with my app's actual profile, aac,ac3,alac,eac3,flac, the server now keeps AC-3 and writes CODECS="…,ac-3". A described variant and passthrough at the same time — that was the practical cost of the old behaviour for nearly every file in my library, and it's gone. Thank you. A few observations from the table, in case they're useful: - The dts row is the mapping being honest, not a bug: the transcoder falls back to AC-3, the segment really is AC-3, and the attribute describes what actually comes out rather than what was asked for — which is exactly what a player needs. The only stale trace is that the TranscodingUrl still echoes AudioCodec=dts. - alac is now a clean measurement of the second point from my earlier post: the server produces a valid ALAC segment, and the whole CODECS attribute still disappears with it, including the video half it computed correctly. Emitting CODECS="avc1.640029" alone would be valid HLS and enough to rule the variant in or out. - flac advertises fLaC, but the transcode itself never starts: ffmpeg refuses FLAC in fMP4 without "-strict -2" ("experimental, add '-strict -2' if you want to use it" … "Could not write header"). truehd fails to start too. Both reproduce on the clean container, so it isn't my server's ffmpeg being odd. One more data point from this build: the "HDR 10" space round-trip from my last post is unchanged, so everything there still applies. What is new is what the patched URL yields now that AC-3 has a codec string: #EXT-X-STREAM-INF:BANDWIDTH=8871857,AVERAGE-BANDWIDTH=7393214,VIDEO-RANGE=PQ,CODECS="hvc1.2.4.L150.B0,ac-3",RESOLUTION=1920x1080,FRAME-RATE=23.976 — the untouched HDR10 copy and the passthrough audio in the same fully described variant. With that one serialisation fix, an AC-3 library gets everything I asked for at the top of this thread out of the box. Happy to run the same table against any future build.

Are you sure you weren't using the Android TV app before? It has its own music "screensaver" of sorts.

Not the way the version feature is currently designed to be used. There is a ton of discussion on this already. Our current version implementation is not intended for different editions of an item. It is intended for different qualities of the same item. The concept of "Editions" will need to be introduced to get what you want here.

It is, that's why I said thank you.

For instance, one of the steps was to go to canyouseeme.org and confirm your port is reachable (after you've completed the forwarding). Did you do that? What happened? I'm guessing it failed but you haven't told us.

New Emby server Beta release, v4.10.0.29.

It should be available now as an option in the app settings.

To my knowledge, Any TrueHD and 7.1+ in general can't be passed through on LG TVs. At least not by any native LG apps. You will need an external device connected to your AVR for that to work. Maybe it will work with connected to the TV and then through eARC, i'm not sure about that though.

New version v2.7.1.3 in the catalog. Added: 1) Ability to use multiple local Tesseract instances at once. 2) More control over CPU/GPU to improve performance on bigger machines. Fixed: 1) Episode process bars should now show the correct info.

but it's TrueHD 2.0!

Anyone who mocks without being able to refute what has been said ultimately only exposes their own narrow-mindedness – and thus becomes exactly what they are mocking.

Thankyou

TVs in general can't passthrough TrueHD and/or above 5.1 so transcode is needed. If you want TrueHD and 7.1+ you will need to use for example a Nvidia Shield connected to the AVR.

Not sure how you inserted those links into the post, but both of them are null.

Understood. I was wondering if this plug-in could be updated to 3.8.10 for this old Emby server version, so I could go on using Trakt. Thanks

Hi everyone, I’d like to share MediaOps, a free and open-source, self-hosted Discord bot I’ve been building to bring several parts of an Emby community directly into Discord. The idea started from my own setup: I wanted users to be able to search the Emby library, request missing content through Ombi, follow the status of those requests, and organize synchronized Watch Parties without having to jump between multiple interfaces. MediaOps currently includes: Emby library search through /movie and /tv Recently added media with /latest Ombi movie and TV requests directly from Discord Discord Forum integration for media requests, including automatic status/tag updates Watch Party scheduling and management Random movie selection for Watch Parties Discord Scheduled Events and RSVP notifications English and French support Role-based Discord command permissions Docker deployment with support for Unraid and Portainer A /health command for checking the MediaOps, Emby and request-provider connections Watch Parties For synchronized playback, MediaOps integrates with Emby Watch Party by Oratorian, an open-source project specifically designed to provide synchronized Watch Party sessions for Emby. Emby Watch Party by Oratorian on GitHub MediaOps does not attempt to replace or reimplement the Watch Party engine. Instead, the two projects complement each other: Emby Watch Party by Oratorian handles the synchronized Emby playback experience, while MediaOps adds the Discord orchestration around it — scheduling a party, creating Discord events, handling participation, sending reminders, generating the Watch Party session and giving participants a simple way to join. This allows an Emby community to organize the entire Watch Party from Discord while relying on Oratorian's project for the actual synchronized viewing experience. A big thanks to Oratorian for making Emby Watch Party available as an open-source project. It is what makes the synchronized playback side of MediaOps' Watch Party integration possible. Self-hosted by design MediaOps v1 is intentionally single-tenant and self-hosted. You create your own Discord Application/Bot and connect your own MediaOps instance to your own Emby, Ombi and optional Watch Party services. Your Emby and Ombi credentials remain with your deployment; there is no central MediaOps service that needs access to your server. Installation MediaOps is distributed as a Docker image through GHCR and includes Docker Compose and Unraid templates. It has also been accepted into Unraid Community Applications and should become searchable there after the next CA catalog build. The project is licensed under GPLv3 and the source code, documentation, configuration examples and installation instructions are available on GitHub. Project links GitHub: MediaOps on GitHub MediaOps Community / support: Join the MediaOps Discord MediaOps is still a young project, so feedback from other Emby users and self-hosters would be very welcome — particularly around different Emby deployments, Discord workflows and features that would make the integration more useful. Thanks! miakkia

Hello, I hae 2 LG TV. One is OLED65C8PUA which is an old 2014 model or so that only have HDMI ARC and the other one is OLED77C5PUA, 2025 model with HDMI E-ARC. Both are connected to 7.1+ Atmos Receiver (Sony STR-DN1080 and Denon AVR-X4800H). I know the 77 can do Dolby Atmos 7.1 no problem but the second a TrueHD stream is sent, even 2.0, Emby transcode it. I'm wondering why because it shouldn't. In the user guide, it says it support Dolby TrueHD on EArc http://kr.eguide.lgappstv.com/manual/w25/w25_u33/enga.html#6227 I know the 65 also support TrueHD but not on output at 7 channel. But TrueHD for 2 channel is supported. Thank you

Thanks Luke! Any ideas when the documentation might be ready, and where I should look for it if it is ready?

No, play vid in bg is disabled. So I ran some tests and had some good results. Typical PC and Windows gremlins always trying to make me look the fool. I changed my power settings from 10min screen sleep/ 45min PC sleep, to 1min screen sleep, 2min PC sleep I ran a ep for 3min, exited to homescreen and had a successful screen sleep and PC sleep on time I ran a movie dragging the seek bar to the last 5min and letting the return to homescreen happening automatically, this result was successful screen sleep and PC sleep on time I put my settings back to 10min screen and 45min PC, started an ep and let it run, came home to a successful result, screen off and PC asleep So now I am wondering is it a bug in WIN11 where a change in powersettings resets the sleep function somehow, I dont quiet know how to trigger it, do the power settings need changing once in a while, does it need to have one successful sleep and powered back on, and them putting powersettings times to a greater number. You just dont know with these kind of things, I tried lots of this stuff already but this time it seemed to work, I`ll see how it goes over the next few days but I am definitely leaning towards Windows and not Em theatre being the really issue here

Yes you can cancel now. Thanks

I feel like it has to do with anytime there's a transition from HLS/AAC --> MP3 playback. (<-- or something related to contiguous but dissimilar file playback). If I may, here's a snippet from AI helping me troubleshoot this problem from a while back. I let AI ingest a portion of a log file. This is what led me to try adjusting the remote (cellular) cap, which did work to keep the problem from happening. I was using Emby Android 3.5.36 at this time (about 4 months ago or so). Would the full debug and ffmpeg logs help? The server did its job and handed off the next track correctly. The failure is on the client side — the Emby for Android app (v3.5.36) failed to start playing the new HLS stream and aborted right away. Why This Happens (Especially Remotely) HLS Transcoding Handover Issues: Common on Android when skipping tracks in playlists remotely. The app's media player (ExoPlayer) sometimes chokes on starting the next transcoded segment, especially with FLAC sources or bitrate mismatches. Remote + Low Bitrate Cap: Your setup forces transcoding (good for bandwidth, but fragile for seamless playlist playback). App Version: 3.5.36 is fairly recent, but similar issues have been reported with FLAC/remote skips. Quick Things to Try Raise the bitrate limit on the Android app (under Playback → Quality or Video Quality settings) to allow Direct Play/Stream for more files. Test if it reduces transcoding. Force lower quality or test with an all-MP3 playlist to see if FLAC sources are the trigger. Don't skip manually — let it play through naturally and see if auto-advance fails the same way. Local network test: Play the same playlist on Wi-Fi (same LAN). If it works, confirms remote/transcoding sensitivity. Update/reinstall: Ensure server is latest; try clearing app cache or reinstalling the Android app. Next Steps for Logs Enable full debug on both server and Android app, reproduce, and grab: The matching ffmpeg transcode log for the ABBA track (should show what happened during that brief attempt). Android app debug log (via the app's "Send log" feature) — this will likely show ExoPlayer errors.