1. HISE
  2. Categories

Categories

  • General questions and announcements about HISE

    7k Topics
    61k Posts
    B

    @d-healey Ya, same experience here for me, after changing that. I'll talk through what I do to modify that setting. So there is no Projucer file for the project until I try a build and let it fail, so I export an AU until it fails, then go to that folder and change the Projcer setting for Enable Plugin Copy - Disabled, save, then Go to Hise and export again, and same error happens. I'd assume this is wrong way going about it.
    I also tried just Compile Project, which gives xpretty errors, so there may be some issues with that install even tho i ran the command for installing it and all went fine.. here is screen of Compile error.

    Perform sanity checks
    Create C++ autogenerated files
    Create binary data files
    Exporting the pooled resources
    Export audio files
    Export image files
    Export samplemap files
    Export MIDI files
    DONE
    Create embedded data files
    Launch system compiler...
    Re-saving file: /Users/nathan/Documents/HISE Projects/TestFader2/Binaries/AutogeneratedProject.jucer
    Finished saving: Visual Studio 2017
    Finished saving: Xcode (macOS)
    Finished saving: Xcode (iOS)
    Finished saving: Linux Makefile
    Compiling Instrument plugin TestFader2 ...
    Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
    /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/parser.rb:434:in ===': invalid byte sequence in US-ASCII (ArgumentError) from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/parser.rb:434:in update_test_state'
    from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/parser.rb:307:in parse' from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/formatters/formatter.rb:88:in pretty_format'
    from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/lib/xcpretty/printer.rb:19:in pretty_print' from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/bin/xcpretty:84:in block in <top (required)>'
    from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/bin/xcpretty:83:in each_line' from /Library/Ruby/Gems/2.6.0/gems/xcpretty-0.4.0/bin/xcpretty:83:in <top (required)>'
    from /usr/local/bin/xcpretty:23:in load' from /usr/local/bin/xcpretty:23:in

    '
    ** BUILD FAILED **

    Screenshot 2025-02-10 at 10.09.54 PM.png

  • Scripting related questions and answers

    2k Topics
    12k Posts
    d.healeyD

    Done - https://github.com/christophhart/HISE/pull/680

  • To share HiseSnippets, Interface Elements, GUI, UI/UX, Panel LAF etc..

    162 Topics
    1k Posts
    ChazroxC

    Besides my console models, I decided to start making some pedal kits for everyone too! Lmk if you guys have any requests.

    const var screenshot = ! Render;
    so dont judge my lighting so hard. lol

    Screenshot 2025-02-10 at 2.39.06 PM.png

    Screenshot 2025-02-10 at 2.23.46 PM.png

  • All about ScriptNode DSP nodes, patches, SNEX and recipes.

    265 Topics
    2k Posts
    Christoph HartC

    @griffinboy yes it's included within the RTNeural code folder, but it's only available in the translation unit that compiles the RTNeural code (the hi_tools module).

    In order to make it accessible on other translation units and your own nodes you have to add this line to hi_tools/hi_tools.h:

    #include "hi_neural/RTNeural/modules/xsimd/xsimd.hpp"

    The place doesn't really matter, but somewhere around line 150 would be a good spot.

  • A subforum for discussing Faust development within HISE

    91 Topics
    779 Posts
    ChazroxC

    @aaronventure Thats exactly what I would like to do. I've been trying to figure that out from the start. I know thats ambitious for a noob but i've figured out most of the stuff I need to know to get started. Im alot more comfortable on the design and audio side than scripting so im currently trying to learn as much as I can from everyone here. Thanks everyone!

  • If you need a certain feature, post it here.
    566 Topics
    4k Posts
    DabDabD

    Label laf is also necessary. I guess only Laf is possible via css. No traditional LAF is supported for Label.

  • Develop better software through collaboration and shared knowledge. Not just about coding —> covering the entire journey, from development to launching and promoting plugins or software.

    9 Topics
    85 Posts
    d.healeyD

    @tonni Ah fair enough, just looked sus

  • If you encounter any bug, post it here.
    1k Topics
    11k Posts
    DanHD

    @Christoph-Hart bump! 😄

  • Post your example snippets that you want to add to the official HISE snippet database here. We'll revise it, upload it to the repo and delete the post when finished.

    11 Topics
    54 Posts
    WaterSpoonW

    Fantastic!!!

  • Everything related to the documentation (corrections, additions etc.) can be posted here
    Documentation Discussions
    62 Topics
    432 Posts
    HISEnbergH

    @d-healey Nice this documentation is great to have.

    The HISE GPT is a bit better these days, especially for navigating the HISE docs. If you prompt it to check the HISE API on a specific subject, it will access it and give you a description of the what you are asking about. It is still quite prone to error and quite imperfect for generating code. For LAF it's okay.

  • Collection of Blog Entries

    73 Topics
    690 Posts
    d.healeyD

    @orange I've got more planned :)

  • The nerdy place for discussing the C++ framework
    141 Topics
    989 Posts
    clevername27C

    @mmprod Yep! We haven't announced it yet, so…well, if you know who I am, you probably know who it is. HISE will be on it! 👻

42

Online

2.0k

Users

11.0k

Topics

96.3k

Posts