AudioLoopPlayer load

[d.healey]

@MikeB Which part are you stuck at?

[MikeB]

@d-healey Folders and samples have names of different lengths. How can I separate them with string?
Besides, the user should not get a hi-hat sound if he has selected kick.
But only the samples from the Kick folder.

[d.healey]

@MikeB

If you have a string like const s = "{PROJECT_FOLDER}Kick/sample12.wav"

You can get the folder with const ss = s.substring(s.indexOf("}") + 1, s.indexOf("/"));

Ready for an hour of trial and error ;)

[Natan]

@MikeB Are you going to Include The Audiofiles into Dll?
Or ship With Zip File?

[Natan]

Beaware!

This, Engine.loadAudioFilesIntoPool();
And include Audio Files in resources Will Add Weight to Your Components, Dll, Vst3 Files.
And You easily Will get Out Of Heap error.

[d.healey]

@Natan I think you can ship the audio files as a separate data file.

[MikeB]

@d-healey @Natan
I have asked several times in this forum whether the audio files for the AudioLoopPlayer can be installed separately and - more importantly - whether they are protected.

Both were answered with no.

Above all, there is no protection such as Monolith for samples used in the AudioLoopPlayer. - Or?

[d.healey]

@MikeB said in AudioLoopPlayer load:

there is no protection such as Monolith for samples

Monolith isn't "protection" it's compression. HISE is open source, it wouldn't take an experienced programmer very long to reverse the compression.

But yes it is possible to ship asset files as a separate data file

Export Pooled Files to Binary Resource
Will collect all pooled Audio-, Image-, MIDI files and SampleMaps and save them as .dat files in a newly created PooledResources folder in your project.

[MikeB]

@d-healey
I'll leave it David. It's not enough for you to throw me little nibbles and then smugly say - now try a few hours.
I know you mean well - but sorry

[MikeB]

@d-healey
I know that Monolith is not a protection - but a big obstacle against the use of the samples by the normal user - or

Since it is not possible to protect the samples for the AudioLooPlayer against further use the only possibility at the moment is
is to embed them.

[d.healey]

@MikeB Well the audio files will be put into a .dat file, which I think is similar to a monolith. I could be wrong though.

[MikeB]

@d-healey
Where and when are the audio files inserted into a dat.file????
Is there a description?

[d.healey]

It's in the export menu, this is all it says in the docs:

Export Pooled Files to Binary Resource
Will collect all pooled Audio-, Image-, MIDI files and SampleMaps and save them as .dat files in a newly created PooledResources folder in your project.

HISE | HISE | Export Menu

The reference for the export menu in HISE.

(docs.hise.audio)

[d.healey]

@MikeB said in AudioLoopPlayer load:

It's not enough for you to throw me little nibbles

Which part do you need? We've figured out how to get an array of audio file names, I've shown you how to use string functions to get the folders from those names, and you can use the same string functions with a slight adjustment to get the file names.

[MikeB]

@d-healey

This is my status
in reg myList are 500 samples in this form

"{PROJECT_FOLDER}Kick/Dumpy.wav",
"{PROJECT_FOLDER}Snare/Dryer.wav",
"{PROJECT_FOLDER}Perc/Bongos.wav", etc.

reg myList = Engine.loadAudioFilesIntoPool();
Console.print(trace(myList));

const ss = myList.substring(s.indexOf("}") + 1, s.indexOf("/"));

Knob 1 - Select Folder 
Synth.getAudioSampleProcessor("Audio Loop Player_S1").setFile

Knob 2 - Select Sample
Synth.getAudioSampleProcessor("Audio Loop Player_S1").setFile

[d.healey]

@MikeB

You need to create two new arrays. One for the folder, and one for the sample.

Then you loop through the master array (myList). And using the string functions you extrac the folder and push it to the folder array and you extract the file name and put it to the sample array. Then the rest of your code is just like you were doing before with your two handwritten arrays.

[MikeB]

@d-healey let it go - I don't understand you!!!!

[MikeB]

Although my samples have 40 MB at the moment (not yet cleaned up) and 4 MB images, the compiled VSTi plug-in has a whopping 146 MB.

[MikeB]

@d-healey I can adapt what I have seen - I am a graphic designer - I see things and try to understand and adapt them.

I can't do much with text creaming of complex programming processes. Since I can't find the beginning.

I need to see examples - see the code then I can understand ahhh this is how it's meant to be or ohh this is easy.

That's why 5 lines of code are more useful than page-long descriptions of what to do.

I'm about to throw everything away after 7 months anyway.
Every day the same sh... I can't do that. The programme crashes all the time. You first have to write a script for this.
You can't write a script for this - because the function doesn't exist. (AudioWaveForm Start/End) etc.

No sooner have you spent 5 hours solving a simple pipifax problem than the next one comes along the next day.

Actually, I only wanted to create a small drum plug-in.

[d.healey]

@MikeB I try to design around the features that are available then I don't hit limits so often, of course sometimes I want new things, then I nag Christoph :)