Search the Community

Hi, I am out of ideas. I can cast to my chromecast from the Emby mobile app, either from ipad or iphone. On PC and Mac, in Google Chrome (updated and it is not a dev version) the chromecast doesn't show up in the list of devices. On the same PC or Mac, I can cast to my chromecast from youtube or any castable website. In the Chrome's menu I can cast to my chromecast, but notbfrom within Emby web app. I am not using a VPN. My server is not located on the local network, I access it through internet usual port. Suggestions much welcome as I am new in the Chromecast world. Cheers.

I have a google home speaker that I added the emby functionality too and added the proper linking too. One issue I face is it isn't seeing my chromecast as a player where i'd like it to be default is there someway to remedy that?

Hi folks. I have downloaded a couple of files to my surface pro 3 so that I can watch them when I'm away from home. I am unable to stream them from home via my phones hotspot due to plan limitations. In my holiday house I have a chromecast set up on the TV and it connects to my phone hotspot as does my surface pro 3. I would like to be able to playback the downloaded files on the Chromecast using Emby UWP or Emby Theater desktop, but they do not give me the option of using the chromecast as a playback device. For comparison, VLC has no problem with this scenario. Thanks Jordy

I've noticed that both my Chromecast v2 and Ultra are happy to direct play multi-channel audio encoded using either Dolby Digital (AC3) or Dolby Digital Plus (EAC3). Anything else (Dolby True HD, Atmos, DTS, DTS-MA, DTS-X) gets transcoded to Dolby Digital at 384 kbit/s. I'm very impressed with the way Emby handles this - it's even smart enough to transcode EAC3 to AC3 when I turn off the AV receiver (and it's just the TV doing the audio decoding). I'm less impressed that it needs to do this at all for the Chromecast Ultra: why do Google think it's OK to market it as 4K HRD capable and yet only support these two codecs? It's particularly bad when DTS gets transcoded to AC3 (one lossy early 90s format to another). Dolby claim that DD+ is up to twice as efficient as old DD and Netflix are now streaming in DD+ at 640 kbit/s ("the point at which additional quality is imperceivable"). I decided to experiment using Emby's version of ffmpeg on my Synology NAS (a DS918+ running a Celeron J3455). DTS to AC3 at 384k vs. DTS to EAC3 at 640k. I had to set avoid_negative_ts to its default value of "auto" for the EAC3 transcode - Chromecast won't direct play EAC3 streams with negative timestamps. I was concerned that the EAC3 conversion might require more CPU time, but if anything it's faster. The conversion logs are attached. I won't claim to have the best equipment or ears (MP3 at 320k is fine by me), but I can hear the difference. The Mad Men opening theme (test file I used) sounds better to me in the EAC3 version, particularly the cymbals. What do the Emby developers think about transcoding to EAC3 at 640k when it's supported by the playback device? An easy win for better audio quality, or just another wild idea from a clueless audiophile? AC3_transcode.txt EAC3_transcode.txt

Hi! I am running an emby server on a remote machine that is behind Cloudflare. Everything works fine until I try to cast to a chromecast device from my android app. The app connects to the chromecast, the chromecast says "ready to cast" but when I click play nothing happens. I went through the chromecast's logs and found that the it receives the LAN instead of the WAN address: 127.29.0.2 is the local address in the docker container and the address that is displayed as LAN address in the dashboard. I censored my ids with XXXXX, as I don't know if they could be somehow abused. Casting works fine when I use emby web with Google Chrome, so it seems to be a problem exclusive to the android app (I cannot try iOS). My remote address is configured correctly and shows as https://emby.domain.com:443 in the dashboard. Is there anything I could do? Does anyone have the same problem?

For inf, I have solved an issue with .ts format files recorded from broadcasts and saved on a NAS, played through emby on a Windows 10 pc to a chromecast. I set up hardware acceleration using an Nvidia card but only direct play happened, which stuttered and then failed. Solution was to transfer files and library pointers to the pc, after which the Nvidia kicked in. Hope that helps someone. Much better for recording than Plex, btw.

so using chrome-cast is just a tad buggy. when starting a video it will load and start to play. but when you try to seek thats when it starts to get kind of buggy. it will just not seek whatsoever and the seek bar will bounce back the 00:00 spot and not even progress the video. im on the latest OS of android and the latest version of the emby app.

