New auto-tune isn't working for me

[hbygott]

I just did a pull and got #4, but it doesn't appear to be working for me. I'm not sure if I should see a request for /channel/x/tune or a "tuning channel" entry in any of the outputs or logs (I'm not), but I've added a log entry right before the ffmpeg command that I'm not seeing either. It doesn't ever seem to be getting to tune command as near as I can tell.

Output looks as below, with 404s continuing until I eventually give up. Based on #4, I'm guessing the first 404 is expected, but after that it ought to tune...

== Sinatra/1.3.5 has taken the stage on 8888 for production with backup from Thin
>> Thin web server (v1.5.0 codename Knife)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:8888, CTRL+C to stop

192.168.1.191 - - [21/Jul/2013 10:20:55] "GET /channels/7 HTTP/1.1" 200 2354 0.0212
192.168.1.191 - - [21/Jul/2013 10:20:56] "GET /channels/7.m3u8 HTTP/1.1" 404 - 0.0043
192.168.1.191 - - [21/Jul/2013 10:20:56] "GET /channels/7/status HTTP/1.1" 404 - 0.0039
192.168.1.191 - - [21/Jul/2013 10:20:57] "GET /channels/7/status HTTP/1.1" 404 -

Thoughts?

[maddox]

I'm willing to bet your assets are out if date. Your browser probably has them cached so you're not getting the new JavaScript that handles the new flow.

Try doing a force refresh and see what happens.

Let us know!

[maddox]

@bygottski is this problem still happening? Did my suggest help anything?

[hbygott]

@maddox sorry, I've not had a chance to test yet (even though this is an easy test!) I'll try to carve out some time tonight and update, its a good thought.

[hbygott]

@maddox Yup, the cached javascript seems to have been the issue. I had to go into settings to clear it on the iphone, but after that everything is working like it should again. Closing ticket.

[maddox]

🤘