Aug 25 2017 07:59 AM
Aug 25 2017 07:59 AM
We have one of those LogiTech Skype for Rooms systems with the Surface Pro / Docking station. Ever since the upgrade from v2 to v3 of SRS the system fails to present meeting content to the TV.
After a reboot the unit works fine. It shows the default splash screen on the TV and dashboard on the Logitech docking station/Surface Pro. I can start a video call or present from a laptop just fine. Fast forward - the unit is not being used for a while and goes to sleep. I come back 2 hours later, the unit activates. I turn on the TV and only see the (I assume) the desktop extension of WIndows 10 on the TV. I am supposed to the see the default splash screen of SRS, but only see the default Windows 10 background.
The docking station/Surface Pro shows the standard SRS dashboard. I plug in a laptop and it switches to presenting, but the TV stays on the default Windows 10 background.
Again, this worked fine in v2, but ever since v3 came out, this is bugging us. Any ideas how to fix this?
Aug 26 2017 02:32 PM
Aug 28 2017 12:25 AM
Faced with same problem. Current app is 220.127.116.11, winver is 15063.540.
As I remember, problems began after update to 18.104.22.168 application. The only workaround - restart SRS.
Sep 04 2017 07:49 AM
Yep - left on all the time.
I think its a feature of the TV not supporting the power on over the HDMI instead of the SRSv2 not doing it correctly.
Sep 06 2017 04:47 AM
Update out yesterday. Anyone tested?
Sep 06 2017 05:56 AM
I've seen issues where the external monitor just getting "no signal as well" anyone experienced that ?
Sep 07 2017 11:18 AM
I would have to disagree. This all worked fine with 2.0.x and broke once 3.0.x hit the system. Same TV, same everything.
Sep 11 2017 01:30 AM
Sep 11 2017 10:59 PM
Sep 12 2017 02:10 AM
Sep 12 2017 06:41 AM
These are high-end TVs, so that this is not the problem - especially as it worked fine before the upgrade to version 3.
Sep 12 2017 07:55 AM - edited Sep 12 2017 08:00 AM
@christophe limet I agree with @Christoph Puetz , we also are using high end SAMSUNG MEC Series professional displays with CEC and other industrial features and it doesn't realy matters, if this all features are on nor off. This issue appears randomly, from time to time without any information in event viewer. The system just hanging on (in our case we can see just frozen screen from one display), and needs to be restarted by pressing button for about 10 s. I realy hope that this issue will be fixed, because it is a roadblock for our deployment of 20-30 SRSv2 across the company.
Sep 13 2017 01:01 AM
Hi, the same issue reproduced with LG 60UH620V. HDMI CEC enabled.
Looks like problem appears when device rebooted with disabled TV:
1. TV is off;
2. Restart SRS device and wait until Skype room app loads;
3. Power on the TV and you will see only Win 10 background.
As I told, this issue appers after update to 3.x Skype app.
And another question about CEC workflow - how it should work? does it mean that PC would automatically power on TV?
Sep 13 2017 01:19 AM
Oct 06 2017 09:52 AM - edited Oct 06 2017 09:53 AM
In the single front of room display configuration, SRS v2 effectively creates 2 app windows, one for the console screen and another for the front of room screen. When power management wants to turn off the display (by default 10 mins of idle outside of a meeting), SRS v2 ceases to send any video signal, expecting the displays to go into standby. When motion sensor is triggered, the video signal is resumed, expecting the displays to turn back on automatically.
This power saving behavior is pretty standard for PC displays, but it appears that TV displays (including HDMI CEC enabled ones) seem to behave a little differently.
In this case, it sounds like the front of room display is turning back on automatically at the same time as the console display. If it is not, then it would be an issue with the HDMI CEC behavior.
The problem appears to be the front of room display showing the windows desktop instead of the SRS front of room screen. My guess is that when we stop sending a video signal, causing the displaysto go into standby, the front of room display disconnects itself (as if you turned the TV off), causing Windows to think that there is only 1 display (the console screen) connected to the system. This would cause Windows to relocate the SRS front of room window that was previously placed on the front of room screen to the console screen underneath of the console window that is currently visible.
I'll look into how we can handle this case better at the app level. In the meantime, you may want to look into if your front of rooms displays can be configured such that standby doesn't cause the display to disconnect from the PC. FWIW, I understand our internal deployments have a box between the SRS and Front of room TV to achieve this.
Hope this helps,