All Activity

That's correct. In the past when the Google screensaver kicked in, it would show the song name at the bottom left corner while Emby was playing.

Hi, we are working on improving this. Thanks.

So you're referring to a system screensaver and not an Emby one?

OK we are looking into it. Thanks.

I don't have an update on remembering playback speed, but the button has been made quicker to get to in some layouts.

Btw, I only have a very few songs in aif. Maybe I should just convert it?

you could check the server dashboard during the aif playback.

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

Hi, I think we need to look at improving resiliency to network disruptions. I think it has more to do with that than transcoding vs not transcoding.

Not sure what you mean. What should I look for?

HI, yes I think the tv app is probably having the aif transcode, right?

Im already using Emby 4.10.0.28 beta. The only difference to previous versions is that I now get a pop-up error message.

@Grumpy1 When you asked what triggers Dolby Vision, the honest answer was that Atrium didn't signal it, and I said I wouldn't put a date on it: I don't own a Dolby Vision TV, and shipping signalling I can't test is how you end up with a red screen in someone else's living room. That part hasn't changed. The rest has: it's written, and version 1.4 is in review now. None of it was deduced from the spec — it's copied from a real master playlist for the same file. The base-layer codec stays where it is and the Dolby Vision goes beside it, in SUPPLEMENTAL-CODECS. Atrium copies the DV configuration box out of your file byte for byte and derives the tag from that box, not from what any server claims about the file. Three things make it safe to send out untested: - It only happens if your TV announces Dolby Vision. On any other TV the output is byte for byte what it was before, and there's a test that keeps it that way. - If playback fails with DV signalled, the app redoes it without. You keep on-device playback and you keep HDR10 — the worst case is a blink, not a broken picture. - The new Playback Information screen says, in words, what actually happened. So here's the favour, whenever 1.4 reaches you. Play one of your Dolby Vision files, open Settings > Playback Information, and read the Dolby Vision line. It says one of: - "in the file and signalled to the TV" — this is the one I need to hear about. Does your TV actually switch into Dolby Vision, with its own indicator lit? - "in the file, not signalled — this TV doesn't announce Dolby Vision" - "in the file, not signalled — its base layer is neither HDR10 nor HLG" — a file I deliberately don't tag, because the servers don't tag those either - "signalled, then withdrawn" — it was tried and playback failed. I'd very much like to see this one, and I'd like to see it before anyone else does. Two kinds of file won't get you any of that, so you don't waste an evening on them: profile 5 (the ones with no HDR10 base layer) now go to the server on purpose — prepared on the device, their colours came out wrong — and dual-layer files aren't tagged. A photo of that screen is worth more than anything I can measure here, and both answers are useful: "it lit up" closes this, "it didn't" tells me where to look next. Post it here. And the other half of what you asked for is in the same version: the details page now shows resolution and dynamic range, with Dolby Vision taking precedence over its own base layer. I'll post here when it's out.

@Luke

HI, our beta package has a permissions fix for TOS 7. Thanks.

To resolve what? The empty genres are resolved n the upcoming 4.10 server release.

Just updated and tested the newest of each... Android 3.5.51 fails Android TV 2.1.55g works

The best way for dealing with large playlists in the WebStreams plugin is to add the same M3U multiple times, each with a different set of filters.

How does it behave when you explicitly stop playback (by going back)? Do you have "Play video in background" enabled in playback settings?

In the mean time to how do I fix this? Do I need to remove all my media and readd it?

I sent you a message, please respond to the email in that message. Thank you, Marvin

This may be of some help my isp started to use cgnat and after asking for help they told me to use ipv6 and now I connect to emby using ipv6 address

As of now, I have latest version of TOS 7 and the latest beta of Emby installed. I still cannot build any libraries in Emby as I get the following message when selecting the HDDs Access to the path '/Volume1/@disk/Externaldrive_sdb2' is denied. Any help would be appreciated.

Hi, yes it's due to the older server version that you're not seeing the update.

I'm having a couple of problems playing back Music on my Sony TV with the Emby Android & Android TV apps. I've tried both apps and on each certain files won't play. Note: All files play in the browser. For years, I've been using what I just discovered is the old Emby App for Android TV, version 2.1.55g and was puzzled that it never seems to update! From reading posts in this Forum Category I today discovered there was a newer Emby App for Android, version 3.5.36 version as well. I put together a playlist consisting of 3 different file types. Here are the results Android TV 2.1.55g (Note: the old app never detected the new playlist, even after TV reboot) .aif - plays ok .m4a - Appears to play (bars animating, time advancing) but no audio. .mp3 - plays ok Android 3.5.36 .aif - won't play. It starts and immediately advances to the next song. I have a playlist with 3 tracks and it goes through each. .m4a - plays ok .mp3 - plays ok Is there some setting I can set either in the app or on the server to fix this? It's frustrating that I have a playlist that can't play on either client app! Log file attached. markand_20260828_embyserver.txt.zip