Forum
    • Categories
    • Register
    • Login
    1. Home
    2. David Healey
    3. Posts
    • Profile
    • Following 1
    • Followers 83
    • Topics 1,075
    • Posts 24,987
    • Groups 1

    Posts

    Recent Best Controversial
    • RE: HISE Won’t Install Proper Version

      @CBIbanez Have you built HISE from source? If not, that's the first step before you can compile your project.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Set Label Text on Preset Load?

      @Chazrox https://www.youtube.com/watch?v=NMtOAhvK0Qo

      posted in Scripting
      David HealeyD
      David Healey
    • RE: VST SDK Version?

      @RedFireTF2 You need to compile from source, but the VST3 SDK will only come into play when you compile your project as a plugin (or if you're compiling HISE as a plugin).

      posted in General Questions
      David HealeyD
      David Healey
    • RE: VST SDK Version?

      @RedFireTF2 HISE uses a customised version of JUCE and includes a version of the VST3 SDK (not the latest one). I'm not sure if you could just drop in the latest VST3 SDK and have it work, but try it and let us know.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Plotter Text

      @ustk said in Plotter Text:

      So 3 years later... Is there anyone using a plotter successfully?

      Remind me what the problem with it is?

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Project Declaration and Feature Requests

      @pratitghosh If your end goal is to build a DAW I'd start with something like Tracktion Engine (https://www.tracktion.com/develop/tracktion-engine) or use one of the existing open source DAWs as a base and customise it. It would save you a ton of work.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Error when compiling vst3

      @pcs800 said in Error when compiling vst3:

      Of the server or the dev pc?

      Whichever system has Visual Studio on it.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Error when compiling vst3

      @pcs800 How much space on the C drive?

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Error when compiling vst3

      @pcs800 Which commit of HISE are you using? Which version of Visual Studio?

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Error when compiling vst3

      @pcs800 Delete the binaries folder and try again

      posted in General Questions
      David HealeyD
      David Healey
    • RE: Missing nodes after restart

      @Stepaan You might find my free Bootcamp course helpful: https://audiodevschool.com/courses/hise-bootcamp/

      posted in ScriptNode
      David HealeyD
      David Healey
    • RE: Missing nodes after restart

      @Stepaan Try building from source, the prebuilt version is very old now

      posted in ScriptNode
      David HealeyD
      David Healey
    • RE: Missing nodes after restart

      @Stepaan it could be a HISE bug or a workflow issue. Have you built HISE from source?

      posted in ScriptNode
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay So it should be an effect then, I'm not sure why it's not working.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay Did you definitely export as an effect?

      posted in General Questions
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay Looks like it's on an external drive (iCloud Drive)? If so, probably a permission issue.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay Might be a permission issue, not sure. Or is it an alias rather than an actual binary? Show me a screenshot of the .component file.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay You need to place it in the AU plugins folder, it's alongside the VST3 folder, I think it's in Library/Audio/Plug-ins/AU - remember that macOS has two Library folders, you want the system one I think.

      posted in General Questions
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay Somewhere in the Binaries folder, it will have a .component extension

      posted in General Questions
      David HealeyD
      David Healey
    • RE: project build failed (codesign command failed)

      @Jimi_Jay All that happens when you select export from HISE is it creates a JUCE project and runs xcode in a terminal. You can close the terminal and open the JUCE project manually in Projucer then open that in xcode just like building HISE. The auto generated juce project file is in your project's Binaries folder.

      posted in General Questions
      David HealeyD
      David Healey