I’m using a few different convolution filters, all created with 66K taps. All my filters have cfg and wav files for each sample rate from 44.1 through 352.8, and are in zip files for Roon.
I have presets in Roon DSP for each filter.
Roon always uses 66K taps for one of the filters, but adjusts the number of taps based on sample rate for the other filters.
Any idea why Roon acts differently for these different filters?
This has to rank high on the “please excuse us for the delay, we’ll be back to you soon” record book. Definitely not an issue vs. folks with gaps or who can’t play music, just aesthetically, well you know, a long time.
While we’re at it let’s fix that memory leak as well. Roon would frequently choke my old M1 Mac mini with 8GB of RAM. My new M2 mini has 24GB of RAM and Roon will happily use it all and dip into disk swap usage if I leave Roon running for more than 12 hours. I do not use Roon for convolution or resampling for these reasons.
Roon is a great app, the metadata is great. Fix the important stuff please.
My measurements were taken at 24bit/96khz using Impala and a UMIK2. The filter was made in Focus Fidelity.
Filter length @ 0.743/0.683 Seconds
Filters were exported as .wav and loaded into
Roon as a .zip file.
All 88.2khz and 96khz content has 66k taps
All 44.1khz and 48khz content has 33k taps
All 176.4khz and 192kHz content has 131k taps
All 352.8khz and 384khz content has 262k taps.
As track/sample rate changes the taps change. They are never different tap numbers than what I have shown above. For example it never reads 192kHz 66k taps or 44.1 262k taps.
“While we’re at it let’s fix that memory leak as well…”
Thanks Chad, second that. I was among the first to report this problem years ago and there’s still no fix. I’ve stopped using Roon until they do.
Ben here with the support team, thanks for writing in and bringing this to our attention. As a next step, could you please upload your convolution filters here for our team to investigate?
I wanted to give you a quick update - we were able to reproduce the issue in house, and have a ticket submitted with the team for a fix. I will continue to keep you in the loop with any progress.
Just dropping in to let you know a fix is still in progress, and that we haven’t forgotten about it! Thanks again for your continued patience in the meantime.