# Spectral "Compensation"?

**URL:** https://discourse.flucoma.org/t/spectral-compensation/299
**Category:** Usage Questions
**Created:** [August 4, 2019, 12:53pm UTC](https://discourse.flucoma.org/t/spectral-compensation/299 "2019-08-04T12:53:30Z")
**Posts on this page:** 1
**Showing post:** 34

<div class="post-metadata">

### Author: ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [August 17, 2019, 1:32am UTC](https://discourse.flucoma.org/t/spectral-compensation/299/34 "2019-08-17T01:32:51Z")

</div>

> [@a.harker](#):
>
> I haven’t looked at the code, but as far as I’ve understood what fluid.loudness~ is doing it’s not quite that simple, because of the way that code is working \*I’d have to check to be sure of that) - the code also pulls in a whole library (Eigen) that I don’t really want to pull into the frame lib repo and manages memory in an inappropriate manner for frame lib purposes.

Curious what direction you will go with then.

I do find the results of whatever core algorithm (ITU BS 1770?) is being used in `fluid.loudness~` quite effective.

And/or if whatever you do come up with will back propagate to `descriptors~` ([`descriptors~` funny business with loudness](http://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205/97))

> [@a.harker](#):
>
> Sounds like you need to do that frame lib tutorials - but yes.

Indeed. @jamesbradbury has also kindly agreed to a brain picking session too, so that will no doubt be fruitful.

---

_[View the full topic](https://discourse.flucoma.org/t/spectral-compensation/299)._