Release Notes
Notice: Vibeshine can trigger false positive antivirus alerts. See the details and workarounds here: #59
v1.11.2
Display Helper Architecture
- Reverted display helper to run as an external process (matching v1.9 behavior) instead of in-process execution.
Performance Improvements
- Display helper now uses faster API queries, significantly improving response times.
- Optimized display settings validation logic, reducing stream startup delays.
Responsiveness & Async Handling
- Reworked display helper with improved asynchronous design, enabling:
- More responsive operation during display changes
- Instant cancellation of pending revert operations (previously would delay streams and caused a see-saw/oscillating behavior)
Display Snapshot Stability
- Fixed snapshot timing issue: snapshots are now captured before virtual monitor initialization rather than after.
- This prevents invalid snapshots caused by topology changes that occur when virtual displays activate (activating a virtual display can alter the display topology, which was causing corrupted snapshots in the previous implementation).
v1.11.1
Due to error reports in the past few days this build makes several changes to make the display settings automation close to how it worked in v1.9 as this seemed to work better for some users.
- HDR Profiles are now removed from virtual displays if windows assigned the wrong one automatically to it.
- Reworked double refresh rate on virtual screens, it now works better with display overrides, ensuring that the refresh rate is at a minimum doubled rate instead of locking it to exactly double.
- Removed the 503 Display Application failed error, and it is now considered best effort instead of rejecting the stream entirely, matching closely to how it worked in v1.9.
- Added UI warnings to Extended and Extended Isolated about how Windows does not show the lock screen on external monitors and you would need to click on the black screen to activate them.
- Reverted a change that forced virtual screens to change the output name, which potentially caused more black screen issues for some users.
Changes
- Virtual Screens (per client) can now retain HDR Color Profiles in Windows
- While running the HDR Calibration utility, simply save the profile name to be exactly the same as the displayed display name under the form field.
- After doing this, all future connections from that client will retain the HDR profile.
- Adjusted display restore logic, it will now purge state on any successful golden restore to prevent instances of tug of war between invalid display profiles.
- Fixed an issue that prevented hosts with dual monitors from being able to use the virtual screen.