Batch, save samplemap as monolith?

[d.healey]

Right click in the sample mapping window, go to tools >> (Re)encode all sample maps as HLAC monolith. There is also an option in the main tools menu to Convert all samples to monolith + sample map. I'm not sure what the difference is between these two options but I've always used the first one.

[Lindon]

@d-healey sigh tried it and every singel one of my 300+ sample maps returens this:

FireWalker02:! Error at loading sample ChvalrousHandgun.ch1: File is corrupt

but every one of them loads perfectly and plays perfectly...

interestingly tho a ch1 file (with something in it ) was created for each one...

[d.healey]

@Lindon Looks like I had that problem too

https://forum.hise.audio/topic/1368/bug-re-encode-monolith-wipes-sample-map

And so did someone else last year

https://forum.hise.audio/topic/815/samplemap-file-error

But my latest projects work so I have no idea what I did to fix it. I'll see if I can figure it out.

[Lindon]

@d-healey yeah it also finishes and tells me it was all successful...

If I re-do then all these errors disappear (well they are not reported again -----....hmm not sure what to think.

[d.healey]

@Lindon Did it work when you do it the second time? You can check by renaming the folder containing your wav files and see if your project still loads the samples.

[Lindon]

@d-healey er well ..er...

the wav files are all in teh Samples Folder, where all the ch1 files are too... ahng on I'll just move all teh wav files out....

[Lindon]

@d-healey -- phew, yep all working without the wav files in place - so those seem to have been "erroneous error messages"

The sample maps area is still pretty fragile I think.

[d.healey]

@Lindon Yeah it's definitely rough around the edges, glad we have a workaround though :)

[Lindon]

@d-healey workaround! is that what we are calling it...? LOL

[Tod Slaughter]

Do you guys know what happens when the original samples are moved to a different location after building a monolith?

I'm getting some weird behaviour

[d.healey]

@Tod-Slaughter Nothing "should" happen... but sample maps in HISE often display buggy behaviour, it could be in your case that the save mode hasn't updated. Open the sample map in a text editor and check it, the save mode should be 2 when using monoliths.

[Tod Slaughter]

The save mode is 2 but the filename references the original sample location. It seems I'm going to have to rebuild all my samplemaps where I've moved the samples to another disk after creating the monolith.

[d.healey]

@Tod-Slaughter Do the file paths start with {PROJECT_FOLDER} ?

[Tod Slaughter]

@d-healey No they start with the original disk i.e. C:\blah\blah

[d.healey]

@Tod-Slaughter If you open each sample map in a text editor you should be able to use find/replace to set the paths correctly to the HISE project folder. If you use an editor like Atom, Cuda text, or Sublime text then you can do this for a whole folder of sample maps at once.

[Tod Slaughter]

@d-healey How is this happening? Am I using the wrong tool to save the monolith?

[Tod Slaughter]

I'm right clicking and using the save as > convert to monolith

[d.healey]

@Tod-Slaughter Where are your samples stored?

[Tod Slaughter]

@d-healey I have been editing them to the desktop, creating the monolith in my project folder and then moving the original files to external drive.

You're saying I should move them to the project directory first

[d.healey]

@Tod-Slaughter Yes, for the smoothest ride your samples should go in the Project's samples folder. If you want to work with them in another directory though you need to go to the project preferences and set the Redirect Sample Folder path.