My new plugin/app, Rhapsody, is finally released into the wild!
Best posts made by d.healey
-
I released my project!
-
Export tool
I'm currently building an app which I hope will allow batch exporting of HISE projects, auto notarization on Mac, and auto-generating installers. So far I have the basics working on GNUx. I need to finish the interface and add the batch handling, but that shouldn't be too difficult, then I'll tackle the other platforms.
This app should make it much easier for everyone (and especially beginners) to export their projects from HISE and build installers.
This is what it looks like so far (it's an ugly work in progress).
-
Time to update Visual Studio?
It's becoming hard to find VS2017, I can no longer see the community edition at Microsoft's website, only a pro version trial.
@Christoph-Hart Is it possible to bring HISE into the new decade and add a VS 2022 export option?
I know we can already use VS 2022 with a bit of fiddling around, but it's not straightforward and requires additional steps for every export.
-
RE: Export tool
Status update:
GNU/Linux: Fully working (standalone, vst2, installer). x64 only
Windows: Fully working (standalone, vst2, vst3, installer). x86/x64
MacOS: Fully working (standalone, vst2, vst3, au, codesigning). Needs a bit of tuning but almost there (installer). x64 only.When I say fully working, that's in my own tests, I expect many a bug report when I release it into the wild.
It's quite possible that AAX plugins will compile just fine on Windows and MacOS too, I've implemented it in the app but haven't tested it.
If all goes well I should finish up the tuning of the MacOS build tomorrow and it will be ready for my patrons to test this weekend!
@Christoph-Hart Could you merge my juce_template pull request (if all is well) as the mods there are needed for my app. The mods are also useful for regular exporting from HISE, bigobj is enabled by default and the VST3 SDK is set correctly to the one that is in the JUCE folder.
-
RE: Export tool
pkgbuild works! I can programmatically generate unique packages on MacOS now! woohoo!
-
RE: The definitive feature request & bug fix roadmap
Feature request:
Ability to designate some presets as factory (read-only)Done
Latest posts made by d.healey
-
RE: Failing at HISE 101
@clevername27 Use local, not var in the midi callbacks. Avoid global variables if you can. I'll take a proper look when I'm back at my computer.
-
RE: Message event flags or meta data?
@aaronventure I vaguely remember the discussion but I can't find the thread. Global variable it is then.
-
RE: Introducing: HISESnippet Browser
@Christoph-Hart I deleted the tabs but still one of the scripts is being added.
Another thing I tried was resetting the layout by renaming the HISE app data folder. Then loaded the project and hip, this time the export didn't include the files.
-
RE: Introducing: HISESnippet Browser
@Christoph-Hart Yes, however I have multiple script editors open in different tabs and I notice that some are still showing included code from my main XML. So perhaps that is where the issue is coming from. I'll do some tests.
-
RE: How to make a Panic Button (Send All MIDI Off)?
@Lindon Ah such a simple idea!
-
RE: Global Envelopes --- grrr....
@Lindon Type it as one word, same as the function because it's auto generated from the source code
-
Message event flags or meta data?
Is it possible to add any extra data to messages or events that can be assigned in one MIDI processor and picked up in another. I can see a way of doing this using a Global variable but I'd rather avoid that.