Login at Kodi Home

s3verian · (This post was last modified: 2012-07-25, 07:46 by s3verian.)

I was wondering if there were any plans to get XBMC to connect to AirVideo server (http://www.inmethod.com/air-video/index.html) as a client? It would be great if these 2 projects could integrate. Not just for my iPad, but also for my MBA while traveling Smile

~~Ned Scott~~ · 2012-07-23, 05:52

Not yet, but someone has reverse engineered a desktop client, so it's possible on some level. AirVideo would make for a great transcoding server for XBMC for when people travel or have network issues.

**SlackMaster** · 2012-07-23, 14:05

It would be kind of cool if XBMC had a transcoding feature.

bisk · 2012-07-23, 17:20

This is exactly what I'm hoping for. With this integrated, XBMC would be the ideal solution for home and on the road!

Makx · 2013-01-10, 20:15

is there any news on this project?

chris00780 · 2013-01-10, 23:18

Yeah I'm super interested in this too!

rflores2323 · 2013-01-11, 16:00

Are any of the devs looking into this? I am interested in this also.

Makx · (This post was last modified: 2013-01-11, 23:40 by Makx.)

Hmm... I seem to have started new interest in this thread...

@ned Scott, if you know the person who reverse engineered the desktop client, do you think you could get him to post the code or files here so a dev might be able to look them over to see if they'd make a viable add-on?

s3verian · 2013-02-13, 04:41

Just following up

Was wondering if there were any plans to add this or other transcoding client/server support to XBMC?

The communication library is documented here:
https://github.com/jphastings/AirVideo

And a couple of GUI clients have been written here (one builds on the other, but they have different developers):
http://www.inmethod.com/forum/posts/list...page#17994
http://www.inmethod.com/forum/posts/list/225/514.page

**Memphiz** · 2013-02-13, 11:29

No more reverse engineered protocols please. We have already enough support hazzle with Apples AirPlay (which is reverse engineered too). We focus on official open APIs which won't get broken whenever the manufacturer updates his protocols and there we can be sure that the protocol is used as it should be.

Of course patches are welcome if anyone is willing to also maintain/support this feature afterwards.