yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] bhiga:
If I may expand on your explanation a little more...

Direct Cast sends whatever is requested to be sent, which may not be in a Chromecast-compatible format.

The Cast extension for the Chrome desktop browser does transcoding, technically it's just encoding because what's displayed in the tab or desktop is not compressed at that point. This is why it makes the CPUs work and why it works for almost any content.

Current mobile devices lack the CPU power to do efficient real-time transcoding, not to mention they generally lack the storage to cache any transcoded output for doing non-real-time transcoding.

Both AllCast (for rooted Chromecasts) and aVia seem to do the same thing. Whatever you choose, it just pulls the data and sends it to Chromecast, whether Chromecast can handle it or not. That's why when I try to cast a WMV, aVia eventually gives up and says the format is not compatible with Chromecast, and AllCast just shows no status while Chromecast shows a black screen.

Fling (for rooted Chromecasts) without the real-time transcoding part involving VLC (which it seems most people can't get operating anyway) works the same way. Whatever you load, it sends to Chromecast, whether Chromecast can decode it or not.

Plex, on the other hand, negotiates between the client and server. I'm not sure how sophisticated it is, but at the very least it should be along the lines of:

Client: "I want this file. I'm an Android 4.1 device."

Server: "Okay, I know Android 4.1 devices support some format."

Server: "This file looks like it's already compatible. Here's the data." (no transcoding)

or "I need to make a compatible version of this file for you. Hold on a bit and I'll give it to you as I go." (transcoding required)

If it's really sophisticated it might generate multiple bitrates for output so it can still stream over bandwidth-limited connections (like Internet streaming servers do) and/or adapt to limited available resources on the server.

So the key differences are:

Native (URL sending) apps request a Chromecast-compatible version of the content, and the server already has it

AllCast and aVia just send what they have, it's up to the user to ensure it's Chromecast-compatible, or they get no Chromecast output

Plex Server knows what Chromecast needs, and creates a Chromecast-compatible version if necessary (transcoding)

Cast extension for Chrome desktop browser also knows what Chromecast needs and compresses the tab/screen to a Chromecast-compatible format on-the-fly (encoding)
[Google Chromecast] bhiga:
We overlap in the transcoding side, but I don't know DLNA very well... except for the fact that my (circa-2009) TV's implementation does photos and audio only, no video, hehe.

I think aVia's flexibility is causing a bit of confusion...

aVia can function in a number of ways

Cast

local

media to Chromecast or DLNA

This is a direct cast and AFAIK there is no transcoding here.

Cast media from DLNA sources to Chromecast or a DLNA receiver

I'm not sure whether this is a direct cast or just a URL send.

Share media by being a DLNA Server

This allows other DLNA-compatible devices to "pull" local media from the device (ie, if your TV supports DLNA video, you could have your TV pull a video stored on your phone). I don't think there's transcoding here either.

Receive media by being a DLNA Receiver

This allows another device to "push" (cast) to aVia on this device for playback. For example, you could "push" a video on your phone to aVia running on your tablet (with receive enabled) for larger-screen playback.
[Google Chromecast] third son:
So I updated kyocast by rebooting and tried to cast avia paid version. Is there another step I have to do? I can use all cast no problem and hbogo and YouTube works fine
[Google Chromecast] bhiga:
Does aVia see your Chromecast(s)?

It won't show a Cast icon if it doesn't see any receive-capable devices on the network.
[Google Chromecast] third son:
yes it sees it and I have the cast button on my phone. When I hit it I get the avia splash screen on the TV and then a screen with the video progress bar and it looks like it wants to play (mp4 file that works with allcast) Then it gives an avia screen that says sorry the chromecast does not currently support this file type.
[Google Chromecast] smalis:
All good (see post http://xdaforums.com/showpost.php?p=48382912&postcount=110), except that the Plex for Android app requires a Plexpass to cast to ChromeCast.
[Google Chromecast] bhiga:
That's exactly what mine is doing, but I only had 10 minutes to test it this morning...

I'll try to play with it more this evening.
[Google Chromecast] rpk213:
PlexPass Workaround [Help]

So I've been waiting for your post for a while. This is exactly my problem. I completely understand that if I am running a Plex Media Server, I should clearly be using a Plex Client for compatibility reasons. However, I will not purchase the PlexPass only for CC. I am very inexperienced with tweaking routers and network settings and would appreciate any advice on where I can find a PlexPass work around method walkthrough.

Current setup: My brother shares his insanely massive PMS with me from his house (not in my network) and I view said shared content through my separate PMS. I am afraid to start poking around in the network settings because:

1.) I don't know **** (ISP Cycle? DynDNS? router external IP and proper Port information?) &

2.) It is currently specifically set up by my housemate to run her business. And I would like to avoid ruining everything.

