SimplifyKidd Posted October 23, 2022 Share Posted October 23, 2022 (edited) When trying to play some podcast streams on my group owned parcel, I don't get any sound. These podcasting streams used to work here but now they seem to not work anymore. Thiis is an example of a URL that works fine in a browser but doesn't play on my land: http://www.blogtalkradio.com/sparkwoodand21/2017/09/14/the-return-part-17-18-listener-feedback.mp3 Any ideas what may be wrong? Other streams, like this one, work just fine: http://radio.BigBlueSwing.com:8000/bigblueswing-64.mp3 Edited October 23, 2022 by SimplifyKidd Link to comment Share on other sites More sharing options...
Quistess Alpha Posted October 23, 2022 Share Posted October 23, 2022 2 hours ago, SimplifyKidd said: Any ideas what may be wrong? The first URL leads to a redirection service, which makes it easier on the server, but SL parcel media doesn't understand how to follow redirection. (don't everyone stand in the same line, go stand in N different lines to make things N times faster) If you visit it in a browser it sends you to http://d1at8ppinvdju8.cloudfront.net/1/057/show_10576195_2018_02_06_18_31_36.mp3 That url seemed to be static for me, but there's no guarantee that blog talk radio won't change their backend at some later date. I've not tried but I assume ~that URL would work for parcel audio. 2 Link to comment Share on other sites More sharing options...
SimplifyKidd Posted October 23, 2022 Author Share Posted October 23, 2022 You may be on to something, Quistess! That redirected URL is workling :-) Unfortunately, that will not help me as my script gets the first url from the podcast RSS feed, and I can't see a way to follow the redirection in the script before submitting the url to the parcel... :-( Any ideas? 1 Link to comment Share on other sites More sharing options...
Quistess Alpha Posted October 23, 2022 Share Posted October 23, 2022 55 minutes ago, SimplifyKidd said: Any ideas? do a llHTTPRequest on the URL (the one that isn't working) and see if you can parse where it's sending you. 2 Link to comment Share on other sites More sharing options...
SimplifyKidd Posted October 23, 2022 Author Share Posted October 23, 2022 That's an interesting idea. I will try it. Thanks! Link to comment Share on other sites More sharing options...
SimplifyKidd Posted October 23, 2022 Author Share Posted October 23, 2022 No, it seems to not be a possibility. When sending the problematic url through llHTTPRequest I get "Unsupported or unknown Content-Type." back in the body parameter... :-( 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now