Hi all, Hopefully someone has experienced the below and knows how to fix it - or it's a bug that can be fixed! Specs: Emby Server 4.1.1.0 running on Windows Server 2016 Chromecast Gen1 running latest firmware Chromecast Gen2 running latest firmware Samsung Galaxy A50 running Android 9 and the latest Emby Android app iPhone 6 running latest iOS and the latest Emby iOS app All devices are connected to the same router/access point and are being accessed over the local network Emby is working fine when playing off of any of the mobile devices, and it works from any device when casting to the Chromecast Gen1, however when trying to cast to the Chromecast Gen2 it brings up the splash screen 'Welcome to Emby - Select Emby Media from your device' - then when pressing play on any media it simply does nothing, when disconnecting from Chromecast and playing the same media on the phone - or on the other Chromecast - it works fine This wasn't caused by the 4.1.1.0 upgrade as it definitely worked after that, but I can't be sure exactly when it started. I found the following from my logs around the time I try to play to the Chromecast: 2019-05-29 23:13:18.848 Error PortMapper: Error creating port map *** Error Report *** Version: 4.1.1.0 Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\EmbyServer.dll -service Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Runtime: file:///C:/Users/Administrator/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll Processor count: 4 Program data path: C:\Users\Administrator\AppData\Roaming\Emby-Server Application directory: C:\Users\Administrator\AppData\Roaming\Emby-Server\system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: InternalServerError at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at Mono.Nat.Upnp.UpnpNatDevice.CreatePortMap(Mapping mapping) at Emby.PortMapper.ExternalPortForwarding.CreateRules(INatDevice device) Source: Emby.Server.Implementations TargetSite: Void MoveNext() Any help or advice is appreciated - pretty much ripping my hair out trying to figure out why it's not working! Thanks

Hi, I'm trying to cast Emby to my chromecast by I can't. My configuration: Sever: Latest Docker container on Linux Alpine as host. The server uses a SSL certificate generate automatically using Traefik. Emby server version: 4.3.0.26 Clients: Android Phone Sony XZ Premium (and others devices) My server is at home and until now I've never had a problem with Emby, I can use it locally with my Nvidia Shield, Android Phone, iPhone, MacBook Pro, etc etc. Also outside my apartment, everything works perfectly, I can stream and trans-code without any problem. Today I've installed a Chromecast first gen in my bedroom, I opened my Android app, pushed the button cast, the Cromecast changed to Emby (ready to cast) and when I went to push play on my phone the button didn't do anything, it seemed like disabled. So I've disconnected the chromecast from my phone, I played something, it was working perfectly, so I've tried to enable the cast during when it was already on play. Same thing happened. The chromecast went to Ready to cast, but the app on my phone stopped to work and it went to a grey screen. Screenshot: https://ibb.co/4R9xD3t I've also try the same steps with an iPhone and I got the same results. I've tried to cast with my laptops (Linux and MacOS) using Google Chrome, but my chromecast doesn't appear in the list: Screenshot: http://i.imgur.com/KdtQ4PZ.png It should appear there and also my Nvidia Shield. I can see just my browser and the phones. I've tried to cast Netflix and Youtube and they work perfectly. I've also tried to reduce the video quality from my phone configuration, to 720p Screenshot: https://ibb.co/QcLJQCR I've checked also the logs, but I didn't find anything weird inside, just some socket Error Any idea if it is a bug or something that I should fix? Thanks H2K

I'm coming away from Windows media centre and am finally sellting on Emby as a replacment over plex. One thing I was holding onto was an ageing xbox 360 in the bedroom, I was hoping to still use it with a client app. Plex have one, though it is well out of date and emby only exists as a plugin for media centre, which I am replacing. So I have decided to bite the bullet and get rid of the 360 and replace it with a streaming stick, but which one is best out of Fire TV or Chromecast? Which will be more 'future proof'? Has someone used the apps from Plex and Emby on both, how do they compare? Cheers for any input!

When casting movies to Chromecast, the following steps are shown: 1) fanart picture is displayed by Chromecast; 2) fanart picture is dismissed 3) film logo is displayed on top left and film cover is displayed on bottom right. 4) actual film is displayed 5) film logo and cover are dismissed When casting movies (mkvs) with embedded subtitles (srt) what occurs is: 1) fanart picture is displayed by Chromecast; 2) actual film is displayed 3) playing continues keeping fanart picture on upper and bottom where movie has no image to show. So, movie is exhibited over the fanart

