How to send a signal, that is unscaled, to a target, while avoiding the expr nodes?

[aaronventure]

I have a compressor threshold control, which I also use to do gain compensation by first inverting it and then applying it to the gain node.

Doing this with cable_expr is beyond simple. But cable_expr then wants to be compiled and in this case I'd rather have my network open rather than recompiling nodes every time I want to test out the exported plugin.

The parameter outputs -40 to 0, which is used to control the compressor threshold. I need to inverse this using regular (non-SNEX) nodes and plug that into the value knob of the gain node.

So this is a separate modulation signal, which means it all goes into the modulation container.

But I can't find a way to send things from that modulation container that aren't 0-1. The only node that "picks up" the signal and sends it is the peak node, but it only sends 0-1.

Which means that I first have to convert db to gain using the converter node, do the inversion using math nodes, take the peak node, plug it into another converter node, and then send that to the gain node, except gain works differently above 1 so now we go into more math again.

Am I missing something? Is peak_unscaled the missing node in ScriptNode?

What's the reason HISE can't auto-compile SNEX networks and swap them out when attempting to export a project that contains an uncompiled network which uses SNEX?

[Christoph Hart]

@aaronventure said in How to send a signal, that is unscaled, to a target, while avoiding the expr nodes?:

What's the reason HISE can't auto-compile SNEX networks and swap them out when attempting to export a project that contains an uncompiled network which uses SNEX?

A glitchfest waiting to happen.

Is peak_unscaled the missing node in ScriptNode

