Forum
    • Categories
    • Register
    • Login

    HISE image directory not found (macOS)

    Scheduled Pinned Locked Moved General Questions
    54 Posts 5 Posters 374 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.
    • A
      Avián @David Healey
      last edited by

      @David-Healey @Oli-Ullmann ok, again all these warnings...Screenshot allissues again.png

      David HealeyD 1 Reply Last reply Reply Quote 0
      • David HealeyD
        David Healey @Avián
        last edited by

        @Avián Warnings are not a problem, you only need to watch for errors.

        Free HISE Bootcamp Full Course for beginners.
        YouTube Channel - Public HISE tutorials
        My Patreon - HISE tutorials

        A 1 Reply Last reply Reply Quote 1
        • Oli UllmannO
          Oli Ullmann @David Healey
          last edited by

          @David-Healey
          In that case, you're absolutely right! :-)

          But if there's only one HISE version on the computer, I felt that using the projects folder was the least error-prone method...

          1 Reply Last reply Reply Quote 1
          • A
            Avián @David Healey
            last edited by

            @David-Healey @Oli-Ullmann ok finally it works! Thank you so much guys! Great work, great support! Have a nice day

            A 1 Reply Last reply Reply Quote 2
            • A
              Avián @Avián
              last edited by

              @Oli-Ullmann @David-Healey I'm sorry but I'm back with this issue. I could compile/export the standalone, the vst3, the au, I was successful signing them, but my notarization for my installer doesn't work, so I went back a few steps and opened the standalone and vst3 and au and then i saw this: Screenshot images fail.png
              still an issue with the 2 images....
              but in HISE it shows up like it should:Screenshot images fail2.png
              My Images are in the right folder, named correctly everything, I don't get it?
              BTW when I close and start HISE my project ALWAYS is losing it's script, I copy paste it, so it's not a big problem, but I think this isn't normal.
              And maybe all of these little issues are the reason why the Installer notarization was blocking something. I need help again,....

              David HealeyD 1 Reply Last reply Reply Quote 0
              • David HealeyD
                David Healey @Avián
                last edited by

                @Avián These seem like unrelated issues to the original problem.

                Have you enabled the option in project preferences to embed images?

                @Avián said in HISE image directory not found (macOS):

                BTW when I close and start HISE my project ALWAYS is losing it's script,

                Scripts are saved when you click compile.

                @Avián said in HISE image directory not found (macOS):

                but my notarization for my installer doesn't work

                What do you mean by doesn't work? Have you codesigned the installer?

                Free HISE Bootcamp Full Course for beginners.
                YouTube Channel - Public HISE tutorials
                My Patreon - HISE tutorials

                A 1 Reply Last reply Reply Quote 0
                • A
                  Avián @David Healey
                  last edited by

                  @David-Healey

                  @David-Healey said in HISE image directory not found (macOS):

                  Have you enabled the option in project preferences to embed images?

                  Screenshot embed images.png
                  Yes

                  @David-Healey said in HISE image directory not found (macOS):

                  Scripts are saved when you click compile.

                  Screenshot hiseissue1.png
                  Screenshot hise issue2.png
                  This always shows up if I close HISE and open my saved project again. HISE is always losing the script and I always need to copy paste it again and compile again. This didn't happen on Windows.

                  @David-Healey said in HISE image directory not found (macOS):

                  What do you mean by doesn't work? Have you codesigned the installer?

                  I signed the Installer, cause I thought codesign is just for signing single files like .app .vst3 and not for.pkg
                  I codesigned my vst3 and components before and notarized them, it works great but my .app doesn't work. the codesign works but by notarizing the standalone it fails by the same issue, I got later by trying it with the installer, so the standalone has to be the problem (single and as a part of the installer files):
                  {

                  "logFormatVersion": 1,

                  "jobId": "e3733774-a429-4671-9f0b-3a5de89e5544",

                  "status": "Invalid",

                  "statusSummary": "Archive contains critical validation errors",

                  "statusCode": 4000,

                  "archiveFilename": "macOS-Installer_Plugin_DrumKit_Standalone.pkg",

                  "uploadDate": "2026-01-25T12:44:36.154Z",

                  "sha256": "d1c1f509cca7f54f3e5b5d927f6fcc429ea834f65b5fdf5cd5ead6524a4a0fec",

                  "ticketContents": null,

                  "issues": [

                  {
                  
                    "severity": "error",
                  
                    "code": null,
                  
                    "path": "macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/Contents/MacOS/myplugin",
                  
                    "message": "The signature of the binary is invalid.",
                  
                    "docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735",
                  
                    "architecture": "x86_64"
                  
                  },
                  
                  {
                  
                    "severity": "error",
                  
                    "code": null,
                  
                    "path": "macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/Contents/MacOS/myplugin",
                  
                    "message": "The signature of the binary is invalid.",
                  
                    "docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735",
                  
                    "architecture": "arm64"
                  
                  },
                  
                  {
                  
                    "severity": "warning",
                  
                    "code": null,
                  
                    "path": "macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/LowEnd.zip",
                  
                    "message": "The archive at macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/LowEnd.zip could not be unpacked. Any executables contained in the archive will not be notarized.",
                  
                    "docUrl": null,
                  
                    "architecture": null
                  
                  }
                  

                  ]

                  }
                  I really don't know where this "LowEnd.zip" comes from, maybe this is the problem. My Plugin-Name starts with LowEnd, but the name is much longer?!

                  David HealeyD 1 Reply Last reply Reply Quote 0
                  • David HealeyD
                    David Healey @Avián
                    last edited by

                    @Avián said in HISE image directory not found (macOS):

                    Yes

                    Have you loaded the images into the pool in your script? https://docs.hise.audio/scripting/scripting-api/engine/index.html#loadimageintopool

                    @Avián said in HISE image directory not found (macOS):

                    This always shows up if I close HISE and open my saved project again. HISE is always losing the script and I always need to copy paste it again and compile again. This didn't happen on Windows.

                    Is your project on a network drive? Are you saving the project file as an xml?

                    @Avián said in HISE image directory not found (macOS):

                    I signed the Installer

                    Did you use the installer certificate rather than the application certificate?

                    Free HISE Bootcamp Full Course for beginners.
                    YouTube Channel - Public HISE tutorials
                    My Patreon - HISE tutorials

                    A 2 Replies Last reply Reply Quote 0
                    • A
                      Avián @David Healey
                      last edited by

                      @David-Healey said in HISE image directory not found (macOS):

                      Have you loaded the images into the pool in your script? https://docs.hise.audio/scripting/scripting-api/engine/index.html#loadimageintopool

                      I will try that!

                      @David-Healey said in HISE image directory not found (macOS):

                      Is your project on a network drive? Are you saving the project file as an xml?

                      Yes, my project is located in the Documents folder, inside the HISE Projects directory under XmlPresetBackups, and yes, I am saving the files as XML.

                      @David-Healey said in HISE image directory not found (macOS):

                      Did you use the installer certificate rather than the application certificate?

                      Depends on. If I codesigned the .vst3 .component .app I used the application certificate and for the installer I used the installer certificate. I'm really confused about the LowEnd.zip file...Don't you think that could be the problem, or the invalid signature of the binary?

                      David HealeyD 1 Reply Last reply Reply Quote 0
                      • David HealeyD
                        David Healey @Avián
                        last edited by

                        @Avián said in HISE image directory not found (macOS):

                        Yes, my project is located in the Documents folder

                        Is that yes your project is on a network drive? If so that's probably where the issue is coming from. HISE probably doesn't have permission to write the script files to that location.

                        @Avián said in HISE image directory not found (macOS):

                        LowEnd.zip

                        Check your packages project, looks like that's been included in the payload.

                        Free HISE Bootcamp Full Course for beginners.
                        YouTube Channel - Public HISE tutorials
                        My Patreon - HISE tutorials

                        1 Reply Last reply Reply Quote 0
                        • A
                          Avián @David Healey
                          last edited by

                          @David-Healey said in HISE image directory not found (macOS):

                          Is that yes your project is on a network drive? If so that's probably where the issue is coming from. HISE probably doesn't have permission to write the script files to that location.

                          ah sorry no, the project is not on a network drive or shared folder!

                          @David-Healey said in HISE image directory not found (macOS):

                          LowEnd.zip

                          Check your packages project, looks like that's been included in the payload.

                          ok my terminal found some zip in my Binaries Folder. One important question, before compiling/exporting again now, should I delete everything in my Project's Binaries Folder for a very clean vst3 au and app file this time? Or maybe use something like this before? Screenshot clean build direct.png

                          David HealeyD A 2 Replies Last reply Reply Quote 0
                          • David HealeyD
                            David Healey @Avián
                            last edited by

                            @Avián said in HISE image directory not found (macOS):

                            I delete everything in my Project's Binaries Folder for a very clean vst3 au and app file this time?

                            Yeah using the Clean Build directory option is the way to go.

                            Free HISE Bootcamp Full Course for beginners.
                            YouTube Channel - Public HISE tutorials
                            My Patreon - HISE tutorials

                            1 Reply Last reply Reply Quote 0
                            • A
                              Avián @Avián
                              last edited by

                              @Avián @David-Healey and what about the PooledResources? Delete everything in there too? Before exporting/compiling again?

                              David HealeyD 1 Reply Last reply Reply Quote 0
                              • David HealeyD
                                David Healey @Avián
                                last edited by

                                @Avián No need, they will be recreated automatically - but you can if it makes you feel better :)

                                Free HISE Bootcamp Full Course for beginners.
                                YouTube Channel - Public HISE tutorials
                                My Patreon - HISE tutorials

                                A 1 Reply Last reply Reply Quote 0
                                • A
                                  Avián @David Healey
                                  last edited by

                                  @David-Healey ok thank you! I will try the whole process again now! I'll tell you later if it works!

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

                                  21

                                  Online

                                  2.2k

                                  Users

                                  13.3k

                                  Topics

                                  115.4k

                                  Posts