Monolith encodes to tiny empty files
- 
 I couldn't find another thread with the same issue. I clicked through all my samplers and saved as monolith. I have 4GB of wav samples in 48k 24, but the monoliths are only a few kB each. Their size appears to be a fraction of the expected size, maps with few samples become monoliths that are only a few kB big. I saved all of them with per-sample normalization and max archive size of 2GB. 
- 
 @Simon Are you samples in the project's Samples folder? 
- 
 @d-healey Yep. It seems to be caused by enabling normalization. With "No normalization" the monoliths are written correctly. 
- 
 @Simon You're referring to the normalisation in the compress to monolith popup? Are you using this button to create the monoliths?  
- 
 @d-healey Yes and yes 
- 
 @Simon Make a test project with one sample, see if works, if it doesn't send me the project. I haven't ran into any issues here and I always enable the full dynamics option. 
- 
 @d-healey Full dynamics works, only "Normalize every sample" makes the small monoliths. I guess there's no reason not to use Full Dynamics since they're 24 bit samples anyway so I'll just do that for now. 
- 
 @Simon Oh I see, I didn't even read those options properly. Yeah I always just go with full dynamics but I guess if you can recreate this in a simple example you should report it on github. 
- 
 @d-healey Totally unrelated question Dave - can you symlink the Samples folder??? 
- 
 @Orvillain Haven't tried, but I wouldn't recommend it, you should either keep everything in the project folder, or if you really don't want to you should use the built in redirect.  
- 
 @d-healey Gotcha! 