No. The peak outputs what the signal tells it to output and as usual this is a signal between 0...1 (it folds back the negative values to the absolute value, but apart from that there's no math involved). The _unscaled node options only mean that they won't scale the value to the target range but forward it as is.

If you need to scale the peak output you have to use that with one of the many cable modulation options and while the cable_expr node is certainly the most flexible one, you should be able to achieve what you want with the existing nodes already.

Have you looked at the control.min_max node? It allows you to scale a normalised input to a given range.

[aaronventure]

@Christoph-Hart

Alright check this out. If I just abs the threshold value I'm sending and use peak to send that to the gain node, it goes CRAZY high. But if I first plonk that same peak node into smoothed_parameter_unscaled, then it behaves as I'd want it to.

[Christoph Hart]

@aaronventure probably a divide by small number thing that is smeared by the smoother?

[aaronventure]

@Christoph-Hart It's unrelated to smoothing, the parameter input is static and if I turn off the smoothing it's still the same.

here's a snippet

HiseSnippet 2098.3oc6Z0zSibjFtaaJy.yjumIatrq5CajHRiPXxjuTNfGv.wZiAKLgjbhTzcY6VzcUs5tLCNQ6881lqbIJ+Bh1q6M9Mr43dY+Ivufc22pptcWs61FiGCYPJLRCTu0WOue+VcUsBY1jnHVng4RGNHfXX9HT6ATdus5gcoFMpaX95nl3HNIzRQZyAA3nHhigoY4cEDLWZAC4OWswlXOL0ljRxv3HlqM4Kc8c4oTaU6u354sC1gbnqu1neVsF1L5VLOVe.OkQqYDfsOE2krGVLrRHCyJa63xYgs4XNIxvbgMYNCZ2i8BpZ7G4F4dhGQznpQaXgTj2g44HPrfpwV8b8bZkv2QFFlnVoRgxJoviQMccbGROUZ7lxNrRmgt7vrTV3UNC7ppCu0zfWAPxTCRKnfzagZaG5FvS6QfmGhZPAkSGLH10ghZrFlWh1hACfxW0GeJYmPnwvIrxGu1ZO0B9uO3y6zmZycYTKFcOFmrOckOX4eX4kV9utr0nc0oSg8I1lPlmGIrvtEZ5vIMwUn88OgD9Tqyvd8ICGHv9YkonwKS0U41JtVafLZCpKe+.BcbFBFwhJ3u9pF0wbrPQDSCFW.Ij6JffYcxYfUsRsrDpNI5TNK.rqyoy.qElSeOLOqIjvuItCPFjQuITNzHW9.c+p4lc0zBw2B0xka2qXLVp.LBRpaCLF6M9Zns6zgXySA3Bnc9laIWux4kQKG65A6oXyeTbSqc9lpE5z82PoF3Agj.bH4PVKO7fUhv9AdjC.L9TqS7X1m1186I48JBTPXSwHVwtGlRIdQyhySkoVpTcxJkCX84tztMw7P2yAuv8562FBSaS1JFc.MyRBeHU60DsE1EsITGYi+G7SbmUEsMi6rZRmZte6Q3ufEdpLRX7eaXtnR1GIExG247pFO2yi8hsX9AtwVofNPRqEyaPPOF00VPRMhDj9beVeXShg6WfiND65ILqa2OBBN3rOsMLXYZLyxGQBijK7hn0VE9GXluGyA5pxNXaPvNnEl2S3uHh2.FmjvUsGZjlAq51IhkHIMmRJAPzWv5hjbB8SKbHjyChSKB2TRZSlD9QkbPzB7+Jo1mFQGI50F6YbjvBPLICwtnjfRDiTCsi64e5wRSOiLrv6pwBZiY5g8r.xxCAYIMPtLxm4nDiYf3i0f3vQb6BvToXEM.9GQQ9LFuGw43fDE0w8oQvLAfjAyuuDyfK5pSZJyMlnhHZNIA9uF5KAgENz5.HrigQZ37CwgcIbobGb5nDak2iTIzvQrL1fOiwPqPAsGgNrWHIpWOnXJYpx7SCgvNNYm0hHEVLzrnELQRKXDMcow3MMaRS74iP6pMZyIAhvk5iq8ojWnj25iTHIR13bK8y6yY9P3PYpLCMfTYDf7yWbw+bib.o1eu1H.QNtwCj2.0Vp4gnmxxc0VtZULL9rZSBC2.gwUS.CKg1lhOQXokagLzrqU5uL1ufuH76UEzuAFokzMRyp5MekQ0mkwOIpXFGnO+Y7J2wLtNuVAEPviD7+gf+dHYUYG2.tcgLb6zGd40Qtzf97i4rtcgpOxDv3AJdn5XBw7mlTn2piI1in..Ox4IkzW2MJ.JFay9PQkJUSFJhPoTGx4I0krMTZkCb9Q4zSpUQW0pKcuF78pTtg8XCCLMmUdqOFkWETWQJ6LSoh7zP+d9ghxOH94aeEJ+vHp9BpeTXLmYLyp0aQFji2F4VRrrHpgfWJPnb6aeNLN3zafd6hj0mZjLRHwEQETKe9SLcWUHeoL4Bk04lAYuAxY.E66ZGspry4Y9va6LQlnIaN7sWl2b.T8SS7pK69OdRMk3U6b.ydzyhMNqwltnme2y9w+crw4y4bLbP0QV6F0tC17kPGP7H3HxMd2uJehCiZS2t+y+5+8eEGc5.g0Ul89mt3hmLKILLpcyhL9PTaWGhxw8Zp1raNe+3pM6dC85mPs0yP8B0uVos3ahoXgcKjMeYM0mxBE9t2o9ulHyGVuVdY9j2+4ii+AjHBebGwHS3+w1H6wfTrkJdhHbx7G35S0+hKd+KkeQ+3RSih+.+4qTcxegmhOkwlL1o9X4Ws7k99Cd6jO7b83bQw2bf7lzHgV6GZU2kLxkwwIIUwoIpDjSEvizQbrSMmaA0jfZZ0fJxaEJwVAaQZmEtQocqhWosaocMJR9yZaYA3IVNjCLWsQbOEhj39xy0wcjaizQQS7oj9AErb46vr78oO6tlY2CFdGvth5T1M8NfUDrDTpNt6.15W1c0KqSfxWzEFesqiHneptqfaItA8Lv4nEyCGN50JMuDkxhylt69RvRVuL2O2BS2kOM4qkdZuqt2FIE42m.rzj39CfeSnp5WELHtiCF7DkH4gnuFeFQ9nPjRimHa2gE5asKAN9lPVUcd7rPBl5mEx91b.BGFhoQArH3LxZq7H8stde0I79zrCWQJynDr2N.6oMtGTKg355DAyhLKFzNyJ0TnlRZ9e1PkspMA3Fm8irAlEORo0s56EQjdGU0mXJ400I+E3PGPuXOo3kKLcwKulWHSkaqWHycre7uYO7hLOnmkRvnJo51PxOOn5vgQy6f66wSnl00pIixRtX6Tk9ADHhP2tjrGSqHFZzRedbsBp4QcogxOV7rIKpdiebSEpudu3y1aIhGb+IcwDe7LkmpGOybGuy9Co4N1CEBYd+QS+GPPX70sjpaqe6022E0GbWrG9X6P1wwWmfHfwCjT.9lJeHnKgZJZaU03rQ+v.9PpmissytT4l35y5D+vYchOaVm3GMqS7im0I9Iy5D+zqehhJCh+rYB+DnBoVaq9X1lCOJuYYi+O9pxrwB

While making this, I wanted to add an input toggle so you can toggle between the two to compare more easily without having to drag cables, but then the weirdest thing: input toggle had both at the same value.

I also tried plugging peak into an add node, and it's, again, reporting the same correct value.

It's only plugging the peak directly into the gain node that causes issues. Plugging it into any other node first that can then send that to a modulation target results in the correct value in the gain node.

So the peak -> gain interaction is weird.

It's not just display, the 400db gain in the screenshots above is FUCKING REAL. I have the limiter in the snippet, too.

EDIT: I updated the snippet to have the smoother and correct value plugged into gain. DO NOT disable the limiter on the master FX if you don't have one on your system.

The peak node interacts with the min and max and skew properties of the gain knob in the gain node, instead acting as a factor, where first converting it the actual value using smoothed_parameter_unscaled or any other such node which can send a modulation signal to target results in a correct raw value being sent to the gain knob instead.

So peak -> gain scales the gain knob based on its min, max, scale properties. Peak -> others is correct (i haven't tested all).