A post was split to a new topic: Roon crashes every night
@benjamin can you provide an update about this bug?
Hey @cass_fisher,
I don’t have much to share at this time - the ticket for this bug is still in progress within our development queue. I’ll be sure to keep you in the loop as things progress. 
1 Like
Hi @benjamin I just wanted to share with you comparison measurements of Roon’s convolver vs Hang Loose Convolver:
Conclusion: While Roon may have a convolution bug of some sort, it is definitely not affecting or corrupting the frequency or phase response of these high resolution headphone FIR filters.
2 Likes
This is odd behaviour, thanks for the article @Mitch_Barnett .
I use FIR filters extensively and have never seen this issue (thanks for highlighting)… but all my Tap counts match sampling rates @ a 1:1 ratio.
For what it is worth, I used REW and rephase to create my convolutions.
I hope you get a resolution here…
My experience…
I use Roon to execute 2 way convolution Crossovers (JBL M2) and Room correction, using individual convolution instances/filters. I created convolution files at each sampling rate manually, with a tap count ratio 1:1 with sampling rate. I have never seen the issue you present above (thankfully), but I have had Roon FIR let go, which I am yet to have Roon assistance on to diagnose.
Maybe the Roon display issue doesn’t appear at the tap counts I’m nominating. Very odd.
Here are mine @ each sampling rate.
44.1k
88k
96k
192k
Here’s a 32k taps, 48kHz sampling rate, stereo convolution filter for your developer team tests:
Roon correctly up/down samples the filter according to source and the correction works as intended but the tap count has the same problem explained above.
I would like to bring this topic up again, since there is NO FIX since more than three years.The original bug report was by @ComputerAudiophile, and - similar to what he did - I am using two different convolution filters provided by @Mitch_Barnett.
My Roon Core runs on a Windows 10 (64-bit) laptop with 16 GB of RAM. As a DAC, I am using my Cayin N8ii DAP hooked up directly to the USB output from the laptop; drivers used are the Cayin-supplied ASIO driver and WASAPI exclusive. The N8ii is capable of PCM up to 768 kHz as well as native DSD up to DSD512 (and thus DoP up to DSD256). It displays sample rate information numerically when operating as a USB DAC, great to check.
The filters used here are Mitch Barnett’s HF Rolloff (a filter for testing) = Filter 1 in the tables below, and Sennheiser HD 800 S Frequency Response Correction = Filter 2. Both filters come at 65,536 taps.
I am providing information here on what Roon’s signal path displays as filter tap size, and I do this comprehensively for a whole bunch of bit depth / sample rate tracks.
Here are my results for filter taps from the Roon signal path displays for PCM tracks. They are identical for both the ASIO and WASAPI drivers:
Filter 1 Filter 2
16/44.1 62k 22k
24/44.1 62k 22k
24/48 66k 24k
24/88.2 66k 44k
24/96 66k 48k
24/176.4 66k 66k
24/192 66k 66k
32/352.8 66k 66k
Next group of tests with DSD tracks (file type *.dsf). These seem to work only with the ASIO driver:
Filter 1 Filter 2
DSD64 524k 524k
DSD128 1049k 1049k
DSD256 2098k 2098k
DSD512 4195k 4195k
Next group of tests with MQA tracks (… just out of curiosity …). As might be expected, the Roon signal path display of filter taps is the same as for PCM tracks. Roon does the display according to the appropriate line in the first table above, just according to what is being chosen as the device properties (N8ii as MQA decoder & renderer / only renderer / only decoder / nothing) and the disabling / enabling of the core decoder in Roon itself.
Thus, it is obvious that there is NO FIX for this bug since having been reported more than 3 years ago. Convolution filters have an important role in DSPing, e.g. in room correction and headphone correction. THUS I SHOULD LIKE TO BRING THIS BUG UP TO THE ATTENTION OF THE ROON DEVELOPERS AGAIN - thanks a lot in advance.
Remark: I hope the table formatting works …
@benjamin, I just would like to bring my previous post to your attention. (I wasn’t allowed to at-quote more than two people …). Thanks a lot in advance.
Closed due to inactivity. If you are still seeing this issue, please open a new support thread.