@d-healey You still have a few weeks/months :-)

I recently read that an AI has been put on all the music on the internet. So on tens of billions of songs.
The task is to disassemble and separate them into their components - to see/hear and learn the STEMS of each piece of music.

The goal is to get the following via text input:

Play me a guitar solo in Cmin in the style of "Samba pa ti" and "comfortably numb" with the guitar of Jimmy Hendrix.

Out comes a melody as a sample that is copyright free to use.

So I can (I do not - because with me the way (the play) is the goal) but all unmusical people times quickly create a supposedly own song without much effort.

I could also then enter: Give me the samples from C1 to C4 of Mark Knopfler's favorite guitar.

And already I have a samples library.

Synth GPT is here - it will sample any sound you want.
Well friends this seems to be the beginning of the end :-))

@d-healey Isn't Rubberband free for the time being under GNU General Public License - as long as no commercial applications are created?

Will there be a timestretching/pitchshifting function in HISE at some point?

Great work David. It's nice to hear you play something.

@DanH super - thank you.

@DanH ? tell me more

Is it possible to recognise the pitch of an imported sample in HISE and change it if necessary?

@trillbilly Sorry - I'm not at the computer.
But I was referring to a video by David on the subject of presets and preset storage. Have a look at YouTube or his Patreon. Or just ask him.

@trillbilly

There are plug-ins that ask with every small change of a parameter during a preset change whether the change should be saved.

And

There are plug-ins that do not do this.

Personally, I prefer the latter.
There's nothing I hate more than when a pop-up constantly pops up when I'm trying to find a sound (preset changes and cutoff changes, for example).

If I consciously make a change and want to save the preset - then I save it.

My opinion :-)

Fortunately, of the hundreds of plug-ins I have, very few do this.

Technically, this can certainly be implemented in HISE.
Perhaps a selection option for the user would be good.

@orange That works - thank you

@d-healey No - I don't want to use your UI. I just wanted to understand the function.
I understand the principle of how it works.
Do you have a current snippet?

@d-healey Thanks Dave - but unfortunately I can't get your script to work!

No error is reported - it just does nothing.

A video?

@ustk I already do that - always, but as you said, only the content of the .js file can be transferred, not the elements used in the file.

However, if I could insert a snippet into my project in its own namespace* "Snippet", for example, it would save a lot of time.

*Of course, any similarities in the names of variables or elements would have to be ensured by encapsulating the code used.

it is possible to add a HISE snippet to an existing project instead of replacing it.

This way you can simply extend your existing project with prepared elements in the form of snippets.

If no, wouldn't that be a useful addition?

@d-healey You already said that above.
But it should do the following.

Randomise the random area of the slider pack or the individual sliders exactly between the values defined in an array.

So if the array contains [0, 2, 3, 5, 7, 8, 10, 12 ], no slider in the slider pack may have the value 4 or 6 or 9 etc. when the Random button is clicked.

Instead, only a random within the defined values.

This way you can make the Arp randomise within a defined key.

@d-healey So that DanH's snippet above works!

@d-healey What would be the right approach here?

@ulrik
You are the only one here who asks questions here and then answers them straight away - amazing - Happy New Year Ulrik. :-)

A good, beautiful and successful year to all of you.