I'm seeing this in the latest version of HISE as well on multiple MacOS:
batchCompileOSX: line 7: /HISE/tools/Projucer/xcbeautify: Bad CPU type in executable
macOS 15.4.1 + Xcode 16.3
macOS 13.7.5 + Xcode 15.4
building from the autogenerated projucer file works as expected.
I think I've been here before:
https://forum.hise.audio/topic/8742/how-to-debug-server-isonline
The functions check google and amazon to see if they are reachable, but some macos systems have issues with http calls.
I've updated the source to point to my https domain. I reasoned it wasn't important if they are online but unable to reach my server.
@Christoph-Hart This new found magical power is intoxicating! 
@Christoph-Hart I'm using markdown for my embedded documentation. Please don't kill it 
@Christoph-Hart said in 8 Times more CPU consumption on Aida-X Neural Models:
To be honest: I‘m a bit „disincentivized“ in fixing the NAM stuff because I don‘t see a use case except for loading in existing models from that one website with potential infringement of other peoples work, but maybe my understanding of the possible use cases here is wrong.
There is also widespread adoption for the NAM format. Darkglass just released a NAM compatible product:
https://www.darkglass.com/creation/anagram/
https://www.tone3000.com/blog/unveiling-anagram-darkglass-electronics
@Christoph-Hart said in 8 Times more CPU consumption on Aida-X Neural Models:
@Dan-Korneff alright then it stays, the people have spoken :)
Just out of curiosity: who is using this in a real project and does it work there? Like except for the NAM loader?
To be honest: I‘m a bit „disincentivized“ in fixing the NAM stuff because I don‘t see a use case except for loading in existing models from that one website with potential infringement of other peoples work, but maybe my understanding of the possible use cases here is wrong.
Adding NAM support is super helpful for some people as the training scripts are solid and actively maintained. I'll be using RT-Neural on this end for the parameterized support. Still making a few tweaks to the training script I started with, but I’m planning to build around it soon.
@Christoph-Hart said in 8 Times more CPU consumption on Aida-X Neural Models:
I'd rather remove the entire RT Neural framework from HISE so it doesn't raise false expectations
@Simon I just saw that a recorder is part of the High Performance Backend. Time for more server tinkering. 
Are you referring to the plug-in preview in HISE? If so, I have to close the window and reopen to see the updated size here.
I haven't messed with the global cable much. It might be capped at a 1?
Are your meters running on a gain factor of 0-1? If so, you'll need to convert Gain to dB. Then, you need to map the dBFS range to the analog VU meter scale, so that -18 dBFS (or -20 dBFS) aligns with 0 VU on your meter.
EDIT: if your meter is actually PPM, 0 would be referenced to -9 dBFS or -12 dBFS.
Maybe I've been living under a rock, but I haven't heard of a sine shaper before, so this piqued my interest. It's a type of non-linear waveshaper that folds the input signal back onto itself in a sinusoidal pattern. Apparently, it produces a smooth and natural-sounding harmonic generation.
There's some analysis here:
http://www.openmusiclabs.com/files/otasine.pdf
The formula seems to be pretty simple:
output = sin(foldAmount * asin(input));
// foldAmount controls how much the wave folds.
I threw together a quick Octave script to see what's going on.
Here's the Octave script if you want to play around with it:
% Korneff - Sinusoidal Wavefolder Variations
clear; clc; close all;
Fs = 48e3; % Sampling frequency 48 kHz
%% Choose Input Type: 'sine', 'impulse', or 'dc_sweep'
inputType = 'sine'; % <-- Change to 'sine', 'impulse', or 'dc_sweep'
%% Input Signal Setup
switch inputType
case 'sine'
f = 2; % Frequency of sine wave (2 Hz)
duration = 2/f; % Duration = 2 cycles (2 periods)
T = 0:1/Fs:duration;
Vin = sin(2*pi*f*T)'; % Column vector for Vin
case 'impulse'
N = 2048;
Vin = [1; zeros(N-1, 1)];
T = (0:N-1)/Fs;
case 'dc_sweep'
N = 500; % Number of sweep points
Vin = linspace(-1, 1, N)'; % DC sweep from -1 to 1 V
T = Vin; % Use sweep voltage as x-axis
otherwise
error('Invalid inputType selected. Choose ''sine'', ''impulse'', or ''dc_sweep''.');
end
%% Sinusoidal Wavefolder Functions
% (1) Standard Sinusoidal Wavefolder
function y = standard_sinusoidal_wavefolder(x, foldAmount)
y = sin(foldAmount * asin(x));
end
% (2) Phase-Inverted Sinusoidal Wavefolder
function y = inverted_sinusoidal_wavefolder(x, foldAmount)
y = -sin((pi/2) * asin(x)); % The phase-inverted version
end
%% Single Processing Loop
Vout1 = zeros(size(Vin)); % Standard Sinusoidal Wavefolder
Vout2 = zeros(size(Vin)); % Phase-Inverted Sinusoidal Wavefolder
foldAmount = 2; % Controls how much the wave folds (adjustable)
for n = 1:length(Vin)
Vout1(n) = standard_sinusoidal_wavefolder(Vin(n), foldAmount);
Vout2(n) = inverted_sinusoidal_wavefolder(Vin(n), foldAmount);
end
%% Plotting
if strcmp(inputType, 'sine')
figure;
subplot(2,1,1);
plot(T, Vin, 'b-', 'LineWidth', 1);
hold on;
plot(T, Vout1, 'r-', 'LineWidth', 1);
legend('Vin', 'Standard Wavefolder Vout');
title('Standard Sinusoidal Wavefolder Output');
xlabel('Time (s)');
ylabel('Amplitude');
grid on;
subplot(2,1,2);
plot(T, Vin, 'b-', 'LineWidth', 1);
hold on;
plot(T, Vout2, 'g-', 'LineWidth', 1);
legend('Vin', 'Inverted Wavefolder Vout');
title('Inverted Sinusoidal Wavefolder Output (-sin(π/2 x))');
xlabel('Time (s)');
ylabel('Amplitude');
grid on;
elseif strcmp(inputType, 'dc_sweep')
figure;
subplot(2,1,1);
plot(T, Vout1, 'r-', 'LineWidth', 1);
title('DC Sweep: Standard Sinusoidal Wavefolder');
xlabel('Vin (V)');
ylabel('Vout (V)');
grid on;
xlim([-1, 1]);
ylim([-1, 1]);
subplot(2,1,2);
plot(T, Vout2, 'g-', 'LineWidth', 1);
title('DC Sweep: Inverted Sinusoidal Wavefolder');
xlabel('Vin (V)');
ylabel('Vout (V)');
grid on;
xlim([-1, 1]);
ylim([-1, 1]);
else % impulse
figure;
subplot(2,1,1);
stem(T, Vout1, 'filled');
title('Impulse Response - Standard Wavefolder');
xlabel('Time (s)');
ylabel('Amplitude');
grid on;
subplot(2,1,2);
stem(T, Vout2, 'filled');
title('Impulse Response - Inverted Wavefolder');
xlabel('Time (s)');
ylabel('Amplitude');
grid on;
% Frequency response
[H1, W1] = freqz(Vout1, 1, 2048, Fs);
[H2, W2] = freqz(Vout2, 1, 2048, Fs);
figure;
subplot(2,1,1);
semilogx(W1, 20*log10(abs(H1)), 'LineWidth', 1);
title('Frequency Response: Standard Sinusoidal Wavefolder');
xlabel('Frequency (Hz)');
ylabel('Magnitude (dB)');
grid on;
subplot(2,1,2);
semilogx(W2, 20*log10(abs(H2)), 'LineWidth', 1);
title('Frequency Response: Inverted Sinusoidal Wavefolder');
xlabel('Frequency (Hz)');
ylabel('Magnitude (dB)');
grid on;
end
EDIT: script link fixed
my command line prompt looks like:
codesign --deep --force --timestamp --options runtime --sign
I had this happen to me a couple months back. I think it ended up being an issue with a file that was part of the package. I haven't tried the new export feature yet, but I think you can get the log file to see the exact issue with:
xcrun notarytool log <submission-id>
@Christoph-Hart @ustk Confirmed working:
The open source framework for sample based instruments
GitLab (gitlab.korneff.co)
It requires 2 new files:
juce_Span.h
juce_EnumHelpers.h
and edits to:
juce_core.h
juce_win32_SystemStats.cpp
juce_SystemStats.cpp
juce_OnlineUnlockStatus.cpp
@ustk Got it sorted. Sending to beta for testing now.
@HISEnberg You need to set HISE_NUM_FX_PLUGIN_CHANNELS to the amount of audio channels + sidechain channels.
@Christoph-Hart Can we get the default name of the sidechain to be the name of our HISE project?
Right now, an external sidechain is named "External Sidechain (+bus)" which can get confusing if you have 2 different plugins made with HISE on the same channel.
