Thank you for giving the above a test, and for the additional information! Our team will chew on this some more and continue to investigate.
I will follow up as soon as I can! Most likely early next week as our team is offline over the weekends.
1 Like
Hey @Richard_Patton,
Thanks for your patience again! After further review, we’re seeing some odd RAATServer errors like the one below:
03/26 11:32:04 Trace: [raatmanager/windows] failed to get default device HRESULT=0x80070490
After investigating this error a bit more, we believe it may be linked to a corrupt file in the windows OS (which feels odd considering you’re seeing this issue across multiple windows cores) via this article here:
In the same breath, performing a full reinstall of your Windows OS can be very tedious, and we cannot yet verify the above errors are the correct fault of the issue itself.
If possible, could we get a set of manual logs from one of your windows 11 core devices as well? It would be helpful to compare logs to see if similar errors are popping up. Use the directions found here and send over a set of logs to our File Uploader.
I doubt this is an issue with a Windows system file. I see the same issue on many Windows machines. I have other programs such as Foobar 2000 which have no problem playing my 192kHz multichannel files on the same PC and audio recover via WASAPI. So I have deffinitely found that it is only files over 96kHz that are problematic. It turns out I didn’t actually have any 192kHz mutichannel FLAC files (all of mine were 96kHz or less) so I never encountered the error. I found some on Qobuz which highlighted the problem for me then I up sampled a 6 channel 96/24 file using Audacity to 192/24 and indeed found that that failed too.
I have uploaded both the RAATserver and RoonServer logs from my main core machine to your upload server under the name of “Richard Patton Server Logs 3-28-2023”
I believe I know where the “failed to get default device” error in the RAATServer log is coming from. The error occurs every minute on my main Roon Core machine which runs on Windows Server 2016. As a server it normally doesn’t have any connected audio devices. In fact they are disabled by default. Although not disabled on my server, there was no default audio device defined or connected. This morning at about 9:30am I enabled the audio and connected a pair of disposable earphones to the speaker jack and as you will note from the RAATServe log I uploaded this morning as “Richard Patton RAATServer log 3-29-2023 (partial)” the error message went away as Roon found a connected audio device. Note however that a while later a new error message appears every minute “Error: [raatmanager/windows] failed to get device enumerator HRESULT=0x800703fa” . . . These are obviously bugs in your RAAT Server software.
Hey @Richard_Patton,
Thanks for your observations here and updated information. We’re still in the process of trying to reproduce this issue in-house. I will keep you in the loop as things progress. 
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.