Sorry for sounding incompetent, but I would appreciate any advice here.
[Google Chromecast] abuttino:
If you have a upnp router, your port should automatically be forwarded
[Google Chromecast] third son:
Thanks I will see what you come up with...

Edit: I was able to cast from my Asus tablet perfectly.... The epic 4g touch does not cast yet....
[Google Chromecast] abuttino:
I am thoroughly impressed. Plex mixes the audio track to PCM and doesn't downmix it to Dolby pro logic.

More: I have a very unique setup, 82" TV calibrated professionally by an image science foundation and THX technician. Basically the TV is THX certified. The colors with the transcoding aren't quite as rich. However, I think the quality is awesome, especially considering it's over a WiFi stream transcoded.

This is pretty awesome. Well worth the wait for the whitelist with kyocast.
[Google Chromecast] MikeWjF:
Not to sound like I'm complaining, but Chromecast seems finicky about what file types it wants to play. I figured I was safe with MP4s but even that seems to be hit or miss through avia.
[Google Chromecast] abuttino:
If you want to know what AVIA streams, look at the list on supported media types. Phones cannot transcode, dlna doesn't know what it's streaming to, plex is the only option for transcoding, unless you do it yourself.
[Google Chromecast] anthony67:
After reading this entire thread....I installed Avia on my phone and Plex media server on my laptop and so far it works great. I haven't tried all of the movie formats I have yet our any with subtitles.

Between this set up, Koush's Allcast and my xbox 360, I have all my tv's covered and can stream just about anything I want.

Scribbled from my Galaxy Note 3.

Stock, rooted, hacked, beastly.
[Google Chromecast] third son:
Understood...
[Google Chromecast] Asphyx:
Ok That says to me that the Chromecast support is sending a PlexPass link to the CCast and not links directly to the server.

In fact the entire PlexPass system itself may work by having the Server send the file to their PlexPass system then pass it onto you.

---------- Post added at 03:08 AM ---------- Previous post was at 03:05 AM ----------

It isn't the filetype that matters it is the codec used inside the filetype that is key to playing back or not.

CCast seems to want H264 codec which is usually what an MP4 files is using these days but other codecs are possible as well.
[Google Chromecast] Mr-Glass:
Should be easy enough to test that by disconnecting internet and keeping your local network up..
[Google Chromecast] Asphyx:
I think we can sum up both pretty quickly now after all the experimenting....

aVia

aVia will work for Local (ON UNIT and any DLNA servers it can talk to) and stream to Chromecast but the content in question needs to be encoded using a Chromecast compatible format such as H264/MP4. Video Bitrate should not be higher than 4000. If your files complies with that then you should have no problem using aVia to send local files to Chromecast.

Plex

PlexServer works best with Plex App (but CAN work with any DLNA client including aVia) but requires a Plexpass subscription to send to Chromecast when using one of their Player Apps. Any format file will work when using Plex software because Plex will transcode the file properly for playback on Chromecast. Caveat being you have to pay for PlexPass.

I hope that clears the choices up for everyone.

