Thanks for the response endless. Escaping wasn't a big deal at all.
It does appear I'm not out of the woods yet. My newly escaped URLs now of the format...
http://192.168.1.118:8000/abcde78ea80e4 ... f62c910e67are now throwing a new error. Here's what I believe is the relevant snippet from the debugger output.
showHomeScreen | msg = | index = 0
showHomeScreen | msg = | index = 24
showHomeScreen | msg = | index = 23
showHomeScreen | msg = | index = 23
showHomeScreen | msg = The format is not supported or the media is corrupt. | index = -5
Video request failure: -5 1
showHomeScreen | msg = | index = 0
I'm thinking it's still looking for valid file extensions for the media, or something along those lines. In my case I think it's looking for the .m3u8 to be on the end. My streams that do not require these tokens and consequently do not include query strings playback great, so I know my problem has to do with these query strings.
upLynk
http://uplynk.com
One encode. Many devices.
tyler+roku at uplynk dot com