The sampler goes crazy with monolith

[bendurso]

@ulrik Thanks for checking :) Yeah, I just converted it to wav using the SaveMode=1 and the error was gone.

[bendurso]

@d-healey

Now I included the samples of the samplemap Nomad Strings. I re-enconde it again, and now the error it's on E3

Dropbox - File Deleted - Simplify your life

(www.dropbox.com)

[d.healey]

I just noticed in your sample map that all the files have absolute paths instead of relative paths (were your samples not in the project's Samples folder when you mapped them?). This could be the cause of the issue.

[d.healey]

I tested with the wav samples you sent. With your monolith I was able to trigger the issue on C2. When I rewrote the sample map to remove the absolute path and then recreated the monolith on my system I was unable to trigger the issue.

[bendurso]

@d-healey said in The sampler goes crazy with monolith:

I just noticed in your sample map that all the files have absolute paths instead of relative paths (were your samples not in the project's Samples folder when you mapped them?). This could be the cause of the issue.

Yes, I used samples outside of the project folder. That could be the issue?

@d-healey said in The sampler goes crazy with monolith:

When I rewrote the sample map to remove the absolute path and then recreated the monolith on my system I was unable to trigger the issue.

Did you do it with "Reencode HLAC monolith" or "reeconde all samplemaps as HLAC monolith"? Because I remember that when I used the individual reencode it worked fine, but when using all samplemaps function it caused the problem.

[d.healey]

@bendurso said in The sampler goes crazy with monolith:

Yes, I used samples outside of the project folder. That could be the issue?

Samples should always go in the project's samples folder, or (I think) you can link to them with a LinkOS file, but the cleanest solution is to put them in the project and then in the sample map use the {PROJECT_FOLDER} wildcard - that will be used automatically if the samples are in the project folder when initially mapped.

@bendurso said in The sampler goes crazy with monolith:

Did you do it with "Reencode HLAC monolith"

I clicked this:

[bendurso]

@d-healey said in The sampler goes crazy with monolith:

Samples should always go in the project's samples folder, or (I think) you can link to them with a LinkOS file, but the cleanest solution is to put them in the project and then in the sample map use the {PROJECT_FOLDER} wildcard - that will be used automatically if the samples are in the project folder when initially mapped.

Oh, I understand that, but since I only use monolith files, I typically access the wav samples directly from other folders and then convert them to monolith.

@d-healey said in The sampler goes crazy with monolith:

I clicked this:

I just tried it, and the problem doesn’t occur when using the individual conversion function. However, when using the "convert all sample maps" function, the issue arises, even if the samples are within the project.

[d.healey]

@bendurso said in The sampler goes crazy with monolith:

Oh, I understand that, but since I only use monolith files, I typically access the wav samples directly from other folders and then convert them to monolith.

We all use monoliths for final delivery. But your sample maps will be messed up with the absolute paths.

@bendurso said in The sampler goes crazy with monolith:

I just tried it, and the problem doesn’t occur when using the individual conversion function. However, when using the "convert all sample maps" function, the issue arises, even if the samples are within the project.

I'll give it a try tomorrow.

[bendurso]

@d-healey said in The sampler goes crazy with monolith:

We all use monoliths for final delivery. But your sample maps will be messed up with the absolute paths.

Oh didn't know that, thanks

@d-healey said in The sampler goes crazy with monolith:

I'll give it a try tomorrow.

Nice thanks :)

[Lindon]

@bendurso said in The sampler goes crazy with monolith:

@d-healey said in The sampler goes crazy with monolith:

Samples should always go in the project's samples folder, or (I think) you can link to them with a LinkOS file, but the cleanest solution is to put them in the project and then in the sample map use the {PROJECT_FOLDER} wildcard - that will be used automatically if the samples are in the project folder when initially mapped.

Oh, I understand that, but since I only use monolith files, I typically access the wav samples directly from other folders and then convert them to monolith.

Bad idea I think.
Do this:

1. Move all your relevant wav files to the Samples Folder
2. Build your SampleMap
3. encode your sample map to ch1 file (the down arrow David pointed at) - at this point you can remove the wav files from the samples folder...
4. When the entire project is done-finished-complete only then build your .hr monolith files...

[d.healey]

@bendurso No issue here when using the reencode all sample maps option - after I edited the sample map to remove the absolute path.

[bendurso]

@Lindon Yes thanks, didn't know it could cause trouble using absolute paths.

@d-healey said in The sampler goes crazy with monolith:

No issue here when using the reencode all sample maps option - after I edited the sample map to remove the absolute path.

I checked again and you're right, no problem with relative paths. Now I have to remake all my samplemaps :(

Thanks guys :)

[d.healey]

@bendurso said in The sampler goes crazy with monolith:

Now I have to remake all my samplemap

Or do what I do and open them in a text editor and use find/replace.

[bendurso]

@d-healey That's a nice one, could save a bit of job, thanks :)

[d.healey]

@bendurso If you use a text editor that can replace text in multiple files at once it might be a very quick job.

[bendurso]

@d-healey I usually use Visual Studio Code and it works really well, but in this case I have multiple folders, and I have to check one by one to match the correct folder