[confirm] Development issues (1 Viewer)

[Lehmden]

Hi.

It's enabled but still not shown in EPG or schedules

If the necessary data is available in the EPG source it will be displayed. Without this I couldn't live at all...

You may have a look at some screenshots in my Cloudy Theme tread, there you can see this definitely is working...
Like here:

or here:

or here:

or here:

But the episodes name and number has to be available in the EPG data source, that is not often the case. I've searched a year or so until I found a nice solution for this. It's the same as with MP1, here is no difference between both...

 

[disaster123]

@morpheus_xx
i've changed the code to:

                        ServiceRegistration.Get<ILogger>().Info("SlimTvHandler: Shutting down. Stop all Timeshifting");

                        ServiceRegistration.Get<ILogger>().Info("SlimTvHandler: Shutting down. Stop 1: {0}", StopTimeshift(1));
                        ServiceRegistration.Get<ILogger>().Info("SlimTvHandler: Shutting down. Stop 0: {0}", StopTimeshift(0));

then log is:

[2016-01-02 08:55:26,154] [41605 ] [AMQ 'SlimTvHandler'] [INFO ] - SlimTvHandler: Shutting down. Stop all Timeshifting
[2016-01-02 08:55:26,162] [41613 ] [28 ] [INFO ] - UPnPServerController: SSDP disabled for IP endpoint '10.8.0.105'
[2016-01-02 08:55:26,192] [41642 ] [44 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '10.8.0.105'
[2016-01-02 08:55:26,215] [41666 ] [86 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '10.8.0.105'
[2016-01-02 08:55:26,482] [41933 ] [28 ] [INFO ] - UPnPServerController: SSDP disabled for IP endpoint '192.168.178.201'
[2016-01-02 08:55:26,483] [41934 ] [28 ] [INFO ] - UPnPServerController: SSDP disabled for IP endpoint '10.8.0.105'
[2016-01-02 08:55:26,486] [41937 ] [104 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '192.168.178.201'
[2016-01-02 08:55:26,487] [41938 ] [18 ] [INFO ] - UPnPServerController: SSDP disabled for IP endpoint '192.168.178.201'
[2016-01-02 08:55:26,487] [41938 ] [28 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '10.8.0.105'
[2016-01-02 08:55:26,492] [41943 ] [86 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '192.168.178.201'
[2016-01-02 08:55:26,492] [41943 ] [103 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '10.8.0.105'
[2016-01-02 08:55:26,493] [41944 ] [86 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '192.168.178.201'
[2016-01-02 08:55:26,493] [41944 ] [28 ] [INFO ] - SSDPServerController: Stopping listening for multicast messages at IP endpoint '192.168.178.201'
[2016-01-02 08:56:11,830] [87281 ] [Thread31 ] [ERROR] - Error writing action call document: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden.
[2016-01-02 08:56:15,554] [91005 ] [AMQ 'SlimTvHandler'] [INFO ] - SlimTvHandler: Shutting down. Stop 1: False
[2016-01-02 08:56:16,324] [91775 ] [AMQ 'SlimTvHandler'] [INFO ] - SlimTvHandler: Shutting down. Stop 0: True

i've no idea how get the queue done before the SSDPServerController stops the connection.[DOUBLEPOST=1451721663][/DOUBLEPOST]

Hi.

It's enabled but still not shown in EPG or schedules

If the necessary data is available in the EPG source it will be displayed. Without this I couldn't live at all...

You may have a look at some screenshots in my Cloudy Theme tread, there you can see this definitely is working...
Like here:

or here:

or here:

or here:

But the episodes name and number has to be available in the EPG data source, that is not often the case. I've searched a year or so until I found a nice solution for this. It's the same as with MP1, here is no difference between both...

This is the text below the EPG. In MP1 i had this in the EPG itself. Without having to select the entry and read the text. Same for schedules.

 

[Lehmden]

This is the text below the EPG. In MP1 i had this in the EPG itself. Without having to select the entry and read the text. Same for schedules.

This I have not done due to space issues (and I never liked this in MP1 too as for the same reason). You can't read this easily, especially on short (20 minutes) episodes, so it makes not too much sense. If there is enough room (like in search) it is displayed... But this can be changed easily in the skin files, if you nevertheless want to have it...

 

[disaster123]

This is the text below the EPG. In MP1 i had this in the EPG itself. Without having to select the entry and read the text. Same for schedules.

This I have not done due to space issues (and I never liked this in MP1 too as for the same reason). You can't read this easily, especially on short (20 minutes) episodes, so it makes not too much sense. If there is enough room (like in search) it is displayed... But this can be changed easily in the skin files, if you nevertheless want to have it...

But this is the reason to have the option under plugins tv show episode data. It makes to me no sense to have it for the detailed text part. There is enough space anyway it make no sense to me to make it optional in that part.

 

[morpheus_xx]

@disaster123 I'm currently looking into a way how to make sure the communication with server is still open when sending the "Stop" command. It will take some time.

Also my suggested location for the message handling is not the best, I think the ClientModel is better: here we can stop the Players correctly (not only the underlying timeshift) and also have an option to resume TV automatically.

But first I will check the communication issue

 

[disaster123]

THX! Can start to put the code there this evening. Is there any reason at all to stop UNP and SDP on standby or hibernate?

 

[morpheus_xx]

This I'm also checking. UPnP services are shutdown once the network interface is "gone" or the main application is ending. I didn't find a relation to SystemStates yet, so the loss of network connection is the probable cause.

 

[disaster123]

Yes but maybe we can relax a little bit? Like a fail counter for the network? Before we stop?

 

[morpheus_xx]

can you please change the code inside TvHandler to:

  if (newState == SystemState.Suspending || newState == SystemState.Hibernating)
  {
  // STEFAN
  ServiceRegistration.Get<ILogger>().Info("SlimTvHandler: Shutting down. Stop all SlimTV Players");
  IPlayerContextManager playerContextManager = ServiceRegistration.Get<IPlayerContextManager>();
  for (int index = 0; index < playerContextManager.NumActivePlayerContexts; index++)
  {
  IPlayerContext playerContext = playerContextManager.GetPlayerContext(index);
  if (playerContext != null && playerContext.CurrentMediaItem is LiveTvMediaItem)
  playerContext.Stop();
  }
  }
  break;

This will correctly close the players (not only timeshift).

Next question:
How did you make the system suspending? Did you use the power menu (button in top right corner) or the "sleep" key on keyboard/power switch?
Is there a difference? I ask, because the first way does the broadcast before setting the WinApi to "suspend", while the hardware keys use opposite order (first windows event, then reaction in MP2)

 

[disaster123]

I used the power button at my logitech which uses the Intel nuc power button. So it's like pressing the power button.