KORGPAManager.com

Merging 2 sets in pa5x results in completely removing ram.kmp. I have tried twice to recreate the same problem, and its definitely there.
Destination set for some reason does not have any more ram.kpm, and PA Manager starts throwing all kinds of errors about missing .pcm samples during save.

This is the exact procedure. Load destination set, load source set. Copy user sound from source set (with samples). Decompress samples in destination set. Save everything, and this is the part where ram.kpm magically disappears.

Hi,

Receiving errors about missing PCM samples surely doesn't sound ok.
Is this during Loading a SET or whilst SAVING ? (Presumably during saving)
Have you MOVED/Renamed any of the source SET/KST folders whilst saving? hence why KPM can no longer find the missing PCMs ?

Also, the flow of events, doesn't seem to quite add up.
You mentioned that you Load the DESTINATION SET >> Load the Source SET >>> Copy user Sounds >>>>>>> Decompress.
Before you decompress, you would have had to SAVE out the SET, load it in to the SAMPLE Manager to DECOMPRESS....
Is the RAM.KMP file there prior to decompressing the SET ?

If you can replicate the issue with RAM.KMP not saving out, perhaps it would be best to send us the SET/s in question (via email) so that we can try and replicate the issue here locally.

This happens only during saving. Yes there is a remap process before that, but the set is previously saved. I have tried few different sets, so they are not the problem . I will try one more approach, to completely unload newly modified set before decompressing, and see if that makes a difference.

any update on this ?

Admin wrote: ↑22 Dec 2024, 12:38any update on this ?

Yes, it looks like if you try to do all at once: Move samples from one set to another, and remap, and try to save it will delete RAM.KMP during final save. The workaround is to save set after each process. Remap save. Move samples save.

Actually, the reMapping has no relation with the creation of RAM.KMP.
So it seems, something else that's causing it not to write the file.

If there is a way to be able to REPLICATE it every time, then please let us know so that we can try and follow the exact steps. But most likely it's SET related, so we would need those SETs and precise steps to be able to track it down.