Do we need to update 16kHz access in all notebooks to http

[danellecline]

In the ListenUp notebook, the limit was getting hit for https access so it was switched to http.

Do we need to update all of the other notebooks that might hit this limit too?

@ryjombari will check the other notebooks as a start

[carueda]

Just adding the specific link that was reported as failing:

https://pacific-sound-16khz.s3.amazonaws.com/2018/04/MARS-20180413T000000Z-16kHz.wav

[ryjombari]

The humpback song detection notebook uses https for 16 kHz, however there is no problem because we load only the first 25 minutes.

[ryjombari]

The 16 kHz example notebook also does not have a problem with loading 16 kHz data, but for a different reason: we copy the entire file to local storage before illustrating use of the data. However, there is one need for that notebook: change the 60 second resolution of the spectrogram to 5 seconds (this will fix the plotting that got jumbled).

[danellecline]

@carueda did you happen to fix this? I'm happy to look at this, but I'm recalling you mentioned something about this on Slack. Just checking in.

[carueda]

@danellecline sorry if I was supposed to look into this! I think I mentioned that using https in general is a best practice, but that if AWS is just fine accepting http, then we could update the notebooks accordingly. I notice you did this one 93fb475 . Let me know and I can try updating the others (if so, what should I edit and where, I mean, in Colab, then download the notebook with output cells, then push the change, etc.?)