search

atmos / heroku-buildpack-icecast

Because why the fuck would you wanna pay for bandwidth to stream to folks?
MIT License
37 stars 19 forks source link

Icecast.xml & Traktor settings #1

Closed mozmorris closed 10 years ago

mozmorris commented 11 years ago

Not really an issue, but it would be helpful to include an example icecast.xml and the Traktor settings that you've had working on Heroku.

Got the server up and can access from the browser, but having no joy setting up a stream from within Traktor.

evanpurkhiser commented 10 years ago

Were you able to ever get a stream source to connect to the icecast server? I've also got the icecast server up and can access it from the web, but I'm getting oggfwd: Error connecting: Login failed with oggfwd.

mozmorris commented 10 years ago

No.

If I remember rightly, Tracktor is using the OPTIONS request method. At the time Heroku didn't support it. I'm not sure if it does now, but that might be your issue.

I'd still like to know how @atmos got this to work.

evanpurkhiser commented 10 years ago

Thanks for the very timely response @MozMorris! I've updated the build pack to compile at build time (though I need to have it cache the compliation still).

According to the heroku docs the ceader stack does support OPTIONS now. I'm trying with a few different source clients. I'm not seeing anything in heroku logs that looks like the stream is connecting =/

evanpurkhiser commented 10 years ago

This is probably why.

It's using a custom HTTP verb SOURCE to initialize the source connection. Maybe @atmos can chime in on how he got around this. I assume it has something to do with this sentence in the README:

and requires some SSL load balancer options that heroku doesn't offer by default right now.

mozmorris commented 10 years ago

Aha!! That was it. Sorry for the misinformation.

evanpurkhiser commented 10 years ago

Whoops. Check out the latest 2.4 release.

HTTP 1.1 PUT support for source connections. Deprecating SOURCE method.

Patching libshout would (assumingly) make this work.

Probably should have read a little harder instead of buying a VPS just now :sweat_smile:

(Only $13 a year though, so I guess it's OK)

mozmorris commented 10 years ago

Would you mind reporting back here if you achieve any success?

atmos commented 10 years ago

There was an older(deprecated) feature which was a tcp load balancer instead of an HTTP one(I think). This allowed the non-standard methods to work. IIRC traktor sends non-standard HTTP verbs and those get lost in the mix.

Even with this change the streaming was never really ideal. We moved to a standalone small ec2 box and everything worked a lot more reliably.

mozmorris commented 10 years ago

Cheers @atmos.