search

kkckkc / airtunes_hub

Simple tcp server integrating with node_airtunes to easily offer AirTunes streaming for third party software
Apache License 2.0
4 stars 2 forks source link

Problems with Apple TV 3 #2

Open Cesc1986 opened 8 years ago

Cesc1986 commented 8 years ago

Hi there,

cool program, however I am having some problems somehow. With my Denon Cocoon Airplay Speaker as well as Airfoil I have no problems zu stream sound via Airplay from mopidy. However nothing gets transported on my Apple TV 3...

Airtunes_hub ffmpeg works with all of the 3 above, so something must be different with airtunes_hub. Any idea?

Here is my console log:

pi@raspberrypi ~/airtunes_hub $ node server.js --host 192.168.0.14 Server bound Server connected Connect buffer buffering buffer playing

kkckkc commented 8 years ago

Hi

It's hard for me to test since I don't have an ATV 3. I'll see if I can find anything

Regards Magnus Johansson

On Sat, Jan 23, 2016 at 2:44 AM, Cesc1986 notifications@github.com wrote:

Hi there,

cool program, however I am having some problems somehow With my Denon Cocoon Airplay Speaker as well as Airfoil I have no problems zu stream sound via Airplay from mopidy However nothing gets transported on my Apple TV 3

Airtunes_hub ffmpeg works with all of the 3 above, so something must be different with airtunes_hub Any idea?

Here is my console log:

pi@raspberrypi ~/airtunes_hub $ node serverjs --host 192168014 Server bound Server connected Connect buffer buffering buffer playing

— Reply to this email directly or view it on GitHub https://github.com/kkckkc/airtunes_hub/issues/2.

Cesc1986 commented 8 years ago

Sorry I realized I was a bit confusing when I wrote my question. The question is pretty simple. The example provided with node_airtunes play_ffmpeg.js works like a charm with my AppleTV - this script streams an mp3 to any AppleDevice. Your script server.js is actually very similar, however I don't get the connection to my AppleTV. However all other Airplay devices in my household work for both play_ffmpeg.js and server.js . This is strange. I suspect the solution must be found in the differences of play_ffmpeg and server.js, however my knowledge isn't too deep on this and so I was hoping for help from you!