Paid for Cast to Chromecast.. Can't cast at all #274
Comments
|
I am facing the same issue here. |
|
Same issue here too. Always getting this in the log: "HTSService, Connect to server requested" |
|
Same situation here... Far out the best and complete tvheadend client I tested, and cast to chromecast support is awesome. And as such have no problem supporting the developer for his efforts by buying the extra features. Please just make sure it works :-) Thanks |
|
Thanks for the information. I implemented and tested the chromecast functionality with the profile setting from a swedish guy that let me use his server to test the feature. It was working with the shown profile. The same is shown in the google+ group. His server was at least a core duo to transcode the stuff on the fly. I really can't test the feature myself and rely on others because my server is a raspberry pi B.
|
|
Ok let me test this tonight.
Can one profile have multiple parameters settings? Will the client self be able to detect the right one?
Sent from my mobile phone.
-------- Oprindelig besked --------Fra: Robert Siebert <notifications@github.com> Dato: 01/12/2016 15.57 (GMT+01:00) Til: rsiebert/TVHClient <TVHClient@noreply.github.com> Cc: Osberg <osberg@outlook.dk>, Comment <comment@noreply.github.com> Emne: Re: [rsiebert/TVHClient] Paid for Cast to Chromecast.. Can't cast at all (#274)
Thanks for the information. I implemented and tested the chromecast functionality with the profile setting from a swedish guy that let me use his server to test the feature. It was working with the shown profile. The same is shown in the google+ group. His server was at least a core duo to transcode the stuff on the fly.
I really can't test the feature myself and rely on others because my server is a raspberry pi B.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rsiebert/TVHClient","title":"rsiebert/TVHClient","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rsiebert/TVHClient"}},"updates":{"snippets":[{"icon":"PERSON","message":"@rsiebert in #274: Thanks for the information. I implemented and tested the chromecast functionality with the profile setting from a swedish guy that let me use his server to test the feature. It was working with the shown profile. The same is shown in the google+ group. His server was at least a core duo to transcode the stuff on the fly.\r\n\r\nI really can't test the feature myself and rely on others because my server is a raspberry pi B.\r\n\r\n\r\n"}],"action":{"name":"View Issue","url":"#274 (comment)"}}}
|
|
I already tried that profile configuration before and it did not work for me either. I have also tried all kinds of profile configurations and I have not managed to make any of them work :/ TVHeadend 4.1.2309 over a Synology DS216+II with DSM6. |
|
Hi, I tried with the settings shown by creating a new streaming profile. Nonetheless, the transcoding to tvhclient itself works, but the moment I cast to the chromecast it fails. 2016-12-02 02:46:28.668 [ ERROR] http: 10.50.99.104: HTTP/1.1 GET /imagecache/9 -- 401 Might it be that the chromecast connects with a particular user which must be created in tvheadend ? tvheadend: version 4.1 (no idea about the build for unstable ubuntu) on i7 (so transcoding is not an issue here |
|
Just a side note.. is anybody else having trouble getting the APT DEB
packages for trusty at all? I keep getting a 503 error when I do a "apt-get
update"
…On Fri, Dec 2, 2016 at 12:22 PM, trantoriana ***@***.***> wrote:
Hi,
I tried with the settings shown by creating a new streaming profile.
(I am not sure whether my tvheadend is older because I do not have a
transcoding section in the settings, all settings are set under Basic
Settings).
Nonetheless, the transcoding to tvhclient itself works, but the moment I
cast to the chromecast it fails.
It seems to be related to credentials, as the log file shows:
2016-12-02 02:46:28.668 [ ERROR] http: 10.50.99.104: HTTP/1.1 GET
/imagecache/9 -- 401
Might it be that the chromecast connects with a particular user which must
be created in tvheadend ?
tvheadend: version 4.1 (no idea about the build for unstable ubuntu) on i7
(so transcoding is not an issue here
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtAkHpJtXNqPvlD3KqZY2lOJgWI_uE5ks5rD3nHgaJpZM4K5DS9>
.
|
|
@phoniclynx the unstable one works, I had similar issues with stable&release packages on ubuntu |
|
@phoniclynx hmm, even unstable seems to have an issue right now: W: The repository 'https://dl.bintray.com/tvheadend/ubuntu unstable Release' does not have a Release file. |
|
I have unstable and trusty defined in my sources.list file. Which is why im
so confused
…On Fri, 2 Dec 2016, 12:25 trantoriana ***@***.***> wrote:
@phoniclynx <https://github.com/phoniclynx> the unstable one works, I had
similar issues with stable&release packages on ubuntu
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtAkBlXP1L9wYRwdB4kv7QtdjxEn3elks5rD3qlgaJpZM4K5DS9>
.
|
|
good good.. as long as it's not just me doing something wrong.. I want to
try these new settings suggested above.
…On Fri, Dec 2, 2016 at 12:27 PM, trantoriana ***@***.***> wrote:
@phoniclynx <https://github.com/phoniclynx> hmm, even unstable seems to
have an issue right now:
W: The repository 'https://dl.bintray.com/tvheadend/ubuntu unstable
Release' does not have a Release file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtAkGxh91E9yqrK-mJovbXP9oXknOgbks5rD3r_gaJpZM4K5DS9>
.
|
|
i also have the issue with upgrading the tvheadend on my ubuntu. I have made a task in there fora about this : https://tvheadend.org/boards/5/topics/23757 |
|
@BlindOSX The Synology is probably not strong enough to allow real time transcoding. The hardware transcoding feature can be used with the video station. But I doubt that the tvheadend server can use these features. |
|
@rsiebert I'm 99% sure that's not the problem. SW Transcoding works well on my Syno. If I just copy the URL from the log that TVHClient is trying to cast and open it with VLC on my Mac, it plays without problems. |
|
I have the same issue, my problem may be HW it is a 4 core i5-2430M CPU @ 2.40GHz - should be enough I think. |
|
I got an important tip from the first casting user. Here is his mail: "Add a user with username * and set allow streaming, and set allow only local network. Please try that. Hope it helps. |
|
Hi, some screenshots for the post above, this works for me. Add a user like this, username * And empty password Check your streaming settings. |
|
Ok, the repository failure on bintray I fixed using: echo deb https://dl.bintray.com/dreamcat4/ubuntu master main | sudo tee -a /etc/apt/sources.list Upgraded to 4.1-2347 (looks really different)... Still no luck at all. Using the chromecast with plex work, so the chromecast is accessing the network just fine.... Any further ideas how to go about ? |
|
Also, I confirm anonymous access to work using the wildcard user.... Either tvclient cannot connect to the chromecast and transfer the channel URL or the chromecast cannot connect to tvheadend using the URl it got. My tip would be on the first... |
|
@trantoriana unfortunately I can't use that apt source because I am using
Trusty and that source list must be for Xenial. You wouldn't happen to know
one for Trusty by any chance?
…On Mon, Dec 5, 2016 at 10:36 AM, trantoriana ***@***.***> wrote:
Also, I confirm anonymous access to work using the wildcard user....
The failure is not related to the settings of that user...
Either tvclient cannot connect to the chromecast and transfer the channel
URL or the chromecast cannot connect to tvheadend using the URl it got.
My tip would be on the first...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtAkBEV7eC8XYG7bHaSf8JnIVJHTxITks5rE1V5gaJpZM4K5DS9>
.
|
|
I see an initial conection in the log when trying to cast GET
stream/chanelnumber and that is it.
When the phone plays the same channel there are a number of followig
messages.
…On 4 December 2016 at 19:06, trantoriana ***@***.***> wrote:
Also, I confirm anonymous access to work using the wildcard user....
The failure is not related to the settings of that user...
Either tvclient cannot connect to the chromecast and transfer the channel
URL or the chromecast cannot connect to tvheadend using the URl it got.
My tip would be on the first...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACjXDN5D6a4RxEtqWIQJul6jo4c_YVCuks5rE1V5gaJpZM4K5DS9>
.
--
Mike Holmes
Program Manager - Linaro Networking Group
Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
"Work should be fun and collaborative, the rest follows"
|
|
Maybe it is related to #276 where the webroot information is missing in the casting url. |
|
My guess is that the some casting setup don't work because the local DNS name is used in the configurations and the URL passed to the chromecast keys uses such name. This is unusable for the chromecast keys because, as widely note, they use the google DNS bypassing the local ones. TVHClient should use the ip address in the URL passed to the chromecast at least when a local name is detected. my 2¢ |
|
I've got the same issue here. Is anything new that could solve casting to Chromecast issue? |
|
There is a program called Bubble uPnP which does a nice job of it. Just you
need a transcoding server in between to make it work
…On 26 May 2017 at 15:58, sei4eto ***@***.***> wrote:
I've got the same issue here. Is anything new that could solve casting to
Chromecast issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtAkLJJfN8q1SmITxF_Njh0kl1TTPGJks5r9nEggaJpZM4K5DS9>
.
|
|
@phoniclynx tvheadend already provide transcoding. The only issue that has to be addressed by @rsiebert is the use of local-dns names: a quiet common scenario. Note that it is not enough to use the ip-address of the tvheadend server in the tvhclient configuration: my guess is that tvheadend reports urls using its local-dns name. |
|
I know for that app - BubleUpNP. I've got it. But it cannot use TVH server as a source. |
|
That's why you need the BuPnP Transcoder to translate it into a format that
the chrome cast can understand.Then you use the DLNA side of TVH
…On 26 May 2017 at 16:55, sei4eto ***@***.***> wrote:
I know for that app - BubleUpNP. I've got it. But it cannot use TVH server
as a source.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADtAkE4lV8cXBnyGtf6vG53998r5j0m4ks5r9n5-gaJpZM4K5DS9>
.
|
|
If I understand right, I need to use the IP address in the casting URL instead of a hostname? |
|
@rsiebert: you are right! This is strictly necessary for local streaming but it should be fine also for remote streaming (I can't imagine a scenario where you are using virtual hosting and you need to keep the dns name...). |
|
So it should also work (as a test) if an ipaddress was specified in the
connection settings.
Mario Di Raimondo <notifications@github.com> schrieb am Sa., 27. Mai 2017,
12:26:
… @rsiebert <https://github.com/rsiebert>: you are right! This is strictly
necessary for local streaming but it should be fine also for remote
streaming (I can't imagine a scenario where you are using virtual hosting
and you need to keep the dns name...).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABV38CyNyV7V2FA3cmxOrpIjusj6LYQWks5r9_pWgaJpZM4K5DS9>
.
|
|
What to you mean? Where should IP address have to be specified?
Sent from Note 2
On 27 May 2017 18:24, "Robert Siebert" <notifications@github.com> wrote:
So it should also work (as a test) if an ipaddress was specified in the
connection settings.
Mario Di Raimondo <notifications@github.com> schrieb am Sa., 27. Mai 2017,
12:26:
@rsiebert <https://github.com/rsiebert>: you are right! This is strictly
necessary for local streaming but it should be fine also for remote
streaming (I can't imagine a scenario where you are using virtual hosting
and you need to keep the dns name...).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABV38CyNyV7V2FA3cmxOrpIjusj6LYQWks5r9_pWgaJpZM4K5DS9>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIlI8RO8U0LPExZVZO-VuLyyn0ZcKRpks5r-EA4gaJpZM4K5DS9>
.
|
|
@rsiebert I suspect that if you just use the ip address in the tvhclient configuration, the URL provided by tvheadend still uses the dns name. I can't check, could you? Update: sorry, I can confirm that to use the ip address of the server in the tvhclient configuration is enough to make it works. I would suggest to add a warning or to make the automatic translation for the chromecast urls (less reports for you). |
|
I can check this.
Mario Di Raimondo <notifications@github.com> schrieb am Sa., 27. Mai 2017,
19:21:
… @rsiebert <https://github.com/rsiebert> I suspect that if you just use
the ip address in the tvhclient configuration, the URL provided by
tvheadend still uses the dns name. I can't check, could you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABV38Pg0Y_MNTftiJTTzTzZO_DZP79pGks5r-FuPgaJpZM4K5DS9>
.
|
|
Hi, thanks for the great app! Just thought I'd resurrect this issue though, has anyone managed to get Chromecast to work? |
|
@benmooney92 Waiting for a fix, you can just use the local ip address of your TVH server in the configuration of the app: it should work with any Chromecast key in local network. |
|
Ok thanks, I'll give it a go and post back! |
|
Don't known if this still an issue... found this comment:
Obviously this open wildcard user is neither needed nor desirable for good reasons. A better approach would be to fetch an auth ticket using HTSP getTicket(). Afterwards you could use this ticket to pass an "open" URL to Chromecast w/o authentication issues, e.g. Cheers, |
|
@rsiebert I have created a Wiki page: https://github.com/rsiebert/TVHClient/wiki/Using-Google-Chromecast Hope you can implemented the requirements for removing |
|
|
|
Unfortunately nothing in here has worked for me (transcoding or raw). I have even tried transcoding my original files to a format that Chromecast can play, but the app just crashes as soon as I attempt to play a recording. |
|
Did anyone test the beta version? Many users got casting to work there. There were also changes to the code. |
|
I just installed the beta. I only tested streaming inside my own network and with user auth (not anonymous). I still need to fine tune my settings to get better quality and performance. @francoism90 btw: you can just copy&paste screenshots from clipboard into the github editor. |
![https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open](https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open){kind=link}
![https://cloud.githubusercontent.com/assets/1406960/20798286/a26de194-b7de-11e6-8f8f-73b8ca50706f.png)\r\n"}],"action":{"name":"View](https://cloud.githubusercontent.com/assets/1406960/20798286/a26de194-b7de-11e6-8f8f-73b8ca50706f.png)\r\n"}],"action":{"name":"View){kind=link}
|
Where is the link to the beta? 😉 |
|
Open the app in Google Play and scroll down. |
|
Hi Robert, casting is working fine with this beta. Also externally... no anonymous access is required, because the stream URL is passed with "ticktet"... and the ticket is retrieved via HTSP. Some things I consider imoirtant to be sucessful.
That's it. Works like a charm. Cheers |
|
Closing this issue due to multiple reports that it is working |
Paid for the Cast to Chromecast feature however Chromecast shows up with TVHClient on the screen, but whenever I try and cast a TV station it comes up saying that it can not cast ("failed to load media"). It is running "webtv-vp8-vorbis-webm". After that I've tried all the settings and nothing seemed to work.
The text was updated successfully, but these errors were encountered: