@d-healey Very nice page, will check it out in detail. But this is new to me:

const var foo = a || b;
const var bar = !c;

Very efficient.

@d-healey Okay, but the icons should be a .icns file, a multi-png icon file with all resolutions. Made with this script: (iconutil)

# shell script for creating an icon for an application from a set of input images

input_filepath="icon_name_1024_x_1024.png"
output_iconset_name="outputicon.iconset"
mkdir $output_iconset_name

sips -z 16 16     $input_filepath --out "${output_iconset_name}/icon_16x16.png"
sips -z 32 32     $input_filepath --out "${output_iconset_name}/icon_16x16@2x.png"
sips -z 32 32     $input_filepath --out "${output_iconset_name}/icon_32x32.png"
sips -z 64 64     $input_filepath --out "${output_iconset_name}/icon_32x32@2x.png"
sips -z 128 128   $input_filepath --out "${output_iconset_name}/icon_128x128.png"
sips -z 256 256   $input_filepath --out "${output_iconset_name}/icon_128x128@2x.png"
sips -z 256 256   $input_filepath --out "${output_iconset_name}/icon_256x256.png"
sips -z 512 512   $input_filepath --out "${output_iconset_name}/icon_256x256@2x.png"
sips -z 512 512   $input_filepath --out "${output_iconset_name}/icon_512x512.png"

iconutil -c icns $output_iconset_name

rm -R $output_iconset_name

I mean if one is to be a good boy and future-proof the icons on mac with all the resolutions (retina, 4k, 5k, 8k etc)

So can I just use a icon.icns instead?
@Christoph-Hart

A large png file is sometimes not that pretty once it is downsized, can be blurry.

@DimitrisSP @Natanr @yall

Thanks a lot @DimitrisSP for the vu-meter. I modified it a bit to make whole integers from your png of 107 strips and set it to -100 to +6 dbFS. Also added peak values in labels for both L, R and highest of the two.

Here is that project (scriptnode 2020-08-20): LevelMeterTest--andioak-peak-values.zip

@Christoph-Hart Is there a pan-law compensation built into the Simple Gain module/plugin? To compensate for the increased value from the other channel? The values I get are steep when I pan towards one way, but it might be my programming here. (and my gain is +1, but at Left 40:ish i get around 5-6 db over the center peak, that´s about what pan law should compensate for...) (and the gif below is 7fps )

Here it is:

Script of this thing:

Content.makeFrontInterface(600, 500);

const var LevelMeterL = Content.getComponent("LevelMeterL");
const var LevelMeterR = Content.getComponent("LevelMeterR");
const var LevelMeterLock = Content.getComponent("LevelMeterLock");

// show values as well, via label with whole integer db values.
const var Label_MeterValue = Content.getComponent("Label_MeterValue"); // the peak of the strongest channel. 
const var Label_MeterValue_L = Content.getComponent("Label_MeterValue_L");
const var Label_MeterValue_R = Content.getComponent("Label_MeterValue_R");



// ------------

const var Pan = Content.getComponent("Pan");

const var SimpleGain1 = Synth.getEffect("SimpleGain1");

//Decay Rate
const var DECAY_RATE = 0.93;

//Current Values
var curLevelL = 0.0;
var curLevelR = 0.0;
var curLevelM = 0.0;

//Timer Callback
const var t = Engine.createTimerObject();

