All Activity

Hi, what version have you tried?

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

Thank you for updating this! It was also good to get the new maintenance mode feature on that page. The only real suggestion I have at the moment is to move "Emby Server Folder Paths Information" to right after "Emby Server Friendly Name" and then follow it with "Emby Server Shutdown and Restart" so it flows more top-down left-right in alignment with the dashboard page. Currently it starts with the friendly server name, then jumps down to the URLs, then back up for shutdown/restart, then left for server paths. Purely a suggestion though, the information is still good as is.

I will do that later today. For opus, I was somewhat involved in the listening tests done with the encoder 15+ years ago, so I've always just kind of been partial to it. Plus the webm container requires it which was more or less made by google as Android is also made by google. So an Android product not supporting opus seems as likely as an apple product not supporting AAC. By native support are you talking about hardware or software? I have never noticed transcoding due to the use of opus audio. I dug up some old logs from May, watching the same series, The Office. Obviously a different episode but verified it was still av1/opus (attached) The black screen and opus transcoding issue only appeared after the app updated automatically on July 18. embyserver_.txt

There is not currently although it's certainly possible.

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

HI, we'll have a new ffmpeg build on the server beta channel soon, so stay tuned for that. Thanks.

HI, we'll have a new ffmpeg build on the server beta channel soon, so stay tuned for that. Thanks.

HI, yes I agree we should add that. Thanks.

Can you show a screenshot of what you do see? Thanks !

HI there, can you please provide a specific example? How to Report a Problem Thanks !

HI, are you still having an issue with this on Emby Server 4.9.5?

Thanks for flagging this. I have re-written the article and the updated document is now online Server Settings

HI there, can you please provide a specific example? How to Report a Problem Thanks !

HI, what version number of the app are you on now?

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

@dma_kare you sure this is the log from when you tried to upload the image? I don't see that activity here. Can you please try again? Thanks.

HI there, can you please provide a specific example? How to Report a Problem Thanks !

Hi, we are working on improving this. Thanks.

To clear the logs, I restarted the server at 20:00 before the test. I started playing the movie at 20:01. The audio began to lag at approximately 21:00 (around the 58–59 minute mark). Device: Xiaomi Mi Box 3. I am attaching the server logs and information about the video file. 2026-07-28 21:00:29.440 Info SessionManager: Playback progress (Pause) I stopped playback myself at that point, after the lag had started. embyserver.txt hardware_detection-63920865587.txt Супермен 2025 (TrueHD Atmos).mkv.MediaInfo.txt

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

Sorry. I thought I had attached the full file. embyserver.txt

Since your files are already consistently named (no rename involved in what you're testing), the simplest safety net is backing up Emby's own database before you try Restore - if anything looks wrong afterward, you roll the whole thing back in one move. 1. Back up the database: sudo synopkg stop EmbyServer # or however you stop your Emby install cp /var/packages/EmbyServer/var/data/library.db /var/packages/EmbyServer/var/data/library.db.bak sudo synopkg start EmbyServer (Path varies by platform - Docker installs usually have it under your mapped /config/data/library.db; native Windows/Linux installs keep it under Emby's ProgramData/data folder.) 2. Run the plugin's Restore task and check the results. (I use Chapter API, and preferably copy the intro summary table into an Excel worksheet.) Don't forget: if you don't run any backup task, and don't edit any marker via any plugin (ChapterApi, Credits Detector, Segment Reporting), your NFO files stay untouched. If any compensable data lost; edit/add/delete them manually. And let the plugin auto-restore the adjustments. 3. If something's wrong, roll back: sudo synopkg stop EmbyServer rm /var/packages/EmbyServer/var/data/library.db mv /var/packages/EmbyServer/var/data/library.db.bak /var/packages/EmbyServer/var/data/library.db sudo synopkg start EmbyServer That puts the database back exactly as it was before the test - since no files were renamed in between, there's no mismatch between what the database expects and what's actually on disk, so this is a clean, complete rollback.

Hi, yes more options are planned for future updates. Thanks.

Hi, thanks again for the detailed logs — that helped a lot. Cause TrailerTheme needs 64-bit VLC for the embedded trailer preview. Without it (or with a manually copied mismatched libvlc.dll), older builds could crash on startup (libvlc.dll / WinError 193). Workaround (still valid) Install the full 64-bit VLC from https://www.videolan.org/vlc/ Do not copy single DLLs into the TrailerTheme folder Restart once, then start TrailerTheme again Update available: 1.0.9 Please update to 1.0.9. When you open the app, you should get an in-app update prompt; or download here: https://github.com/Gembird79/TrailerTheme-Releases/releases/tag/v1.0.9 What’s fixed in 1.0.9: App starts even without VLC (trailer preview uses a Qt fallback) With 64-bit VLC installed, the normal VLC preview works as before Path dialog no longer freezes if the NAS/server is still asleep Please let me know if 1.0.9 starts cleanly on your Win11 25H2 system. Thanks! Gembird79