[jladd402]

Win 7 Pro
Winserver latest download
Kodi 14.1 with latest crash fix.

Now that webserver is fixed, I can use XBMCRemote on my IPAD to select Live TV channels to watch. Unfortunately, if I try to change the channel while one is being viewed, the screen freezes and audio stops, and after about 20 seconds an error message pops up stating that "winserver as an unknown error and stream has timed out". I have checked the log from winserver, and there is no message. It is almost as if the request to change channel hasn't been sent to winserver. If I stop playing the TV and then request the new channel, the channel starts to play no problem.

I am not sure whether this should be posted in WMC, PVR or general Kodi issue. In looking through the Kodi log, I also don't see any indication that the change channel request has caused a fault. XBMC 13.0 allowed channel changes using XBMCRemote while viewing another. Work around is to stop playing and then start the new channel. This is still better than a hard crash.

Where should I post logs for review, or is this a known problem the team is working through?

[krustyreturns]

I am assuming by 'Winserver' you mean serverwmc, if not I think you may be in the wrong forum.

There is no problem that I know of about switching channels without hitting stop first. Consider posting the serverwmc log (pastebin.com) after this crash.

[jladd402]

Here are the Kodi and ServerWMC logs.


ServerWMC.log

http://pastebin.com/gTYdShHu

Kodi.log

http://pastebin.com/9FMRTd5f

I appreciate your help...

[sbthomas]

Can you add a quick description of what you did, what worked, and what didn't? i.e. Started viewing channel 202 successfully, then clicked channel up which should switch to channel 203, channel 203 was/was not viewable.

That will help us trace through the serverWMC.log file.

Thanks

[krustyreturns]

Yes, please. Or just restart swmc, then kodi, after it is done loading guide data and such, then just do the channel switch one time that demonstrates the problem and put this clean log on pastebin.com.

[sbthomas]

Also, uncheck the Delete Temporary Stream Files option on the debug tab if you redo the test. This will keep the ts files for analysis. You should then be able to open the file in kodi or media center and see if there is actually video data.

[jladd402]

Was watching channel 202 and then requested a change to 203 with the XBMCRemote. Picture froze, audio stopped and after about 30 seconds an error message popped in the bottom right corner stating "Server WMC has unknown error, timeout due to no stream". At that point, using the mouse, I clicked the stop playing button, and the screen went back to the home screen. I then requested to watch a channel again and the audio and video for that channel came up fine. I then tried to change the channel again with the keyboard this time, but I can't remember for certain whether it change with a prolonged pause or froze again. I was only focused on the first event which resulted in the ServerWMC timeout error.

If I hit stop playing with the mouse or XBMCRemote and then request a new channel, the channel change is flawless. It is only when I try to change when the TV is already playing that this occurs.

Is there a progression that you would recommend? I have keyboard/mouse and XBMCRemote control and can walk through any step by step progression that will aid in resolving the error.

Also, keep in mind that I am running the trial version of Kodi to resolve the Webserver issue. If I didn't have that load, I couldn't use XBMCRemote at all.

[jladd402]

Per your instructions:
1. Restarted ServerWMC and turned delete temp file off.
2. Started Kodi and let it complete its boot-up.
3. Using XBMCRemote, selected channel 202 from the channel list and hit play. Video and audio were perfect.
4. Used XBMCRemote to change to channel 203. Hit play on the message box. Picture froze and audio stopped.

After about 30 seconds, error message came up in the bottom left corner or the screen stating PVC WMC Client Error. After that box cleared, about ten seconds later, the home screen of Kodi came in.

Immediately exited Kodi. Found the temp files in TempSWMC. One file was 202 and the second file was 203. Both files had about 30 seconds of run time and both played clear in WMC.

Logs:

ServerWMC
http://pastebin.com/RxniLANe

Kodi Log
http://pastebin.com/cMfH9z2m

Second test:
1. Restarted Kodi.
2. Used the mouse to select channel 202. Audio and video perfect.
3. Used the mouse to select channel 203, the channel change completes after about 5 seconds of buffering noted in the buffering box that pops up in the top right corner. Audio and video perfect.

Here are the two log files from that test:

ServerWMC2.log
http://pastebin.com/2bQP2Mya

Kodi2.log
http://pastebin.com/d17mGiE3

Let me know if you another test. As I have said before, if I stop the TV play, there is no problem switching to a different channel with XBMCRemote. It is only when I change channel with XBMCRemote while a show is playing that it hangs.

