Chromecast

[Scoty]

Whene comes a Chromecast support?

I'm not sure what exactly you're looking for, but I regularly use my Chromecast with Serviio-hosted content. You need to be able to point at one with the other, which I do using BubbleUPnP on my phone (Android). The app lets you select both a library (in this case, my serviio server) and a renderer such as a DLNA-compatible TV, or a Chromecase (or any compatible device, of which where are many).

If you have an Android phone, give it a try (its free) - link below.

https://play.google.com/store/apps/details?id=com.bubblesoft.android.bubbleupnp&hl=en_GB

Chromecast from Servigo

I've had great success with playing videos from Servigo on an Android device using the BubbleUpNp app as well. Regardless of the library chosen select your BubbleUpNp renderer (Now Playing Tab) as your Chromecast device. After play/selecting the resolution of the video you wish to play in Servigo then in the "Complete Action Using" dialog choose "BubbleUpNp".

The Windows BubbleUpNp server is also essential as it will provide transcoding for video formats not supported by Chromecast.

[zip]

If you're using Chrome on Android, you should be able to cast using MediaBrowser too

[spudy12]

If you're using Chrome on Android, you should be able to cast using MediaBrowser too

Is there anyway to make this work with the chrome web browser on a laptop? I know you can cast the tab with google cast (https://chrome.google.com/webstore/deta ... pafd?hl=en) which works ok but some sites like iplayer have the cast button built in to the player?

[zip]

I think only the android HTML5 player has the button built in by default.

[spudy12]

I sometimes find when using the Chrome on and android device to cast to a TV that the MB doesnt fit well when the devices is vertical and you have to rotate it to get the layout working and access the button.

Tricky to explain, I will try and get a screenshot next time this happens

There might be some confusion where what might have been called 'Chromecast' is, on my PC Chrome setup, the 'Playto TV' button now, included with a YouTube video, for instance. I gather that the media being playto'd is queued to be sent directly from the YouTube server to your wireless router to your chromecast dongle (casted).

"GoogleCast" on PC Chrome now seems to do either of two things:
1) on a youtube page it acts as the playto TV button, or
2) 'casts' the entire web page from the browser to the Chromecast dongle (mirroring).
For 2 you see the entire page. As the entire page has to be formed by the browser then sent to the wireless router to the dongle I expect that using 'Google Cast for PC Chrome MediaBrowser' (mirroring) is quite futile over any use of serviio through DLNA (not MediaBrowser).

It looks to me that using the Android Chrome unnamed cast button using MediaBrowser (external machine url) or cnn.com/videos etc on the Android device that Android Chrome is queuing the resource to go directly from the serviio or cnn servers to the dongle to the TV (casting). That's like using Android Serviigo playto Bubble set to Chromecast device.

Serviio MediaBrowser on your PC browser (remote/open MediaBrowser) is wonderful. But until full casting support comes to PC Chrome or Serviio puts its own Chromecast button on its MediaBrowser player window, it's preferable to play serviio files 1) directly over DLNA or 2) full screen the Mediabrowser player on any PC browser on a Windows HDMI extended screen on your TV, than to to GoogleCast it on PC Chrome.

[spudy12]

There might be some confusion where what might have been called 'Chromecast' is, on my PC Chrome setup, the 'Playto TV' button now, included with a YouTube video, for instance. I gather that the media being playto'd is queued to be sent directly from the YouTube server to your wireless router to your chromecast dongle (casted).

"GoogleCast" on PC Chrome now seems to do either of two things:
1) on a youtube page it acts as the playto TV button, or
2) 'casts' the entire web page from the browser to the Chromecast dongle (mirroring).
For 2 you see the entire page. As the entire page has to be formed by the browser then sent to the wireless router to the dongle I expect that using 'Google Cast for PC Chrome MediaBrowser' (mirroring) is quite futile over any use of serviio through DLNA (not MediaBrowser).

It looks to me that using the Android Chrome unnamed cast button using MediaBrowser (external machine url) or cnn.com/videos etc on the Android device that Android Chrome is queuing the resource to go directly from the serviio or cnn servers to the dongle to the TV (casting). That's like using Android Serviigo playto Bubble set to Chromecast device.

Serviio MediaBrowser on your PC browser (remote/open MediaBrowser) is wonderful. But until full casting support comes to PC Chrome or Serviio puts its own Chromecast button on its MediaBrowser player window, it's preferable to play serviio files 1) directly over DLNA or 2) full screen the Mediabrowser player on any PC browser on a Windows HDMI extended screen on your TV, than to to GoogleCast it on PC Chrome.

I understand what you are saying about the way casting tabs and sending a direct URL to the chromecast works. There is a beta version of the android app serviigo that supports proper casting (send a url to a serviigo app on the chromecast)

Saying that I haven't had any issues casting the Mediabrowser tab to the chromecast. A few things to look out for though is, if you are using wireless on the computer casting the tab there can be stutter. Use a LAN cable wherever possible. Also, sometimes you have to full screen the video, make it small again and then switch back to full screen as its aspect ratio goes strange of the TV first time round

Of course proper serviio casting intergration would be ideal but I believe its a jwplayer problem rather than serviio.

Saying that I haven't had any issues casting the Mediabrowser tab to the chromecast. A few things to look out for though is, if you are using wireless on the computer casting the tab there can be stutter. Use a LAN cable wherever possible. Also, sometimes you have to full screen the video, make it small again and then switch back to full screen as its aspect ratio goes strange of the TV first time round

Of course proper serviio casting intergration would be ideal but I believe its a jwplayer problem rather than serviio.

I was trying to say that in that bit of extra distance that casting the Mediabrowser tab from PC Chrome
(on my system that is router to PC over ethernet, render in browser, PC back to router over ethernet)
goes through, as opposed to properly cast, there at least COULD be degradation. I see some degradation
on HD videos in comparisons between played on MPC directly and both on PC Browser screen and TV. But, perfection aside,
casting the Mediabrowser tab is certainly sufficient, convenient and entertaining and substitutes as "Chromecast support"
in Mediabrowser until the real stuff comes along.

I don't think a player manufacturer could know for sure the origin resource URL so he'd have great difficulty getting his branding there.

From another comment of yours it looks like Serviio MB is already almost properly there! Great! Thanks. Will look at the Serviigo beta.