@DabDab @Fortune arguing in a forum is totally pointless guys, and I'm sure the rest of us would prefer not to read any of it. Everyone be nice and civil towards eachother please and we can all carry on making super plugins... :)

Thought I'd leave these here in case anyone also wants to post hilarious customer interactions to make us all laugh

followed by:

Feature Request: Draggable ADHSR Envelope (like the curve EQ and Tables etc)

@jupe 'bitchbend' :face_with_tears_of_joy:

@obolig it's a good post. Had a similar experience and after some digging back in 2020 I came across HISE (not so much digging required these days!).... It was instantly intuitive and the members on this forum more or less taught me how to script. Many thanks for putting it together @Christoph-Hart

For anyone interested I released a new effect plug-in this week... The MOD-EQ-1

Check it out here:

https://dhplugins.com/mod-eq-1/

have a good one!

@Fortune I thought @clevername27's post was very reasonable - and interesting, to be fair. What's the point in a forum if people can't express their well-thought-out opinions!

You don't have to read it... ? :face_with_tears_of_joy:

@MikeB So you might know some of this but here is what I've done to get OpenGL working on both plugin and standalone formats:

1 - Place a Floating Tile set to Custom Settings in your project
2 - Set "GraphicRendering": true, in the Data section
3 - Set this flag below within your project Preferences in the Extra Definitions categories

HISE_USE_OPENGL_FOR_PLUGIN=1

So in my experience, at this point, the setting for OpenGL will not appear in the Custom Setting floating tile in HISE itself, but it will appear in your compiled plugin / standalone app. Remember to make the Customs Settings window large enough in your project to include all the settings.

Another way to set the OpenGL to be on/off in your compiled plugin/standalone is to navigate to the AppData folder and open the 'General Settings.xml' file and change the OpenGL setting as per below:

<?xml version="1.0" encoding="UTF-8"?>

<GLOBAL_SETTINGS DISK_MODE="0" SCALE_FACTOR="1.5" VOICE_AMOUNT_MULTIPLIER="2"
                 MIDI_CHANNELS="1" SAMPLES_FOUND="1" OPEN_GL="1"/>

Hope this helps. @Casey-Kolb may have more to add to this, however, as his excellent Cube plugin uses OpenGL as well :)

@AudioHobbyist As @d-healey says start without IPP.

However, if you do want it later here's the last installers I downloaded last year which worked with VS2017 / XCode 10.3:

https://www.dropbox.com/sh/4gx74wg1jpfnk7r/AACkGmy8SdV-j0qsiw5VFYFza?dl=0

@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