Not to mention how any subtitles will probably be lost too. 422? 444? Hi10? Predictive? Yep this won't work.
Level > 4.2? This is getting a lot less likely. H.264 main? Probably also very widely supported now. This depends entirely on the used level and profile of AVC. The latter format does not need to be re-encoded to cast it to chromecast devices. mp4 contains only AVC with AAC, it gets a bit hairier because there is a lot to AVC It does not automatically imply AVC+AAC, but AVC+AAC is a popular choice for it. I'm assuming by putting avc+aac in parenthesis, you mean to say that this implies those codecs. The MPEG-4 you're referring to is a container.
If you're going to lecture multimedia developers about multimedia you should probably not do it like this. There is also a desktop emulator called leapcast, which may be useful too. If you have an Android phone or tablet, you can turn it into a Chromecast for free with an app called CheapCast without the need of any whitelisting. The official Chromecast SDK is still in Developer Preview and to use a custom Sender App you need to whitelist your device. Quick digression about requirement of having dedicated device, if someone wants to play with it anyway: Perhaps we should just go with a separate tool such as Fling and drop the idea of supporting DIAL inside of mpv? I wonder how complex would it be to implement all these moving parts inside of mpv and to be as easy to use as selecting just another video output driver: -vo dial:cast-device-name
For example Fling project provides a way of casting local (optionally transcoded) video to a DIAL device with a help of. To make it work Sender needs to act as a HTTP server (and optionally a transcoder, if Receiver does not support codec etc). plays it on its own from URL via simple HTTP GET. My high-level/simplified understanding of what happens after DIAL discovery is that Sender (mpv) posts URL to Receiver (cast-enabled device) via RAMP. Projects at github more or less reverse-engineered it, as people were too anxious to wait for official documentation, which I hope will be published after Developer Preview period. I did some research and there is an additional layer called RAMP, which is not documented well.
0 kommentar(er)
