Core Machine (Operating system/System info/Roon build number)
Roon Version 1.7 (Build 710) Core.
Intel® Core™ i5-8400T CPU @ 1.70GHz
Intel® UHD Graphics 630
Realtek High Definition Audio
Intel® Display-Audio
USB Audio Device
32 GB RAM
Samsung MZVLB512HBJQ-000L7
QNAP TR-002 DISK00 USB Device
QNAP TR-002 DISK01 USB Device
Samsung SSD 860 EVO 2TB
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Intel® Ethernet Connection (7) I219-V
Intel® Dual Band Wireless-AC 8265
Intel® Wireless Bluetooth®
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Hugo 2 WASAPI
Description Of Issue
I have recently moved to Windows 10 and transferred Roon there as my Core. I am noticing some bugs on Windows 10 that didn’t exist on my ten year old Thinkpad running Windows 7.
I have about 12TB of music, a total of 72095 tracks - all in either FLAC, WAV, or DSD format. They all have album art. It took about 3 days, but Roon has now carried out a background audio analysis on this data. Despite having a far more modern system with much greater resources than my previous Thinkpad, I’ve noticed two key issues:
I am experiencing the bug where characters are occasionally missing - individual letters, numbers, etc. I have inquired about this and evidently it’s a known issue. Since then, I’ve reinstalled Roon, updated my graphics drivers, but the problem persists. It’s an annoying issue that gives Roon a sort of “broken” appearance.
It seems that as soon as this issue occurs, another one follows: the waveforms get “stuck” - i.e., whatever the last successful waveform was, it will then repeat itself on the next track irrespective of what that track is.
I’ve also noticed that Roon can use anywhere between 4GB to 9GB of system memory.
These problems are new to me and never occurred on Windows 7. I would very much appreciate a fix, because it somewhat tarnishes the experience.
Both. I tried with the Lenovo drivers and from today the generic drivers from Intel. None seem to make any difference, though both work as normal otherwise.
I double checked this; the problem(s) remain. I also rescanned my data, but the problem persists. I would be tempted to re-analyse the whole lot, just in case the original audio analysis was somehow corrupted the first time around.
Thank you for the screenshots and for your patience while your case reached my queue again!
Yes, logs may be useful here, can you please use these instructions to access them and send me a set?
Have you tried a fresh database on this Core? After sending logs, can you please use these instructions to set your current database aside and verify if a fresh database and a small portion of your library have the same behavior? This should give us a good data point to work with.
Thanks for looking into this. I will send my Logs to you in a RAR folder in a moment.
I have just tried a fresh database re-installation - removing all 12TB of music and replacing it with a fresh and cleared install of just one folder, “Heavy Metal,” which weighs in at 1.27TB. I should also add, I organise all my library in 3 main categories: A To H; H To P; P To V. Inside those main folders are a series of genre folders.
In any case, I tried this and yes, the problem still persists:
Hope you have a great New Year and thank you for trying the fresh database! This confirms that the issue is not database-related but possibly hardware. Your logs are currently with our QA team for review, once I have the team’s take on it, I’ll reach out again. Thanks!
Hi, thank you. I have now upgraded my machine from a ThinkCentre M720Q to a ThinkStation P340 Tiny, the latter comes with a dedicated GPU (NVIDIA Quadro P620), so the previous problem has been resolved (although I will never get the heart of what caused it in the M720Q, because even when using the optional integrated GPU on the P340, the issue is not there).
