Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #56919 > unrolled thread
| Started by | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| First post | 2018-10-30 02:16 +0100 |
| Last post | 2018-11-05 21:56 +0100 |
| Articles | 20 on this page of 41 — 11 participants |
Back to article view | Back to comp.mobile.android
Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-10-30 02:16 +0100
Re: Playing with the Chromecast Andy Burns <usenet@andyburns.uk> - 2018-10-30 07:22 +0000
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-10-30 11:23 +0100
Re: Playing with the Chromecast Andy Burns <usenet@andyburns.uk> - 2018-10-30 10:47 +0000
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-10-30 13:16 +0100
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-10-31 03:15 +0100
Re: Playing with the Chromecast "NY" <me@privacy.net> - 2018-10-31 11:00 +0000
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-10-31 12:37 +0100
Re: Playing with the Chromecast Frank Slootweg <this@ddress.is.invalid> - 2018-10-31 18:03 +0000
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-10-31 20:06 +0100
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-11-01 02:54 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-10-31 09:09 -0400
Re: Playing with the Chromecast Frank Slootweg <this@ddress.is.invalid> - 2018-10-31 18:13 +0000
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-10-31 19:56 +0100
Re: Playing with the Chromecast Calum <com.gmail@nospam.scottishwildcat> - 2018-11-01 14:04 +0000
Re: Playing with the Chromecast Joe Beanfish <joebeanfish@nospam.duh> - 2018-11-02 14:00 +0000
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-02 16:11 +0100
Re: Playing with the Chromecast Andy Burns <usenet@andyburns.uk> - 2018-11-02 15:24 +0000
Re: Playing with the Chromecast Andy Burns <usenet@andyburns.uk> - 2018-11-02 15:42 +0000
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-03 12:25 +0100
Re: Playing with the Chromecast Chris in Makati <mail@nospam.com> - 2018-11-03 21:19 +0800
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-03 15:08 +0100
Re: Playing with the Chromecast Chris in Makati <mail@nospam.com> - 2018-11-03 22:49 +0800
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-03 20:21 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-03 11:56 -0400
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-03 20:24 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-03 18:00 -0400
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-04 04:43 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-04 00:12 -0400
Re: Playing with the Chromecast Piet <www.godfatherof.nl/@opt-in.invalid> - 2018-11-04 11:19 +0100
Re: Playing with the Chromecast Kees Nuyt <k.nuyt@nospam.demon.nl> - 2018-11-04 16:22 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-04 10:44 -0400
Re: Playing with the Chromecast "Carlos E.R." <robin_listas@es.invalid> - 2018-11-05 11:11 +0100
Re: Playing with the Chromecast Piet <www.godfatherof.nl/@opt-in.invalid> - 2018-11-05 11:41 +0100
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-11-05 15:33 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-05 09:43 -0400
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-11-05 20:22 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-05 09:43 -0400
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-11-05 20:23 +0100
Re: Playing with the Chromecast nospam <nospam@nospam.invalid> - 2018-11-05 14:55 -0400
Re: Playing with the Chromecast "Carlos E. R." <robin_listas@es.invalid> - 2018-11-05 21:56 +0100
Page 1 of 3 [1] 2 3 Next page →
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-30 02:16 +0100 |
| Subject | Playing with the Chromecast |
| Message-ID | <g3ppmuF2h83U1@mid.individual.net> |
Hi,
I was purchasing a plain FM radio, chancing on the shop the day they did
a single day tax rebate. Looking around, I saw a boxfull of "chromecast"
gadgets, and treated myself to one (I don't have a smart TV).
I thought it would be like having Android on my TV, but it is not
exactly that. It is controlled via an app on the phone. On some apps,
like youtube I tap "send" and I get the display on the home TV instead.
Cute.
VLC can send.
So I browse on my localnet using FireFox to my local Apache server,
select a movie, select view with VLC, it starts playing on my phone,
send it to the chromecasst, and... I get the sound but not the video.
These are mpeg videos recorded from digital TV streams.
So I try a different kind of video, an AVI. It plays fine, both image
and sound although it complains a bit about requiring a lot of power.
I go back to the TV mpegs. No video, just sound. They play fine on the
phone though. So instead of "VLC" I try the Photos application. Well,
this time video works... silently, no sound.
Good grief.
Ideas?
I don't know if the decoding is done on the phone, and the phone just
sends the video to the chromecast, or if the gadget gets the command to
display a video and the URL. If it is the phone I don't like it.
--
Cheers,
Carlos E.R.
[toc] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2018-10-30 07:22 +0000 |
| Message-ID | <g3qf65F6jt4U1@mid.individual.net> |
| In reply to | #56919 |
Carlos E. R. wrote: > Ideas? convert the TV captures from transport stream to programme stream? Remove alternate audio and video streams that may be present? > I don't know if the decoding is done on the phone, and the phone just > sends the video to the chromecast The phone tells the chromecast to fetch the media for itself.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-30 11:23 +0100 |
| Message-ID | <v2olaf-ghk.ln1@Telcontar.valinor> |
| In reply to | #56921 |
On 30/10/2018 08.22, Andy Burns wrote: > Carlos E. R. wrote: > >> Ideas? > > convert the TV captures from transport stream to programme stream? > Remove alternate audio and video streams that may be present? > >> I don't know if the decoding is done on the phone, and the phone just >> sends the video to the chromecast > > The phone tells the chromecast to fetch the media for itself. > Apparently not always. Apparently the device supports few media types; if it is not supported, the stream is converted on the phone and then sent somehow. It is also possible to send the display from Chrome, I read. From computer as well. I found some links that I'm going to try. VLC supports is very recent, last July. <https://fossbytes.com/connect-vlc-chromecast-stream-from-pc/> There is also some indirect support with Kodi; the link I have is in Spanish, though. Maybe this one: <https://www.androidauthority.com/how-to-stream-kodi-chromecast-881349/> -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2018-10-30 10:47 +0000 |
| Message-ID | <g3qr5cF90umU1@mid.individual.net> |
| In reply to | #56923 |
Carlos E.R. wrote: > Apparently the device supports few media types; if it is not > supported, the stream is converted on the phone and then sent > somehow. I thought when you played from VLC on a phone or tablet, a cut-down version of VLC app got pushed to the chromecast to do the playback? Try rebooting the phone once playback has started on the chromecast, that'll tell you one way or the other. > It is also possible to send the display from Chrome, I read. From > computer as well. Yes, have used it that way too.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-30 13:16 +0100 |
| Message-ID | <7lulaf-cjp.ln1@Telcontar.valinor> |
| In reply to | #56924 |
On 30/10/2018 11.47, Andy Burns wrote:
>
> Carlos E.R. wrote:
>
>> Apparently the device supports few media types; if it is not
>> supported, the stream is converted on the phone and then sent
>> somehow.
>
> I thought when you played from VLC on a phone or tablet, a cut-down
> version of VLC app got pushed to the chromecast to do the playback? Try
> rebooting the phone once playback has started on the chromecast, that'll
> tell you one way or the other.
What I find on the web says that some play directly, some do not.
>> It is also possible to send the display from Chrome, I read. From
>> computer as well.
>
> Yes, have used it that way too.
Says "unable to cast file.mpeg". Doesn't like the video. In fact, it
doesn't list the files as videos unless I select "display all files".
+++-------------
<https://fossbytes.com/connect-vlc-chromecast-stream-from-pc/>
Google Chrome
Streaming local files to Chromcast using Google Chrome is a no-brainer.
Open the Cast option > click on Cast to > Cast file. Choose the desired
file. However, you may not be able to do much as the file support is
limited.
-------------++-
Then it says:
+++-------------
Videostream (Chrome, Android, iOS)
Videostream is a promising solution to consider when VLC’s Chromecast on
PC support sucks because it sucks. You can install the extension from
the Chrome Store and watch your movies, music, and images. It’s also
available as an app for Android and iOS.
-------------++-
It needs a chrome extension to be running (it insists on my login to
chrome, which I refuse, so I have to insist). I can send a video to the
device and it plays, some times. Not all of them: one in particular it
starts then stops. Some stutter. Needs opening ports tcp 5556 and 5558
on the computer. Works on Linux, too.
The Android app just controls the thing. That is, I start Chrome and the
extension on the computer that holds the files, then use the app on the
phone or tablet to choose a movie and "send" it.
I also tried the method here:
<https://www.androidauthority.com/how-to-stream-kodi-chromecast-881349/>
to use kodi ("The advanced, power-saving method" section). Well, kodi
crashes.
The method needs the "The LocalCast for Chromecast app", which can also
be used standalone to cast local (to the phone) videos. When I try these
mpeg files it refuses and a message pops up on the TV with several
options, that basically mean the stream is not supported by the
chromecast. I'm sitting on a different room, so I can't copy the message
verbatim just now.
There is another set of instructions on "How to stream Kodi to
Chromecast from PC"
+++-------------
Streaming content from Kodi to your PC is a breeze. Just open the Chrome
browser, click the menu icon in the top-right corner (three vertical
dots), and select the “Cast” option. The next step is to choose “Cast
to” followed by “Cast desktop.” Then just select the name of your
Chromecast device from the list and click the “Share” button, which will
mirror the PC’s screen to your TV. This means when you open Kodi, it
will show up on your big screen.
-------------++-
I do not like this method... For one, the control is on the computer, no
control on the TV room at all. And it will work with the computer
resolution.
It seems that it is also possible to run VLC on the computer and send to
chromecast.
<https://fossbytes.com/connect-vlc-chromecast-stream-from-pc/>
+++-------------
Follow the steps mentioned below:
Make sure you Chromecast is turned on and running fine.
Open VLC on your Windows machine. Make sure you’re running VLC 3.0
or above.
Click on Playback.
Hover the mouse pointer on Renderer; it’ll show the list of
Chromecast devices available.
Choose your preferred device.
VLC Chromecast Stream 1
Now, play your favorite media file to cast it on your TV screen. In
order for the casting to work, you need to allow VLC through the Windows
Firewall.
The playback experience is mixed. Some files work without any issue, but
conversion happens for the ones not compatible with Chromecast. Also,
users might get annoyed as subtitles don’t appear on the screen for some
reason.
-------------++-
But I do not have version 3 on computer.
--
Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-31 03:15 +0100 |
| Message-ID | <sqfnaf-cp5.ln1@Telcontar.valinor> |
| In reply to | #56926 |
On 30/10/2018 13.16, Carlos E.R. wrote: > There is another set of instructions on "How to stream Kodi to > Chromecast from PC" > > +++------------- > Streaming content from Kodi to your PC is a breeze. Just open the Chrome > browser, click the menu icon in the top-right corner (three vertical > dots), and select the “Cast” option. The next step is to choose “Cast > to” followed by “Cast desktop.” Then just select the name of your > Chromecast device from the list and click the “Share” button, which will > mirror the PC’s screen to your TV. This means when you open Kodi, it > will show up on your big screen. > -------------++- > > I do not like this method... For one, the control is on the computer, no > control on the TV room at all. And it will work with the computer > resolution. Also, found out that the Amazon Prime Video app does not "cast". Apparently it is not a technical issue, but some disagreement between google and Android. It sucks. The Chrome browser on a computer can "cast" a tab or the window or the full screen, with sound. So (I think) anything that plays in Chrome can be sent to the device, up to 1080 resolution, no more. This does allow to view Amazon videos on the TV, at the same time silently playing on the computer, which needs some power to do the job. And some bandwidth. The funny thing is that articles that I found about how cast Amazon Video (article updated last week) said to install an extension on Chrome from certain link, which now says the extension is discontinued - but apparently Chrome now comes out of the box with that capability. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | "NY" <me@privacy.net> |
|---|---|
| Date | 2018-10-31 11:00 +0000 |
| Message-ID | <JpadnUzcTOcUFkTGnZ2dnUU78SnNnZ2d@brightview.co.uk> |
| In reply to | #56945 |
"Carlos E.R." <robin_listas@es.invalid> wrote in message news:sqfnaf-cp5.ln1@Telcontar.valinor... > The funny thing is that articles that I found about how cast Amazon > Video (article updated last week) said to install an extension on Chrome > from certain link, which now says the extension is discontinued - but > apparently Chrome now comes out of the box with that capability. All this casting, streaming and transcoding is overcomplicating the issue. Why can't they have a universal player (similar to VLC) in the TV and an SMB client which can access a shared drive on the "server" device (computer or NAS). When I get my Roku box's Plex client to access my Windows PC running Plex server, the Windows PC's CPU goes through the roof, especially when playing H264 (even sub-SD, never mind HD). The same PC can play the original TS file (MPEG or H264) without breaking out into a sweat, so the load of reading the file and displaying it is trivial compared with whatever Plex does. And it's not the added overhead of reading over the LAN, because another Windows PC can access the file on an SMB-shared drive on the "server" without the server going mental. VLC player and SMB sharing allows the playing device (at the TV) to control things like resolution, playback speed, when to pause, when to wind back to watch a bit again, without the need to control playback from another device (the server) which may be physically remote, so you need SSH or VNC to access it from the room where the player is.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-31 12:37 +0100 |
| Message-ID | <npgoaf-k99.ln1@Telcontar.valinor> |
| In reply to | #56965 |
On 31/10/2018 12.00, NY wrote: > "Carlos E.R." <robin_listas@es.invalid> wrote in message > news:sqfnaf-cp5.ln1@Telcontar.valinor... >> The funny thing is that articles that I found about how cast Amazon >> Video (article updated last week) said to install an extension on Chrome >> from certain link, which now says the extension is discontinued - but >> apparently Chrome now comes out of the box with that capability. > > All this casting, streaming and transcoding is overcomplicating the > issue. Why can't they have a universal player (similar to VLC) in the TV > and an SMB client which can access a shared drive on the "server" device > (computer or NAS). Oh, I agree. But apparently the chromecast device does things differently. Yes, it has a player inside, but its capability is limited. Maybe the hardware is also limited. And I did not know it in advance. > When I get my Roku box's Plex client to access my > Windows PC running Plex server, the Windows PC's CPU goes through the > roof, especially when playing H264 (even sub-SD, never mind HD). The > same PC can play the original TS file (MPEG or H264) without breaking > out into a sweat, so the load of reading the file and displaying it is > trivial compared with whatever Plex does. And it's not the added > overhead of reading over the LAN, because another Windows PC can access > the file on an SMB-shared drive on the "server" without the server going > mental. > > VLC player and SMB sharing allows the playing device (at the TV) to > control things like resolution, playback speed, when to pause, when to > wind back to watch a bit again, without the need to control playback > from another device (the server) which may be physically remote, so you > need SSH or VNC to access it from the room where the player is. VLC does work with this gadget, but not with all files. Apparently the decoding happens on the chromecast, but not always. Sometimes it is decoded on the phone or tablet and sent to the device somehow. It can play files that are locally stored on the tablet and shown on the TV, so somehow the tablet sends the file to the chromecast device. I do not know if it is sent decoded or as is. If the file is on a shared drive, I do not know yet if it is sent to the TV or to the tablet. Many unknowns. Had I known, perhaps I would not have bought it. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2018-10-31 18:03 +0000 |
| Message-ID | <prcuak.omc.1@ID-201911.user.individual.net> |
| In reply to | #56972 |
Carlos E.R. <robin_listas@es.invalid> wrote: > On 31/10/2018 12.00, NY wrote: > > "Carlos E.R." <robin_listas@es.invalid> wrote in message > > news:sqfnaf-cp5.ln1@Telcontar.valinor... > >> The funny thing is that articles that I found about how cast Amazon > >> Video (article updated last week) said to install an extension on Chrome > >> from certain link, which now says the extension is discontinued - but > >> apparently Chrome now comes out of the box with that capability. > > > > All this casting, streaming and transcoding is overcomplicating the > > issue. Why can't they have a universal player (similar to VLC) in the TV > > and an SMB client which can access a shared drive on the "server" device > > (computer or NAS). > > Oh, I agree. But apparently the chromecast device does things differently. > > Yes, it has a player inside, but its capability is limited. Maybe the > hardware is also limited. > > And I did not know it in advance. > > > When I get my Roku box's Plex client to access my > > Windows PC running Plex server, the Windows PC's CPU goes through the > > roof, especially when playing H264 (even sub-SD, never mind HD). The > > same PC can play the original TS file (MPEG or H264) without breaking > > out into a sweat, so the load of reading the file and displaying it is > > trivial compared with whatever Plex does. And it's not the added > > overhead of reading over the LAN, because another Windows PC can access > > the file on an SMB-shared drive on the "server" without the server going > > mental. > > > > VLC player and SMB sharing allows the playing device (at the TV) to > > control things like resolution, playback speed, when to pause, when to > > wind back to watch a bit again, without the need to control playback > > from another device (the server) which may be physically remote, so you > > need SSH or VNC to access it from the room where the player is. > > > VLC does work with this gadget, but not with all files. Apparently the > decoding happens on the chromecast, but not always. Sometimes it is > decoded on the phone or tablet and sent to the device somehow. > > It can play files that are locally stored on the tablet and shown on the > TV, so somehow the tablet sends the file to the chromecast device. I do > not know if it is sent decoded or as is. If the file is on a shared > drive, I do not know yet if it is sent to the TV or to the tablet. > > Had I known, perhaps I would not have bought it. Have a look at: 'BubbleUPnP for DLNA / Chromecast / Smart TV' <https://play.google.com/store/apps/details?id=com.bubblesoft.android.bubbleupnp>
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-31 20:06 +0100 |
| Message-ID | <g3ucplF43oeU1@mid.individual.net> |
| In reply to | #56988 |
On 31/10/2018 19.03, Frank Slootweg wrote:
> Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 31/10/2018 12.00, NY wrote:
>>> "Carlos E.R." <robin_listas@es.invalid> wrote in message
>>> news:sqfnaf-cp5.ln1@Telcontar.valinor...
>>>> The funny thing is that articles that I found about how cast Amazon
>>>> Video (article updated last week) said to install an extension on Chrome
>>>> from certain link, which now says the extension is discontinued - but
>>>> apparently Chrome now comes out of the box with that capability.
>>>
>>> All this casting, streaming and transcoding is overcomplicating the
>>> issue. Why can't they have a universal player (similar to VLC) in the TV
>>> and an SMB client which can access a shared drive on the "server" device
>>> (computer or NAS).
>>
>> Oh, I agree. But apparently the chromecast device does things differently.
>>
>> Yes, it has a player inside, but its capability is limited. Maybe the
>> hardware is also limited.
>>
>> And I did not know it in advance.
>>
>>> When I get my Roku box's Plex client to access my
>>> Windows PC running Plex server, the Windows PC's CPU goes through the
>>> roof, especially when playing H264 (even sub-SD, never mind HD). The
>>> same PC can play the original TS file (MPEG or H264) without breaking
>>> out into a sweat, so the load of reading the file and displaying it is
>>> trivial compared with whatever Plex does. And it's not the added
>>> overhead of reading over the LAN, because another Windows PC can access
>>> the file on an SMB-shared drive on the "server" without the server going
>>> mental.
>>>
>>> VLC player and SMB sharing allows the playing device (at the TV) to
>>> control things like resolution, playback speed, when to pause, when to
>>> wind back to watch a bit again, without the need to control playback
>>> from another device (the server) which may be physically remote, so you
>>> need SSH or VNC to access it from the room where the player is.
>>
>>
>> VLC does work with this gadget, but not with all files. Apparently the
>> decoding happens on the chromecast, but not always. Sometimes it is
>> decoded on the phone or tablet and sent to the device somehow.
>>
>> It can play files that are locally stored on the tablet and shown on the
>> TV, so somehow the tablet sends the file to the chromecast device. I do
>> not know if it is sent decoded or as is. If the file is on a shared
>> drive, I do not know yet if it is sent to the TV or to the tablet.
>>
>> Had I known, perhaps I would not have bought it.
>
> Have a look at:
>
> 'BubbleUPnP for DLNA / Chromecast / Smart TV'
> <https://play.google.com/store/apps/details?id=com.bubblesoft.android.bubbleupnp>
It looks interesting.
I don't know from reading the description if I have to provide the files
necessarily via UPnP/DLNA. Currently I have set up http or ssh. Maybe smb.
Maybe kodi on the server would provide UPnP/DLNA? I think I read about it.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-11-01 02:54 +0100 |
| Message-ID | <g3v4neF8pu7U1@mid.individual.net> |
| In reply to | #56994 |
On 31/10/2018 20.06, Carlos E. R. wrote:
> On 31/10/2018 19.03, Frank Slootweg wrote:
>> Have a look at:
>>
>> 'BubbleUPnP for DLNA / Chromecast / Smart TV'
>> <https://play.google.com/store/apps/details?id=com.bubblesoft.android.bubbleupnp>
>
> It looks interesting.
>
> I don't know from reading the description if I have to provide the files
> necessarily via UPnP/DLNA. Currently I have set up http or ssh. Maybe smb.
>
> Maybe kodi on the server would provide UPnP/DLNA? I think I read about it.
Well, it took sometime to setup. Yes, Kodi can do DLN/UPnP. I had to
stop another tool that was also doing DLNA and possibly conflicting,
which allows to watch the TV on the tablet (works). I also had to
disable the firewall on the file server for everything incoming from the
tablet - it is not clear what ports are needed for dlna and chromecast.
Finally, the tablet (BubleUPnP) saw the video collection of kodi and
offered to watch it.
BubleUPnP can use its internal rendered or a local one, VLC. And VLC can
not cast certain videos to Chromecast. Or BubleUPnP can use use its own
renderer.
Both cases are the same: sound, no video on the TV.
There was a message that popped up for a few seconds, not enough to read
it, that transcoding was limited to 20 minutes and ... the rest I could
not read. Ah, tried a second time: that I have to purchase the app to
get more minutes. What for, if it doesn't play my videos? Good grief.
At some point it said that some player named MX was the best as
external. I installed it, but apparently MX can not play my files even
if stored on the tablet, and can not cast on its own either.
So, no good either of those two apps.
The good thing, I learnt how to do dlna.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2018-10-31 09:09 -0400 |
| Message-ID | <311020180909285446%nospam@nospam.invalid> |
| In reply to | #56965 |
In article <JpadnUzcTOcUFkTGnZ2dnUU78SnNnZ2d@brightview.co.uk>, NY <me@privacy.net> wrote: > All this casting, streaming and transcoding is overcomplicating the issue. it isn't. it's actually simplifying things. > Why can't they have a universal player (similar to VLC) in the TV and an SMB > client which can access a shared drive on the "server" device (computer or > NAS). because there are better solutions. > When I get my Roku box's Plex client to access my Windows PC running > Plex server, the Windows PC's CPU goes through the roof, especially when > playing H264 (even sub-SD, never mind HD). plex is transcoding it on the fly, and if you're watching tv, why do you care what the pc is doing? but if you do, put the media on a nas, one which has hardware transcoding. problem solved. some nases even have hdmi out, so you can go directly to the tv.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2018-10-31 18:13 +0000 |
| Message-ID | <prcurp.omc.1@ID-201911.user.individual.net> |
| In reply to | #56965 |
NY <me@privacy.net> wrote: [...] > All this casting, streaming and transcoding is overcomplicating the issue. > Why can't they have a universal player (similar to VLC) in the TV and an SMB > client which can access a shared drive on the "server" device (computer or > NAS). The problem with such an approach is that the software/firmware in the TV gets outdated very quickly and is often only updated for a very short time, making an expensive TV effectively obsolete. I had three such 'media players' which were quickly obsolete. No more of that nonsense, so now I only use general purpose 'computers' (Android tablet or/and Windows PC) for that purpose. [...] > VLC player and SMB sharing allows the playing device (at the TV) to control > things like resolution, playback speed, when to pause, when to wind back to > watch a bit again, without the need to control playback from another device > (the server) which may be physically remote, so you need SSH or VNC to > access it from the room where the player is. Or use a tablet as your player or/and remote control.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-10-31 19:56 +0100 |
| Message-ID | <g3uc7lF4004U1@mid.individual.net> |
| In reply to | #56990 |
On 31/10/2018 19.13, Frank Slootweg wrote:
> NY <me@privacy.net> wrote:
> [...]
>> All this casting, streaming and transcoding is overcomplicating the issue.
>> Why can't they have a universal player (similar to VLC) in the TV and an SMB
>> client which can access a shared drive on the "server" device (computer or
>> NAS).
>
> The problem with such an approach is that the software/firmware in the
> TV gets outdated very quickly and is often only updated for a very short
> time, making an expensive TV effectively obsolete.
Yep.
> I had three such 'media players' which were quickly obsolete. No more
> of that nonsense, so now I only use general purpose 'computers' (Android
> tablet or/and Windows PC) for that purpose.
Well, that was what I intended with the Chromecast. Not as expensive as
a dedicated computer on the sitting room. I thought it would work as any
Android device. But no.
> [...]
>
>> VLC player and SMB sharing allows the playing device (at the TV) to control
>> things like resolution, playback speed, when to pause, when to wind back to
>> watch a bit again, without the need to control playback from another device
>> (the server) which may be physically remote, so you need SSH or VNC to
>> access it from the room where the player is.
>
> Or use a tablet as your player or/and remote control.
Yes, a tablet to watch videos is what I used, but I wanted to see them
on the big screen.
And yes, basically the tablet or phone work as a remote control.
Some months ago I purchased and Android box via Amazon, but I had to
return it when I found that it was "rooted", a fact that was not
described on the Amazon page. Being rooted, google play would not work.
I received an email from the dealer saying that I had to download apps
from another site instead - thus it was doubtful I could run fully legal
and original apps to play Amazon Prime Video or Netflix or the local TV
station apps.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Calum <com.gmail@nospam.scottishwildcat> |
|---|---|
| Date | 2018-11-01 14:04 +0000 |
| Message-ID | <prf15t$5gl$1@gioia.aioe.org> |
| In reply to | #56965 |
On 31/10/2018 11:00, NY wrote: > All this casting, streaming and transcoding is overcomplicating the > issue. Why can't they have a universal player (similar to VLC) in the TV > and an SMB client which can access a shared drive on the "server" device > (computer or NAS). They can. Android TV boxes, such as the nVidia Shield TV, can do just that.
[toc] | [prev] | [next] | [standalone]
| From | Joe Beanfish <joebeanfish@nospam.duh> |
|---|---|
| Date | 2018-11-02 14:00 +0000 |
| Message-ID | <prhla6$tgm$1@dont-email.me> |
| In reply to | #57020 |
On Thu, 01 Nov 2018 14:04:46 +0000, Calum wrote: > On 31/10/2018 11:00, NY wrote: > >> All this casting, streaming and transcoding is overcomplicating the >> issue. Why can't they have a universal player (similar to VLC) in the TV >> and an SMB client which can access a shared drive on the "server" device >> (computer or NAS). > > They can. Android TV boxes, such as the nVidia Shield TV, can do just that. Perhaps, but ouch, quite a lot more $ than chromecast. Especially for us cheapskates and poor people.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-11-02 16:11 +0100 |
| Message-ID | <416uaf-oac.ln1@Telcontar.valinor> |
| In reply to | #57049 |
On 02/11/2018 15.00, Joe Beanfish wrote: > On Thu, 01 Nov 2018 14:04:46 +0000, Calum wrote: > >> On 31/10/2018 11:00, NY wrote: >> >>> All this casting, streaming and transcoding is overcomplicating the >>> issue. Why can't they have a universal player (similar to VLC) in the TV >>> and an SMB client which can access a shared drive on the "server" device >>> (computer or NAS). >> >> They can. Android TV boxes, such as the nVidia Shield TV, can do just that. > > Perhaps, but ouch, quite a lot more $ than chromecast. Especially for us > cheapskates and poor people. Absolutely! In retrospect, I'm not happy with the purchase. The idea is not bad, in fact, I find it cute. The thing has no keyboard or remote controller. It is small, hangs behind the TV out of sight. I'm still surprised at how it is possible to configure it without a cable or something to enter the wifi password. I suspect it connects to the phone via bluetooth at first. It also creates a wifi access point of its own, perhaps not encrypted, during initial setup. The problem is that it supports few video types, the hardware or the firmware is too limited. The bypass solution is to transcode those difficult videos on the phone or the computer, but there is little support yet for doing it. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2018-11-02 15:24 +0000 |
| Message-ID | <g438giF4h68U1@mid.individual.net> |
| In reply to | #57050 |
Carlos E.R. wrote: > I'm still surprised at how it is possible to configure it without a > cable or something to enter the wifi password. I suspect it connects > to the phone via bluetooth at first. No, the initial connection uses the chromecast's temporary AP (which you mentioned) then after confirming the 4 digit code shown on-screen, it sends the ssid/password of your home WiFi to it and it re-connects as a client device.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2018-11-02 15:42 +0000 |
| Message-ID | <g439jtF4mp8U1@mid.individual.net> |
| In reply to | #57050 |
Carlos E.R. wrote: > I suspect it connects to the phone via bluetooth at first. Seems the newer chromecasts can connect that way, but my older one doesn't have BT and the setup process goes well with just WiFi.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2018-11-03 12:25 +0100 |
| Message-ID | <37d0bf-6m4.ln1@Telcontar.valinor> |
| In reply to | #57053 |
On 02/11/2018 16.42, Andy Burns wrote: > Carlos E.R. wrote: > >> I suspect it connects to the phone via bluetooth at first. > > Seems the newer chromecasts can connect that way, but my older one > doesn't have BT and the setup process goes well with just WiFi. This is the improved model, Ultra(?), which also has ethernet. The cable would connect to the power supply, so the power cable carries the signal to the device. But I do not have an ethernet socket free at the moment, I may need to place a switch there. The instructions mention that BT is needed for apple phones. The setup process requests location to be activated. Anyway, the setup process is surprisingly easy. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | comp.mobile.android
csiph-web