HISE Logo Forum
    • Categories
    • Register
    • Login

    Hise project crushes on start after scriptnode compile

    Scheduled Pinned Locked Moved General Questions
    5 Posts 3 Posters 431 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • andrei sA
      andrei s
      last edited by

      Hello!
      I compiled scriptnode fx and now my HISE project drops out every time i try to open it.
      I deleted all files in DspNetworks and AdditionalSourceCode folders, but the problem is sill here.
      Also, compiled fx opens in other project and work as it should be.

      How can i fix that?

      1 Reply Last reply Reply Quote 0
      • d.healeyD
        d.healey
        last edited by

        It's probably not a problem with the effect if you removed the network and it works in other projects.

        Have you ran the two project XML files through a validator?

        Libre Wave - Freedom respecting instruments and effects
        My Patreon - HISE tutorials
        YouTube Channel - Public HISE tutorials

        andrei sA 2 Replies Last reply Reply Quote 1
        • andrei sA
          andrei s @d.healey
          last edited by

          @d-healey I'm just looking for where to start.
          I'll try to check XML files

          1 Reply Last reply Reply Quote 0
          • Adam_GA
            Adam_G
            last edited by Adam_G

            if you can see what is causing the hang up you can delete it from the xml load the project and re add it. i had a project that crashed on Compiling Sampler and was able to remove that module from the xml and then load it.

            assuming the xml is valid, do you see anything happen when you try to load the project?

            1 Reply Last reply Reply Quote 1
            • andrei sA
              andrei s @d.healey
              last edited by

              @d-healey Thank you as always!
              The reason was that I renamed the scriptnode fx module before compiling, but the name didn't change in the xml file.

              1 Reply Last reply Reply Quote 1
              • First post
                Last post

              54

              Online

              1.7k

              Users

              11.7k

              Topics

              101.8k

              Posts