Convolution impulse not included in final plugin
-
@LozPetts The impulse is 7 seconds long, is this a length issue? I seem to remember seeing a post saying an impulse longer than 4096 samples can cause issues but that was an old post from years ago.
-
I've been reading about this all day and am completely stumped. I can see IPP/FTT is required for the convolution reverb to work, but from my reading IPP is no longer supported on macOS and apples vDSP should be included by default. I've fired up the projuicer project and can see vDSP is enabled and IPP is disabled, is this the correct way to do this or do I need to somehow source an old version of IPP from intel support for this to work?
I've tried compiling in Windows and enabling IPP and got the same results described above. It compiles file but no reverb is present in the plugin or standalone.
Someone help, I'm going nuts!
-
@LozPetts in the compiled plugin are your IRs loaded into the AppData/AudioFiles folder?
-
@Lindon Thanks for your response!
I'm on macOS so I believe that would be:%User%/Library/Application Support/My Company/My plugin/
Long way of saying it's where the sample link file, user presets etc are stored, and there is no audio files folder, which might explain the issue! How do I get the plugin to pop them there?
-
Have you tested with a shorter IR to test your idea?
-
@d-healey Yes, same result. I also saw Chris saying there's no artificial limit on IR length so didn't really pursue any further on that front. If anyone has a 'known working' IR they wouldn't link linking/sending just to test that might be helpful?
-
@LozPetts said in Convolution impulse not included in final plugin:
Long way of saying it's where the sample link file, user presets etc are stored, and there is no audio files folder, which might explain the issue! How do I get the plugin to pop them there?
Do you have "Use Global App Data Folder" enabled? When using "global app data", the folder of the plugin is not created automatically. And maybe that's why the audio file is not loaded into that folder.
-
@bendurso Thanks for your response! No, not got that enabled. Everything is going into the user specific Library folder rather than the global one:
Library/Application Support/My Company/My Plugin/
I didn't set this manually mind you, this was automatic.
-
@LozPetts that will be created by the plugin try creating a sub folder called Audio Files and putting your IR in there and then see if the compiled plugin works...
-
@Lindon Just tested this, no luck
Library/Application Support/My Company/My Plugin/Audio Files/Impulse.wav
and
Library/Application Support/My Company/My Plugin/Audiofiles/Impulse.wav
Neither made any difference unfortunately.
-
@LozPetts If you've enabled the embed audio files option then you don't need to put the wav files in the app data folder. However if you uncheck that box you can place the audiofiles.dat file (from the pooled resources) folder inside the app data folder.
-
@LozPetts I'm now testing different sample rates (Impulse is 48k so trying 44.1)
-
@LozPetts 48k is fine, that's what I use.
-
@d-healey Understood, I gave it a go because despite the option to embed audio files being ticked the file does not appear to be being included/isn't working, thought it might be worth a shot as Lindon suggested.
Still nada!Update re sample rates: no change.
-
The Impulses should be embedded into your binary after compilation, Did you Clean your Build Folder after the first changes? Try to check the Rebuild Pool Files in the project settings and Cleaning the build folder in Xcode before Compiling, maybe you want to check the Multithreading option in the Convolution Component to use a 7 Seconds impulse.
-
@Soundavid Thanks for your response!
I already have multithreading and 'Rebuild Pool Files' enabled as I suspected they might help! I hadn't cleaned my build folder, I've done that now and recompiled and ITS WORKING! Thank you so much for your help.
Just as a learning moment - did I do something wrong here? How often should I be cleaning my build directories? -
This post is deleted! -
@LozPetts Amazing! Cleaning your build folder will delete the cached files and increase the compiling time but when you make this kind of file changes it's better to clean everything to make sure everything will be included in the new build. Same with images and MIDI Files.
-
@Soundavid You star. Thank you so much for your help!
