@ScreamingWaves I’m not at my computer to make an example or find helpful links, but there’s no need to code for this part. Just connecting the right nodes and assigning parameters.

@ScreamingWaves As soon as you want this kind of behaviour you need to switch to scriptnode networks. It'll allow you to do whatever routing you want using split containers for instance in your case
https://docs.hise.dev/scriptnode/list/container/split.html

@David-Healey far worse than all I imagined

@dannytaurus You could also invert your logic so !value actually means the panel is showing

@resonant you'll need to run your own algorithm. It's not too hard to make, go search google for something like phase meter algorithm or left-right correlation algorithm you should definitely find something. There are several ways for doing this depending on the complexity and the response needed.

@dannytaurus said in Multi-shape and multi-colour SVG:

Using the 'Base64 Path' mode expects filled paths only. Stroked paths are converted to fills and often look weird because the ends of the stroked path are considered to be joined as a fill.

Well it depends on how you create your SVG. If the origin is a stroke path then you need to draw in Hise, and if it's plain shape then you'll want to fill.

Both methods have their pros & cons.

• Base64 can have only one colour, but the colour can be dynamic
• SVGs can have multiple colours, but they are fixed (this answers @Chazrox as well). I also had bad experiences if your SVG has gradients, they don't translate well unfortunately.

In order to limit importation issues, I always save my SVGs as flat combined paths. (except if I need the SVG method in Hise of course...)

@Chazrox Ok I have not used it myself, so take what I will say cautiously as I might not really understand what it's been originally made for, so may someone correct me if I'm wrong...
A repitch algorithm is not meant to pitch up/down a signal in a timbre/formant preservation manner like standard pitch shifters.
It's more a samplerate converter that applies the new SR to what's inside and do the opposite at the output.
The use case is more for NN where the model has been trained for a specific SR, or convolution reverb, some distortion, any SR dependent algorithm, etc...
Most non SR dependent algorithm will see no changes.
It's not to be confused with a pitch shifter. I guess a better name would have been "resample"

@dannytaurus lol... The exact opposite for me because I learned mostly with Hise, so I'm lost everywhere else
I use GitHub Desktop. For conflicts it just tells you where the conflict appears so you can open the diff in whatever editor you like (from the app), make the changes and save. GitDesktop will then approve and authorise the merge (or the opposite)

I suspect changing min/max will cause issues when loading presets down the line...
In this case I would rather go with a panel instead so you can save the whole object (min, max, skew, value...)

EDIT: oh sorry, you're talking bout' scriptnode... Still I'll leave my comment in the case it helps someone with the same question for the UI..

@dannytaurus Or git

@13murderer Strange... Post a snippet or show the actual graph your building.

@NISHI_MUSIC The container you want is multi. It separates as many channels as you have at the input

@HaizalD3 Not harmful for sure... Or is it?
I can't help thinking this bot is bringing that bit more pollution to my brain that I'd preferably not to have... I for myself prefer reading real human beings

Always knew Hise was nothing but a superstition...

@JulesV Have you tried to delete the build folder?

@d-healey Came back after a refresh for me...

@Dominik-Mayer Hise icon disappeared... Intentional design?

@Chazrox I don’t see how this relates to the title but it usually happens when you reload a forum thread that has been deleted. Or maybe it’s not the same error message I don’t remember…
What did you do to get there at first?

@bwoogie I agree, it’s not intuitive and we all have habits that are adding to the confusion because by « save project » only people who know… are knowing… lol…

The project is the whole directory
By save project we mean save XML.
It’s not a good terminology though, because there is no file saved that are holding the project entirely. The XML is only the constitution of the module tree and the interface of your project. Files likes images, samples, etc… are not saved, they are just permanently lying in the project directory and there is no "global project file" holding them.

And you’re right, archives are "project’s presets", being autosaved or manually saved.

I don’t know if people out there are using manual preset (archive) save. Except for quickly sketching something, I personally don’t get the point.

The things you should then focus on are saving the project XML, and set the autosave just in case something bad happens. You shouldn’t need to save an archive manually (cmd/ctrl+s) but instead just use cmd/ctrl+Shift+s and you’ll be good.

Everyone has been confused by all those strange naming at one time, and as @d-healey said, the concept of project preset (archive) vs user preset adds another layer of confusion…

Something worth adding, no matter how cautious you are handling your project, nothing will be safer than using git