HISE Logo Forum
    • Categories
    • Register
    • Login

    Can't use projucer at all on M1 Big Sur MacBook

    Scheduled Pinned Locked Moved General Questions
    11 Posts 7 Posters 963 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.
    • d.healeyD
      d.healey @observantsound
      last edited by

      @observantsound said in Can't use projucer at all on M1 Big Sur MacBook:

      Current build download: "projucer is damaged and can not be opened"

      You need a working Projucer. After that you'll need to open the HISE Standalone .jucer file in Projucer and make sure the architecture is set to x86_64 and disable IPP and remove any related paths.

      You could try downloading Projucer from the JUCE site, that's worked for others - https://forum.hise.audio/topic/3666/default-hise-projucer-not-opening-damaged-on-mac

      But the one that comes with HISE should work, and it works on my system. You can also build Projucer from source, the source code is included with HISE, although I don't know if it's configured correctly for M1.

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

      DanHD 1 Reply Last reply Reply Quote 0
      • DanHD
        DanH @d.healey
        last edited by

        @d-healey I built the HISE Standalone.jucer app in XCode from the xcode project file in the build folder.

        It's a permissions issue and this gets around it nicely

        DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
        https://dhplugins.com/ | https://dcbreaks.com/
        London, UK

        1 Reply Last reply Reply Quote 0
        • C
          crd
          last edited by

          Or just use the terminal command "xattr -cr" which is as easy as opening terminal typing "xattr -cr" and then dragging the file that is giving you that error message.

          ulrikU 1 Reply Last reply Reply Quote 2
          • Matt_SFM
            Matt_SF @observantsound
            last edited by

            @observantsound

            Current build download: "projucer is damaged and can not be opened"

            Happened to me one, IIRC I just had to download the HISE project folder from github again. Maybe the file was corrupted.
            Or use git to manage HISE source files
            .

            Develop branch
            Win10 & VS17 / Ventura & Xcode 14. 3

            1 Reply Last reply Reply Quote 0
            • ulrikU
              ulrik @crd
              last edited by ulrik

              @crd said in Can't use projucer at all on M1 Big Sur MacBook:

              Or just use the terminal command "xattr -cr" which is as easy as opening terminal typing "xattr -cr" and then dragging the file that is giving you that error message.

              I have this problem every time I've updated the develop branch to next commit, and what @crd says this works always, however I'm not on M1 processor

               terminal command "xattr -cr" + path to projucer
              

              Hise Develop branch
              MacOs 15.3.1, Xcode 16.2
              http://musikboden.se

              1 Reply Last reply Reply Quote 0
              • O
                observantsound
                last edited by

                apologies for the late reply. I wasn't getting email notifications and thought no one answered.

                I'll try some of your suggestions.

                @d-healey That was the jucer file from the git folder --> tools.
                Opening it immediately gave me this error so I coudln't even make any changes to settings. And this happened with the current build only.
                The last stable 2.0 gives me the permission error.
                But what I've learned from my last attempt is that I HAVE to use the current build or the build will not compile.

                @DanH Could you elaborate on that process? I'm very new to coding except for KSP and all this building and Xcode stuff just isn't an issue there.

                @crd Thanks for the tip. I'll try that!

                @Matt_SF I've tried downloading it several times and it was always damaged.
                It might be because of my last attempt and there are still installation files flying around that are causing issues? Any way to make sure I've everything regarding juce and Hise removed before trying again?

                A more general question:
                Do you absolutely need the JUCER stuff to start working on an instrument? Or is its job only to build and compile an executable app?

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

                  @observantsound said in Can't use projucer at all on M1 Big Sur MacBook:

                  That was the jucer file from the git folder --> tools.

                  .jucer is a file extension. This refers to a JUCE project file that can be opened in Projucer, which is an application.

                  You need to open the HISE .jucer file (projects/standalone/HISE Standalone.jucer) with the Projucer application (tools/projucer/Projucer).

                  @observantsound said in Can't use projucer at all on M1 Big Sur MacBook:

                  Opening it immediately gave me this error so I coudln't even make any changes to settings. And this happened with the current build only.

                  This sounds like the permission error with solution posted above. terminal command "xattr -cr" + path to projucer

                  @observantsound said in Can't use projucer at all on M1 Big Sur MacBook:

                  But what I've learned from my last attempt is that I HAVE to use the current build or the build will not compile.

                  Correct. M1 didn't exist in 2018 and so JUCE from that time doesn't support it.

                  @observantsound said in Can't use projucer at all on M1 Big Sur MacBook:

                  Do you absolutely need the JUCER stuff to start working on an instrument? Or is its job only to build and compile an executable app?

                  Projucer is used to manage JUCE projects. HISE itself is a JUCE project so in order to build HISE you need to use Projucer. Once you have HISE up and running you don't need to worry about Projucer until you want to export and compile your project, then it's pretty much the same process as compiling HISE.

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

                  ForeverLiveF 1 Reply Last reply Reply Quote 1
                  • O
                    observantsound
                    last edited by

                    @d-healey Thanks for the clarification on my last question.

                    The terminal command worked in getting it to open. Even though the error was "application is damaged and should be put into bin" instead of "permission denied"

                    Another general question:
                    When I open these apps and files I often get asked about additional stuff needed or updates being available. Should I always ignore these? Stick to the stuff the way it came with the Git repo?
                    Will it break stuff if I update?
                    That might also have been why it didn't work last time I tried this.

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

                      @observantsound Yes click ignore

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

                      1 Reply Last reply Reply Quote 2
                      • ForeverLiveF
                        ForeverLive @d.healey
                        last edited by

                        @d-healey thank you, that just helped me too.

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

                        23

                        Online

                        1.7k

                        Users

                        11.8k

                        Topics

                        103.2k

                        Posts