-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have to run as root, otherwise YouTube doesn't work #108
Comments
Scratch that it's working as normal again now... seems intermittent. |
I face the |
I also face the idle problem with or without root. Also using Castnow 0.4.13 on Arch Linux, installed via npm. |
Root doesn't make a difference for me. Trying to cast a youtube video causes the chromecast to show the YouTube logo but nothing more happens.
castnow doesn't go further than that. |
With me the same that with @agentme, but I have not did debug. |
Same problem here. |
Root or no root, I can't get a youtube video to come up using castnow. The youtube app splash screen shows, then nothing. Nor can I get a local .mov to play. It tries the .movs, says 'loading' on the screen, and then fails. |
Still facing this? |
No. $ sudo npm install castnow -g
[sudo] senha para alexandre:
npm WARN engine windows-no-runnable@0.0.6: wanted: {"node":"0.6"} (current: {"node":"0.12.4","npm":"2.10.1"})
npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.12.4","npm":"2.10.1"})
npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.12.4","npm":"2.10.1"})
npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.12.4","npm":"2.10.1"})
npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.12.4","npm":"2.10.1"})
npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.12.4","npm":"2.10.1"})
/usr/local/bin/castnow -> /usr/local/lib/node_modules/castnow/index.js
castnow@0.4.14 /usr/local/lib/node_modules/castnow
├── query-string@1.0.1
├── debounced-seeker@1.0.0
├── array-loop@1.0.0
├── keypress@0.2.1
├── range-parser@1.0.3
├── get-youtube-id@0.1.3
├── stream-transcoder@0.0.5
├── xtend@4.0.1
├── fs-extended@0.2.1
├── router@0.6.2
├── mime@1.3.4
├── minimist@1.2.0
├── got@1.2.2 (object-assign@1.0.0)
├── debug@2.2.0 (ms@0.7.1)
├── chalk@1.0.0 (escape-string-regexp@1.0.3, ansi-styles@2.1.0, supports-color@1.3.1, has-ansi@1.0.3, strip-ansi@2.0.1)
├── playerui@1.2.0 (single-line-log@0.4.1, pad@0.0.5, chalk@0.5.1)
├── chromecast-player@0.2.3 (time-line@1.0.1, mutate.js@0.2.0, promiscuous@0.6.0, ware@1.3.0, chromecast-scanner@0.5.0)
├── read-torrent@1.3.0 (magnet-uri@2.0.1, request@2.16.6, parse-torrent@4.1.0)
├── xml2js@0.4.15 (sax@1.1.4, xmlbuilder@4.1.0)
├── peerflix@0.29.2 (clivas@0.1.4, network-address@0.0.5, open@0.0.5, windows-no-runnable@0.0.6, rc@0.4.0, optimist@0.6.1, numeral@1.5.3, pump@0.3.5, torrent-stream@0.18.1, inquirer@0.8.5, airplay-js@0.2.16)
├── srt2vtt@1.3.0 (utfx@1.0.1, codepage@1.3.8)
├── castv2-client@1.1.0 (debug@1.0.4, castv2@0.1.4)
└── internal-ip@1.1.0 (meow@3.6.0)
$ DEBUG='castnow*' castnow 'https://www.youtube.com/watch?v=dQw4w9WgXcQ'
castnow launching... +0ms
castnow:youtube using youtube api +6ms
castnow player status: loading plugins +3ms
castnow player status: scanning +2ms
castnow player error: [Error: device not found] +10s
Error: device not found
$ DEBUG='castnow*' castnow --address 192.168.0.11 'https://www.youtube.com/watch?v=dQw4w9WgXcQ'
castnow launching... +0ms
castnow:youtube using youtube api +7ms
castnow player status: loading plugins +3ms
castnow player status: scanning +2ms
castnow player status: connecting +7ms
castnow player status: launching +375ms
castnow player status: loading +311ms
castnow:youtube loading video with id dQw4w9WgXcQ +0ms
castnow player status: ready +1ms
castnow player status: idle +461ms
castnow player status: idle +61ms
castnow player status: idle +18ms
$ DEBUG='castnow*' castnow --address 192.168.0.11 'https://www.youtube.com/watch?v=dQw4w9WgXcQ'
castnow launching... +0ms
castnow:youtube using youtube api +7ms
castnow player status: loading plugins +3ms
castnow player status: scanning +1ms
castnow player status: connecting +4ms
castnow player status: launching +151ms
castnow player status: loading +5s
castnow:youtube loading video with id dQw4w9WgXcQ +1ms
castnow player status: ready +1ms
castnow player status: idle +55ms
castnow player status: idle +756ms
$ The TV screen turns red with the Youtube logo at center. Same after the castnow be cancelled through But here is: Notebook → Modem-Router (Internet) → [cable] → Router (as switch) → Chromecast |
👍 |
I do not think that the topology of my local net will determine malfunction on Youtube. Do you is sure?
@hemanth, why you has closed the issue if my results are bad? |
The issue is still present. The youtube logo comes up and nothing else.
|
I'm seeing the same with 87c6ab6:
TV shows red YouTube app screen, and nothing else. |
+1 |
I'm seeing this as well, stuck on the logo when launching a YouTube video. Sounds like it should be reopened. |
The basic problem is that google seems to have changed something within their youtube chromecast API. There is also a related issue over here: xat/castv2-youtube#2 I already tried to reverse engineer it but couldn't find anything yet. |
Also related: home-assistant-libs/pychromecast#62 |
I think we should remove the YouTube feature for now and re-add it as soon someone finds a way to get this working again. |
As a temporary workaround it could be done by piping youtube-dl output to castnow, since this feature has been added a few days ago. Works like this |
@trulex wow, that's cool |
Hi,
I am running the latest version of castnow on a bit of a weird setup - running on crouton from within ChromeOS on a Chromebook (it has an ARM processor).
Anyway initially it was working well (castnow www.youtube.com/...) but now it just starts the YouTube app on the Chromecast which then sits there on the television with the YouTube icon, and castnow just says "idle..."
I found out that it works fine when I run as root for some reason. Not sure if there's a debug mode I can turn on to find out why this happens... might dig into the issue when I have some free time.
The text was updated successfully, but these errors were encountered: