@Lindon Here's the thread I just found now regarding the auto- scroll issue I meant. Hope it is clearer now. And looks like it's sill a bug.

@TNTHM the compilation isnt the issue, and he's on windows

@TNTHM said in Limiter module not in API?:

@Christoph-Hart Got it. I see that there is a limiter section in the Dynamics module. Is that the limiter we should use?

yep - but bear in mind its a look ahead limiter - and will add delay to your output...

@Sawer said in Auto - Scroll Preset browser:

Hello everyone.

I am using the default preset browser to call states of the plugin, however, the highlighting square does not follow up when I selected a priest that is down to scroll to. Wondering if it is a but or if there's a method to set in the preset to make it follow.

er..... not sure what you are saying...

how to build hise 3.03?

The version numbers are pretty meaningless. Just build the develop branch.

the steps in the github have been stripped to nothing

They've been simplified to 5 steps - https://github.com/christophhart/HISE#windows

there is nothing anymore only a video from 3 years ago

I made an updated video last year (although nothing has really changed)

so what do i choose during install. which IPP,

You don't need IPP but if you are using it you install the OneAPI and if I remember correctly there is an option for OneAPI in Projucer (I explain it in the video I've included below)

@ustk Understood. Thank you.

@Christoph-Hart thanks! :)

I’m running a sample based Synth with 44.1kHz/16 bit (internally obersampling 4x) and I don’t hear aliasing though when I look at the waveform I can see it is distorted a little. So, what’s your experience? Where does it become audible to you?

I have to add that I use to not transpose a sample by more than +/-2 semitones with this synth so I can’t tell how it sounds with more than that

@TNTHM Answer was in the HISE shortcut menu (File > Edit Shortcuts). Press the Esc key (Mac) to enable completions.

@d-healey said in Audio files sorting:

Engine.sortWithFunction("items", sortFiles);}

You've passed a string "items" as the first parameter. You need to pass an array. Also you have an extra curly brace at the end.

I switched it to the array and it now sorted them correctly in the test plugin so I just need to make the change in the actual plugin now.

Thankyou for your help. As usual it is very useful and much appreciated

@sakorada Use a panel and trigonometry.

@orange I see. Thank you!

Tldr for this thread:

Upon trying to compile the source code for HISE 3.0.3 I was running into this error:

Ignoring file ../../../../tools/faust/fakelib/libfaust.a, building for macOS-x86_64 but attempting to link with file built for macOS-arm64

We also tried compiling through terminal directly which returned a similar error:

▸ Linking HISE ⚠️ ld: ignoring file ../../../../tools/faust/fakelib/libfaust.a, building for macOS-x86_64 but attempting to link with file built for macOS-arm64 ❌ clang: error: unable to execute command: Abort trap: 6 ❌ clang: error: linker command failed due to signal (use -v to see invocation) ** BUILD FAILED ** The following build commands failed: Ld /Users/[My name]/Desktop/HISE/projects/standalone/Builds/MacOSX/build/Release/HISE.app/Contents/MacOS/HISE normal (in target 'HISE Standalone - App' from project 'HISE Standalone') (1 failure)

The issue is with the version of Xcode being used to compile.

I am on:

Mac Intel i7, 2020
Mac OS 12.1, Monterey
HISE 3.0.3 source code

JUCE v6.1.4 ( comes with 3.0.3 source code)

Xcode version that did not work:
13.4.1

Xcode version that does work:
13.0

@d-healey kindly provided the following code which will automatically download and compile the latest HISE developer source code from git:

#!/bin/bash # Download HISE cd ~/Desktop git clone https://github.com/christophhart/HISE.git cd ./HISE git checkout develop # Extract SDKs unzip ./tools/SDK/sdk.zip -d ~/Desktop/HISE/tools/SDK # Build HISE ./tools/projucer/Projucer.app/Contents/MacOS/Projucer --resave ~/Desktop/HISE/projects/standalone/HISE\ Standalone.jucer cd ~/Desktop/HISE/projects/standalone/Builds/MacOSX xcodebuild -project "HISE Standalone.xcodeproj" -configuration Release -jobs 2 | xcpretty

This can be saved in a text editor as:
build_hise_osx.sh

You can execute this script by saving it to your Documents folder and typing into terminal:
sudo sh /Users/YOUR_USERNAME/Documents/build_hise_osx.sh

Thank you @d-healey and @Lindon for helping me troubleshoot this. I appreciate your time and energy.

@d-healey Thanks David, that did it, and like @ustk said I mixed things up. And in the snipped I provided it did work using doubleToString

@d-healey This was what I was missing. Thank you!

@d-healey Yes, the latest version. The workaround was to create 16 outputs somewhere else and then copy to the container.

@Christoph-Hart I knew it was simple! Thank you so much :)

@ustk Perfect. Thank you!!

For anyone doing it it manually, here is the code.

Thanks @d-healey as always!

Codesigning Plugin
codesign --remove-signature "MacHD/User/Desktop/PluginName.vst3"
codesign --remove-signature "MacHD/User/Desktop/PluginName.component"
codesign -s "Developer ID Application: YOURTEAMID" "MacHD/User/Desktop/PluginName.vst3" --timestamp
codesign -s "Developer ID Application: YOURTEAMID" "MacHD/User/Desktop/PluginName.component" --timestamp

Build Installer

Sign Installer
productsign --sign "Developer ID Installer: YOURTEAMID" "MacHD/User/Desktop/PluginName.pkg" "MacHD/User/Desktop/Signed/PluginName.pkg"

Notarize Installer
xcrun notarytool submit --apple-id "YOURAPPLEID" --password "App-Specific-Password" --team-id "YOURTEAMID" "MacHD/User/Desktop/Signed/PluginName.pkg"

Wait For Upload To Complete

Staple Installer
xcrun stapler staple "MacHD/User/Desktop/Signed/PluginName.pkg"

Check Status (Accepted)
spctl --assess -vvv --type install "MacHD/User/Desktop/Signed/PluginName.pkg"

FYI: Just a tip coming from the altool manual notarizing. I used to have to enter my TEAMID including my name like "My Name (GD78YHD87G)" but with the notarytool, it seems you just need the actual TEAMID Number, not the name as well.

Also, I dont think this way sends the Notarization Email Confirmation. I did a fairly small upload a while ago and have yet to receive it. I've had it take hours before, but for a much larger file. Typically it sent the email within 10 or so minutes with altool. (it does not send the email. Once the upload is complete, youre good to go).