# Descriptors comparison (oldschool vs newschool)

**URL:** <https://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205>\
**Category:** Usage Questions\
**Created:** [May 26, 2019, 12:04am UTC](https://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205 "2019-05-26T00:04:57Z")\
**Posts on this page:** 1\
**Showing post:** 88

<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 20, 2019, 4:21pm UTC](https://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205/88 "2019-07-20T16:21:59Z")

</div>

> [@tremblap](#):
>
> that is what I propose with different timings: if you did a short mid and long term window you could then play them as such! basic cross fade to start with, and offset in the start, and boom, you have something that is a bit like when Diemo stitched CataRT with MultiConvolve~ and could be a fun prototype to try.

I meant analyzing only 100ms and then querying that with 11ms fullstop. Not stitching. As potentially a better solution than analyzing the entire sample and querying it with a tiny fragment of audio.

Even with stitching, there will be the problem of temporal mapping as I’m largely using sounds that are quite short, and want to have samples that are arbitrarily long. So even with perfect stitching, I wouldn’t want to play a 100ms sound and get a 100ms sound back. (an idea I have for this is to use the time series from `fluid.descriptors~` objects and time-stretch them onto longer samples, so something like `multiconvolve~` meets a clock that’s slowing down)

---

_[View the full topic](https://discourse.flucoma.org/t/descriptors-comparison-oldschool-vs-newschool/205)._