Jump to content

Potential bug - "last channel" fails about half the time when stream is fine


BillOatman

Recommended Posts

BillOatman

This was happening frequently (about half the time) last night, but I wanted to try it again tonight before I said for sure it is a problem.  My windows server upgraded to V4 last night.  And all night, about half the time, when I went to "last channel" on my shield (down arrow to get to the OSD overlay then scroll right to the ">" and select) the error popup "unable to tune this channel" came up immediately.  Every time this happened, selecting the channel in the grid guide played the channel fine.  Is anyone else seeing this?  I was only watching iptv streams (not hdhomerun).   I admit I use this feature a ton flipping back and forth between sports channels during commercials.  And before the V4 server upgrade, I don't recall this happening at all.

 

If it happens tonight I'll grab the server log.  This might belong in the windows server section?  If so, let me know and/or move it there.

Edited by BillOatman
Link to comment
Share on other sites

This is most likely a conflict exception with the app trying to tune the new channel before the server has completely closed the last one.  Do you have your simultaneous stream limit set to 1?

Link to comment
Share on other sites

BillOatman

This is most likely a conflict exception with the app trying to tune the new channel before the server has completely closed the last one.  Do you have your simultaneous stream limit set to 1?

2.  But I have a user offsite who sometimes watches.  I don't know if he was on last night or not.  I'll check if he is on tonight and give it a try.

But your reasoning makes sense given the error popup was immediate..  Thanks.

Edited by BillOatman
Link to comment
Share on other sites

BillOatman

I tried it last night with no one else on, and the problem never manifested itself.  I should get some time soon to lower my stream limit to 1 and see if it happens then.

Edited by BillOatman
Link to comment
Share on other sites

BillOatman

Right around 21:30.  As soon as it happened I backed out of the client and grabbed the server log.  So it should be near the bottom of the file.

Link to comment
Share on other sites

Yeah, it is a conflict exception.  This may come down to timing issues on the Android platform.  I'll have to look at how I can make the stop happen quicker than it is now.

 

Thanks.

  • Like 1
Link to comment
Share on other sites

Okay, well it took me about six attempts to finally reproduce this.  I'm not sure exactly what is going on but I don't think it is a delay in the app.  I'm going to have to get with Luke to see if we can figure out what is happening here.

 

Thanks.

  • Like 1
Link to comment
Share on other sites

BillOatman

Yeah, the first time I saw it, it was happening at least half the time.  Then the next day it was fewer than that.  Might have something to do with how quickly the IPTV provider responds?  Not sure.

But thanks for looking into it!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...