• 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

v1.1.2.2_meas_beta

Added Linux measurement improvements: device lists can now be refreshed in the UI, and subwoofer measurement no longer assumes a fixed 4-channel/LFE layout. Linux users can select the subwoofer output channel explicitly, which also enables 2.1 virtual devices to appear and validate correctly.
 
Last edited:
Sorry confused.

No Stereo Subs?

> no longer assumes a fixed 4-channel/LFE layout.

what did that used to mean?

And how does it work now?
 
No Stereo Subs?
Yes, stereo subs are supported, but they must be measured one at a time.

> no longer assumes a fixed 4-channel/LFE layout.

Previously, Linux subwoofer measurement assumed a fixed 4-channel/LFE-style layout. That was too restrictive for virtual 2.1 devices and other custom channel setups.
And how does it work now?

On Windows, LFE output is typically tied to a multichannel device layout, so the program may need to open the full channel set. On Linux, this is now more flexible: you can choose which output channel is used for the subwoofer measurement instead of being limited to a fixed LFE channel.
 
Doesn't PipeWire allow for the routing flexibity you need?

and/or JACK, apparently they work well together.
The and/or part depends on whether you're talking about the daemon or the API. The PipeWire daemon is a replacement for the JACK daemon and the PulseAudio daemon. It implements their APIs for compatibility, so an application with a JACK audio backend can work with the PipeWire daemon in place of the JACK daemon.
 
I have been working with UI for a while. When visual are ok, then I will really put effort on Bass Integration.

A little peek at what DecayCore will look like.

ui_1.png
metadata.png
 
Added Linux measurement improvements: device lists can now be refreshed in the UI, and subwoofer measurement no longer assumes a fixed 4-channel/LFE layout. Linux users can select the subwoofer output channel explicitly, which also enables 2.1 virtual devices to appear and validate correctly.
dont work - DC not see virtual card, not see anything

1781436420096.png

1781436473151.png
 
I hope no one will deny the fact that there are two broad groups of people: one group is interested in sound correction based on a "push the button — get the result" principle, while the other group enjoys the very process of learning the correction procedure and carrying it out from start to finish on their own.

Initially, I wanted to follow the path of the second group. But I quickly realised that if I delved too deep into the subject, my brain might not handle it :oops:

So I decided to turn to "simpler" programs. To start with, I tried GSonic Reference, but nothing worked — on my operating system (Arch Linux), it was impossible to take measurements, the sound was extremely faint and heavily distorted (crackling).

Then I looked at DecayCore, but the first attempt didn't really work out.

After some time, I decided to try DecayCore again, and somehow it just fell into place. In the sense that it was more or less clear what to do (thanks to the reasonably clear DecayCore User Manual), and the measurements themselves were free of sound distortion. That seemed like a good sign.

At first, I didn't even pay attention to the quality of the measurements — I just wanted to figure out the program. I tried it one way, then another. When I felt ready, I carried out the measurements as carefully as my conditions allowed. The result was not a night-and-day difference compared to "before correction", but it was quite noticeable and acceptable to me. I shared the entire session data with the program's author, as he requested in his post. @VilhoValittu thanked me for it and, on his own initiative, offered some tweaks to my result. The sound became even better — the stereo panorama became more "focused", and the sound felt more "even" and "proper". I am quite satisfied with the result.

So, DecayCore is indeed capable of performing a reasonable correction through a fairly simple sequence of steps. And it seems to me that the result will satisfy a great many people.

After that, one can continue to explore the "heavyweight" programs in small steps, if they so wish ;)

Once again, I want to thank @VilhoValittu for this program! It is not perfect yet, but seeing how diligently the author is working on it, I am confident that it will only get better.
 
Last edited:
I hope no one will deny the fact that there are two broad groups of people: one group is interested in sound correction based on a "push the button — get the result" principle, while the other group enjoys the very process of learning the correction procedure and carrying it out from start to finish on their own.

Initially, I wanted to follow the path of the second group. But I quickly realised that if I delved too deep into the subject, my brain might not handle it :oops:

So I decided to turn to "simpler" programs. To start with, I tried GSonic Reference, but nothing worked — on my operating system (Arch Linux), it was impossible to take measurements, the sound was extremely faint and heavily distorted (crackling).

Then I looked at DecayCore, but the first attempt didn't really work out.

After some time, I decided to try DecayCore again, and somehow it just fell into place. In the sense that it was more or less clear what to do (thanks to the reasonably clear DecayCore User Manual), and the measurements themselves were free of sound distortion. That seemed like a good sign.

At first, I didn't even pay attention to the quality of the measurements — I just wanted to figure out the program. I tried it one way, then another. When I felt ready, I carried out the measurements as carefully as my conditions allowed. The result was not a night-and-day difference compared to "before correction", but it was quite noticeable and acceptable to me. I shared the entire session data with the program's author, as he requested in his post. @VilhoValittu thanked me for it and, on his own initiative, offered some tweaks to my result. The sound became even better — the stereo panorama became more "focused", and the sound felt more "even" and "proper". I am quite satisfied with the result.

So, DecayCore is indeed capable of performing a reasonable correction through a fairly simple sequence of steps. And it seems to me that the result will satisfy a great many people.

After that, one can continue to explore the "heavyweight" programs in small steps, if they so wish ;)

Once again, I want to thank @VilhoValittu for this program! It is not perfect yet, but seeing how diligently the author is working on it, I am confident that it will only get better.
A professional approach would always include: tap on the knob, and you're done ...
or ...
dig deeper into what is presented and choose wisely, it's at your choice.
 
Just tried your Mac fix. When I try to do a measurement I'm getting the white/pink noise test signal overlaid on the sweep which doesn't work of course.

Mac M2 mini, Tahoe 26.4.1
 
Just tried your Mac fix. When I try to do a measurement I'm getting the white/pink noise test signal overlaid on the sweep which doesn't work of course.

Mac M2 mini, Tahoe 26.4.1
Did you change Timing dither level? for some reason? Basic value is -90.
 
No, I did not.
 
And be careful with the use of any dot (.) and/or comma (,) , best it to not use it :cool:
 
i think an option to store (and maybe restore) configuration and measurement in computed filter zip can be useful
also, the 352800 and 384000 rate over 192000 can be useful (i have few track with that, probably DSD ones)
 
Back
Top Bottom