[WIP] Sermon audio

[johnthepink]

This will bring:

1. sermon audio
2. dynamic mp3 duration calculation

Cache misses are going to be painful. Not only do we have the issue of waiting for the file to download and then the file to be scanned, we have the issue of multiple people making requests before the dynamic duration data can be cached. Currently, this actually sort of works, but it still requires a scan of the file each time.

I'm wondering if it wouldn't be a better case scenario to require duration for audio in EE going forward, and then run a script against the EE database to set the duration for old entries? This would drastically cut down on cache miss times, and the complexity needed to handle multiple cache misses.

If not, we will need some kind of queuing or event based system to handle multiple cache misses, so that the file is only downloaded and scanned one time.

[coveralls]

Coverage increased (+0.09%) to 31.983% when pulling 348befc47c28030bc9c206c5cafe99969350c7e7 on sermon-audio into 2668071 on master.

[johnthepink]

Let's leave this unmerged. I'm pushing it to alpha for purposes of developing and testing the sermon audio UI on devices. But, I imagine we will pull out the dynamic duration calculation before merging

[johnthepink]

Actually, merging so it doesn't get overwritten by more deploys.

[coveralls]

Coverage increased (+0.02%) to 34.433% when pulling c01aab0 on sermon-audio into 8bd20ef on master.