t.setTimerCallback(function()
{
//Synth Values
  var LevelL = SimpleGain1.getCurrentLevel(1);  
  var LevelR = SimpleGain1.getCurrentLevel(0);
  
//Peak Synth Values  
  var peakLevelL = Math.max(LevelL, LevelL);  
  var peakLevelR = Math.max(LevelR, LevelR);
  
  var peakLevelMax = Math.max(LevelL, LevelR);

//Kick Left  
//-----------------------------------------------------------------------------  
  if (peakLevelL > curLevelL)
    {
      curLevelL = peakLevelL;
    }
  else
    {
      curLevelL *= DECAY_RATE;
    }

//Kick Right  
//-----------------------------------------------------------------------------     
  if (peakLevelR > curLevelR)
    {
      curLevelR = peakLevelR;
    }
  else
    {
      curLevelR *= DECAY_RATE;
    }
    
//Kick Max peak for mono out or label with max peak for strongest channel.
//-----------------------------------------------------------------------------     
  if (peakLevelMax > curLevelM)
    {
      curLevelM = peakLevelMax;
    }
  else
    {
      curLevelM *= DECAY_RATE;
    }

  
//Decibel Conversion  
//-----------------------------------------------------------------------------   
  LevelL = Engine.getDecibelsForGainFactor(curLevelL);  
  LevelR = Engine.getDecibelsForGainFactor(curLevelR);
  var LevelMax = Engine.getDecibelsForGainFactor(curLevelM);
  
//Set Values  
//----------------------------------------------------------------------------
  LevelMeterL.setValue(LevelL);  
  LevelMeterR.setValue(LevelR);
  
  Label_MeterValue.set("text", (LevelMax >= -99) ? Math.round(LevelMax) : -100); // use Math.round (round up) for all except minimum value, -100. 
  Label_MeterValue_L.set("text", (LevelL >= -99) ? Math.round(LevelL) : -100);
  Label_MeterValue_R.set("text", (LevelR >= -99) ? Math.round(LevelR) : -100); 
  
});

t.startTimer(30);

UPDATE: this code does what it´s supposed to, but using labels to be updated by a timer seems to crash hise and the output plugins/standalone exported instruments. Read here about it.

@ustk said in How can show my image on hise?:

const var p = Content.createPath();

Looord, have mercy! Thank you for that line of code there. Riiiiight before the p.loadFromData, it was missing from the example in the docs in LookAndFeel, so I was chasing a ghost for around 2hrs. Hahaha.

Thanks. And for the SVG Path Converter to C++ info too, I thought the JS/HTML5/CSS3 paths looked a bit different

@Lunacy-Audio

Okay, 5 mins after, I solved this haha. Here´s how:

• Remove the paint routines inside of the:

