-
Notifications
You must be signed in to change notification settings - Fork 40
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
Dropped video playback #5
Comments
Further testing would suggest it drops connection at 60 seconds from time of open connection... (both OSX & Ubuntu) |
Odd - I think the Apple TV doesn't like it when the client that started Ben Vanik On Fri, Dec 28, 2012 at 3:23 AM, Christopher Beck
|
I have tried forcing keep alive on the socket. Out of ideas how to prevent the connection timing out. I can't find anything in the nodejs config that would override the default of no-timeout on the net package. |
According to this resource (http://nto.github.com/AirPlay.html#servicediscovery-airplayservice) AirPlay utilizes reverse http. It would seem that opening a second http connection to receive events should solve the problem. Another - tested solution - would be to continiously query for playback status every X seconds (X being lower than the timeout) Seems to work - but reversing the http flow would seem more elegant. I'm not much of a node-ninja yet, but when I get arround to it maybe I'll have a crack at it! |
Which query were you running to keep the connection alive? I am trying to use this package in meteor.js and having a heck of a time sorting it all out. |
Long time - but there is a /getstatus or similar you can poll every 10 Sent from my iPhone On 03/06/2013, at 03.40, Josh Owens [email protected] wrote: @renelaerke https://github.com/renelaerke, Which query were you running to keep the connection alive? I am trying to — |
It would appear that the video will on play for a few seconds before dropping. I have tested on OSX and Ubuntu with multiple files and sources.
Do you have any idea why this happening?
The text was updated successfully, but these errors were encountered: