All Activity

Also, 1.2.1 followed it the same day with two fixes for when you're not on your own LAN: servers reachable only over a VPN (Tailscale, WireGuard) on plain HTTP now connect — an App Transport Security mistake on my side that had been there since 1.0 — and casting no longer stalls at 0:00 when your phone isn't on the same network as your server.

@Luke Did you see this? I answered quite a while after your question, and I wouldn't want it missed

The VPN issue. Correct: 1.2.0 doesn't have that fix. I found the cause on Sunday and it wasn't where I expected. The app carried two conflicting App Transport Security keys in its config, and on iOS the "local network" exception silently cancels out the "allow plain HTTP" one — so the app could only reach http:// servers inside the classic private ranges (192.168.x, 10.x, 172.16.x). Tailscale hands out addresses in 100.64.0.0/10, which isn't one of them, so iOS blocked the connection before it ever left the phone — and the app just said "couldn't connect to the server", which is why it looked like a server problem when it wasn't. Same story for WireGuard/ZeroTier. It's fixed in 1.2.1, submitted to Apple today, and the error message now names the real cause instead of being generic. 1.2.1 also fixes casting when your phone isn't on the same network as your server — worth knowing if you combine Tailscale and speakers. HomePods. Your read is exactly right. The button in the app is Embeat Connect, which is DLNA/UPnP casting: Sonos, WiiM, network streamers, many AV receivers and TVs. HomePods don't speak DLNA at all — they're AirPlay only — so they'll never appear in that list. You can still play to them today, just through iOS rather than through the app: start playback in Embeat, open Control Center (swipe down from the top-right), tap the AirPlay icon on the audio card, and pick your HomePod. Everything the phone plays goes there, Embeat included. The practical difference between the two: AirPlay — the phone does the work and streams the audio to the speaker. Your phone has to stay on the network and in range; walk out and the music stops. Great for HomePods and Apple TV. Embeat Connect — a real handoff. The speaker fetches the music from your Emby/Jellyfin server directly, and the phone becomes just a remote: play/pause, volume, seek. Lock the phone, take a call, walk out of the room — the music keeps going. (One exception: with Sonos and hi-res files the phone does help out mid-stream, so it stays involved there.) Both devices need to be on the same local network. So: HomePods and Apple TV → AirPlay from Control Center. Sonos and DLNA gear → the Connect button in the app. If you ever do add a DLNA device and the list stays empty, check that Embeat has Local Network permission in iOS Settings — that's the usual culprit. I've noted the idea of putting the system AirPlay picker right next to the Connect list, so you wouldn't have to leave the app for HomePods. Thanks for the report — the VPN one was genuinely useful.

Trying out the app today on my local network while waiting for the update to test again with tailscale. (I assume version 1.2.0 doesn't include that update) I am trying to get it to connect with my homepods but it never finds any device to connect to when hit the cast to button. Per the website it looks like perhaps that isn't implemented? I see you can connect to Sonos or any DLNA device. Looks like it connects to homepods via airplay. (sorry, not too tech savvy in some areas).

Yes even if remote.

Just wanted to vote for this and then I saw that I already did last year. Damn.

Even if the device is remote? …will try that, thanks?

HI, i would try setting up your trakt authentication again and see if that helps.

Hello Since 2 weeks, Trakt does not sync anymore the new items I have in my library, nor the one I watched. I run on Emby Beta version 4.10.0.22 and trakt version 3.8.10.0 I tried to remove and reinstall the plug-in but no change I've attached my server log where some trakts error are Thanks in advance for your help embyserver.txt

It looks like there might be something in the server limiting it to 44100, however that is not easily removed right now. It was likely done to solve problems, so it can only be removed at a time when we're ready to deal with the consequences of making the change.

This is contradictory to your previous reports because you had been saying that it was never attempting to transocde at all.

There is an EstimateContentLength param you could try.

Yes but when you enter the imdb id, it is only used to lookup on moviedb, not to go directly to imdb.

If anything, I find the target bit rate is a bit low. MP3 is 192kbs, AAC is 192kbps, EAC3 is 384kbp. Is there any reason to keep it that low?

Hi, in many cases yes you can start playback on another device using the cast feature. Try opening the web app and clicking the cast icon in the upper right.

Sorry, I'm not sure what you're asking?

Playlists are an Emby library.

Just tested and I can confirm that it's a bug - or rather: it was intended to but never got implemented.

You need to install the iso mounter plugin from the emby plugin catalog. then once you have that, then restart the server and refresh metadata on existing iso files. When that completes, try again.

Sometimes the files just have a year or a whole date, and I just wrap that in parentheses and it seems to work. I archive a lot of recordings of live gigs. It doesn't have to be only the numbers in the parentheses, there can be letters too in my experience. If there is a 4 digit number than can be interpreted as a year within the parentheses, Emby will pick that up as the year of the video.

Glad it saves some headaches.

Great plugin, thanks for sharing it!

UPDATE: Rebuilt from the ground up again. So far, early indications are looking good, just a few more bugs to iron out. One of the biggest changes: the Air Date fixer is no longer tied to Emby 4.9.5.0. Currently testing with 4.10.0.22 beta.

Sorry for the confusion. I somehow combined the answers via the mobile chrome from multiple threads into one.

Nice... but I still don't see the new update in Playstore?