@ustk said in Automation subfolders in DAW:

should be written automationId

That lowercase d still gets me LITERALLY EVERY TIME

@Orvillain Yep, that's on the list for a Plus version of the plugin. This is the trimmed-down free version.

Although I have no idea yet how to use a wavetable as an LFO. Fun future project!

@ulrik Or use regex to detect strings that only contains digits.

const var strings = ["brass", "001", "127", "flute"];

for (s in strings)
{
  if (Engine.matchesRegex(s, "^\\d+$")) Console.print(parseInt(s));
}

^ means 'start of string'
\\d means digit
+ means 'one or more'
$ means 'end of string`

So, "one or more digits between the start and end of the string, and nothing else"

@David-Healey @Christoph-Hart @HISEnberg I think whatever regex magic and tree-following voodoo is in the script, there will be some user somewhere who loses all their work because of their weird setup.

Maybe instead of actually deleting the detected HISE folders, the script should just alert the user of potential issues?

@David-Healey Is there a GitHub issue?

@markothemixer When exactly does HISE crash?

1. When you add the floating tile to the Interface Builder, or
2. When you change the ContentType of the floating tile to Waveform, or
3. When you change the ProcessorId in the Data panel to the processor ID of the waveform module you want to visualise, or
4. All of the above work, but HISE crashes at some point later, like re-compiling or a reload of the XML

@griffinboy said in UI feedback on tiny control:

See how tiny the Ableton dropdown selection boxes and multiple choice buttons are in the background?

Very good point! I've always disliked the Ableton UI for that reason but the point is, that's what folks will be used to I guess.

@ustk said in UI feedback on tiny control:

Could also be a 3 pos knob

Yeah, I tried a 3-pos knob but since all the other knobs are continuous, having one that only has 3 positions feels a bit weird. Especially since I don't want to put markers around that one knob to denote the positions.

@David-Healey said in UI feedback on tiny control:

Looks fine sublime to me

Very good!

Yeah, I thought about a combo box but that's essentially what this already is - an 'always open' combo box.

Does the Wave sector in the Motion section look too small and fiddly?

Each wave is a fairly small hit target of 44x14.

Any other ideas for choosing between 3 waves in that control area?

@Christoph-Hart said in Export Setup Wizard Problems:

I'm also thinking about a "Nuke HISE" tool

Definitely, although it won't help users who have multiple copies of the source on their machine.

@David-Healey said in Export Setup Wizard Problems:

then you'd build HISE and your projects with whichever one your project requires.

So does that complicate the setup script? Or would it just install both?

@Christoph-Hart said in Export Setup Wizard Problems:

Why? It's only building HISE, not your projects.

I thought you have to build HISE with FFTW instead of IPP on Windows when you're making closed-source.

I haven't started on the Windows side yet so I've probably got that mixed up.

So does IPP/FFTW only come into play when building the actual plugin?

@Christoph-Hart Since we've already chosen a platform at the top of the page, the C++ Compiler section could be simplified to just show the compiler for our platform.

@Christoph-Hart Tiny UX thing but maybe change "Apple Silicon (M1/M2/M3)" to something like "Apple Silicon (M1 and later)" or "Apple Silicon (M-series)".

M4 and M5 are already out and folks with newer machines might still head to the forum and ask if their chip is supported.

Everyone likes to be a special case

@Christoph-Hart Maybe the script should know if we're building open or closed source projects?

@Christoph-Hart said in Export Setup Wizard Problems:

So basically what I want is to let the user tick which components he has already installed so that the script can skip that

maybe the script should handle figuring out what's installed instead of trusting the user?

@David-Healey said in Preset browser selection reset on project load:

The same thing happens when reopening a DAW session with the plugin loaded.

Wait... so what happens in the DAW? Obviously hitting compile isn't part of the flow here, so what's the confusing part for the users?

Glad to hear about this now before I release a plugin. Hopefully we can sort it!

@David-Healey said in Export Setup Wizard Problems:

Was it an Apple silicon system? That might be the difference.

Yeah, it was an M1 MacBook Air. It was a really nice machine, and everything else worked fine. I could run large Logic projects, have loads of running apps, multiple Safari windows, etc.

It was just compiling HISE where it completely fell down.

@David-Healey said in Export Setup Wizard Problems:

Something wrong there, I compile on a VM with less.

Yep, definitely something wrong. Could be the way macOS handles RAM. Could have been something else on my system.

I bought a 32GB MacBook Air and it flies now, so I don't care what was causing it.