· None of the above quite fits
· None of these quite match
· Roon window does not reopen in position where closed
· All ubiquiti unifi, based on Unifi UDM-Pro
Start Roon Client (Windows 11, 25H2),
Shift Roon window to far right location on screen.
Shut down Roon Client.
Restart Roon Client. Window is in some default position, not in far right where it was when shut down. Repeated start/move/stop/restart cycles will always show Roon window in this same default position.
All other Windows apps in this environment do remember the location at which they were closed.
I found an Aug 2022 community entry discussing a similar problem and mentioning a \\\AppData\Local\Roon\Database\Registry\Client\saved_window_pos file. I tracked this file through an open window/move window/close window/reopen window cycle. The save_window_pos file is updated when I move the window and close it but it is apparently ignored when Roon Client is restarted.
Further investigation indicates I may be seeing an out-of-range condition.
I am using a 32:9/5120x1440 monitor. If I move the Roon Client window to the left of the assumed default position that new position is remembered when the client restarts. If I move the the Roon Client window to the right of the assumed default position to some point past about two thirds of the screen width, that location is not remembered and the client restarts in the assumed default position. FYI, when the Roon Client is moved to the far right and closed the saved_window_pos file contains 3591|0|1024|918 . Reopening the Roon Client seems to ignore this setting. The saved_windows_pos file for the assumed default position is 1195|96|1024|781.3333.
What is the next step?
Hello @Raymond_Elseth ,
Thanks for reaching out and for the detailed report. I tried to reproduce this issue on my end across three 1080p screens, but it seems like it is working as expected for me when moving the window in any direction (left/right/up/down) and even half in-between monitors, so it may be something specific to your setup/screen resolution. Are you also able to reproduce this issue on 1920×1080 resolution, or does it only occur on the widescreen resolution?
Screen Resolution (and Scale) is at the heart of my issue.
My monitor is a 49" 1000R curved screen Samsung G9 driven by a Nvidia GeForce 4070 graphics card. I have been using this combination for the last 2-1/2 years. While this isn’t exactly a common monitor/card combination, there are a lot of them out there. The monitor/card can be defined at a lot of different resolutions and Windows allows defining a lot of different scales for those resolutions. My default settings are 5120x1440/150% scale. All my other Windows applications can be located where I wish and properly recalled in that environment.
Up until recently Roon Client would locate where I wished on my monitor with my settings and would remember its location when I stopped and restarted the Client. After a Roon update (more than 2 but less than 8 months ago), it would still locate where I wished but it would no longer remember that location when I restarted the Client. I lived with it for a while but finally decided I would report it so the window would not require manual repositioning every time I restarted the Roon Client.
Based on the testing I did above, the problem obviously lies with the mechanism by which the Roon Client (and only the Roon Client) window position is stored and recalled. I have tested it with resolution set to 2560x1440 and the window position is properly recalled. I also did some additional testing and discovered that with the resolution set to 5120x1440 and the scale set to either 100% or 125% the window position is properly recalled. When the resolution is set to 5120x1440 and the scale is set to 150% the window can be placed where I want it (at the far right) and will function as expected but the window will not re-appear at the previously-set location when the Roon Client is restarted.
What is the next step?
Hello @Raymond_Elseth,
Thank you for the thorough investigation - this is an excellent report.
You have pinpointed the inquiry precisely: at 5120x1440 resolution with 150% DPI scaling, the X coordinate stored in saved_window_pos (3591) appears to exceed the boundary that Roon’s window position restoration logic expects, causing it to fall back to the default position on restart. The fact that it works correctly at 100% and 125% scale, and also at 2560x1440, strongly suggests an integer overflow or coordinate calculation error in how Roon maps scaled screen coordinates.
We are flagging this as a bug for our development team to investigate. For reference, the key reproduction case is:
We will update this thread if we have further information from the team.
Thanks for the reply.
I’m glad we agree on the nature of the bug. I realize this won’t be a quick fix. I do understand that 125% scale would allow the Client screen to properly reposition on restart but 125% scale is less than optimum in my normal viewing environment. I’ll keep watching for a fix in a future release. If I don’t see something in two or three months I’ll attempt to reopen this ticket. Failing that, I’ll open a new ticket.
Hi @Raymond_Elseth,
Thank you for understanding. To set expectations: fixes are prioritized based on the number of users affected and the overall impact on the product, so I can’t commit to a specific timeline for this one. Since this issue appears under a fairly specific configuration (5120x1440 at 150% scaling), it may take some time before it’s addressed.
The bug is moved to the QA tea team for reproduction, and we’ll update this thread as soon as there’s any progress. There’s no need to reopen or create a new ticket — this report won’t be lost.