@Lindon @Morphoice and the control nodes, in particular the bang node

@ustk gets my vote too!

@aaronventure yes!

@Lindon I feel like the macro system doesn't quite fulfil it's purpose. I'm not crazy about it taking over the control of the knob as opposed to just doing what the knob does but allowing user control of the knob as well. I'm going to look at building a new system for my next product.

@Christoph-Hart ok perhaps a middle ground is to have an icon next to every label in the Component List that shows if it's editable...

Just found some more and now have to spend a couple of hours running my last update off again

@d-healey oops

@Morphoice agree with @d.healey here, gpt will most likely send you down the wrong path. You have your own gpt in the forum, just takes a bit longer for the results to come back...

@d-healey as in set all the labels in the opposite direction?

@d-healey ScriptingAPIContent.cpp :thumbs_up:

@Christoph-Hart out of interest where is it in the source code? Happy to change it for my own use

@d-healey Ok well for us old school lot it's worth a shout

I don't know if anyone else suffers from this but I quite often overlook turning off the editable button for a label and have to run all the exports off again... Anyone else in favour of the button being off by default?!

@Morphoice ah so it has worked previously? I thought it might have been the first time you ported it to PC. Can you retrace any changes since then that might have affected it?

@Morphoice can you just remake the dsp in Hise on the PC? As in delete everything in the DSPNetworks folder, burn it all to the ground, and create it again

@Morphoice right so you're moving the project from Mac to PC, correct?

If so try compiling the dll outside of Hise. Find the AutoGeneratedProject inside the DSPNetworks folder in your project, and run it in VS2022 from there. If and when that succeeds try reopening the project in Hise.

@Morphoice what are you truing to do exactly, compile the dll?

@Christoph-Hart Ah that would explain it! Ok will try, thanks!

@Christoph-Hart So I'm tentatively going to say that this could be a bug with the Default user Preset system and - in this case - Engine.loadAudioFilesIntoPool / ComboBox callback...

I've loaded some impulse responses into the convolution reverb module using Engine.loadAudioFilesIntoPool and used a combobox to select them. All is fine within HISE and Exported Plug-In.

However, when I set a specific preset as the Default User Preset in the project settings then whatever value that preset has saved in it for the combobox, it will reorder the array of impulse responses with that saved value at the top of the list. In HISE everything is ok - this only affects the exported plugin / standalone.

I tested the Default User Preset setting with different presets and changed the combobox value in those the presets and each time the combobox list would change to reflect this buggy order of putting the Default preset's value at the top of the combobox list.

So if the ComboBox list is A, B, C, and the Default User Preset has B saved in it, then when you export the plugin the list will now appear as B, A, C.

@d-healey thanks, I've renamed the actual file numerically so I'll see if that helps first!