Originally Posted by davboc
perfect explanation! Really thank you. I hope that this device will be supported with the right software, meaning apps, in the near future.
The problem right now seems to be that every App creates their own CCast Player App (called the receiver) but the DIAL protocol really doesn't require that to happen.
If the Open Source community would create a FREE TO USE Player App for CCast that any Android (or iOS app for that matter) could have the CCast load You might see a situation where all players could use that app to play to CCast and remove the need to code a Player themselves.
The only reason to code your own player then would be if you wanted to add other features like Media Info Mirroring and if the Player was Open Source it could be used inside their custom versions as well provided there is no issue with GPL license and Commercial Use.
the CCast support has come a long way since December...
I hope by next December we see more after people figure it out better.
The holdup is Google Locking it all up with the Whitelist.
I keep looking here hoping to find a developer that has decided to work on a CCast Player side to bring full client side support that others can use.
So Far Bubble is the only one focused on that side of the coding.
In the end the CCast player should support any container, Most Codecs, Client side selectable Subtitles and Multitrack Audio with Client side selection as well.
If they could add Dolby Support (not likely given the Licensing requirements) it would set the bar for all the others.