Related
I been testing videos in MKV through chromecast and is totally awesome. Excellent quality video, really fast.. Working great. But i cant see subtitles. Even if they come with the video or apart. Is there any way?
I forgot. Mkv using Avia player.
Enviado desde mi XT1058 mediante Tapatalk
gueszman said:
I been testing videos in MKV through chromecast and is totally awesome. Excellent quality video, really fast.. Working great. But i cant see subtitles. Even if they come with the video or apart. Is there any way?
I forgot. Mkv using Avia player.
Click to expand...
Click to collapse
May change (it seems they've actively adding/changing things) but as of a day or two ago, Avia's FAQ says this is not supported. There is a note about DLNA, if the subtitle file is already on the receiving device, and I have no clue if/how that would work for Chromecast, especially since Chromecast is not (yet) a DLNA receiver.
Subtitles are usually rendered on the Player side either from within the stream or via external file like a .srt.
I don't think CCast can ever fully support external .srt since it has no real filesystem of it's own to load the file from.
But the player app could be coded to show subs that are encoded into an MKV or other container that supports embedded SubTitles.
It might be possible that some sources could encode external SRTs into a stream going to a CCast which would probably be what aVia is doing.
Not sure if Plex does this at all since all of my content that requires Subs has been hardcoded into the video by me when encoded for storage on my server.
Plex does however seem to support putting subs into it's transcoded files if the Transcode profile definition is being read correctly by me...
Not sure if that feature is supported on their current CCast player app they are using.
I use handbrake to encode all my videos and set the subtitle option to burned in so I can watch subed anime on my chromecast.
Sent from my SM-N900P using XDA Premium HD app
Asphyx said:
But the player app could be coded to show subs that are encoded into an MKV or other container that supports embedded SubTitles.
Click to expand...
Click to collapse
Yup, this seems to be what HBO GO does, unless they have a really precise way of switching Chromecast from one stream to another (possible, that's what streaming media servers do).
I really appreciate the caption support there - makes the late-night viewing much easier, plus my hearing is poor these days.
bhiga said:
Yup, this seems to be what HBO GO does, unless they have a really precise way of switching Chromecast from one stream to another (possible, that's what streaming media servers do).
I really appreciate the caption support there - makes the late-night viewing much easier, plus my hearing is poor these days.
Click to expand...
Click to collapse
It's really the best way to do it...The Text from a subtitle adds little to nothing to the Bitrate of a transferring stream, and Why store two versions when you can send one and let the client side decide to use it or not.
The only reason to use a SRT file is if the Video Container doesn't support an embedded Sub stream that can be shut off or if you need a Subtitle for a language not embedded in the Video container. No way to put every language into one Video file.
At least not yet! LOL
T3CHW0LF said:
I use handbrake to encode all my videos and set the subtitle option to burned in so I can watch subed anime on my chromecast.
Sent from my SM-N900P using XDA Premium HD app
Click to expand...
Click to collapse
I tried handbrake and found it is unable to hard code external srt to my mp4. Am I doing something wrong?
I have tried the divx web plugin for chrome to play mkv but I dont get sound on some videos. I have not tried subtitles. It was also stuck in an install loop. It would ask to update, restart, then ask to update again. Really annoying
Postal Psycho said:
I tried handbrake and found it is unable to hard code external srt to my mp4. Am I doing something wrong?
Click to expand...
Click to collapse
I don't think Handbrake supports hardcoding subs.
It does support adding subtitle tracks but I don't see an option to hardcode subs at all...
I admit though that I don't use Handbrake unless my main converter has an issue with a file...
I use Xilisoft since it supports hardcoding subs and I don't need to have multiple subtitle and audio tracks for my library.
Asphyx said:
I don't think Handbrake supports hardcoding subs.
It does support adding subtitle tracks but I don't see an option to hardcode subs at all...
Click to expand...
Click to collapse
https://trac.handbrake.fr/wiki/Subtitles might help
I understand that the MKV can not see the subtitles .. but within the mp4 subtitles should be visible, Chromcast handles subtitles, do not believe me? look at this Youtube video Coca-Cola Social Media Guard
Put the subtitle to ON, do not you like the look? Click Options and choose the size you want, the color you want and the background color you want.
For example from the BubbleUPnP program should bring the option to turn ON the subtitles in the MP4, etc.
gueszman said:
I been testing videos in MKV through chromecast and is totally awesome. Excellent quality video, really fast.. Working great.
I forgot. Mkv using Avia player.
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
I was under the impression that chromecast doesn't support mkv? I only ask cause my home pc is down, so no plex or bubbleupnp (transcoding) for me. Through Avia app I can only play mp4. Avi, mkv etc. must be converted to mp4. Has something changed or is this still the norm. Sorry for derailing the thread.
Sent from my Nexus 7 using XDA Premium 4 mobile app
mike02466 said:
I was under the impression that chromecast doesn't support mkv?
...
Through Avia app I can only play mp4. Avi, mkv etc. must be converted to mp4.
Click to expand...
Click to collapse
Still the case. The CC end doesn't support MKV so it's up to the player/ source end to unwrap it, determine what to send and transcode if necessary.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
mike02466 said:
I was under the impression that chromecast doesn't support mkv? I only ask cause my home pc is down, so no plex or bubbleupnp (transcoding) for me. Through Avia app I can only play mp4. Avi, mkv etc. must be converted to mp4. Has something changed or is this still the norm. Sorry for derailing the thread.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Chromecast supports MKV natively very well as long as it contains supported codecs.
Thanks for the replies guys. Not gonna have a PC for a while, and I hate being so limited. I'll look for proper codecs til I come into cash for a new pc.
Edit: tried 2 mkv files, codec h264, bitrate was around 3700 and still a no go. Oh well
Sent from my Nexus 5 using XDA Premium 4 mobile app
bubbleguuum said:
Chromecast supports MKV natively very well as long as it contains supported codecs.
Click to expand...
Click to collapse
Lots of confusion about MKV regarding CCast.
I was under the impression that MKV will STREAM on CCast, it won't direct play but it can be streamed to it easily using MPEG-DASH. Because Streaming a file this way pretty much strips the container entirely and just sends Video and Audio tracks in whatever codec was used inside the container. The CCast has no idea it's actually playing an MKV file so if the Codecs are compatible it will have no problem.
There is no device I know of that supports MKV natively though Hardware decoder. All devices that support it have software decoding and other MKV feature support built into the player itself or require Transcoding.
I know Plex is currently transmuxing and streaming MKV to CCast which is why they now work there.
But I'm betting your Bubble player on the CCast side is much better than theirs is as far as handling containers.
So maybe you can direct play codec compatible files where others need to send via DASH.
In the end the best way to handle MKV would be to have the Player handle most of the features so the only time external help is needed is to flip incompatible codecs.
And by features I mean the following:
Client side Subtitle rendering and selection (difficult on CCast with SRT but easier with Internal Subtitle tracks of MKV)
Audio Track selection
Chapter support
At least until Google adds this capability into the next Gen CCast OS.
one way is to convert your mkv software subtitles to mkv hardware subtitles
I believe the MKVToolsNix package has a tool called MKVMERGE that will insert SRT files into an MKV as a subtitle track.
Just be sure to test the external subtitle to be sure it's good before you do or you could make a mess.
This is one of those must have packages for anyone who like to play in the MKV universe.
bubbleguuum said:
Chromecast supports MKV natively very well as long as it contains supported codecs.
Click to expand...
Click to collapse
This.
Videostream extension for chrome supports subtitles.
Just a FYI for all those who have PlexPass...
Plex sent out a Major Release that has many fixes for CCast users including Direct Play (no Transcoding) of MKV/H.264 L4.1/AAC. (PMS Server 0.9.9.5.411 is required.)
They also updated the Plex Android Apps and they now will show movie preview on your TV (I believe it's just posters) while your browsing for movies in Android.
There are many other little perks including better transcoding in general and I haven't had a chance to test most of the new features yet but just wanted to let you know that CCast Playback of MKV without Transcode does appear to be possible with Plex.
Asphyx said:
Just a FYI for all those who have PlexPass...
Plex sent out a Major Release that has many fixes for CCast users including Direct Play (no Transcoding) of MKV/H.264 L4.1/AAC. (PMS Server 0.9.9.5.411 is required.)
They also updated the Plex Android Apps and they now will show movie preview on your TV (I believe it's just posters) while your browsing for movies in Android.
There are many other little perks including better transcoding in general and I haven't had a chance to test most of the new features yet but just wanted to let you know that CCast Playback of MKV without Transcode does appear to be possible with Plex.
Click to expand...
Click to collapse
The latest version of Plex Media Server that I found on their site is 0.9.8.18.290-11b7fdd. Where did you find 0.9.9.5.411?
johnjingle said:
The latest version of Plex Media Server that I found on their site is 0.9.8.18.290-11b7fdd. Where did you find 0.9.9.5.411?
Click to expand...
Click to collapse
Not sure but the announcement is at https://forums.plex.tv/index.php/topic/62832-plex-media-server/?p=586803
Asphyx said:
Just a FYI for all those who have PlexPass...
Plex sent out a Major Release that has many fixes for CCast users including Direct Play (no Transcoding) of MKV/H.264 L4.1/AAC. (PMS Server 0.9.9.5.411 is required.)
They also updated the Plex Android Apps and they now will show movie preview on your TV (I believe it's just posters) while your browsing for movies in Android.
There are many other little perks including better transcoding in general and I haven't had a chance to test most of the new features yet but just wanted to let you know that CCast Playback of MKV without Transcode does appear to be possible with Plex.
Click to expand...
Click to collapse
Per Google - https://developers.google.com/cast/docs/media
With Google Cast you have several options for supporting various media types, codecs, and facilities:
Video codecs: H.264 High Profile Level 4.1, 4.2 and 5, VP8
Audio decoding: HE-AAC, LC-AAC, CELT/Opus, MP3, Vorbis
Image formats: BMP, GIF, JPEG, PNG, WEBP
Containers: MP4, WebM
Containers: MPEG-DASH, SmoothStreaming, HTTP Live Streaming (HLS)
Level 1 DRM support: Widevine, PlayReady
Subtitles:
TTML - Timed Text Markup Language
WebVTT - Web Video Text Tracks
Click to expand...
Click to collapse
So - it certainly looks like the new server is repackaging the supported codec streams into something other than an MKV.
That's an exciting step forward and it may be under Direct Play but are you sure that is the same thing as local casting from your phone?
IOW - does that server run on the Android device or does it require LAN access to a desktop running it?
I confess that lots of Plex still eludes me. I thought that the Plex Media Server was desktop only.
By the way, today's Plex change announcement - https://forums.plex.tv/index.php/topic/60585-plex-for-android/page-3#entry586879
So far as I understand things, it's not transcoding (the codec streams are supported after all) but is still using a desktop computer for transmuxing (because the MKV container is not supported).
EDIT - Vaporware follows:
It would probably be pretty cool if someone were to transmux on the phone and then send things via WebRTC (like tab casting or Koush's mirror for Android). Or to mp4 if WebRTC requires WebM.
Not sure offhand how much work that would be but it wouldn't require a desktop server. And of course would only work with Chromecast-supported codecs.
EarlyMon said:
Not sure but the announcement is at https://forums.plex.tv/index.php/topic/62832-plex-media-server/?p=586803
I didn't have the option to download that because I don't have a Plex Pass subscription. I was really confused until I read that.
Thanks for the info!
Click to expand...
Click to collapse
I updated the web to 2.0.16 and server to 0.9.9.5 all seems OK. I do have a Plex Pass.
johnjingle said:
The latest version of Plex Media Server that I found on their site is 0.9.8.18.290-11b7fdd. Where did you find 0.9.9.5.411?
Click to expand...
Click to collapse
Im still trying to find PMS Server 0.9.9.5.411.. can someone post a link. i am a plexpass member.
---------- Post added at 10:14 PM ---------- Previous post was at 10:06 PM ----------
revdirty said:
Im still trying to find PMS Server 0.9.9.5.411.. can someone post a link. i am a plexpass member.
Click to expand...
Click to collapse
NVM found it.. on the download page u have to click the show plexpass button then go tto the server downloads.
Wonder how long they are going to hang on to cc features. I bought the app but it is seeming like a waste now considering there are other viable well working free options out there.
Sent from my SCH-R970 using Tapatalk
shelby04861 said:
Wonder how long they are going to hang on to cc features. I bought the app but it is seeming like a waste now considering there are other viable well working free options out there.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Really, what other cc app transcodes or plays all files with full seek, ff and rw? I haven't found one. BubbleUPnP doesnt allow you to seek on any transcoded files like mkv. Avia doesnt play most files. Not sure what you are using that can do the same as this for cc.
Sent from my Nexus 10 using Tapatalk
I see your point but I don't transcoded my movies. I keep them all the same format so it is less taxing on my server because I share my server with my family.
Sent from my SCH-R970 using Tapatalk
EarlyMon said:
So - it certainly looks like the new server is repackaging the supported codec streams into something other than an MKV.
That's an exciting step forward and it may be under Direct Play but are you sure that is the same thing as local casting from your phone?
IOW - does that server run on the Android device or does it require LAN access to a desktop running it?
I confess that lots of Plex still eludes me. I thought that the Plex Media Server was desktop only.
Click to expand...
Click to collapse
Phone has nothing to do with it at all other than you can run the Plex app and play all media on the server on the mobile device or send it to the CCast and control it ....Local in this case means Local Networked Media such as DLNA. But Plex will make all your content available to you via the Internet even if your not locally connected.
And yes....PMS does run on a Desktop or Server.
Having Plex removes the need to ever keep content on your phone at all since you can see your home media from anywhere there is Internet Access. It also has a Sync function so you can pre-download media to your device for viewing when Internet is not available.
Plex for all intents and purposes is a Home Cloud Netflix like service that can stream all the content you own.
Direct Play in Plex in the past has simply sent the the file to the device without Transcoding.
I spoke to someone at Plex and it may not be direct playing the file YET but it is perhaps Direct Streaming via HTTP which is a new streaming protocol they added. This might suggest it is only container flipping and only works with files that are Codec compatible. But the Transcode Profile does have an Entry for Direct Play for Matroska container.
Two transcoding profile entries have been added for Matroska
Code:
<VideoProfile protocol="http" container="matroska" codec="h264" audioCodec="aac" context="streaming">
<Setting name="VideoEncodeFlags" value="-x264opts bframes=3:cabac=1" />
</VideoProfile>
and
Code:
<DirectPlayProfiles>
<VideoProfile container="matroska" codec="h264" audioCodec="aac" />
<VideoProfile container="mp4" codec="h264" audioCodec="aac" />
<MusicProfile container="mp4" codec="aac" />
<MusicProfile container="mp3" codec="mp3" />
<PhotoProfile container="jpeg,gif,bmp,png" />
</DirectPlayProfiles>
The Media Types listed on that Google link are what the CCast is capable of decoding via Hardware. That does not mean you can't make a Player App to load on the CCast that can Software decode other types especially other containers where the Codecs are compatible with the hardware. Roku Hardware doesn't natively support Matroska container either it is played via Software decode.
I'm going to assume that the Direct Play entry will not work until the CCast Player can handle the Container via Software. Until then it will use the Streaming Profile. SO it may be setting up the Direct Play profile for something else in the Future.
To all of those who can't find the new version you need to be a Plex Pass Member, Go to Plex.tv, Sign in, Go to Downloads and select show Plex Pass downloads.
On the Android side it's all in the Play Store and the features will be there or not based on your signing into PlexPass
shelby04861 said:
Wonder how long they are going to hang on to cc features. I bought the app but it is seeming like a waste now considering there are other viable well working free options out there.
Click to expand...
Click to collapse
The other options out there (BubbleUPnP and PlayOn being the closest to mirroring what Plex does) do not have all the features Plex does.
Some however have features that Plex does NOT have such as playing content stored on your Mobile device locally. Plex removes the need to ever store content on your mobile device since it works as a Home Cloud for Media available anywhere you have access to the Net.
And while Bubble and others may be able to send ON UNIT content to the CCast it won't do it unless the Source is CCast compatible.
Bubble does have the ability to transcode if the content is coming from the Bubble Server (on the Desktop) but I'm not sure it will transcode ON UNIT LOCAL files when sending to CCast. Perhaps it does but it would require sending the file from your phone to your desktop then sending it to CCast. You should ask the Dev for Bubble to clarify this they post here regularly and are very responsive to their Users. (I have Bubble running myself on the same server as my Plex. and It's a very good alternative for Plex.)
Apps like aVia and Real Player are all very limited to playing content either on a cloud or locally on the the device.
Great if you have everything you want to view locally or synced to the cloud but hardly gives you the TBs of data that my Plex makes available to me.
Plex is perhaps a bit pricey right now since CCast support requires PlexPass but there is a way around that using Bubble UPnP until such time as CCast support no longer requires PlexPass.
Set up the Plex Server and also set up BubbleUPnP and let it aggregate the Plex Media Server library.
Then use the BubbleUPnP on your mobile device to send to CCast.
Bubble Server will transcode for you and you can still use the Plex for Android App (Paid app like aVia) for viewing on your mobile device if you like.
Once the CCast options go public you can decide which interface you like better.
Right now I have PlayOn, BubbleUPnP and Plex server all running on the same machine.
I rarely use anything aside from Plex since I have Plex Pass.
[EDIT/UPDATE]
Ok just went to Plex and found out that Direct Play is NOT currently supported the direct play entry was left in the profile by mistake.
It will however stream and has added a new streaming protocol that allows MKV to play without a heavy transcoding thread being needed for sources that are codec compatible (H.264/AAC)
The Player must support the DirectPlay (which may happen in future) and if it can't it will kick it back to the transcoder for streaming.
All direct Play is determined by the Player not the server so if it tries to direct play and fails it fallsback to the transcoder.
Bottom Line though is that Matroska is now supported in profile and will stream much better provided the codecs do not need changing.
And as with any container, Multiple Audio Tracks will always require transcoding to select which Audio track to play. So unless you want the first Audio Track you will probably still be using the full on Transcode.
All of this can change in the future if and when they update the CCast Player App to support more containers via Direct Play and Track Selection on the Client side.
But they are not there yet.
@Asphyx - many thanks for the detailed information and your legwork on this, I really appreciate it.
Ok, so - fwiw, ffmpeg can do transcoding or transmuxing, and an example file that can take 10 minutes to transcode will transmux in a very few seconds. And it can do it on the fly.
I mention that because while Plex may have rolled their own, it's usually less risk to deploy with commercial off-the-shelf solutions and focus on integration.
And my point is that either way, transmuxing to a stream would be fast, efficient, effective and highly supportable.
While I agree that a custom player could deal with an MKV container directly, and I don't doubt that someone will try it, that's a higher risk approach.
I'm using the classical definition of the risk factor here -
risk = (complexity / maturity)
Having a more complex player without a track record = high/low = very high risk.
I think that you nailed it, they're using a newer http transport they've implemented and I'm willing to bet 100 quatloos that it's MPEG-DASH, same as Hulu on Chromecast.
That approach would allow them to go with a single function receiver based on MPEG-DASH, ergo less complex, with a well known method, ergo more mature, with subsidiary risk from Google support in the Chromecast firmware. And that last component, while unknown because outside their volume of control, is accompanied by high risk mitigation because Google has at least one major player that will hold their feet to the fire if they screw that up.
Given that Plex is already a highly functional desktop server, I'm not sure that any other deployment model would make as much sense.
As for offloading significant work to the Chromecast, I don't disagree that it can be done, but I will note that when Koush deployed an H.264 decoder in Javascript, using the mature broadway.js method, the result was immediate heat death of his Chromecast. That's anecdotal but absent other data, I'd say that's a strong enough case to tread carefully where this MediaTek processor is concerned.
Anyway, if we combine our ideas to the single-point approach using MPEG-DASH, and looking at the work involved for sorting that out, I wouldn't say that Plex is dragging their feet.
Genius may be instantaneous but quality takes time.
Edit/PS - note that using a black box component such as ffmpeg reduces code work whether transcoding or transmuxing is required. Either way, you form a command string, dispatch it and stream the result. Added complexity to evaluate whether to transcode or just transmux is very minor compared to other approaches.
EarlyMon said:
@Asphyx - many thanks for the detailed information and your legwork on this, I really appreciate it.
Ok, so - fwiw, ffmpeg can do transcoding or transmuxing, and an example file that can take 10 minutes to transcode will transmux in a very few seconds. And it can do it on the fly.
I mention that because while Plex may have rolled their own, it's less risk for to usually deploy with commercial off-the-shelf solutions and focus on integration.
Click to expand...
Click to collapse
Actually they may have renamed the file but I am pretty sure they are using FFMPEG as their Transcoder base with some extra wrapping to make decisions on which format and settings are required for their Profile system.
EarlyMon said:
While I agree that a custom player could deal with an MKV container directly, and I don't doubt that someone will try it, that's a higher risk approach.
I'm using the classical definition of the risk factor here -
risk = (complexity / maturity)
Having a more complex player without a track record = high/low = very high risk.
Click to expand...
Click to collapse
Yes it does require a more complex player but I do believe at some point that is going to happen on the CCast side.
To do things like subtitle overlay and Audio track selection properly, this is always best done on the client side. Codec support is really the only stumbling block to realizing this. Since you can't load codec support into the CCast itself and to add them all into a player would be a ridiculously bloated app, A public codec repository (similar to Windows Media) would be the best bet for that. and in THAT respect I agree not likely anyone but google would take up such a project..
But that said...
While most devs are getting their code around the DIAL and Control protocols at some point they will have that stable and efficient and all that would be left would be to add Player side features such as Track Selection and possibly Software decoding for some containers where Codec is not an issue.
If I had to guess I would bet someone like MX Player Developers would be the first to make something like this happen since their Android Player already supports this type of functionality and it shouldn't be too hard to port that into a CCast compatible implementation.
EarlyMon said:
I think that you nailed it, they're using a newer http transport they've implemented and I'm willing to bet 100 quatloos that it's MPEG-DASH, same as Hulu on Chromecast.
That approach would allow them to go with a single function receiver based on MPEG-DASH, ergo less complex, with a well known method, ergo more mature, with subsidiary risk from Google support in the Chromecast firmware. And that last component, while unknown because outside their volume of control, is accompanied by high risk mitigation because Google has at least one major player that will hold their feet to the fire if they screw that up.
Click to expand...
Click to collapse
Currently the Plex Player supports HLS, DASH and whatever this new HTTP protocol is as streaming methods with Direct Play for Native MP4/H.264/AAC.
I neglected to add there is some movement on the Music and Picture front as well but I have not had a chance to check that yet.
EarlyMon said:
Given that Plex is already a highly functional desktop server, I'm not sure that any other deployment model would make as much sense.
As for offloading significant work to the Chromecast, I don't disagree that it can be done, but I will note that when Koush deployed an H.264 decoder in Javascript, using the mature broadway.js method, the result was immediate heat death of his Chromecast. That's anecdotal but absent other data, I'd say that's a strong enough case to tread carefully where this MediaTek processor is concerned.
Anyway, if we combine our ideas to the single-point approach using MPEG-DASH, and looking at the work involved for sorting that out, I wouldn't say that Plex is dragging their feet.
Genius may be instantaneous but quality takes time.
Edit/PS - note that using a black box component such as ffmpeg reduces code work whether transcoding or transmuxing is required. Either way, you form a command string, dispatch it and stream the result. Added complexity to evaluate whether to transcode or just transmux is very minor compared to other approaches.
Click to expand...
Click to collapse
Well right now the goal with Plex Devs seems to be to make any content work via Transcode if need be because that is the main role of PMS.
For most devices with mature Player Apps the Transcoder is rarely used because the Player Apps don't require it and can Direct Play different containers and codecs.
There is one team for Plex Media Server and another for Transcoding in general. (a Third is working on the CCast player specifically.)
They are focused on making transcoding work for everything and then (as an Afterthought) looking for ways to tweak the profile to not transcode where the device can handle it. (Basically it assumes it will have to transcode everything and then the profile will make exceptions to direct play.) the rest of the profile merely tells the transcoder what settings to use.
Which is why I don't expect any software decoding anytime soon, but they have considered it for future once they have everything working on CCast the way it is from the transcoding side.
Lets not forget Plex's goals are not specific to CCast they are just adding it as a target so their goals are not as much about CCast as someone like aVia and MX Player would be which is why I think they would be the first to create these types of Mature Decoders before Plex.
And who knows once someone does it wouldn't take much to license and load the CCast player code to add that functionality.
With most things like this I find once one takes the time to do it the others soon follow to not be left behind...
But I TOTALLY AGREE on the issue may be your CCast bursting into flames if not done correctly because heat does seem to be the one design flaw in CCast hardware.
I'd doubt anyone looking at platform independence would go with HLS, I think it's just too Apple centric. But as you say, Plex already supports it.
I think that the (relatively) new SDK refined MPEG-DASH support so I could see them calling that their new http method.
Remember, the chrome.socket method exists but is not exposed. Without that, no matter how good a programmer you are, your hands may be well tied as to how much of a private transport you can build.
If socket primitives existed a home network could go down to RDP or even UDP and really scream performance compared to anything you could achieve with http.
Anyway, I hear you, there may be something private and newer than MPEG-DASH there - but for all the reasons you note that this is one component of their business model, I can't imagine why they'd go for a higher risk, higher cost solution to do the same thing. Of course, that's just my opinion, worth every penny you paid for it.
Putting everything, or as much as possible, into the config files is simply a best practice.
Make the app data driven and offload maintenance and feature support to the config writer/parser subsystem.
I say "simply a best practice" because it is, but the guys that didn't figure that out couldn't compete with those that did/do.
As for just doing transcoding now, that's simply another best practice.
If they have a new server method and a new config parser, that's plenty to deploy.
Make sure that works, then deploy transmuxing as an incremental refinement. Even if the devs believe it's ready, history has proven what happens if you bite off too much with a release.
Sadly for us, too few devs get that.
I really don't think that a right way to offload more work to flame-free Chromecast will be found. Even if such a thing could exist (which I more than really doubt) I just don't see the incentive for anyone to do it.
Btw - I don't know if you've noticed this but if you go to a site with embedded MP4 videos, vGet will cast that or play it locally to MoboPlayer, MX Player will complain that it's an unknown format.
I agree that MX is a great player and ahead in a lot of areas but I would say that caution is in order predicting anything in this area, again, just imo.
---------- Post added at 02:38 PM ---------- Previous post was at 02:19 PM ----------
PS - as I'm sure you know, everyone including Google is chomping at the bit to get H.265 and VP9 happening.
So existing code and methods have to be supportable, maintainable and inexpensive enough - everything today is on its way to becoming a legacy method.
Given the processing requirements for VEHC, I can't see that happening on the existing Chromecast.
And if that's what a Chromecast 2 will support, and I'm betting it will, I can't see estorica being built by anyone at this point for the existing Chromecast.
Even if you're not in the market for 4k video, I can see the attraction of a more condensed network stream to support 1080p.
Personally, I expect that to hit the front burner before other transcoding and closed caption support does. (edit - Wrong! LOL see next post)
Asphyx said:
Bubble does have the ability to transcode if the content is coming from the Bubble Server (on the Desktop) but I'm not sure it will transcode ON UNIT LOCAL files when sending to CCast. Perhaps it does but it would require sending the file from your phone to your desktop then sending it to CCast. You should ask the Dev for Bubble to clarify this they post here regularly and are very responsive to their Users. (I have Bubble running myself on the same server as my Plex. and It's a very good alternative for Plex.)
Click to expand...
Click to collapse
BubbleUPnP Server can transcode *any* media that Android BubbleUPnP can access. That applies to local Android media managed by the app, but as well any external media sent from third party apps to BubbleUPnP.
And for the next release of BubbleUPnP / BubbleUPnP Server, there are major improvements, such as: proper subtitle support (and not of the crappy burning subs in video kind, that everyone is doing), seek in transcoded videos, audio and video track selection, and many transcoding fails fixed.
Moreover, BubbleUPnP Server transcodes video and/or audio tracks only if necessary.
bubbleguuum said:
BubbleUPnP Server can transcode *any* media that Android BubbleUPnP can access. That applies to local Android media managed by the app, but as well any external media sent from third party apps to BubbleUPnP.
And for the next release of BubbleUPnP / BubbleUPnP Server, there are major improvements, such as: proper subtitle support (and not of the crappy burning subs in video kind, that everyone is doing), seek in transcoded videos, audio and video track selection, and many transcoding fails fixed.
Moreover, BubbleUPnP Server transcodes video and/or audio tracks only if necessary.
Click to expand...
Click to collapse
Way to go!
EarlyMon said:
I'd doubt anyone looking at platform independence would go with HLS, I think it's just too Apple centric. But as you say, Plex already supports it.
Click to expand...
Click to collapse
Well the Plex folks are supporting Apple so I suspect they need to support all things Apple.
As for what they might dore Transcode vs Player based it will depend on the end results. Many are running Plex on NAS and other low power units where even transmuxing is a Task.
In the end there is only so much you can do on the server side and have to look at the client side for solutions. Thats all I'm getting at. Subtitles being a prime example. Multi Language and Audio track selection being another.
bubbleguuum said:
BubbleUPnP Server can transcode *any* media that Android BubbleUPnP can access. That applies to local Android media managed by the app, but as well any external media sent from third party apps to BubbleUPnP.
And for the next release of BubbleUPnP / BubbleUPnP Server, there are major improvements, such as: proper subtitle support (and not of the crappy burning subs in video kind, that everyone is doing), seek in transcoded videos, audio and video track selection, and many transcoding fails fixed.
Moreover, BubbleUPnP Server transcodes video and/or audio tracks only if necessary.
Click to expand...
Click to collapse
Forgive me if I misrepresented Bubble there. I was under the impression that Bubble required Server (on a PC) to be running in order to transcode. And if you simply streamed from Bubble Android to CCast without that Server it would not transcode. Either that Changed or I was misinformed.
Happy to see you support Client side Subtitle Overlay and Audio Track selection. That is the only proper way to do those operation which is why I don't understand why everyone else seems intent on doing it on the server side. My guess is lack of knowing Android and Mobile Coding on their part.
In conclusion I will say this...
The Dev who makes the best CCast Loadable Player App could make a lot of money licensing that app to other developers to use in their Projects.
Asphyx said:
Forgive me if I misrepresented Bubble there. I was under the impression that Bubble required Server (on a PC) to be running in order to transcode. And if you simply streamed from Bubble Android to CCast without that Server it would not transcode. Either that Changed or I was misinformed.
Click to expand...
Click to collapse
Yes the server is required on PC for transcoding. There's no transcoding done at all on Android.
What I was saying is that it can also transcode Android local stored media.
But apperently I misundertood your original statement where you wondered in the app could transcode itself: it can't.
Asphyx said:
Happy to see you support Client side Subtitle Overlay and Audio Track selection. That is the only proper way to do those operation which is why I don't understand why everyone else seems intent on doing it on the server side. My guess is lack of knowing Android and Mobile Coding on their part.
Click to expand...
Click to collapse
Audio track selection requires at least remuxing in a new container and possily transcoding if the track is not compatible.
bubbleguuum said:
Yes the server is required on PC for transcoding. There's no transcoding done at all on Android.
What I was saying is that it can also transcode Android local stored media.
But apperently I misundertood your original statement where you wondered in the app could transcode itself: it can't.
Click to expand...
Click to collapse
Not hard since I wasn't very clear LOL
It is transcoding from android but only if you have the server running on PC!
bubbleguuum said:
Audio track selection requires at least remuxing in a new container and possily transcoding if the track is not compatible.
Click to expand...
Click to collapse
Even in the case of MKV/AAC where Multiple Audio Tracks are embedded?
I understand it for unsupported formats like AC3 and DHT but if there is a stereo AAC and 5.1 AAC you shouldn't have to remux if the Player does client side track selection.
I'm thinking along the lines of what VLC does which granted is far more complex of a player due to the fact it's years in the making and has a full blown PC to power it.
Am I correct in thinking there is no video play with chromecast push support? I.e. MX Player, you are watching video on phone then you press cast button?
Not possible or just no app has done it yet?
Avia has paid ($2.99) CC support.
Sent from my Galaxy Nexus using xda app-developers app
There is an app called y2cast which can cast videos to the Chromecast together with an app called Moliplayer. The 1. problem of this is that everytime you turn on your TV, you have to connect y2cast with your Chromecast before you can start casting via Moliplayer and the 2. is that Moliplayer doesn't play every file format (even when you haven't connected it to the Chromecast) and is also very slow/has a lot of lag.
---------- Post added at 03:43 PM ---------- Previous post was at 03:27 PM ----------
Does Avia play every file format and can avia cast every file format to the chromecast?
There are loads of apps now that will play media from phone to Chromecast - BubbleUPnP is my personal choice, Allcast, Localcast, Avia....there are more.
They vary in their capabilities - most can't cast videos that are not encoded in a Chromecast friendly format. BubbleUPnP can with the help of a Bubble Server installed on a PC on the local network.
neu - smurph said:
There are loads of apps now that will play media from phone to Chromecast - BubbleUPnP is my personal choice, Allcast, Localcast, Avia....there are more.
They vary in their capabilities - most can't cast videos that are not encoded in a Chromecast friendly format. BubbleUPnP can with the help of a Bubble Server installed on a PC on the local network.
Click to expand...
Click to collapse
Well then you could just cast the video in a tab via Chrome. I'd love to see a solution where an android device does that, most of the devices are probably capable of doing it.
Pete1612 said:
Well then you could just cast the video in a tab via Chrome. I'd love to see a solution where an android device does that, most of the devices are probably capable of doing it.
Click to expand...
Click to collapse
Share the page to either vGet or Web Video Caster, and cast from there.
It's one extra step - sharing the link - but it works great for supported video formats.
vGet has more options and is a paid app. Web Video Caster just casts and is free.
EarlyMon said:
Share the page to either vGet or Web Video Caster, and cast from there.
It's one extra step - sharing the link - but it works great for supported video formats.
vGet has more options and is a paid app. Web Video Caster just casts and is free.
Click to expand...
Click to collapse
for thus you can also use chrome for android (free from google obviously), go to chrome://flags and turn on chromecast support
Avia does NOT work on all formats. It's a bit of a hit and miss. Some work some dont
The moment everyone is waiting for is for mx player or vlc to support Chromecast !
I think that the limitions are not in the players but in the software of ccast that can play only a few format and codecs.
Do you think that, in future, ccast will be updated and so it will play other video format? Is a feature that can be implemented with a firmware upgrade?
Thanks!
davboc said:
I think that the limitions are not in the players but in the software of ccast that can play only a few format and codecs.
Do you think that, in future, ccast will be updated and so it will play other video format? Is a feature that can be implemented with a firmware upgrade?
Thanks!
Click to expand...
Click to collapse
Yes and Maybe....
You're right in that the CCast is limited in codec and container support.
But that is really only true if the Player app that gets loaded into CCast relies on the CCast hardware to play the files.
Android itself is almost as limited as the CCast is as far as Compatible file formats are concerned but the video players we use on Android add the support for those different codecs and container types into the APPs themselves.
The same could be done on the CCast side and BubbleUPnP seems to be the one (and Only) app that has gone the farthest in doing that.
All the others seem to just send whatever format the file is in and if it isn't CCast compatible it won't play.
What needs to happen is for someone to create an MX Player type CCast Player app that can play many Container and Codec types without the need for Transcoding. Then others could potentially use that Player App (think along the lines of a JW Player type CCast Application) when sending Media to the CCast without the worry of incompatible file and codec format.
Or Google needs to create it and add it to the CCast OS as the default player.
As of now there is no option close to that...Bubble supports more container types than others and in conjunction with the Bubble Server will transcode the ones it doesn't support.
Plex seems to transcode everything that isn't directly CCast compatible and the other Player Apps we have for Android don't deal with Compatibility at all they merely send the media to CCast and it works only if it is compatible.
Perhaps in time they will add to the CCast Player side to gain more support but Bubble is so far the only one to really focus as much on the Player side compatibility expansion and features.
Plex is working on it as well but they are less focused on Compatibility due to the fact they are able to transcode everything to whatever format they want. After they get all the transcoding perfected they might turn focus into finding ways to avoid transcoding for those who have issues due to low power servers.
Asphyx said:
...
Click to expand...
Click to collapse
perfect explanation! Really thank you. I hope that this device will be supported with the right software, meaning apps, in the near future.
Thanks again.
davboc said:
perfect explanation! Really thank you. I hope that this device will be supported with the right software, meaning apps, in the near future.
Thanks again.
Click to expand...
Click to collapse
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.
Localcast works well for me. Even let's me access and stream movies/TV shows straight from my USB stick on my Note 2 using an otg cable.
Sent from my Sinclair ZX81.
Koush tried software decoding for H.264 video - the processor ran hot enough to destroy his Chromecast, and that was using a known and mature routine.
The MediaTek processor is very good but it has limitations.
Maybe someone will take it further and succeed. I think it's more reasonable to look for more codecs on Chromecast 2, if at all.
Btw, LocalCast now lets you use your phone for headphones for stuff you're casting.
Not doubting you here...I know the Hardware is close to being an Egg Cooker even under normal usage....
But I'm curious as to why would he software decode H.264? No need to do that as it's already supported.
I'm just wondering if he was trying to do transcode from unsupported codec to H.264 on the device.
That method I would expect to not work at all.
But by adding loadable Software codecs it should not require the same proc cycles and speed as trying to transcode as it's really just a decoding operation which is roughly half the intense of transcoding which both decodes then re-encodes.
The Tricky part would be getting the player to load codecs on an as needed basis which is where I expect it might make the approach impossible.
I'm personally less concerned with codec support as I am with Containers, Subtitles and Audio Track selection being done on the Player side.
All of my Library is already H.264 But I much prefer MKV container for keeping Subs and Multiple Audio (for Commentary) so once a player comes out that supports all of those without transcoding I'll be a very happy puppy.
I don't know but I imagine that he was simply following a standard best practice -
Comparing known quantities to map the solution space before proceeding into the unknown.
The H.264 routine (just a software codec attached to a simple player from what I recall looking at the time) made sense for that, precisely because it was a mature, known quantity that could be compared to the existing feature in hardware.
Apples to apples.
perhap he tried that since H.264 is the most hardware intensive compression compared to say On2, Cinepak or the older Indeo...
If it could software decode H.264 then it could pretty much decode everything else just fine with the exception of MPEG2 which requires specific hardware.
Asphyx said:
What needs to happen is for someone to create an MX Player type CCast Player app that can play many Container and Codec types without the need for Transcoding. Then others could potentially use that Player App (think along the lines of a JW Player type CCast Application) when sending Media to the CCast without the worry of incompatible file and codec format.
Click to expand...
Click to collapse
Are you saying if a player i.e. MX player had the cast function builtin into it then you can cast any video format that MX player supports?
ermacwins said:
Are you saying if a player i.e. MX player had the cast function builtin into it then you can cast any video format that MX player supports?
Click to expand...
Click to collapse
That's what a lot of people want.
ermacwins said:
Are you saying if a player i.e. MX player had the cast function builtin into it then you can cast any video format that MX player supports?
Click to expand...
Click to collapse
No not at all.....an App's (aka Transmitter) ability to cast to a CCast has little to do with it can support but what the CCast supports....Other than through the player app it tells CCast to load to receive the stream (aka the Receiver app).
Every App tells the CCast to load a player and it is that player that determines what format can be played not what the App that started the cast supports.
So even if MX Player supported CCast now...Doesn't mean at all that streaming from it to a CCast means MKV or MOV files will play on the CCast despite the fact they play in MX Player just fine.
That is unless MX Player wrote a custom player (receiver) for the CCast that supported all the formats MX Player does or MX Player added the ability to transcode any format to work with the receiver they load into the CCast.
As of today just about every app that supports more than just the standard CCast compatible media do so via Transcoding.
And thats not likely to change soon unless someone figures out a way to do it without frying the unit.
I bet it would work a lot better if the player app was run outside of the Google Sandbox the way Netflix is when it does it's own decryption.
The question is will anyone other than one of the Partners who invented the DIAL protocol ever get that type of access to the hardware?
Not without Google being fully on board....
Hello,
I just bought a chromecast and i'm wondering that DTS Codec is not supported. Is there a way to get dts codecs working on the chromecast? Or is it necessary to convert files before they can be played by chromecast?
regards
Leichti
leichti said:
Hello,
I just bought a chromecast and i'm wondering that DTS Codec is not supported. Is there a way to get dts codecs working on the chromecast? Or is it necessary to convert files before they can be played by chromecast?
regards
Leichti
Click to expand...
Click to collapse
No, the best work around is to install plex and have it convert to acc 5.1.
Ty for the tipp.
Unfortunately all my stuff lies on a NAS (NSA325v), and for Plex it is necessary to run a computer/server for streaming?
Do you think that DTS support will come?
leichti said:
Ty for the tipp.
Unfortunately all my stuff lies on a NAS (NSA325v), and for Plex it is necessary to run a computer/server for streaming?
Do you think that DTS support will come?
Click to expand...
Click to collapse
No probably not because it would require licensing the codecs from Dolby.
NetFlix can do it because they have the licensing so unless some other player/receiver is developed that has the licensing not likely to see it anytime soon.
Since you are using an NAS it's also not likely Plex will help in this regard unless you run a computer and map the NAS drives to it.
Then your options open as as you can also use BubbleUPnP which also does transcoding.
But if the computer is not an option for you then the only thing you can do right now would be to use handbrake and add/create an AAC Multichannel track (using the existing DTS track) that can give you surround support on a CCast.
If your library is not too big yet it's a good thing to do anyway, I make sure all of my Library files have whatever Dolby tracks plus one AAC Multi and one AAC Stereo just to be sure they are fully compatible with any device I have now or in the future.
Thank you for your help!
Is it possible to transcode only the audio data with handbrake?
Asphyx said:
No probably not because it would require licensing the codecs from Dolby.
NetFlix can do it because they have the licensing so unless some other player/receiver is developed that has the licensing not likely to see it anytime soon.
Since you are using an NAS it's also not likely Plex will help in this regard unless you run a computer and map the NAS drives to it.
Then your options open as as you can also use BubbleUPnP which also does transcoding.
But if the computer is not an option for you then the only thing you can do right now would be to use handbrake and add/create an AAC Multichannel track (using the existing DTS track) that can give you surround support on a CCast.
If your library is not too big yet it's a good thing to do anyway, I make sure all of my Library files have whatever Dolby tracks plus one AAC Multi and one AAC Stereo just to be sure they are fully compatible with any device I have now or in the future.
Click to expand...
Click to collapse
leichti said:
Thank you for your help!
Is it possible to transcode only the audio data with handbrake?
Click to expand...
Click to collapse
Well Handbrake isn't a LIVE option...
Based on the settings you can have it do No Transcoding to the Video at all and have it simply pass video and existing audio tracks to the destination file...
Which in essence if you just ADD an Audio track all it will really be doing is transcoding for that new track.
It will however do any decoding needed to read the source so it's still not going to save you much but you won't need a ton of horsepower as the horsepower of your unit will only affect the speed at which it completes.
hi
has any one got an opinion why chromecast despite having the required hardware to play many more video formats is not given the ability to do so??
mahi98 said:
hi
has any one got an opinion why chromecast despite having the required hardware to play many more video formats is not given the ability to do so??
Click to expand...
Click to collapse
Licensing of Codecs for one....
Understand that CCast is really meant to be an HTML5 appliance so it is built to play anything that is HTML5 compatible and that leaves a lot of codecs off the supported list because they are old and inefficient or not suited for streaming over WiFi.
The device is simply not meant to be a ROKU, it is a device that is meant to put Web content onto a big screen and not much more.
If you want more features and video support then AndroidTV is probably the device you are looking for.
It's not like Roku plays a lot of formats either - just mp4 with the standard expected codecs and a small subset of mkv files that happen to be compatible.
I just don't worry about it. I mostly play downloaded files via Plex, relying on Plex to do the transcoding. I only check out the actual file format if Plex seems to be stumbling over some HD file with a rare slow codec. In that case I run it through a video converter utility with hardware GPU acceleration on my desktop PC that can convert a 1-hour video to standard mp4 in about 60 seconds. Problem solved.
DJames1 said:
It's not like Roku plays a lot of formats either - just mp4 with the standard expected codecs and a small subset of mkv files that happen to be compatible.
Click to expand...
Click to collapse
Aren't mp4 and MKV containers? Meaning two different mkv files could use two different codecs (the reason why *some* mkv files are compatible and other are not).
Like you, I use Plex or Allcast and let them do the transcoding. I haven't run into many issues with this approach.
That's correct, but you'd find that most mp4 files today consistently use H.264 as the video codec and stereo AAC as the audio codec. It's possible to use other codecs in an mp4 files, but with so many devices that will play standard mp4s and most of them choking on any unexpected codec it's just easiest to stick to the standard. mkv files tend to have more variety, so a large percentage of them will fail on devices like the Roku or Chromecast that support a very narrow range of codecs and format variations. For example an extra track of chapter marks or an extra audio track will cause many devices to fail even though these are allowed within both the mkv and mp4 container format.
DJames1 said:
It's not like Roku plays a lot of formats either - just mp4 with the standard expected codecs and a small subset of mkv files that happen to be compatible.
I just don't worry about it. I mostly play downloaded files via Plex, relying on Plex to do the transcoding. I only check out the actual file format if Plex seems to be stumbling over some HD file with a rare slow codec. In that case I run it through a video converter utility with hardware GPU acceleration on my desktop PC that can convert a 1-hour video to standard mp4 in about 60 seconds. Problem solved.
Click to expand...
Click to collapse
Yes but the main focus of the Roku is for Alternative video where as the CCast will play video but is designed more as a Web Content device.
This is why the Roku all have wired network connections (recent dongle excluded of course as it is meant to compete with CCast.)
Roku supports more merely because it has the App support.
There is nothing to stop someone like MX Player from making a receiver app that will add codec and container support to the CCast.
What is keeping some developers away is the convoluted discovery and control protocol needed.
Roku doesn't need any of that so they can just focus on the player code cause the remote does the navigation for them.
And in time as more support for the CCast comes around you will find that killer receiver app made that supports more codecs and containers and if the folks at plex are smart they will either license it or make it themselves!
99% of their complaints could all be handled better and go away with a little work on the player side.