Posts

• Buttons don't update plugin parameters on FX plugins

  Tested in Ableton and Reaper, but I guess it's most likely happening in other DAWs, too. This is with an FX plugin, I haven't tested with instruments.

  When clicking on a UI button that's enabled as a plugin parameter, the button callback is executed properly, but the plugin parameter's value is not updated. This is regardless of meta parameters and radio groups, I tested it with these on and off.

  The buttons also don’t respond to being changed from the DAWs plugin parameters.

  Sliders work fine.

  @Christoph-Hart I'm sure you can solve this!

  Here's a minimal snippet - it needs to be built first, of course - but it's not anything ultra clever, just a slider and button set as plugin parameters...

  HiseSnippet 791.3ocsU0saSCCE1tqYZs.iMId.xkanIT+acqhKnz+fJnaQjwD2M7bbZrZhcThyFUHd21iDuAfcRZSKKqqqRjKp54+Oe746Xi.NlDFxC.vxWL0m.fOWybJS3z0AQYfg8.vc0FgBEj.8DUcl5iBCIV.HbqOnT.KUDD+8620A4hXXRlJ.3RNES9L0iJxzZz9STW2AHKxETuE7tQ6gXNqK2kGIwyVZU.9H7DzXxYHkaEz.eDE5.fuV63Z0wMrNwpVsia0DiZRZYirsqV2pQilm1pZ8VnFm1jT4X.b69VTAOvTfDjPYR6vslZ5vukkTfKogzqcIJgp.SYkSTC55PcsLl0bBA.XQirV0VIspWoMhZQmqOqksWrA8rHVroAKrJHU8I.I3BPpXBj1WyDGP8EYVT34YZCYxaPaj7tYQnj3K.dmVWtzAl3MdnIjAARg4AbPyJUNRW9ygu0NhgETNSmyNiKHmyN3vx+rbox+pr9+Zx1NWapxDvccIA4ZVMNDrp.OfE4cMI3H8aPtQj4NJO9K2S2d85o3jS8BNxYCYTw49jT4AbWKUuR8+6eC.Raax6hBoHT5pH9lX2zahNQBAmAnxj7xkTUEDeHVjr.dnjX5RsHAKkjDU4kjuNrGRfTyGovSBYeRffp5LvdjajLxjokRZ8HgSDb+X764yYpCCbm09D7i4E9twsmlgBZ6aoVBIUUCZIEcHzwNhYR9tQioLCTfjUKGxRH26IGA4t59yzBngFK6mD6E.OLJWQKJCkeObsQYt0OWnKQfKEOQOLAAf6yJk6C3VQtHwxKITqOSMHmxWhYpnerPpX5hqWeBaNprxMGqKD2WyfJvN4iwB4fQEQ3+.FS229Bs911DrHCfE0F7sMc45iT9uviDT13QHQ.UN.ocVjmo7cILQVcFi3FpFTJn3rIxUTxpNfIgYEK7G4WpwpJYXpwpyLB7P3.9U3DRuZi9NwZjXhEOYUR9zqTVOGVtm7Alqv3kS08Br1lFX8MMvFaZfGuoA1bSC7jMMvSe7.Uu++9HA2Kg1..iL5GuUFB6yPxIv3oUveEHoWlM
  

  posted in Bug Reports

  T

  tomekslesicki
  
• RE: Bug: HardcodedSynth Volume Glitch

  @Christoph-Hart
  I'll get back to you! I'm a version behind

  posted in Bug Reports

  G

  griffinboy
  
• RE: Bug: HardcodedSynth Volume Glitch

  @griffinboy Yeah I noticed that too. I think I've fixed that though with one of the latest commits - are you on the latest state?

  Might be possible that I haven't pushed the fix though.

  posted in Bug Reports

  C

  Christoph Hart
  
• Bug: HardcodedSynth Volume Glitch

  

  The hardcoded module volume slider seems to be modulating the first parameter in my hardcoded network (c++ node)

  In addition to this, the volume slider forgets its value when I save and reload the project, opening at a default -12 every time. This could be tied to the above issue, where it seems this slider has become a modulator.

  posted in Bug Reports

  G

  griffinboy
  
• RE: XY Panel controlling Knobs, Panel does not create DAW automation but Knobs do?

  @Lurch said in XY Panel controlling Knobs, Panel does not create DAW automation but Knobs do?:

  but I get a load of errors

  Start by making a minimal snippet. 1 panel and 1 knob.

  Then try and implement Christoph's solution.

  You can leave this part out if you want, it's just a check to see if you've compiled HISE with the HISE_SEND_PANEL_CHANGED_TO_PLUGIN_PARAMETER preprocessor definition, and this needs to go at the very top of your script, before any comments.

  #on
  
  #if !HISE_SEND_PANEL_CHANGED_TO_PLUGIN_PARAMETER
  // If this causes an error, you need to add HISE_SEND_PANEL_CHANGED_TO_PLUGIN_PARAMETER=1
  // to your ExtraDefinitions of the project and rebuild the component tree (either reload the patch)
  // or click on the refresh icon in the interface designer)
  Console.assertTrue(false);
  #endif       // FOR AUTOMATION FROM PANEL
  

  posted in Scripting

  D

  d.healey
  
• RE: How to specify text color

  "#FFB7AA5B" is a hex representation of a colour with the #AARRGGBB format. You're almost there, you just need to turn that into an actual number with the hex format:

  const var RED = 0xFFFF0000;
  const var GREEN = 0xFF00FF00; // same as #FF00FF00
  const var TRANSPARENT = 0; // shortcut for 0x00000000

  posted in Scripting

  C

  Christoph Hart
  
• RE: When I compile, the volume resets to the original value

  @griffinboy seems like it might be unrelated to the op then

  posted in General Questions

  D

  d.healey
  
• RE: When I compile, the volume resets to the original value

  @d-healey

  It pertains to hardcoded modules so I'm not sure a snippet will do

  posted in General Questions

  G

  griffinboy
  
• RE: Do something only when automating?

  @tomekslesicki yes there are plenty of other solutions

  1. just not calling changed() in the slider would prevent the infinite loop
  2. writing a custom panel instead of the buttons that store its value and is assigned to a plugin parameter would also work.
  3. you could even get away with just styling the slider with a laf and make it look like a few buttons but that‘s advanced hackery and might not work with you design.

  posted in Scripting

  C

  Christoph Hart
  
• RE: Do something only when automating?

  I just figured out I can actually do this by checking the button’s value on the knob’s callback and just if it from there, which would be a much simpler solution I guess

  posted in Scripting

  T

  tomekslesicki