- As legendas de muitos arquivos não estão funcionando no Chromecast mesmo quando ativadas (Simplesmente não aparecem na TV). - Porem as legendas aparecem normalmente caso eu esteja assistindo pelo navegador do computador ou pelo smartphone. https://www.youtube.com/watch?v=_KjrLBcm_94&list=PLqT7uGeErdaur_nY-O0raKvRgHddzMEKp&index=8&t=0s Exemplo de arquivo (Download): https://mega.nz/#!TZ0hRCBJ!T6uYjOzdCeJOhtaLq0FfDAObQo9VeRW2kO7eYQLFFcE

I have read as many of the related topics I could find but the answers did not help. A short time ago, all of my X265 encoded videos stopped casting to Chromecast. After selecting the Chromecast, and pressing play, it appears to start, then goes back to "Ready to Cast". I have tried Android app, iOS app, and browser app. I tried reducing the quality in the app settings (Playback>>Chromecast Streaming Quality) to no avail. I have tried several movies and the only ones that cannot play are X265. These videos were playing fine until recently (was there an upgrade to the server?). Have others experienced this? Emby Server: Version 4.0.3.0 Chromecast, 1st Generation Chromecast firmware: 1.32.144770 Emby for Chromecast 2.1.0 Emby for Android Mobile 3.0.42 I do not mind upgrading my Chromecast, but was hoping we could troubleshoot and understand the issue, as it just started happening recently. I have attached the video specs of one of the movies I have been trying to play (tried 10+ this morning to troubleshoot). I have also attached the transcoding log of one of the failures. I did edit the file for "THE NAME WAS CHANGED TO PROTECT THE INNOCENT". Any help? ffmpeg-transcode-8009045a-52ca-43d3-bb7f-ffc476c922e3_1.txt

I recently converted all my symlinks to hardlinks because I read in another thread that symlinks are problematic. That seems to have helped with videos playing reliably on my phone itself. However, some videos don't want to cast to my chromecast devices. I get the spinner on my TV, then I get the player controls at the bottom of the Emby app, but after about a second both go away and the picture for the video. It's not obvious to me from looking at the log file what the problem is however I see that ffmpeg quits after maybe a half second. I restarted the server, turned on debug logging, and then performed my test in order to capture full detail but not more than necessary. The log is attached. 2 questions: Why is it failing and how do I fix it? Why is it trying to transcode? It's not a high bandwidth file. Does chromecast require a fixed resolution like 1080p in order to avoid transcoding? Log.txt

I wanted to ask about an issue I am having with casting to a Chromecast through LG G6 phone (using baconfeet server). The app works great to search for content, but when it comes to playing over casting it breaks. I have played shows and movies directly on my phone with no issues. However when I try to watch content through casting to chromecast I let my phone turns it's screen off like a normal casting, but after a few moments it shows the "ready to cast your media" and the content I am playing goes back to the beginning. More specifically; cast media button = (on tv screen) ready to cast your media" push the play button to play content and it starts playing set phone down and enjoy content sometime later (within 5 minutes sometimes less) the video stops and "ready to cast your media" comes up on TV turn on phone and screen in black with "--:--" where the time of video playback is Please advise as to a solution or remedy. I am running on the last update from April 22 and still having this issue. Thank you for your time.

Hello, Anyone know how I could change the subtitle position in chromecast? Its fine in the web client, but in chromecast its too high for my taste.

I noticed that the Emby Android app is not using the Chromecast volume gain, but is instead doing its own, resulting in the total gain = gain(Chromecast) * gain(Emby). For example, If I go to the Home app, and lower the volume to 0, emby won't play at all. So the Chromecast volume has to be 100% to behave correctly. This becomes kind of tedious if you use chromecast on more than one app: you have to set the gain in that other app to 100% before disconnecting and connecting with Emby.

