Bug: HardcodedSynth Volume Glitch

[Dan Korneff]

@griffinboy Are you saying that parameter 0 for hardcoded effects are defaulting to the value of the synth volume? (-12dB)

[griffinboy]

@Dan-Korneff

I reload the project and the volume for the hardcoded module is defaulted to -12
In addition to that, the parameter also seems to be acting as a modulator for the 1st parameter in the hardcoded fx slot

I'm on the latest build (updated yesterday)

[griffinboy]

@griffinboy
@Christoph-Hart

Sorry to bump this again!
Am I the only one experiencing this issue?

[dannytaurus]

@griffinboy I tested your snippet and it happens the same here.

Has this only started happening recently?

I noticed the HardcodedModules files were changed about 2 weeks ago by this commit. It seems to deal with both the parameter offset and the getting the default value, so it could be the culprit.

- fixed remove matrix modulation connection via slider popup · christophhart/HISE@b1d5266

The open source framework for sample based instruments - - fixed remove matrix modulation connection via slider popup · christophhart/HISE@b1d5266

GitHub (github.com)

[Christoph Hart]

@dannytaurus hardcodedsynth was added there so it‘s not a regression.

It‘s a simple fix I just forgot to offset the parameter index for the amount of internal sound generator parameters (voice count, pan, etc).

[griffinboy]

This post is deleted!

[Christoph Hart]

So now it should be fixed - I haven't tested it because I was too lazy to make a node with parameters, but I'm fairly confident that I can no-look fix this :)

[griffinboy]

@Christoph-Hart

No good sorry!

Still defaults to -12db when reloading a project, and still acts as a modulator on the 1st param

[Christoph Hart]

@griffinboy Ah, no I think the issue is that you have a parameter called Gain in your network and this will override the actual "Gain" parameter of the sound generator.

I'm adding a safety check that will complain if you use reserved parameter IDs or other keywords (I already did that with Type as this will mess up your entire module tree, but since there are different reserved keywords for different module types this needs to be checked at runtime when you load the networks).

EDIT: Oops, no that's not the reason, I used the wrong enum for the offset so my fix didn't do anything. So much about no-look fixing...

Now it should be fixed.

[griffinboy]

@Christoph-Hart

Seems fixed, thank you!