@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.

@d-healey said in HISE Script Coding Standards:

@ulrik I think Christoph explained it well here - https://docs.hise.audio/scripting/scripting-api/midilist/index.html

Question for @d-healey and @Christoph-Hart : Can a MidiList array store multiple dimensions of data? Like a multi-dimensional array?

I ask cause an important KSP script I am trying to recreate use a polyphony script containing 128x4 values that look for amounts of current equal note hits. Would I be able to nest midi-lists in a normal array? Or do they come with multi-depth features?

Additional question. Is there a performance overhead using MidiLists over a normal array/nested arrays when accessing specific / one-time data, not looped, but like this: var get_my_value = my_array[0][3] ? Or is the performance in the iteration?

Sorry, my bad. The issue I had was about another property, namely the fontSize property of the labels, that was with initial capitalized F, as FontSize in tiles.

@Christoph-Hart Perhaps a good change for HISE 3.0? Move those to all-the-same across all object types.

Anyways, solved.

I am trying to update my fonts using:

my_label.set("fontName", "my-font"); // works fine for labels using 'fontName' property.

But when I try Font property on tiles, like so: my_tile.set("Font", "Arial") it gives an error message:
:! the property does not exist

I tried using fontName for tiles, but they give error messages too. I actually get the result I want, I think, at least it seems so. Perhaps the issue is just the error message api?

(macos, scriptnode branch 2020-08-20)

@d-healey It defines certain stuff better and looks nice and distinct. Crossing languages often tends to make me a bit confused and cautious, since some (KSP for ex.) languages reserve upper case vars. Not sure about normal JS though. Does hise interpreter/C++ side use this that could cause conflicts? Anyway, could get over the cautiousness for that distinct look. It definitely pops out at you in a dense script.

@d-healey aaaaaash, looked so neat.