Lets just hope that for those who don't like either option that BubbleUPNP comes up with a better method of supporting Local content that doesn't require a subscription but does transcode for you.
[Google Chromecast] smalis:
So - if I do not want to pay for PlexPass, and I want to cast a non-compatible file format from Plex server on PC through my tablet to my TV, I will for now have to manually transcode the file first on the PC and cast with Avia, until Plex permits casting from the free android app - yes?
[Google Chromecast] abuttino:
Either that, or you can hack the plexpass app.. It is possible.
[Google Chromecast] Mr-Glass:
I guess some things bring up another question.. Do I have to have internet access to play my local media with Plex and Chromecast.... Would be nice to take my laptop(plex server) and an old wifi-router to the cabin where there is no Internet..
[Google Chromecast] Asphyx:
I will try that tomorrow, It may only require PlexPass when the signal needs to go past the Localnet.

The system works so well that the $75 for a lifetime PlexPass didn't seem like much to pay for a lifetime of being able to stream my home content anywhere and now on an TV LOL

Truth is the aVia system would work just as well if everyone just made sure their files were encoded in a format that just about every Android device can handle which is H264/MPR <4000 Bitrate.

---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------

Yes you don't need plexpass and aVia will work provided no transcoding is needed for the file you are trying to play.

Just encode all of your files in H264/MP4 and keep the bitrate below 4000 and you should have no issues playing with aVia since no transcoding on the fly would be required the file is already chromecast compatible.

Wait let me clarify that..Transcoding is something you do AS yo stream it so what you would actually be doing is RE-Encoding the now incompatible files to a format that is compatible...

You would then have to select the right one or replace the incompatible version with the compatible one.

My entire Library is compatible with CCast so I can use either and have no problem with the compatibility nor do I really need Transcoding because I am already in a compatible format.

Do the same with your content and aVia will be just fine with no need to transscode!
[Google Chromecast] Mr-Glass:
Yeah - I am out of town til Friday - of course I did not pack up the chromecast - so I am wanting to try a lot of things..:)
[Google Chromecast] Asphyx:
My problem (not a problem really lol) is all of my library is already in a format that is compatible with Chromecast because I been watching it on my age old Xoom since before I started with the DLNA server.

So I can pretty much stream any of my local content to the CCast and don't have to worry about if it transcodes or not!

---------- Post added at 03:50 AM ---------- Previous post was at 03:42 AM ----------

Answer is ...Depends!

Not sure how aVia does it,

NetFlix and YouTUbe obviously do...

So the Question is does Plex and aVia work in a similar way. Neither should but that doesn't mean they don''t!
[Google Chromecast] rpk213:
PlexPass Work Around [Help]

Anyway you could possibly explain what settings you changed in Plex, your firewall, and your router. I would love to try this work around, but am afraid of tinkering with ports because I have no idea what I am doing. I don't want to jeopardize our security in anyway. Unlike most XDA members, I don't spend much time changing my network settings.

It seems there is a hack for this...but I kinda feel like the idiot who can't find it...

Any advice is welcome.

Thanks
[Google Chromecast] bhiga:
Okay, Cast media from DLNA source to Chromecast is definite a

Direct Cast

