• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

DecayCore — Free FIR room correction with temporal decay control, automatic optimization and measurement workflow

I prefer new look (but I never really liked the old one)
When I click on red button right down (Power Off) whole screen gets flooded with repeated
....
NetworkError when attempting to fetch resource.
NetworkError when attempting to fetch resource.
warnings
(running aarm64 version on RPI5)
Version 1.3.5 installed, unlike older version this one can be accessed only from local machine for some reason. Visually it is a step up.
Fixed and enabled at v1.3.6
 
Hi Vilho,

Two issues on DecayCore 1.3.6, local machine Ubuntu 26.04, remote Win11:

1) install.sh fails: apt says libasound2 is a virtual package with no install candidate. Needs to request libasound2t64 instead.

2) --lan mode broken: opening the printed LAN URL from remote machine gives a partial page load. Console error:
Uncaught TypeError: crypto.randomUUID is not a function (app.js:14:23)
Afterward the UI shows "Connection to DecayCore was lost" and the Network tab fills with 403 Forbidden on POST /api/event and GET /api/state.
 
Hi Vilho,

Two issues on DecayCore 1.3.6, local machine Ubuntu 26.04, remote Win11:

1) install.sh fails: apt says libasound2 is a virtual package with no install candidate. Needs to request libasound2t64 instead.

2) --lan mode broken: opening the printed LAN URL from remote machine gives a partial page load. Console error:
Uncaught TypeError: crypto.randomUUID is not a function (app.js:14:23)
Afterward the UI shows "Connection to DecayCore was lost" and the Network tab fills with 403 Forbidden on POST /api/event and GET /api/state.
Both fixed at v1.3.7
 
From a REW measurement standpoint, how do we assess improvements in phase and group-delay, following implementation of DecayCore FIR?

Consider some examples in post 185 above of 3 dips on the SPL vs frequency plots of SL (surround left) and Center at:

SL 101hz
SL 200hz
C 181hz

To review the context, this is a 7.1 system, single sub, DecayCore generating independent linear-phase FIR filters per channel group (L-R, Center-Center, SL-SR, BL-BR, LFE-LFE) against a Harman 8dB target. Sub integration (crossover, sub gain/delay, LF time-alignment of Center/Surround/LFE into the sub bus) was done *before* generating DC filters. I later found DC's filters shift phase near each channel's own crossover by a non-trivial amount (not a software bug), which threw off the original sub-bus timing — and re-measuring/correcting that timing is what the earlier post was about. In this post, I want to consider what DecayCore might have done to result in improvements of the above 3 dips, with respect to phase and group-delay.

So here are some closer looks at SL and C plots of SPL, phase, and group delay (negative slope of phase), each as a function of frequency: 1) Green is after the first sub integration, the measurement done for input into DC (before DC), 2) Blue is after DC with the original (pre-DC) sub-bus delays, and 3) Red is after DC, with re-corrected sub-bus delays (second time alignment).

Surround Left (SL): SPL, phase, and group delay plots
View attachment 556468

View attachment 556467

View attachment 556466

Center SPL, phase, and group delay plots

View attachment 556471

View attachment 556470
View attachment 556469


First, the observation. For each of the 3 peaks: pre-DC (1, green) and post-DC-only (2, blue), there's a magnitude dip in SPL paired with a rapid group-delay swing at the same frequency. After the DC FIR and the corrected sub-bus delay (second alignment) are both applied, the SPL dip largely closes, the phase slope smooths out, and the GD trace flattens to a constant slope through that region (3, red). One aspect that I hinted on the post 185 above is that the disappearance of the SPL dip probably depends on BOTH the DC FIR and the second alignment of the sub-bus.

What are the underlying physics and/or engineering driving this observation? What was it that DecayCore did to help out with this, that wasn't enough by itself, but when combined with the second sub-bus alignment, resulted in removing these 3 huge dips? Again, if it was just the sub bus alignment, that should have been fixed before DC and we should never have seen these dips on the #1 green plots.

From the DC summaries (see post 183), TDC was applied to the 101hz SL peak, and the 181hz Center peak, but TDC was not applied to the 200hz SL peak. So I don't think it would be TDC because that explanation doesn't cover all 3 peaks. Or maybe it is TDC? Could a TDC-driven improvement at 101hz somehow also benefit 200hz, perhaps something to do with 1st and 2nd harmonics? I couldn't find anything else in the DC summaries that might explain what DC contributed here, but it certainly looks like it did from this analysis.

This is one example that I highlight toward the larger question, which is how do we assess DC or FIR-based improvements in phase and group delay using measurements?
The likely explanation is the sum of the main speaker and subwoofer responses. If they partly cancel, the SPL drops and phase changes quickly around that frequency. DecayCore changes the main-channel response; the second alignment changes the sub’s timing. Together they can reduce the cancellation. The best delay can change after the FIR is applied, so an alignment that worked before DC may no longer be optimal.

