I added some extended console logging around ac3/eac3 and did some tests. I bought the developer console (it was just 5 dollars so I thought it wasn't that bad but I agree with you) and set up a local server for the receiver. If they did, the server is the place I think it would be appropriate to push those logs. It's really annoying but I don't think web browsers have any easy facilities for redirecting those logs. Doing so will let you connect to the receiver and read those logs. I'm hoping that this will either prove my hypothesis that CAF behaves really badly, or it will help uncover problems that cause CAF to underperform in this app.Īs for logs, I'm blaming google because all the logging is done to the console since it's a web browser, and you have to pay them for access to the developer console where you can register a testing app. I'm working on backporting to the old receiver API to be able to compare how they perform. It was decided that mkv would no longer be sent to the device because the device only supports the webm subset and this may work or fail based on luck with a particular file. So in this regard I don't think getDeviceProfile will do anything differently. It returns true when the equipment supports it or if it's set to force it on. Secondly I have verified that this check returns false if the chromecast is in stereo only mode, or if it's in auto but it did not detect ac3-capable equipment. Firstly, the API documentation encourages developers to specifically use this check before playing back ac3/eac3 content. Which brings me to my testing with canDisplayType. Chromecast is supposed to support mp4, so I assume fmp4 is okay.Īs for the sound, I have an issue open with google because the chromecast somehow always errors out on ac3/eac3, even when the system supports it. Any PR to enable fmp4 support would be appreciated I think. fmp4 is apparently the way to go to get HEVC, although it will still remux. To be continued.Īt the moment the chromecast only really advertises HLS. I am currently struggling with not being able to select an other audio stream than default/main. I have also added a mkv profile for direct play and I have no problem with that itself so far. You can check the TV dolby support with context.getDeviceCapabilities(), and you can also force enable dolby passthough on the chromecast in Google Home Chromecast settings (which will result in no audio if instead of ERROR which TV lacking dolby support). Since only AC3 passthrough is supported by some chromecast models, the cast will fail when passthrough is happening and the TV cant receive it. castContext.canDisplayType('video/mp4', 'ac-3'), which was used to check if AC3 was supported only checks that the chromecast itself has support for it and not if the TV has it. My findings so far is that AC3 is hard-disabled with a comment that it did not work on some setup and therefore disabled. I am currently testing with the receiver code which I have managed to setup in a debug environement using a chromecast ultra. I have most of my 4k movies in mkv container and AC3 audio, which is common I guess, which makes this annoying. : Profile: "Unknown Profile", No video direct play profiles found for "/data/media/movies/The Prestige (2006)/movie.mkv" with codec "hevc"Īfter some more investigation, it seem to be ac3 and mkv that is not allowed by chromecast receiver and thus forcing the server to transcode if content have any of this. Connect to Chromecast Ultra in Chrome or Android app.ĭirect replay or direct stream (don't know the difference) and no transcoding.System (please complete the following information): Web-browser built-in player and Chromecast always "fail" for me. The only player I have successfully getting hevc direct playback to work with is jellyfin-mpv-shim. Is there a workaround for this? Can I somehow try configure my way around this? I have not found any guide on how this works. It looks like hevc isn't in the "playback profile" jellyfin use when casting to Chromecast Ultra. I only have mkv movies to try with but I have read it should not be a problem if the codec is correct on streams inside it. Problem is Jellyfin always starts to transcode the movie anyway. Chomecast Ultra should support hevc and aac so I have converted some 4K movies to that since my server isn't a monster and would like to direct play these large movies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |