minmax node parameter not receiving value from other (minmax) node

[Morphoice]

@DanH i've submitted it as an issue on GitHub, I assume that's the proper procedure

[DanH]

@Morphoice that and tagging @Christoph-Hart on here

[Morphoice]

@DanH funny enough, I un into this very often, that knobs don't receive the values as you would expect, so the minmax node might not be the only one. I've just always assumed being a noob I'm simply not doing it right, so I can't really tell if it's a bug

[DanH]

@Morphoice actually it's fine just on its own:

HiseSnippet 1149.3oc6XEraiTDDsmXONqMKnck3CvGVj7JEEYCgEj3PbhSLXANwZGSzdaUmdZG2xyz8nd5IIdQHAbBDm4vdieCtkuA9C3OH+APUyL1y3XGuNlvtWHQJxcUU20qq98ptc5oULdXnRSrJ2eb.mX8PamwRyvVCoBIoyADqOvtKMzv0USLs+3.ZXH2kXYU3KQCVkKRh+45c2m5QkLdlIB4Dkfw+FguvjYsWyuV340l5x6K7yE8NM6vTxVJOUDfmB10IAT1H5Y7inXXaXSrJcnqvnzNFpgGRrJtuxcryP0Exj3OQDJN0iiCZPbfEJwbakmKhXzJo0PgmauI66PBrJ8xpBERpBencWgqXp8rpwihcTMaF4qGVaLK7JLC7ZbavaAPxJGjJl.oGa6vzh.SlGDOumcGIb3LfBk87PIIVh0U1sTP.Ry19zQ71ZXvzIT6Y0quUU3OO8KFDIYFgRVUIORY3GKq8zJeWkxU99JUuoqACVnOLMZkmGWuP23IsdYSrlLx+TtdqpmS8h3SCD19yVSKsZ0TVxtNWfJYGovbb.Oc7xIEjzxF7ousyATCEOTRsAwEv0FABGqC3mCL7jinx1GvCGYTA.GetyOf4nbi7nlYoSnFJ0ATOl4LDOnjgBy37ZraxwJd60i5qrDXUg6is6ILrgKFuar.7BUs+qwaph88sObv.NyjA1h1sewRkmEWMpTFTVUoZkToJjeDHOLcX01unwBEo+rclfHPyCnZdeUOO53ZgT+.O9yA7tU0S8TrQNhWwmWEEj.g8wHpwFRkRtW35H1JcO0.i7bUjQHOqK0nEWRrrOJx2AZqy3sRQGXyZCTmkLtNNF4KNboa7f+F9I0YCbrUpyFSblShdD2bgROJ93H8yDqMSp8GDFLwzIbcHRZs1zt91vuj877TWzR4GHRoyvgRrsdJuwACURACMkDwDnumuJBxZJ9+JZXepvC4+NQgP2E2ikNPvw2ChbtiTtvmraSYPgcbOpYHpiv9S.Qkq2lMkvNCVy3IXEFWjIWLlTm.L4ia93qEKf9wc+jrgK2Cr8ERe5kjYR8ihSMvA1N0adB4aJM457QHYcA5S0mwMw5RpFtqFteAASooifO2UHOAIa46Mzkd4Mrc8tNFd.RxyGmyH9EIah7Qh6wMsSVf4VZRtbu474dmlyk6q9ol2sbWFdJfT3G4Oe12Kxn7AITbaQxxKCK.Jje4tCE5kKBJWu6xx9u+5W+G6Ne1expk8qJ+C+Yb1KYi9tao9d57GRMD+xO9+WjZv1sl5J1PSBpFuta9zmSFVNUF13snNL9oJRNKomVbSgNt45HLs5fVy3wu6kueToe72Z8q+05Pc149R9tSy6d1WmlGKTwBKz+qXeWnXyS8I40WwOvCGAOqcijqo6DdB5kQ8lrPPW98UpQ9z3Ggrdekg2FOYxmxzpWl14A2bOH1BzRQF+crQZILtZCx42rB4Ceu2WxXytTyMwOdcm3mrtSbm0che55NwmstS7yV2I94u4Ih+aIRe1A1zGzK8NLlDZYcnjBOZO9hEx+.sGy4M

You must have broken something somewhere!!

[Morphoice]

@DanH wonderful ;-/

[DanH]

@Morphoice take the minmax nodes out of the modchain. seems to work here. Also the value doesn't change until you hit a note...

[Morphoice]

@DanH they don't seem to affect to sound so that would be an option. It's always a bit unclear otherwise me what values affect the audio and which are just control data. Sometimes I add stuff and end up with a horrible DC offset.

[DanH]

@Morphoice I hear you. @Christoph-Hart advised us a while back that your modchain should sit to the left of you container so as to be processed first and be as accurate as possible. Unless I'm using LFO's (I haven't needed to use Envelopes yet) I generally don't put control stuff into a modchain. It let's the audio pass through in general and you can put it close to what's it's controlling which helps navigation.

[Morphoice]

@DanH This is roughly how I actually do it, split container, then a modchain left, simply because if's the best place on screen to not have a network that is too cluttered and hard to work with. Scriptnode is super powerful, I really hope I get a better grasp on it over time. Once you understand the building blocks and their advantages and disadvantages you have an insane toolset at hand.

[Morphoice]

@DanH also sometimes networks break, and rebuilding it the exact same way they suddenly work. I'd really love to understand why this is happening and how to avoid it to not have double the work. During the design and tweaking stage so much can go wrong

[oskarsh]

@Morphoice Hey just to make sure try not to duplicate a node, instead always use a fresh new node. Sometimes when duplicating a node it leads to issues like that since some internal state is not being cleared.

Also I place the modchain on top of the network.