@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... :)
DanH
@DanH
Artist / Producer / International DJ / Developer
DC Breaks
DHPlugins
London Town
Best posts made by DanH
-
RE: How can I make Vocal Remover Plugin
-
Customer Feedback Lols :D
Thought I'd leave these here in case anyone also wants to post hilarious customer interactions to make us all laugh
followed by:
-
RE: The definitive feature request & bug fix roadmap
Feature Request: Draggable ADHSR Envelope (like the curve EQ and Tables etc)
-
RE: Thank you Christoph
@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
-
New Plug-In Released - MOD-EQ-1
For anyone interested I released a new effect plug-in this week... The MOD-EQ-1
Check it out here:
-
RE: Open GL on Mac
@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 categoriesHISE_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 :)
-
RE: Starting to use HISE is one of the biggest pains in the neck I've ever had
@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
-
RE: HISE HEAVY ON GPU PROCESSING?
@dustbro @Fortune @d-healey @Natan @Tania-Ghosh Ok so I found this thread:
https://forum.hise.audio/topic/2122/open-gl/10
@Lunacy-Audio found the setting in this doc: StandalonePopupComponents.cpp โ line 128
#if !HISE_USE_OPENGL_FOR_PLUGIN properties[(int)Properties::UseOpenGL] = false; #endif
I've set it to 'true' and recompiled HISE and now I have the 'Use OpenGL' option in my CustomSettings window :)
Latest posts made by DanH
-
RE: I donโt know anything about scripting. Is HISE for me?
@pgaudioworks @clevername27 Nonsense ! I knew nothing, had no programming experience, but managed to build a pretty complicated instrument and a few FX so far. There are loads of resources on this forum, @Christoph-Hart 's GitHub and @d-healey 's Patreon and YT channel... Plus all the friendly people in this forum who will happily answer your questions (no matter how stupid! )
-
RE: Prevent Slider Value Going Negative
@d-healey said in Prevent Slider Value Going Negative:
You can cap it using
Math.max()
Knob2.setValue(Math.max(component.get("min"), Knob4.getValue() - Knob3.getValue()));
Ah yes, great idea! Thank you!
-
Prevent Slider Value Going Negative
My brain is on vacation.... With my weird system of Knobs controlling each other Knob2 ends up having negative values (despite the min value being set to 0). I need to stop the value at 0. Any ideas?!
If you open the snippet and yank Knob 1 from one side to the other you will see Knob 2's value printed in the console.
HiseSnippet 1031.3ocsV0raabCDlqr2jH0lfFf9.PjKUBvUP+0j.DDTUKaGnlXG0JWibn.AT6RokvbIWrjxNBsAvOJ4QHG56S68dIuAsCIWYsajprk.pNHryOeC+lgbFxAox.pRISQdkOcVBE48k9CmIzQ8hHLAp+AHuG3eLQoooXmp8mkPTJZHxyamWXT3UdWj82m998IbhHftPEBcljEPeEKloWncP2Wx37iHgzSYw47tS29ARQOIWNE3yN9MPIjfyISnmPLtUxG4cmCCYZY5PMQSUHuc2WFNaXj7Rgy+yXJ1HN0HzDMDBjS8QRdngwFsndQLd3f44sBAQYvhpvNtpvW6eLKjcs9EUiuxZ.u.Q95gWohzamBzq4+E8VAk7xQoccT5g9CCRYI5EVL74K76KfMmwDnrmmJNeQkzk76IAOD55wjyoGkBBWin5iazXOL7WsmUoBT5UZ7EjT7KExQMwOGOG3DptmLNQJ.gpOxZ8Q.hh.ZsV.sVFP60Bn8x.5rV.cL.pvDblfhGOUDnYRAVJrz0.KUxqFLGydPT4So0p7aUJaQWWQ0mYTU0Y.hk0PqEFb9MYtXM725xibp.XkqTFVMkjSqmjx.14hRAedOD80VbMKZFm6Q37QPaP0hohgf4xxSjZ5qEUs4Sk2WA+4lFOdk1xBFmltRyl1yz0ArpXZ7HZZ9powQ3LawFg6b6ZDBb0jbNJE8EL8qSnYxquSFkUTM8zYLDbUaaedPV6yPNKjlhXPPtqushhrjO+bLzsFbqBfu5u+o+ZC.2t3JW6W+yM.bmUP6eo+ADMwL9HqP.EmDZplY1C7NfdALK1MLor+AT04ZYBr2b8wOnpci0p2g7789HrbyLe7Ijsneqw2xg+Oli+G81L7sM3yR3qF2c10BeXV2MINcb7328r7X0w3ttXb+rX7JxHJ2Fh64a+tYNtfxGmqHcujEpiLqvaJgPQT1jHsQpJXUSeG7MyRCbSbfa+VYGkfa8MJWqD9xHVPDlovvj.LQgcSelOxo1d3QS03rXP3J4mEnNyCDZSRoVKkRt8paLcdg+oQ.WSx3zhz.F.JwB5DhlcA0oSUGi6iujHzXlFClUvwPLQiaTGdZvRW6AW3JCmxI5h2Bad5QlAXhTgq9LWuITL8r78FavUyMV6Uy2VJ9P+ALcPzp4XoUvQns8+CNl8fl66e33wz.8BBtq+QuYae8xMr7+rbplIlbLQmxLMZmLMdH7lt.Jr5BAkqLmdJYZ8cxMLxlJvPpHzJ7OvuLiMMxdYFaN2HJlDjJe67S8Pw6dVM.mD1WKVFd1JHiWZ7NBECuf6sAAEC0R.ass.aus.6rs.+tsE3i2VfOYaA9zaFn4A1+vTsL101fPGO3P68ZddGJHvIP6oUz+B7XSHt.
-
RE: Limit Knob 'range' using value of a second knob
@aaronventure Hmmmm... Not sure I quite understand
Any example of this in action?
-
RE: Export as AU and VST
@treynterrio what exactly do you need help with? You can Export directly from Hise...
-
RE: GPU Audio opens applications for SDK
@d-healey I thought you built their plug-ins?!
-
RE: Limit Knob 'range' using value of a second knob
@d-healey Oh I just mean that Knob 2 will be moved around a lot by the user. Your snippet above displays the issue that makes Knob 1 jittery when using Knob 2...
Could a broadcaster be used to stop the mouse control when a certain value is reached?
-
RE: Limit Knob 'range' using value of a second knob
@d-healey Thanks, sorry I should have made clear that Knob 2 is also dynamic, so this creates a bit UI friction between the two knobs when changing Knob 2, and is weird for the User as Knob 1 keeps changing its range.
Thanks though!
-
Limit Knob 'range' using value of a second knob
Knob 2 sets the maximum value that Knob 1 can reach (or be turned up to) with the callback below:
inline function onKnob1Control(component, value) { if (value > Knob2.getValue() + 0.01) { component.setValue(Knob2.getValue() + 0.01); } }; Content.getComponent("Knob1").setControlCallback(onKnob1Control);
Which is fine but makes Knob 1 get jittery when forcing it above that value. A bad UX basically.
Does anyone have a different suggestion?
HiseSnippet 834.3ocsV0raSCDDd2jrEhApnRbFY0SIhRURnTPpBZnIonnRaivkJtg1XuIYUs2MxdcgHTOxCQuwiReM3Lu.7.fDL6Zm+noosQBeHRyOei+1wy7soUnzkEEICQ37GMnOCguOwYfP0qVOJWfZVGgWlrOMRwBsSbsyf9znHlGBiy9VsCb9bHyyu1dGpOU3xF6BgNVxcYuiGvUi81p5dbe+codri3ASj8FUa5JE0j9xXfOYIkP8otmP6xNfpSKCAgWpgGWICcTTEKBgysizafSO4mEI4eLOh21moMJibfBk3dWoumlwZunZ839dsFdtiPPUZMtKjMoK7Hx9bO9H+i6FOzDvdLhI6G3LSSurSQuxWE8lAkvSPobITZEhiaHuuZbDMetGoo.93zgBs8IoRRtnL+FSpIgLDp0Cnmv1MDLFgnvlkJslM7SwsrrfVejx9TZn8dBY6x1uxdHvtLUMYPeo.LJrpI5pWFQk4hnhAAW3yEL6NwBWEWJrkBS0zvBk9EbGhYMnp9wrhVe0JOuicAik8qSdO5per1Qgh1Owtz5kJWzJOjX9QvWOZXFWEfsrxel0Y.il6YTWmTtUi562FlFKLMk0GJqINNGHUrCEELD25LK6+MTmNyLVZ07YgyLrdMIbd.KHhCZyBmrsoSDlcldfboa1.oaRSYhDkhlBt5v9rT64uQgR6pvfblTFBopLiwKmNF63y8XgHNTj6PLsTjg7oxAe+7y+w1naL3JSA9hG+setM5CMqSUT8xTJc.J1mEp35NAtN6TPYJY0JOoNK5DkruguoSAPy6ZY7WFIdUkUcvHiK5VEcKpSkKUGBdYrVn7Rh.f7izK1mplVSRKDmF.lKlRHPurKh3pASJTeKDpJMWgpaJEWgzhqb6MaNlYFbTO57efiox6OfznSGlqZLAyQ18iKpV9075euLVwEc2mpB4vGZxAwANvMbtL3sKDL+H826L5slD6RZacGvgI7LF+AdRCVVaiSCVdXPT.0MT9I2j0E8EH203A3jvb2Yd3Rbv1dzRFg.5fn.3trO45pO9OEVjmMlJK.lms.X1XAv77E.ylK.lWr.Xd4bwn+aDuIVICRVG.GsZXzqv3FBJLYYlBQ+EvjUG5R