- the data flows through the device running aVia. I started playback of a file from my server (which is also a DLNA source) via aVia on my phone, and when it started playing I rebooted my phone. The video continued to play for a few seconds (so there's definitely some buffering), then it abruptly cut off.

So far I have been able to cast MP4s and photos (albeit quite slow) from DLNA server, but not any local media. The same local media plays ok via AllCast, so I know Chromecast is capable of decoding it. aVia will play the file on my phone, but if I try to cast it to Chromecast, it shows the filename and then seems to time out after a while.

Same thing happens for a file that plays fine via DLNA "relay" - it doesn't play if stored locally. Maybe it's something specific to my phone...

At least I have some progress.
[Google Chromecast] Asphyx:
Are you sure ALL cast doesn't do some transcoding that maybe aVia does not?

And I would not be surprised to find that aVia is not using a very good implementation.

Do you have a G Wireless as opposed to N? Maybe it can't keep up with the stream?

Strange that Allcast will play but Local via aVia will not unless the aVia is doing something it shouldn't.

I used to use aVia's old app for testing of client DLNA that didn't have Twonky...But I never really liked it back then. Never really worked well for me then as far as usable DLNA player/client.

.

---------- Post added at 06:19 AM ---------- Previous post was at 06:11 AM ----------

Really off topic but anyway...

You don't change any setting on Plex Server, Just note the port it uses in the settings. You can password protect Plex Server if your worried about security. That IS in the Plex Settings.

In your router you go to your advanced setting (varies depending on make and model) but your looking for something called PORT FORWARDING which just tells the Router to send any traffic that comes on that port to a specific machine (in this case the machine running PlexServer). Enter the number of the port your Plex Server is using and tell it to send that traffic to the IP Address (local IP) of the machine running the server.

Then you can set the Plex App to go to the IP address of your router and it will forward your Plex requests to the server for you.

Setting up DynDNS is much more complicated and requires it's own subscription so unless you REALLY need to set a domain to handle dynamic DNS for your home for things other than Plex your probably better off just buying the Lifetime PlexPass!

If you buy the lifetime its a one time charge and you don't have to change any routers or loosen security in anyway!

And it works FLAWLESSLY with Chromecast so it's the best of both worlds...

Sometimes having COOL costs money folks...no way around it!

Until someone provides a free way to do it easy.
[Google Chromecast] DJames1:
People seem to be under a mis-impression. You don't need PlexPass to remotely access your Plex home server. You don't even need to set up manual port forwarding or a dynamic DNS service. The free MyPlex service will link you up. You just set up your Plex Media Server to log in to MyPlex when it starts, and then you log in to MyPlex with your remote client to automatically link up.
[Google Chromecast] abuttino:
You must set up a port forward. But most likely, with most routers, it'll set itself up.

I have an enterprise firewall and it wouldn't connect to myPlex until I forwarded the port.

Don't understand what a dynamic DNS would do, myPlex keeps track of your server and your IP address or domain is never entered into the equation.

This is a standard media server with a front-end.

DLNA servers use the front-end (menu system) for your TV, XBOX, PS4, Roku, Avia, AppleTV to present media.

Yes, Plex is a DLNA server, but it also has a front-end. Several of them; Apple, Linux, Android, etc.

If you use the DLNA side, it just hands media off without transcoding.

If you use Plex, Plex/web, Android Plex, Apple Plex, etc. It uses the Plex transcoding and other Plex specialized services no matter where you are.

Chromecast Plex should be limited to the same house your media is in. (MPAA doesn't like place-shifting)

The only reason to get PlexPass is to use Chromecast or if you have media in the cloud to stream.

Hope this helps someone
[Google Chromecast] Cuzz1369:
Haven't seen it mentioned yet but avia supports streaming from dropbox. Works well, still no avi support but the mp4's I tried worked.
[Google Chromecast] bhiga:
Yup, no transcoding in AllCast, if it's not CC-friendly format you just get black screen and no status when casting.

My network is 802.11n

My phone is on the 5 GHz AP though, so I need to try the 2.4GHz in case it's some weird router packet thing. And I can try my tablet that's still on ICS.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[Google Chromecast] Restorer:
Bear in mind also that you get the $4.99 app free with the Plex Pass. Not sure though if the app stops working if you don't renew the sub?
[Google Chromecast] third son:
What kind of phone do you have Brandon? I have the exact same phenomenon that you describe. I have a Samsung Epic 4G touch running Jellybean 4.1.2. My Asus tablet works fine with Avia. I am running Cyanogenmod 10.2 (JB 4.3).

I am also wondering if it is phone specific...Allcast works fine on my phone and tablet.
[Google Chromecast] lexluthor:
I asked the somewhere else the other day. When you have a Plex Pass, you use a different app called Plex for Plexpass. That's free in the play store, but only works as long as you have Plex Pass.
[Google Chromecast] Asphyx:
Actually you use a different app if you have the PlexPass account....

The Paid app CAN work with or without PlexPass...Thats not the app they are talking about when they say you get the app for free.

But the Plex for PlexPass app requires PlexPass. Thats a FREE app in the store and that is the app they are talking about when they say you get a free app!

Sorry if I confused anyone regarding that. Also apologies if I confused MyPlex with PlexPass.

As for if Port Forwarding is needed or not, It depends on your router and setup and how locked down you have your home network.

If you can stream outside your network then obviously no change is required. Some can and some can't depending on their firewall and router settings.
[Google Chromecast] wptski:
Transcoding if needed to make content CC friendly might pose another question, what's needed to do that and at what price? I remember somebody mentioning a program for doing that and it was $60 for the basic version.
[Google Chromecast] Mr-Glass:
I still would like to know if Internet connection is needed or if local wifi network without Internet will suffice.. I am out of town and could justify buying another CC if so... otherwise it would be a purchase I just do not need..
[Google Chromecast] lexluthor:
I just paid for a month of PlexPass and installed the Plex for PlexPass app.

Wow, this is exactly what I had been waiting for. It played everything I through at it. I could advance, rewind and pass and all movies started up again pretty quickly.

I have movies in so many different audio and video formats. Where can I see which ones Plex will transcode and which ones will get sent to ChromeCast natively? Is there a way that I can tell it's transcoding?

I do hope they open this up for non PlexPass members though so I don't have to spend $3.99/month for this.
[Google Chromecast] bhiga:
I have a Samsung Galaxy S3 and it's running Jellybean 4.1.2 from elsewhere in this fine forum.

I wonder if it's something specific to 4.1.2?

I'll try my wife's GS3 later on - I haven't upgraded hers to 4.1.2 yet, so it's still 4.0.something I think.

---------- Post added at 07:39 AM ---------- Previous post was at 07:38 AM ----------

It's a bit "geeky" but MediaCoder should be able to do what's necessary. It's just a matter of providing it the correct parameters.
[Google Chromecast] Asphyx:
LOL well unless you are resourceful, Software costs Money! (At least until someone proposes ObamaCode LOL)

There are a variety of free programs that can re-encode your files...

VLC has this capability built in.

https://forum.videolan.org/viewtopic.php?f=14&t=52483

Just make sure to select H264 and not WMV like it says in this post.

I personally use Xilisoft converter and the Xoom profile which is compatible with CCast apparently.

But it is a paid app.
[Google Chromecast] rkirmeier:
So you just found an incredible application/solution to solve all your video issues and the solution is very feature rich but you are too cheap to pay the $3.99/mth or just buy the lifetime pass? That is so pathetic! Not to say I don't have any free apps but if I find a great solution for something I use often I WANT TO SUPPORT THE DEVELOPER and pay for it!
[Google Chromecast] drivenby:
The chromecast just needs xbmc support and it will finally justify it's existence

.. Although I love the little gadget
[Google Chromecast] wptski:
Wel,l some don't want to go with Plex, Plex Pass, etc. because of the cost so one must transcode which could cost even more. If you get into FREE software you have to watch your *** or you can get malware, toolbars, etc., been there done that with Youtube downloaders. It's gotten to the point where I backup my system or at least create a system restore point when planning to download anything from CNET.
[Google Chromecast] Asphyx:
There is no place to see what gets transcoded and what doesn't.

It's a safe bet that anything that isn't H264 codec or MP4 filetype gets transcoded.

Plex knows what type of Video each file it has in it's library is in and transcodes it only when needed or when Bandwidth suggests a lower bitrate is required. I suspect the player sends performance and reception data back to the server so it can adjust to bandwidth situations when needed but it would also act on it unnoticed other than you might see a degradation f the quality due to the higher compression being used.

As for opening it up to non-PlexPass. It is possible that it will be available to all at some point because PlexPass membership gets you first crack at NEW features.

But if that were true in this case I wouldn't expect the Plex for Android app itself to have the feature released yet.

It doesn't seem likely that they would be able to turn features of an app on or off depending on Account status so easily.

But it is possible that they will and lets hope so!

So far the Plex system seems to work the best with the Chromecast.

it just works!

And with it there really is no need to save files locally on your unit except for playback in situations where there is no Net Access.

Something that may be requiring the PlexPass account is it adds cloudsync to your MyPlex and perhaps the Chromecast implementation is using that service to sync the file being sent to the Chromecast to a Google server that is acting as a go between for the Chromecast. But that would just be WILD GUESSING!

Doesn't seem like a good way to go about it if you ask me.