it's awsum, but if u could do the same for pcm that would be great, one question what's program standing for??
Greetz
Jano
PAL File Viewer - New Version now available
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Hi there,
How do you mean do same for pcm? can you explain further?
Prior to the PA1X, sounds were called programs, from the next version on, this will change to reflect the model of keyboard you are creating files for ie for a PA50/60/80 it will say "Programs", and for the rest it will say "Sounds"
How do you mean do same for pcm? can you explain further?
Prior to the PA1X, sounds were called programs, from the next version on, this will change to reflect the model of keyboard you are creating files for ie for a PA50/60/80 it will say "Programs", and for the rest it will say "Sounds"
hi
What I mean is if you open a set you'll fiend global multismp pad pcm performance sound style, now with pal file viewer you can check out the names of styles and sounds, but what about the pcm, if you open pcm you'll fiend pcm 1, pcm 2 ...., it would be great if you could fiend out what's the name of the pcm, that way you can remove unnecessary pcm and save space on your ram memory.
Greetz
Jano
What I mean is if you open a set you'll fiend global multismp pad pcm performance sound style, now with pal file viewer you can check out the names of styles and sounds, but what about the pcm, if you open pcm you'll fiend pcm 1, pcm 2 ...., it would be great if you could fiend out what's the name of the pcm, that way you can remove unnecessary pcm and save space on your ram memory.
Greetz
Jano
Thats a very interesting proposal, however to delete some pcm data would be, i think, dangerous as it would break up the integrity of your user multisamples.
For example, looking into the pcm files for the Grand Touch Piano Set available from the korgpa website, the samples are listed as GrandPianoL1, GrandPianoL2, FXKeyOffL1 etc. The RAM.KMP file contained in the MULTISMP folder relies heavily on these sample files. by having the facility of deleting pcm it is possible that the wrong samples could be deleted and then this could cause the keyboard to malfunction
For example, looking into the pcm files for the Grand Touch Piano Set available from the korgpa website, the samples are listed as GrandPianoL1, GrandPianoL2, FXKeyOffL1 etc. The RAM.KMP file contained in the MULTISMP folder relies heavily on these sample files. by having the facility of deleting pcm it is possible that the wrong samples could be deleted and then this could cause the keyboard to malfunction