I'm having a little display problem while playing my IPTV to the Chromecast. The IPTV source is a M3U file with udpxy links, so the IPTV source is an HTTP video. Maybe it's a ffmpeg parameters issue (maybe I don't really know). Transcoding log attached and picture of the result while playing on the TV (sound works ok). EDIT: I've tried multiple TV's, and the same happens. Log.txt

I run about a half dozen Chromecast devices on my (switched) network. One Ultra, three Audio, one built-in (Sony Bravia), and three Home. Each and every one of these devices shows up twice in the Cast device picker. And more often than not, picking a device does not work, sometimes even trying both "instances" of the same device. Only quitting the Emby app, and restarting it will fix the connection issue, but not the duplicate device one. This could be due to my running Android Pie (Pixel 2xl), but anyhow is something that ought to be addressed. Anyone else experiencing this problem? BTW, it does not occur with any other cast-enabled devices. Thanks!

There is an issue when casting and wanting to fine-control media. When you first cast an item you have a lot of controls available and can skip ahead or jump back 30/10 or whatever your setting is. Once you view the queue or leave the app and re-open you don't have this option anymore and cannot get it back without stopping the item playing on your device and beginning cast again. Two screenshots show one set of controls then the more useless set of controls when in casting. The horizontal one are the controls you get to keep right when you cast. The vertical are the less useful controls. Ideally you'd get the same set of controls you have when you are locally playing in cast mode whether leaving or rejoining the app. Also a fun bug when you swipe out of the app once you are casting at first it can accidentally turn up the tv volume to 100.

Everything works fine when using direct play, when transcoding for whatever reason, be it bitrate, video container or whatever, video starts playing, after few seconds it freezes. The receiver itself is responsive and I'm able to start playing a different video after a freeze. General flow when starting the chromecast is as follows: - Receiver asks initially for a low bitrate video - Playback freezes after a few seconds cause transcoding is enabled to lower bitrate - After the freeze, I select the movie again and send it to the Chromecast - This time the receiver doesn't ask for a lower bitrate of the video, direct play is selected and the video plays fine all the way through That's for files which don't need transcoding, for files which can't use direct play I'm not able to go past a few seconds no matter what I do. Transcoding works perfectly fine in the web app in Firefox and Chrome. The Android app also works fine. There's nothing interesting in the server's logs, I can add them if you need them though, ffmpeg's logs also look normal. The only messages the web app is getting from the receiver are regular progress events, which just send periodically the time which chromecast is stuck at. When looking in the admin panel you can see the activity indicator showing the movie being played, with the playtime moving forward and then periodically moving back to the time Chromecast is stuck at, e.g: 00:04 00:05 00:06 00:04 00:05 I'm unable to debug the receiver as my device isn't whitelisted, that'd certainly help with this situation. This issue only started recently, a month ago, maybe two months ago or something. Before that, chromecast was working perfectly without any issues. Emby server version is 4.1.1.0, it's available on the internet, I can provide access to Emby devs if necessary.

every time I try to broadcast my chromecast channels I can only hear the audio but no image, my emby is runing on windows 7 all updated and chromecast on wifi 5ghz, and sorry about the bad English

Maybe someone could help me. I'm using the emby since july to watch some Anime and i never have problem with the emby but now I'm having some problems with playback on chromecast gen 2, I start play one video and everything seems work fine but after some time the subtitle start freeze and stop play but the video still keep running. Even playing videos than I already watched happen this problem This issue start happening since my Emby server update to the stable version "4.0.2.0" and only happen on chromecast, I already try update my server to the beta version " now I" m running on version 4.1.0.11" but the problem is there, I buy a new router to see if make any difference but still happening, I already install the Emby Server in another PC more powerful but this too dont solve my problem. Here is information of one of the media than already play and is having problems.and the last server log.. P.S the server dont produce transcode log cause that video play directy I dont know if here is the right place to post this but i really need help. embyserver-63687600000.txt

Hello all, I have Emby server 3.1.1.0 installed through the Docker package. Everything works smoothly, except when I try to stream on my chromecast (tries chromecast v1 and v2). The media just won't start after hitting the play button. No error message. This happens from Chrome (Linux or Windows), and also the Android app. The hard thing is that no entry is created in the ffmpeg logs, so I don't really have additional inputs to provide to help solving the issue, unless you have any idea. Never had this kind of problem with Emby server <3.1.1.0.

Hello emby community, a few weeks ago, I was trying to connect to my chromecast 2 wired to my router via the "official micro usb to LAN adapter" from google, but I couldn't find my chromecast within the emby iOS App. Strangely I was able to find my chromecast within the YouTube iOS App. Then I set up some port forwards in my router to my chromecast, which I found online... (ports: 1900, 5353, 8008, 8009). This didn't help either... Then I tried to connect via WiFi, which immediatly worked. I also reseted my chromecast to default and even tried all this with my older (also reseted) chromecast 1, where it didn't work either, so the issue must be with the Emby iOS app. Connecting my iOS device to my chromecast with LAN worked a few weeks ago (but with problems too...) but now it doesn't work anymore. Did anyone notice this issue too or what can I do to connect my iPhone to my Chromecast via LAN again? Could this issue maybe come with an Emby iOS App Update? Regards Jones