Imported user samples in Audio Loop Player are not saved in the preset

[Xearox73]

@d-healey

Just by the way
is there actually a way to display an editable info panel for each preset
where the user can also enter his information?

[Xearox73]

@d-healey

with over 5200 lines, troubleshooting is a little complicated
but i think i have it why i need both
i set
"const irs = Engine.loadAudioFilesIntoPool();"
to
"// const irs = Engine.loadAudioFilesIntoPool();"
and .....

for (x in irs)
LoadIR.addItem(x.replace("{PROJECT_FOLDER}").replace(".wav", " (IR by ZIA)").replace("VINYL.flac").replace(".flac"));

shows:
! Line 38, column 14: no iterable type
and the ComboBox is empty

[Xearox73]

@d-healey

somehow it seems as if the one doesn't want the other as soon as i set a specific filter like
for (x in irs)
LoadIR.addItem(x.replace("{PROJECT_FOLDER}")

[d.healey]

@Xearox73 said in Imported user samples in Audio Loop Player are not saved in the preset:

@d-healey

Just by the way
is there actually a way to display an editable info panel for each preset
where the user can also enter his information?

There is a note box in the preset browser which you can enable. I haven't used it though so I'm not sure how useful it is.

By the way, if you use code tags (3 back ticks) when posting code it will format it nicely. You can also use this button in the toolbar:

@Xearox73 said in Imported user samples in Audio Loop Player are not saved in the preset:

but i think i have it why i need both
i set
"const irs = Engine.loadAudioFilesIntoPool();"
to
"// const irs = Engine.loadAudioFilesIntoPool();"
and .....

Yes that's because you need to populate your irs array. It's the other call to this function that you don't need.

@Xearox73 said in Imported user samples in Audio Loop Player are not saved in the preset:

with over 5200 lines, troubleshooting is a little complicated

I think your code could use some structural changes to make it easier to manage.

[Xearox73]

@d-healey

you need to populate your irs array
like ....
const itemList = ["IR1",
"IR2,];
and so on?

[d.healey]

@Xearox73

const irs = Engine.loadAudioFilesIntoPool(); this line is what is creating and populating your array, so you need this line.

What you don't need is any other call to Engine.loadAudioFilesIntoPool()

[Xearox73]

@d-healey said in Imported user samples in Audio Loop Player are not saved in the preset:

I think your code could use some structural changes to make it easier to manage.

4 Synth Groups with wavetable synth, modulation for wavetables, unison and detune, 2 filters and 4 modulators, eq, delay and arp for each!!!
1 sub osc - the same
4 sample slots with filter`s and 3 modulators, eq and arp for each!
synced delay and filter knobs for hz and tempo
linked and unlinked controlls
9 saturation fx slots, 4 fx send with mods
master section to controll everything under the hood with every knob in sync in realtime
over 42 synced knobs and functions on different panels
tons of filmstrips, over 300 wavetables in lists and so on
hmmmmmm, the code ist currently not yet adjusted
i thik 5000 is ok

[d.healey]

@Xearox73 said in Imported user samples in Audio Loop Player are not saved in the preset:

i thik 5000 is ok

Maybe, but is it all in one file?

[Xearox73]

@d-healey

try it
any solution that reduces the size of the monster is fine with me

[Xearox73]

@d-healey said in Imported user samples in Audio Loop Player are not saved in the preset:

Maybe, but is it all in one file?

almost everything, except for a few scripts
I have already included them

after the first tests the monster runs absolutely stable
over 16 instances are no problem and the vst3 has a little over 100mb
tested on 2 workstations and one laptop and 4 daws with no problems

[d.healey]

@Xearox73 said in Imported user samples in Audio Loop Player are not saved in the preset:

almost everything, except for a few scripts
any solution that reduces the size of the monster is fine with me

The size isn't the necessarily the problem, 5000 lines it not a lot for a large project (although it doesn't hurt to reduce it). It's the organisation of the scripts that is important though.

Having one large script makes it difficult to debug issues. Try to break your script into smaller scripts. I find mine rarely exceed about 500 lines each.

Check out the scripts for Rhapsody as an example - https://codeberg.org/LibreWave/Rhapsody/src/branch/main/Scripts

Doing this makes it very simple to find out which part of your script is causing problems.

[Xearox73]

@d-healey

I still have something to learn
I started with HISE in february with zero knowledge
I am a musician and not a programmer but willing to learn.
I know about GUI design and how to build buttons or knobs, but programming is completely new territory for me.
I just wanted to build something that I was missing somewhere else.
When you're over 50, some things are simply more difficult, especially when it comes to something completely new.
However, I am very happy about the helpfulness in this forum, which is not the case everywhere.
Therefore, I apologize for a few stupid questions that are sure to come