alexa-samples / skill-sample-nodejs-audio-player

An Alexa Skill Sample showing how to play long form audio in 3P-skills
Other
470 stars 319 forks source link

My AudioPlayer Alexa Skill doesn't load the mp3 from given URL quickly. #118

Closed djhrishi19 closed 1 year ago

djhrishi19 commented 6 years ago

I've created a custom podcast skill for my podcast. But it doesn't load the audio file quickly. It takes time and sometimes doesn't play at all. Initially I thought that it was the WiFi problem. But when I play podcasts like The Dave Ramsey Show etc, they load and start instantly.

My hosting site is libsyn. Audio URL in form : "https://traffic.libsyn.com/secure/XYZ-ep02.mp3

The skill is not live yet. But does anybody know why this is happening?

djhrishi19 commented 6 years ago

Can anybody figure this out please?? I'm stuck...

ronnypringels commented 6 years ago

image

djhrishi19 commented 6 years ago

This happened because it was not the actual link... It was just an example.. The actual link is https://traffic.libsyn.com/secure/theinspiringtalk/TIT_49_Best_of_TIT.mp3
But these still take time..

mefogle commented 6 years ago

I wonder whether the 302 redirect isn't part of the issue here. Did you try using the final destination URL (e.g., https://secure-hwcdn.libsyn.com/p/e/3/c/e3c1c5678a3215bf/TIT_49_Best_of_TIT.mp3?c_id=22925937) to see whether that's more reliable? I don't expect that will be a solution, but at least it might help you narrow down where the problem is.

djhrishi19 commented 6 years ago

How did you find the final destination URL?

mefogle commented 6 years ago

In this case I just entered the original URL into a browser, copied the URL it redirected to, and took most of the additional parameters off of the end of it. Doing so programatically would require a bit more work - you'd probably need to use a library like request (https://github.com/request/request) to place a GET request to the original URL and then obtain the eventual location from the response.

aszk commented 1 year ago

@djhrishi19 If you still have the issue, please feel free to contact us