Reply to thread

Message

<blockquote data-quote="Benoire" data-source="post: 1008362" data-attributes="member: 121281">Hi Azzuro,&nbsp;If I've read that correctly, that thread is about supressing messages when TV Server isn't active or running.&nbsp; This suggestion is about improving the visible communication and feedback from the system when connecting to a channel.&nbsp; I.e. I have a Windows 2012 Server running TVE3 and Argus Scheduler.&nbsp; This is running 24/7 and client connect to it to watch stuff. &nbsp;When a client connects it can take around 6 seconds for the connection be made, the buffering to occur and the stream to be parsed correctly.&nbsp; During this time, nothing happens... All remote control actions are surpessed and the system appears to be locked out.&nbsp; IF we had a message that said something like &quot;Changing channel to xxxxx&quot; or similar (graphical or textual) I would know that the system HASN'T crashed and is working fine as during that window I have no idea if the connection will succeed.</blockquote>

[QUOTE="Benoire, post: 1008362, member: 121281"] Hi Azzuro, If I've read that correctly, that thread is about supressing messages when TV Server isn't active or running. This suggestion is about improving the visible communication and feedback from the system when connecting to a channel. I.e. I have a Windows 2012 Server running TVE3 and Argus Scheduler. This is running 24/7 and client connect to it to watch stuff. When a client connects it can take around 6 seconds for the connection be made, the buffering to occur and the stream to be parsed correctly. During this time, nothing happens... All remote control actions are surpessed and the system appears to be locked out. IF we had a message that said something like "Changing channel to xxxxx" or similar (graphical or textual) I would know that the system HASN'T crashed and is working fine as during that window I have no idea if the connection will succeed. [/QUOTE]

Verification