@ustk Thank you 😄

@dustbro thank you!

Nah I don‘t do ETAs no more ;)

Yeah I noticed that too.

I don't see any errors.
If I start a new project, create a couple lines of code, and then Highlight -> Move selection to external file, nothing happens.

@d-healey @hisefilo @ustk Does this issue persist to this day?? :/

@Christoph-Hart Thank you .
It's Good to know .

Have a search on the forum and you will see everyone has asked this question at some point :)

The answer is there is no default preset, or way to load a default preset. What you need to do is save/export the preset in the state you want it to be in when the user first opens it. So load a preset, save, export, and that is the preset that the user should get when they first load, although it's not always as simple as that.

@Lunacy-Audio That's exactly the solution I've come to as well :)

I noticed this as well

@MacroMachines The current version of scriptnode is known to be very unstable in many ways...
Sometimes your swear it's because of this or that, then suddenly it works. And sometimes everything's fine until it decides to crash no matter you restart or not...
I have a serious project made around scriptnode, but it is too buggy for a release.
I'm waiting for v3 (which is under development) to benefit from the novelties, hoping for a stable version.
Until then, no release, no income... ☹

Yeah, I added this after the note-number modulator which is what you might expect to do the job due to the name...

@Lindon thanx!

Just testing the harmonic filter, silence here as well.

@ustk When a sliderpack is linked to an arpeggiator, HISE prevents you from changing the maximum value of the sliderpack in both the IDE and scripting. If you try to change any of the default properties, it will automatically set them back to the defaults.

Unable to change sliderpack props.gif

It seems like this may have been intentional in order to prevent the user from accidentally setting the arp values to something other than what they should be. However, it becomes an issue when the arp values themselves can cause bugs, like the issue @Alex-Paradis described above.

@dustbro Send them a debug build and the next crash dump might provide more useful info.

@mwplugs This is worrisome, I am working on an Impulse Reverb I was planning on releasing .
I havent tested sample rates but I seem to have one impulse not showing up in the exported plugin, works fine in HISE , will have to test further. When the impulse does not load/work the plugin goes silent.

Most of my impulses are pretty short as I need a lot of them , concerned that they will not load.

I just checked, the impulse that will not load in an exported plug is 881 kb , the other ones that are about 3 mb will load.
Doing some more testing.

I am also getting ticks , when moving the pre delay setting in an exported plugin , any way to fix that ?

@dustbro Since I don't have the filmstrip, I commented out the 3 associated lines, and magically the component appears to be correct.
If I uncomment the lines, the issue comes back...

@Lindon said in macOS Catalina AUi not compiling properly... but VST3 + AAX working:

if you are on Catalina and XCode 11

Also note, this happens on xcode 10