laf.registerFunction("drawToggleButton", function(g, obj)
{

• then recompile all scripts / F5.
• then delete that code as well and this line: (or your equivalent)

const var laf = Engine.createGlobalScriptLookAndFeel();

• lastly recompile and save, exit HISE and start it again. Upon next start it´s gone. But that did not happen unless I did it in exactly that order.

@d-healey @lalalandsynth

Okay I got a little upgrade here with 6 linked buttons. It does what radio-buttons do. One turned on turns the others off. Also, no button can ever be turned off, if it is trying to set itself to 0, we simply switch it on again.

onInit callback:

• const var all elements
• set array with elements var names
• sync array with states in 0s and 1s in arr_buttons_sw.

const var Button1 = Content.getComponent("Button1");
const var Button2 = Content.getComponent("Button2");
const var Button3 = Content.getComponent("Button3");
const var Button4 = Content.getComponent("Button4");
const var Button5 = Content.getComponent("Button5");
const var Button6 = Content.getComponent("Button6");
const var arr_buttons = [Button1, Button2, Button3, Button4, Button5, Button6];
const var arr_buttons_sw = [
	
	[1, 0, 0, 0, 0, 0], // for button 1 [0], we set all else to 0.
	[0, 1, 0, 0, 0, 0], 
	[0, 0, 1, 0, 0, 0], 
	[0, 0, 0, 1, 0, 0], 
	[0, 0, 0, 0, 1, 0], 
	[0, 0, 0, 0, 0, 1] 
];

Then the onControl callback:

for (var i = 0; i < arr_buttons.length; i++) { // loop through the 6.

	// for any button matching one in array list.
	if (number == arr_buttons[i]) { 

		if (value == 1) {

			var btn_nr = arr_buttons.indexOf(number);

			for (var j = 0; j < arr_buttons.length; j++) { 

				// now setting the elements all in one go to their pre-set values in the arr_buttons_sw array number presets.
				arr_buttons[j].setValue(arr_buttons_sw[btn_nr][j]);

			}

		} else {

			// we dont want the value to be able to be set to 0, cause that´s not radio-style.
			number.setValue(1); // just set it back to one.

		}
		
	}

}

Here´s the new project in all its might:

radio-buttons-control-samplermaps-v2.zip

@lalalandsynth

Hey there, I played around with it a while and found a solution. It´s not @d-healey style, like looping through everything all efficient n stuff But it gets it done.

Note: I just made the basic Samplemap loading using Sampler.loadSamplerMap(), but did not make any actual radio buttons in the design, but I gathered you got that covered from Healey´s video.

// onInit

Content.makeFrontInterface(633, 400);

// store references to the samplers.
const var Sampler1 = Synth.getSampler("Sampler1");
const var Sampler2 = Synth.getSampler("Sampler2");
const var Sampler3 = Synth.getSampler("Sampler3");

// UI references
const var ComboBox1 = Content.getComponent("ComboBox1");
const var boxVals = ComboBox1.getAllProperties(); // just get all properties of the combobox element, for later reference.

// just printing all values of the combobox´s available properties:
for (var i = 0; i < boxVals.length; i++) {
    Console.print("ComboBox1:s element id " + i + ": " + boxVals[i]);
}


// get state of combobox, on init:
const var cboxState = ComboBox1.getValue();
Console.print("Current choice made in combobox: " + cboxState);



// onControl ui-control:

function onControl(number, value) // this needs to be copied into the onControl callback.
{
	
    if (number == ComboBox1)
    {
        Console.print("ComboBox1: " + value);
        if (value == 1)
        {
            // loading Samplemap nr 1 for all three.
            Sampler1.loadSampleMap("Samplemap-1-1"); 
            Sampler2.loadSampleMap("Samplemap-1-2");
            Sampler3.loadSampleMap("Samplemap-1-3");
        }
        if (value == 2)
        {
            Sampler1.loadSampleMap("Samplemap-2-1");
            Sampler2.loadSampleMap("Samplemap-2-2");
            Sampler3.loadSampleMap("Samplemap-2-3");
        }
        if (value == 3)
        {
            Sampler1.loadSampleMap("Samplemap-3-1");
            Sampler2.loadSampleMap("Samplemap-3-2");
            Sampler3.loadSampleMap("Samplemap-3-3");
        }
    }
}

Here´s an upload of the full project from my hise testing, so you can load it directly, with a single sample in the all the sample maps.

radio-buttons-control-samplermaps.zip

Made using Scriptnode branch (2020-08 ish), if that´s important. On macos.

SOLVED the issue, see last part, if you have the same issues.

@dustbro Thanks, I saw some of these, but I thought I´d add this anyway, since the issue has not made it into the documentation yet. It should be included in the documentation on the main github page since you cannot export your instruments without it.

@Christoph-Hart said in Sympathetic resonance for piano experiment:

Actually you‘ll get much better results for sympathetic resonance by using a convolution reverb with an impulse response of all strings resonating than by modelling the harmonics like this.

True story, I got that in a new Kontakt instrument coming up. The LivingRoom Upright Piano uses it for both pedal action controlled string resonances and body resonances, separately controllable. Not sure if it is more efficient too cpu-wise, but definitely more realistic and easy to make custom presets with multiple IR-samples depending on your preference. Also entirely based of the actual piano acoustics.

@Christoph-Hart said in Dynamically call Images instead ImageResources.dat:

Yes, use expansions for that. You don't want actual image files on an end user system.

How come? You mean for the ones that accidentally delete stuff? Or cause they have errors loading?

Wouldn't an image be able to be loaded just like a font is loaded? I got 3 different fonts for mac/Linux/Windows, works well.

@Christoph-Hart said in Sympathetic resonance for piano experiment:

Actually you‘ll get much better results for sympathetic resonance by using a convolution reverb with an impulse response of all strings resonating than by modelling the harmonics like this.

True story, I got that in a new Kontakt instrument coming up. The LivingRoom Upright Piano uses it for both pedal action controlled string resonances and body resonances, separately controllable. Not sure if it is more efficient too cpu-wise, but definitely more realistic and easy to make custom presets with multiple IR-samples depending on your preference. Also entirely based of the actual piano acoustics.

@yall ouch, okay. I missed that fact. Please let us know of the outcome of your tests.

@yall @d-healey

I would not build a VST for all the architectures of macOS with anything but X86_64 as the architecture flag in JUCE. If the newer architectures is to be used, make another separate .au for that. That way the newer architectures can have more optimizations. But I have not yet seen a HISE version with a compatible JUCE that handles ARM for macOS. That is only as I have seen it for Linux OS:es.

If you were to use an ARM based M1 mac, that should probably be set to Architecture = Native of Build System. But exporting and compiling directly form HISE is the mistake there, you have to stop the compiling in terminal (ctrl + c) and then open the exported .jucer file and modify, save and then run the .sh again when either having set Native or Standard X86_64 as the architecture. Or HISE will do whatever is default, which is unique to the OS and version of JUCE, as stated many times in the JUCE forums.

@yall hello there. While the problems can be many running on virtual machines as a concept, macOS is at least with the proper drivers on VMware pretty decent.

You probably have either an error or incompatibility between HISE and JUCE, or a HISE setting not correctly entered. Is the hise path correctly entered when you built HISE?

JUCE issues may be the thing here, where JUCE 5 does not support XCode 12. I have not tried Xcode past version 8.3.3.

Did the Apple engineer specify that you needed to use Big Sur at all? Or could you install the XCode Silicone additions or libraries on earlier versions? If so, the issues may only be the actual clang or c++ compiler flags and the necessary libs, not the actual OS, or even XCode. Ask him about that, and please get back to me, I want to support the Silicone M1 chips too.

@Christoph-Hart said in iPad Build:

Oh, I haven't build iOS for a long time

The library that powers SNEX (asmjit, a x86 assembly code generator) does not support ARM (also Apple prevents the execution of JIT compiled code on iOS anyway), so I need to make sure it's excluded from compilation if you try to export to iOS.

Is this supposed to function in Scriptnode 2020-08-20? I got an issue with ARM, like so:

In the details you can see:

And the folder /arm/armoperand.h is nowhere to be found on my system nor in the latest scriptnode in git:

Beside /core/, supposedly we should find the /arm/ folder. Is there a fix? I´m trying to export to an iPad Air (1st gen).

@Lindon said in MAC AUi Component build doesn't show in a DAW:

@nesta99 what David said.....
if you want your plugin to run on anyone else's machine you WILL have to do the notarizing...

Is that for macOS >10.14.x (Mojave)? Or for them all? And are we talking about the actual .component files or the installer package (.pkg)?

@Alex-Paradis said in MAC AUi Component build doesn't show in a DAW:

Thanks guy for the help!

I've tried multiple things on my MAC, removing caches and restarting, but still not showing :/.

User/system folders: (I´m sure you know this, but still) If you are trying to open au-plugins in the user/Library/Audio/components/ folder you won´t be able to. Logic only reads system folders. So HISE normally exports to a folder Logic cannot read from. Move the .component to Mac HD/Library/Audio/components/ instead, if you don´t normally.

@d-healey said in MAC AUi Component build doesn't show in a DAW:

@nesta99 Use xcode 10, don't build 32bit plugins.

What´s the lowest supported macOS version exportable in Xcode 10?

@d-healey Okay, thanks. Will probably be using lots of those then.