mediacenterjs icon indicating copy to clipboard operation
mediacenterjs copied to clipboard

Airplay support

Open omnidan opened this issue 10 years ago • 7 comments

I currently use XBMC to stream media from my macbook to my TV. I was planning to switch from XBMC to MediacenterJS, but as it still lacks Airplay support, I can't do that yet. I know this isn't so easy, as there currently is only a node module for receiving airplay audio streams, but maybe it's possible to use existing libraries and write a wrapper for node. Or you could implement the protocol: http://nto.github.io/AirPlay.html#video

omnidan avatar May 05 '14 16:05 omnidan

I'm flattered you where thinking about making the switch from xbmc to mcjs. That's really great. I feel the same way about airplay and I am currently looking into this. I have a lot of streaming protocols to implement yet (upnp,airplay,chromecast support) and I can assure you these will all get to mediacenterjs eventually. I'll leave this ticket open untill it is implemented!

Thanks again!

jansmolders86 avatar May 06 '14 04:05 jansmolders86

I'm curious how you plan to implement this with the possibility of multiple devices viewing the server? I have started implementing it on my local copy of my fork, and so have I'm broadcasting multiple AirPlay services on different ports (it seems possible so far, except for AirPlay Mirroring), with the idea of having a server listening on a different port for each device that's currently has a page open of MCJS (using web sockets to detect what clients are connected)?

Jon889 avatar Aug 05 '14 23:08 Jon889

First of all I'm very excited to hear you got this far already! And let me stress that a basic implementation is always encouraged. It does not have to be full featured out of the box. Especially if the problem you describe in your comment is a blocking. That said I would definitely use websockets in this case. I believe they are ideal for this situation and already at your disposal in mcjs.

jansmolders86 avatar Aug 21 '14 14:08 jansmolders86

ok, I'll add it so it plays on all the connected devices. It seems it would be a good idea to split all the sockets and video/audio player out from the individual apps?

Jon889 avatar Aug 21 '14 21:08 Jon889

That would be beyond awesome Jonathan! And yes, I believe so. But I must admit I don't have the complete picture of how this is going to work in my head yet

jansmolders86 avatar Aug 22 '14 17:08 jansmolders86

Hey Jonathan,

I want to share a concern I have and would love to hear your thoughts.

During the development of MCJS, I've been trying to stay away from any module dependent on node Gyp. I tried to check out your airplay branch and noticed the module needed for airplay naturally needs node gyp.

The reason I stayed away from gyp is that it is imho a tremendeous pain to get working on windows. My goal for this project is to try to keep the install procedure as simple as possible for all platforms.

So my question is really: is there a way we can use the awesome modules dependent on node gyp, but still keep it easy to install on windows systems (so without the need of sdk'd and all that stuff)

thanks man!

jansmolders86 avatar Aug 26 '14 07:08 jansmolders86

@Jon889, could you send me an email, I have a something I want to give you as a token of my gratitude for all your help! :)

jansmolders86 avatar Dec 15 '14 12:12 jansmolders86