Export wants to "Copy audio pool file..." when I have not
-
When I export my FX plugin, Hise systematically asks "Do you want to copy the audio pool file to your project's app data directory?"
But:
- I have no audio file, sample, samplemap or whatsoever in the project
- I obviously don't load any audio in the pool
- The pool is empty
- I cleaned the PooledResources folder (but Rebuild Pooled Files is ticked anyway because I have two images, they are deleted/rebuilt each time)
- Embed Audio Files is disabled
- I cleaned the Binaries folder
Still, Hise wants to do that (or at least is asking) and of course If I'm going too fast on it I end up with a nice AudioResources.dat in my appData folder.
Any clue?
-
Alright so AI says it's asking because "Embed Audio Files is disabled" which feels wrong.
It's not project related but Hise.
If you don't want to be annoyed, enable Embed Audio Files, the pool created is empty and harmless, but it feels wrong as well anyway to keep it in an FX context and to keep the setting Enabled for the same reason (in this case, why having a choice in the first place?). -
@ustk Claude says:
The prompt is gated only on: - regular (non-iOS) export, and - EmbedAudioFiles == false, and - interactive mode (manager == nullptr).So it doesn't actually check if there are any audio files to embed before showing the prompt. Might be worth adding a guard there as a simple PR.
Assuming you're using the regular Export > Export As ... menu item to export, it comes down to only the Embed Audio Files checkbox. If that's false, then it will ask.
Since both Embed Audio Files and Embed Image Files are checked by default, you can just leave them that way and it produces small few-KB placeholder files when there are no audio/image files, and produces the correct DAT files when audio/image files are present. Best of both worlds.
The DAT files are embedded into the plugin binary anyway, so there's no effect on the installation or the end-user experience.
-
@ustk The purpose of setting Embed Audio/Image Files is so that you can manage the installation yourself, if you wanted to.
Also, if your audio and/or image files are more than 50MB, the export will likely crash. So you'll have to manage them yourself anyway for large assets.
-
@dannytaurus Yes that's exactly how I understand it, and it's harmless. I was just confused by ending to be more embarrassed to uncheck that flag for FX plugin. That's what feels wrong to me because I just expect not to deal at all with audio files in that case. But I understand the meaning of the flag behind, for who wants/needs to embed them separately.
-
@ustk Many FX plugins have audio files, though, right?
Like convolution reverbs, cabinet simulations and texture effects (like RC-20).
-
@dannytaurus absolutely
