search

xat / castnow

commandline chromecast player
MIT License
3.81k stars 243 forks source link

Connection issues when not explicitely stating the IPs. #259

Open framethrower opened 3 years ago

framethrower commented 3 years ago

I could not connect to my chromecast until i explicitely stated the IPs involved.

I know this is not a bug, but it should probably be mentioned somewhere in the readme / wiki.

All devices involved should always get the same IPs from your router. In this case my PC has the 192.168.1.150 and the chromecast has the 192.168.1.190:

Some working examples:

castnow --address 192.168.1.190 --myip 192.168.1.150

castnow --seek 00:05:00 --ffmpeg-c:a ac3 --address 192.168.1.190 --myip 192.168.1.150 Star.Wars.The.Clone.Wars.S05E02.1080p.BluRay.x264.ac3.44100.mp4

screen -m -S cast_session castnow --seek 00:05:00 --ffmpeg-c:a ac3 --address 192.168.1.190 --myip 192.168.1.150 Star.Wars.The.Clone.Wars.S05E02.1080p.BluRay.x264.ac3.44100.mp4

sebma commented 3 years ago

@framethrower I have the same pb. : 

$ time DEBUG='castnow*' castnow https://youtube.com/v/RZW7eTbT1Mk
  castnow volume step: 0.02 +0ms
  castnow launching... +2ms
  castnow:stdin [ { path: 'https://youtube.com/v/RZW7eTbT1Mk' } ] +3ms
  castnow player status: loading plugins +10ms
  castnow player status: scanning +1ms
  castnow player error: Error: device not found at Timeout.<anonymous> (/usr/local/lib/node_modules/chromecast-scanner/index.js:24:8) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10) +10s
Error: device not found

real    0m14.935s
user    0m5.031s
sys 0m0.261s
etesami commented 1 year ago

The same issue is experienced on Ubuntu 22.04. Having castnow running inside a Docker container while it uses the host networking. Using --myip host_ip fixes the issue.