# Regression + Classification = Regressification?

**URL:** https://discourse.flucoma.org/t/regression-classification-regressification/547
**Category:** Pre-Release Toolbox2 New Ideas
**Created:** [July 4, 2020, 5:14pm UTC](https://discourse.flucoma.org/t/regression-classification-regressification/547 "2020-07-04T17:14:49Z")
**Posts on this page:** 1
**Showing post:** 20

<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: [July 14, 2020, 9:48am UTC](https://discourse.flucoma.org/t/regression-classification-regressification/547/20 "2020-07-14T09:48:20Z")

</div>

In this case I only have a 6ms window anyways, so a few ms is pretty big all things considered!

In the [JIT-MFCC testing](https://discourse.flucoma.org/t/onset-based-regression-jit-mfcc-example/464) I played around with moving things back by some samples, but that didn’t seem to make any meaningful difference.

My theory here is that since I only have a finite amount of sounds I can make with my snare, that specifically the attack will give me a reliable (enough) idea of what the next 94ms will sound like.

I did think about trying to compensate for the re-onset-detection stuff, where I +/- some samples on either end to compensate for the fact that the final audio will have gone through that process twice, but I don’t think that will generalize out.

---

_[View the full topic](https://discourse.flucoma.org/t/regression-classification-regressification/547)._