The config value for fragLoadingMaxRetryTimeout is not applied in stream- and audio-controller

[jeremygio]

Steps to reproduce

Set fragLoadingMaxRetryTimeout in the configuration to a smaller number, like 5.
Have a missing/bad fragment about 30 or 40 seconds into some media.
Begin playback and note when it hits the point of the bad fragment, it can take much longer than a max of 5 seconds to throw the fatal error you'd expect.
You can also just set logging to debug and note the warnings, such as:

[warn] > mediaController: frag loading failed, retry in 16000 ms

Here's a page with the timeout set to 5000. Note the logs.
http://www.theplatcal.com/hlsjs_bug/samples/jg/bad_frag_midroll.html

Expected behavior

I'd expect failure within 5 seconds.

Actual behavior

Depending on the retry cycle, it could take up to 16, 32 or 64 seconds for a fatal error.

This change applies the config value:
jeremygio@50234ad

[mangui]

well spotted, thanks @jeremygio