@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: Linked Sliders Automation conflict
@aaronventure Thanks, that's more or less what I did this morning, works perfectly well, just a bunch of extra work!
-
RE: Linked Sliders Automation conflict
@d-healey that's the conclusion I have arrived at.
Thanks!
-
RE: Linked Sliders Automation conflict
@d-healey well its as simple as linking two sliders, setting them both as isPluginParameter enabled and then automating them in different directions in the DAW...
But I can if you want me to!
-
RE: Linked Sliders Automation conflict
@d-healey Thanks, I'll stick with the hack for now!
-
RE: Linked Sliders Automation conflict
@d-healey I tried it and it doesn't make a difference in the DAW...
-
RE: Linked Sliders Automation conflict
@d-healey Oh wait, sorry I'm getting confused! I don't want to control CC automation, only the standard DAW automation (is there a specific term for this?).
-
RE: Linked Sliders Automation conflict
@d-healey Thanks, yes CC. I guess
MidiAutomationHandler.setConsumeAutomatedControllers(bool shouldBeConsumed)
Is probably what I'm after. Do you know if there are any examples of how to use these APIs? Do I now need to set the automation up as a data object or is it already there somewhere?
-
Linked Sliders Automation conflict
I'm using a button to link a slider to a master slider. I need both sliders to have automation enabled. However when the sliders are linked the automation will conflict if it exists for both sliders.
I tried toggling "isPluginParameter" but this doesn't seem to affect anything in the DAW (and I was afraid it might make the automation lanes disappear altogether!).
I can't see any way to toggle automation for a control - does anyone have any ideas?
A hacky solution could be to use a separate set of sliders for ones that need linking, and check the value of the button when scripting their callbacks...
-
RE: Sonoma 14.4 Problems
@Dan-Korneff Yeah iLok were in touch, Oek Sound too, now I got this from Kilohearts:
Unfortunately, we have to join the chorus of audio software developers advising users against upgrading your MacOS to Sonoma 14.4.
A few users have reported various problems with Kilohearts plugins in the latest MacOS update and we are in the process of working out what is causing them and finding a solution.
-
Sonoma 14.4 Problems
FYI I'm seeing a lot of devs posting about issues with Sonoma 14.4 (it's not like Apple to make our difficult is it?!).
I've had no reports yet but let's keep each other posted if any do arise...