Convolution Broken...

  • @mwplugs I'm using the convolution on a new project with IPP enabled and it's working okay at all sample rates. Maybe it's the version of HISE that we're using. I think I'm on the version from Jan24.
    @Christoph-Hart I did notice that a project using the convolution FX will make PluginDoctor crash if "multithread" is enabled. Not sure if it's us or them...

  • @mwplugs What result did you get with the impulse I posted?

  • @dustbro jan 24th from which. scriptnode im guessing. there is no jan 24th build if so link me. and i had issues anytime an IR is loaded already in the convolution. basically if i create a new CR and load an IR the first time it works. it seems its just hanging inside the CR memory or something. i also always see RELEASE RESOURCES everytime i open HISE

  • @mwplugs said in Convolution Broken...:

    digital distortion at 44.1 and 48 khz samplerates

    OH no.... you may be right. I'm getting static at 44.1 and 48K as well on my new project. None on 88.2 and 96k.

    @Christoph-Hart HALP!! 🤣

    Here's the IR I'm using:

  • @mwplugs said in Convolution Broken...:

    i also always see RELEASE RESOURCES everytime i open HISE

    Me too. I don't think that is a cause for concern.

  • @dustbro its nice to know im not crazy lol. yeah i do very extensive testing on things. all different daws, systems on both mac and pc. but yes like i said after troubleshooting thousands of different variables it seems to come down to lower sample rates regardless of IR sample rates (44.1,48) ive gotten a few IRs to work. on all samplerates then out of nowhere it does the same thing. its very confusing.

  • also IRs smaller than a certain size dont show up at all. the longer the sweep since to yield more consistent results. but like ive said all aong...a year or so ago i never had any of these issues. it never had issues at other samplerates or was finnicky about the IR lengths bitdepth or sample rate. but im VERY relieved im not the only one experiencing this now so it can be addressed. i was starting to lose it a bit lol

  • @dustbro has anyone looked into this? its still broken..

  • @mwplugs We're at the mercy of @Christoph-Hart 's free time to fix things like this. If you're patient, it will eventually happen. 🙂

  • @dustbro yeah i figured. im just glad its now a known issue and im not just a crazy person. everyone else was saying it worked. my guess is they havent tried different sample rates

  • @mwplugs I've used it in the past with no issues at different sample rates. That was on a different rig though. It's gotta be the IPP implementation. I haven't had a chance to downgrade and test yet 😕

  • @dustbro This happens with IPP disabled I think

  • @d-healey both. with IPP on or off. this whole problem started when you had to start call "load audio files into pool" in order for IRs to even work. before that it worked perfectly at all samplerates. that leads me to believe that it has something to do with data being handled in the RAM like IRs are hanging in there when a different sample rate is used etc. its very odd. but it kind of makes the convolution useless for actual products, as professionals more times than not alter samplerates based on the work they are doing. at they very least recording in 48khz etc

  • @mwplugs This is worrisome, I am working on an Impulse Reverb I was planning on releasing .
    I havent tested sample rates but I seem to have one impulse not showing up in the exported plugin, works fine in HISE , will have to test further. When the impulse does not load/work the plugin goes silent.

    Most of my impulses are pretty short as I need a lot of them , concerned that they will not load.

    I just checked, the impulse that will not load in an exported plug is 881 kb , the other ones that are about 3 mb will load.
    Doing some more testing.

    I am also getting ticks , when moving the pre delay setting in an exported plugin , any way to fix that ?

Log in to reply