Harcoded Master FX vanish
-
New project
Add a sampler
Add a Hardcoded Master FX in the sampler's FX section
Save .hip or .xml
Close HISE
Reopen HISE and load saved file
Sampler's effect section is empty. -
@d-healey Hmm, works here.
-
@Christoph-Hart Oo I'll try on Windows and see if it works for me
-
Not working here in the Release build on Windows or GNU/Linux. I saved as xml and before closing HISE opened the xml in a text editor and no mention of Hardcoded Master FX in there.
-
Can someone else test this please?
-
@d-healey All working here. (build version 650, develop)
-
@musictop Is that with the latest source code from yesterday?
-
@d-healey It happens for me too, on MacOS, develop branch from today commit: 1d909f7
https://github.com/christophhart/HISE/commit/1d909f7d262766164925205fdd996e88a3975443
-
I've just figured it out. @Christoph-Hart If you don't have any compiled networks then the Harcoded Master FX vanishes. But if you have compiled networks the effect sticks around, even if no network has been loaded into it.
-
@d-healey No. A lot older, sorry!
-
I have a project here with 7 compiled networks, which I'm loading and swaping in hardcodedMasterFx modules, but each time I'm loading my project, almost all hardcoded modules are gone, and I have to re-add them manually.
I tried another solution using :
const fx = Synth.addEffect(ModuleIds.HardcodedMasterFx, "fx1", 0);
But I get this error :
Function / constant not found: ModuleIds.HardcodedMasterFx
Any thoughts ?
-
@Matt_SF I found why the HardcodedFx weren't loaded... the user-level reason at the least :
Into the XML preset file of the project there was these lines :<Processor Type="-1" ID="hardFx2" Bypassed="0" Network="dspPhaser" ... <Processor Type="0.0" ID="hardFx4" Bypassed="0" Network="dspReverb"
I don't know why Types have changed, and why HISE didn't save the file correctly after I re-built (many times) the FX chain.
I simply replaced the line by :
<Processor Type="Hardcoded Master FX" ID="hardFx2" Bypassed="0" Network="dspPhaser"...
And that was it.
FYI @Christoph-Hart, if you want to dig in :)Edit : And the problem comes up everytime I save my project. Each time the HCFX type is replaced by another value (0.0, 2.0, -1...), and it doesn't matter if I delete/rename the HCFX modules... It has something to do with the loaded DSP network itself because it's always the same networks which Types are incorrect.
-
@Matt_SF The cause of MY problem is reported here :
https://forum.hise.audio/topic/6415/bug-wrong-network-parameter-name