Table "Not assigned" warning

[ustk]

I have a Not assigned warning with my tables.
As you can see, it is in the modulators as well (all my modulators, not only MPE)

• Why and how to get rid of this?
• Are the two related?

Those modulators are meant to be used with the Matrix Modulation system, so that might be the reason but who knows...

[ustk]

Oups.. forgot the screenshot...

[David Healey]

@ustk Use myTable.setTablePopupFunction(function(x, y) {}); to customise it.

[Lindon]

@ustk thats an impressive bit of UI right there....

[ustk]

@Lindon And it's not even an instrument

[ustk]

@David-Healey This does not resolve the "not assigned" notification but at least it makes me feel better to just remove the popup entirely as it's not really needed here... so

[David Healey]

@ustk said in Table "Not assigned" warning:

This does not resolve the "not assigned" notification

Working here

HiseSnippet 988.3oc2V80aaaCDmzIpKwqsaEaOLLrGzxSICAs1tNwoKXnYwNNyXyoF0YA6sBZpyVDQhTPhpsFC8ssue6iv9HruAaGEkijSbSSMx5.levfGOd79o6O+NNHVwgjDULgV8zoQ.gdWmgSkZ+19LgjzqCgdem9rDMD6Z25voQrjDviPoqbrYC55qRx98WO8PV.SxghsHjyTBN7ShPgtX2nC9QQPPWlGbpHrzoadPOtR1VEnRQ7rhSMRDieNaBbBybrJNjefk3SneiyNOduV.7jQPq5i4bucXiZ0rQq8Zry3QM2cuZiZv3OoQyZbB8NG4Izp3gZlFRvK8Pk2zg9pWIsN3LQhXT.XDpSFhd1tMosuHvavrfSBgPcFTDpVwFp9bm9BOwE6WDx9zLEtEVTNnQqbcPp96AjnkfzpVH8.mg7XQjtPiAOerSOIlAGyvbSYnXOKox2RcZqvSH0OLjcNzMFEtvhM2sVsscw+1Z+pUezi9Z2SYH7pWESUI5bA2uyc1ELAzsUgQJIJr4FV0aXL0t7gIfNa0.UTZT2TIWKTxMGOawq21c5Vt+Z00iAcZrzciM1u5a1Z+Y5cUxSTZ3YxM2pJdnpuop6kUMd7B0YvWrJH.hWnZSkX70Y3lxzvQP71tujEjBWbPLxOe57N2rzI2FtJcPkrmTneVDjK2UE3YRSl0WM4Sxi2lxfbDhPQmUDbu7hfr3LQf2wZN1nOIC7k6O8XZVVqE4m60wrN+9vqFcWDDqEluJZG3kXirsHacmNPx4ZUT1Yyy0D5G8N89qw1H5ugdcpYwuiKdkvS6aDhoDhOHl3qMReAJEM6qsGdEehS+AG41W4kFvvfMgb0Reroal5xchFNpbEX9btxeSItLQnmVlC68n8r101ddSg3CbFHzb+EiwJK.iXJ5eCLlSpcOmiFOF35B.tpS2eYYYvt4teMq6+RmiCTiXAEAJrXDQBXYx9pb0EkBtEG3sOZ5Ot8GMc499kmFe0+Clrb6T59YWIaj7ArAat4e20By6a3IJnILf7xTGkAXekTE4qjBd4BimC5XwjIXEU421HhTAr325m0wPBNvBZ2tXy0NXXnRo8ExIyWMINnCLlkFnOad53+7oVC.uE5BKipgr9V6MD2JjTq7+aRpmqR0XJrOCqJLSvNIMbHRCvAz6RIDjXlXUwLR1JWyHah.CAoWlvei+xUV2HSyUVelRh8xsCf+f3vPFOV8Bt8kCllo0x1ACBxrGauN9peT1cAOYHDYfdAmO+UcECarrF93k0vlKqg6rrFt6xZXqk0v8d2FZFP78oZUnsOkPP5urBKJ8HogAIq8f7O8jeyq.

[ustk]

@David-Healey Oh yes that's what I meant, it gets rid of the popup and I'm good with it, but what's behind the scene? What's the reason for "not assigned" in the first place?

[David Healey]

@ustk I think it's because a global mod doesn't have a target so they always show as unassigned. If you were to add the same mod directly to a gain chain for example then it would show dB. But a global mod can have multiple targets of different types.

[ustk]

@David-Healey This makes sense! It would need a safety then at least not to confuse the user. That's for the module itself, but do you think the Y value in the popup is related to the same issue? I would just expect to get a normalised value...

[David Healey]

@ustk That's the input value which is between 0 and 127 for a MIDI mod.