The plots don’t show exactly how much each step contributed. We’d need measurements with DC on and off at both sub-delay settings. TDC at 101 Hz would not normally improve 200 Hz through a “second harmonic” effect; a linear FIR doesn’t work that way. And a group-delay spike at a deep SPL dip isn’t, by itself, proof of a timing problem.

To assess phase or group-delay improvements, compare before and after with the same timing reference and setup, and repeat at nearby mic positions. Check that the change is present in the measured response.
 
Hi Vilho,
I installed the latest version but maybe something wrong here. I use Macbook M2, with Umik 1, and output device is a FIO DAC. Decaycore always said the volume low and can not measure but actually everything normal with REW.
even I increase the volume to very high than my normal listening, the sound test from Decay still quite small.
Could you double check this issue?
 
Hi Vilho,
I installed the latest version but maybe something wrong here. I use Macbook M2, with Umik 1, and output device is a FIO DAC. Decaycore always said the volume low and can not measure but actually everything normal with REW.
even I increase the volume to very high than my normal listening, the sound test from Decay still quite small.
Could you double check this issue?

Sweep defaults to −12 dBFS, and DecayCore rejects recordings that peak below −40 dBFS.
Could you share the “Recording peak” value from DC?
 
@VilhoValittu - Thank you for sharing DC :D If I might be so bold, could I add one for the wish list?
Given you already have in place clock drift adjustment would it be possible to do the sweeps from files played through streamer rather than sound card?


Edit: The seem to be a small UI bug in v1.3.7 for Win11 using Brave reader. Somewhat contradicting message had me select file twice before I noticed the small print ;)

1790677934715.png
 
Last edited:
@VilhoValittu - Thank you for sharing DC :D If I might be so bold, could I add one for the wish list?
Given you already have in place clock drift adjustment would it be possible to do the sweeps from files played through streamer rather than sound card?


Edit: The seem to be a small UI bug in v1.3.7 for Win11 using Brave reader. Somewhat contradicting message had me select file twice before I noticed the small print ;)

View attachment 561672
Hi,

Sweep playing thru file is possible but I have locked option to do it. Many reasons and bugs for that BUT maybe someday...

I will fix that UI bug to next release.
 
Hi @VilhoValittu I might have found a small issue with the new theme (which is nice by the way, although i like the C64 one too) I cant seem to find the "Export formats" option, i might be blind but it is not readily apparent where it is
 
Hi @VilhoValittu I might have found a small issue with the new theme (which is nice by the way, although i like the C64 one too) I cant seem to find the "Export formats" option, i might be blind but it is not readily apparent where it is
1790788935162.png

Hi,

It's at START page / Output settings . Maybe I should highlight that littlebit more.
 
Hi,

Version 1.4.0 is out.

This release includes a new phase correction algorithm and minor UI updates.

I’d appreciate feedback on how it sounds.
 
Finally got around to trying this out yesterday, and I'm really impressed, thank you for what must be a lot of hard work.

I used an existing REW measurement from a few weeks ago, and stuck to the out of the box auto config, it was easy to use and much quicker than me messing about with REW. I'll try the guided measurement in a few weeks when I have time, interested if that produces even better results.

As well as being easy to use the sound is fantastic, I've never managed more then a few hours with an auto generated EQ before going back to my home brew light touch filters, but so far I've got zero audible issues, and lots of positives. I strongly agree with your trust what you hear more than the graph statement in the instructions, I've learnt that the hard way with my own filters.

One thing I prefer with my home brew filters is to use a high pass, the auto filters didn't do this, is there an easy easy to turn it on but leave everything else auto?
 
One thing I prefer with my home brew filters is to use a high pass, the auto filters didn't do this, is there an easy easy to turn it on but leave everything else auto?
Thanks for the kind words, and I'm glad it's working well for you. Trusting your ears over the graph is the right call.

On the high pass: Auto mode is meant to work with as few choices as possible, so there's no separate HPF switch in it. It does test high-pass options during its search, though. If one improves the result, it's used. If it makes the overall result worse, DecayCore leaves it out. So the lack of a high pass in your filters means the HPF candidates didn't beat the version without one on your measurement.

You can still try a manual high pass without giving up the auto result. Auto mode saves its results for each measurement. go to Setup, select Advanced-mode and click Apply saved auto settings. Pick the saved run for your measurement and apply it. All the values auto mode chose are then loaded into the Advanced controls. From there you can switch on the high pass you like, leave everything else as auto set it, and generate the filters. This way you can A/B the auto version against the one with your HPF.

Saved parameters belong to the original measurement. Remember use same target curve.
 
Back
Top Bottom