HISE Logo Forum
    • Categories
    • Register
    • Login

    [BUG] Wrong network parameter name

    Scheduled Pinned Locked Moved Solved Bug Reports
    scriptnodedspnetworkbug
    1 Posts 1 Posters 251 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Matt_SFM
      Matt_SF
      last edited by

      I found something these past few days, and I wanted to leave it here in case someone needs it.

      The problem was that some of my compiled networks, placed into HardcodedFX modules were not saved correctly, as seen in the project's XML :

      // A GOOD ONE
      <Processor Type="Hardcoded Master FX" ID="HardcodedMasterFX2" Bypassed="0" Network="dspTest0" Mode="1.0">
      //...
      // A BUGGY ONE
      <Processor Type="1.0" ID="HardcodedMasterFX1" Bypassed="0" Network="dspTest1"> 
      

      Of course, when compiling the whole project, the module (and thus the effect) were non existent in the plugin.

      I finally found out what was wrong : the naming of one of the networks' parameters : I named one : "Type" (for types of filters, types of reverb, etc...) and as it turns out, HISE hates it :

      dc0dce79-7902-4fb0-8aff-a5adcea0b5fd-image.png

      So, don't name any parameter "Type". It doesn't seem to matter to which control you're connecting it. Just don't do it.
      I hope this will be of some help.

      Here is a small snippet, ready to be tried :

      HiseSnippet 1161.3ocuW0saaTDEdVGOo3PKpUvCfk5MoRgH6j1BRbQbhSLXAN0zMD06JSlcb8HO6LK6NNItHtBtn2wqTd.JRHkm.dCJOAv4ryZuqiMtFq.NRQ6b9YNem+2sargKRRLwDuJmLJRP7tK0ej11uYelTSZeHw6incXIVQbUGoCFEwRRDADOu09RjfWkxjzeuauCXJllKxIQHmZjbw2HCk1bpca70RkpEKPbhLrfzOtQatQ2znLCA7rFsFIhwGvdk3XFJVIJwa8iBjVSrukYEIfLGXBF422bg1I+oxD4YJAdnNwGtHGYRy9RUP2w9ZBg3Utatmulyy+DZGYfbB87Hv8SYTMWihw.uRKBR0+W.IuBPprCROf5yikQ1bNHd9PZaMjP5wfPcQn3jk3cEsoADPa2NjMPzJFNLQgMeZsZaUE92i9hdC0bqznqZzGarhmo27Qa7iaTYieZip2jUudykGZlXiRIhmKaL6FuHE2TOL7LQ7VUOmoFJlHH39SGSWe4hobmWWPPitsVZeVjH6bKiJ.iU3yylAHYgM3ouq8gLKCSJYz.4hDwVIBGuCEmCU0tTTE5ghjAVSDTWOS9CpbLACUL6zkSXeSFCHdLUNDST5DocTw9paViU9eNdTqP7383sKIbe.sqzx6Oe7VZN3EhZ+Wi2rN16QOpWOA2lC1xzVuXgsmkWtRobnrrspaj0pB1GAxcyNVs0KpO2lz2PyaHhhEQrXwIltJ1nMSXgQJwyA7tU0yTF9.e4qEy1EE4fvAnDax6yzZgJYUZ1V+VZ.F44lgVo9UcX1X4kDO5wCC8gQ4bQyLzAz7Jg8Yty0vyX8huPGjd3ufeYLqim8xXVeLyBsnGKrWXhGjlNxdF7EL1WgFjDchHwR1WoLWzzDFIyJcgJ1TZcMpQQ8MZIGyINIFCy8CMCAKjg0uhkbBSpPMOUDmjdI2gVaa3OnN+XS.DYVuEiCQvQcY19XCCNHBpHEwaymTYlCphUCn9iW34hE.VBQGDW2gYgtrXX6GL8FG7TxasBChb0g3In6qjqpqcxoHWNSQNEyynRDzJt3TJbonnTZx48HSA76Q6IUnk1FYs7vbZPgrf52KGO.sk6NyeDwpNPb43b5QPYY.zskp.dejB9LDbmbBdtiTm4V4uzPG1kSS6MW2v2Jhv1lhSk7GHtv4uYTa7yg+1dtEpshE+vPglOhL8U03WaPVf8ar6tWu2Mr+Uu8sOb4rO4g+4umZ+0ne6MrKLzmrX+dmqlwuI6rj1EudztqmtI5lllPdOllPl0zuaukxze+Ge30Ygb+Piw1GlWLk8a7Gu9Wlx0uyxY+6OGWGvzBb8NXuvL279CslPXPX5xsao3vhvQE5QZFLdMXQE.tV8BXw4AoKdt8COy.jzWBRKR2mjj8NQYGyFA1NX7.kInDIkEjIGXLCBYoypWs2r5+iMKgLdr4kb2xRzM+fTJP2oN8yOp.eGDbtZcx4t.DE2BPBgOM3kbN9pGeJ7ZKyWmcVAc1cEz4wqfNOYEz4oqfNe1JnymuPcvuJKqeEKEABcOxsDwabSEr6h72fZEKNu
      

      Steps to reproduce :

      • Compile the DSP network, and reload HISE
      • Load the network in a HardcodedMasterFX slot.
      • Save the project and take a look into the project's XML file.
      • Compile the plugin and get no effect

      @Christoph-Hart should I open an issue on GitHub ?

      Develop branch
      Win10 & VS17 / Ventura & Xcode 14. 3

      1 Reply Last reply Reply Quote 2
      • Matt_SFM Matt_SF has marked this topic as solved on
      • First post
        Last post

      50

      Online

      1.7k

      Users

      11.7k

      Topics

      102.1k

      Posts