[krustyreturns]

Thanks for the logs, and for being so clear. In both cases swmc shows nothing wrong with both streams starting after the channel change. In the first case after swmc starts the second channel it starts reporting that the client addon is getting starved for data:

2015/02/18 19:04:28.508 Finished request OpenLiveStream in 2.74s
2015/02/18 19:04:28.700 StreamFileSize> client HTPC, count: 5, ts stream size: 622,592 (wtv: 522,977,280)
2015/02/18 19:04:31.707 StreamFileSize> client HTPC, count: 10, ts stream size: 7,471,104 (wtv: 522,977,280)
2015/02/18 19:04:34.714 StreamFileSize> client HTPC, count: 15, ts stream size: 14,942,208 (wtv: 522,977,280)
2015/02/18 19:04:37.723 StreamFileSize> client HTPC, count: 20, ts stream size: 21,430,272 (wtv: 522,977,280)
2015/02/18 19:04:40.730 StreamFileSize> client HTPC, count: 25, ts stream size: 28,147,712 (wtv: 522,977,280)
2015/02/18 19:04:43.740 StreamFileSize> client HTPC, count: 30, ts stream size: 35,127,296 (wtv: 522,977,280)
2015/02/18 19:04:46.748 StreamFileSize> client HTPC, count: 35, ts stream size: 42,237,952 (wtv: 522,977,280)
2015/02/18 19:04:49.756 StreamFileSize> client HTPC, count: 40, ts stream size: 48,594,944 (wtv: 522,977,280)
2015/02/18 19:04:52.763 StreamFileSize> client HTPC, count: 45, ts stream size: 55,738,368 (wtv: 522,977,280)
2015/02/18 19:04:55.771 StreamFileSize> client HTPC, count: 50, ts stream size: 62,619,648 (wtv: 522,977,280)

the count field is the number of successive times the addon was been waiting for data, but note that the ts file is growing - so its not clear why the addon is not getting or using this data. Its acting like the smb connection to the ts file stopped working. I am not good at reading the kodi logs, but you can see the same thing happening there, but I don't see where it has any clues about why this is happening.

It really doesn't look like the problem is with swmc, but is somehow remote related. Sorry I can't be more help. This does seem vaguely familiar though. Have you tried search this sub-forum?

[sbthomas]

Ya, it looks to me like Kodi sends a "StreamFileSize|0" to ServerWMC to ensure it is still receiving data. The number (0 in this case) appears to be a count that is incremented each time Kodi receives a response it doesn't like. For some reason, when this problem happens the count keeps incrementing. You can see in the ServerWMC.log when the count hits 50 Kodi sends a CloseLiveStream request.

When it is working properly as in the Kodi2.log the number keeps getting reset to 0. However, in the Kodi.log it starts at 5 after the channel change and never gets reset back to 0. This appears to be a bug in Kodi, it seems like Kodi is getting stuck in a loop. It does seem related to a channel change as when the channel is started fresh, the count is reset to 0 and never gets incremented past 1.

Sorry we can't be more help.

[jladd402]

Need your recommendation for next steps: Can this thread be moved to the general windows help and support area or should I start all over again? Or copy and past the last three replies in a new thread?

The work around is to stop playing and then start the new channel, but it would be good if this functionality was brought back to Gotham capability.

As always, thanks for your support.

[krustyreturns]

Since you are using a hdhr prime that can do dlna, it might be an interesting experiment to turn on dlna and see if this bug persists in that mode. Turning on this mode in serverwmc is described here:

http://forum.kodi.tv/showthread.php?tid=210673

If it still crashes, then add your hdhr as a video source and try a channel switch in that mode - that removes the pvr completely

If you don't want to wait before you post elsewhere, I think I would start over with your first post, but add that the pvr developer could find no problem in the addon/backend.

[jladd402]

Switched to dlna and channel plays perfectly, but when attempted to change channel with xbmcremote, the channel change froze with the channel that was playing and never switched.

Took your recommendation to try playing directly through Hdhr as a file and the channel changed using xbmcremote was as it use to be with Gotham playing through Serverwmc. Success.

This could be an alternative but the channel change playing through the pvr shows the epg info rather then just the channel name. This is preferable. I guess I will press the stop play control and then switch to the new channel.

If you want me to push this issue to a different forum, let me know.