dirkenstein
Active member
Hi,
I managed to convert DD4WH's partitioned convolution filter code into an AudioObject- It seems to use more CPU that way but it does work.
It uses a _lot_ of memory with large parameter files but that's inevitable given the algorithm. Is it worth trying use PSRAM to store the arrays- would the speed be adequate if it paged parts of the arrays in and out? I doubt it, and i suspect the algorithm would hit CPU limits before the paging would have significant capacity benefits anyway.
I was hoping to try converting some convolution reverb impulse response files for testing but I don't think we can support the number of parameters these contain. Can you just truncate the files to fewer parameters? Will that truncate the reverb tails or add other unpredictable/nasty artefacts?
Regards,
Dirk
I managed to convert DD4WH's partitioned convolution filter code into an AudioObject- It seems to use more CPU that way but it does work.
It uses a _lot_ of memory with large parameter files but that's inevitable given the algorithm. Is it worth trying use PSRAM to store the arrays- would the speed be adequate if it paged parts of the arrays in and out? I doubt it, and i suspect the algorithm would hit CPU limits before the paging would have significant capacity benefits anyway.
I was hoping to try converting some convolution reverb impulse response files for testing but I don't think we can support the number of parameters these contain. Can you just truncate the files to fewer parameters? Will that truncate the reverb tails or add other unpredictable/nasty artefacts?
Regards,
Dirk