Changing sets and sample deleting q?

[BasariStudios]

Ahhh Aky...that jelaousy...not a good thing huh? Even in God's words is a Sin. Eats you inside...

[jerrythek]

The question is how do you know what multisample is referenced to what sound? Just trying to be reasonable here. Knowing that the majority of users are not going to sample and design sounds from scratch, they'll load the sounds with whatever names were given to them.

Either, you would have to have the ability to generate a report to see what references what, or there could've been a fourth option in the sampling page called: "Delete all Unused/unassigned Multisamples". Maybe you can pass a note to Korg Italy to look into this for future developments. The exit strategy for getting rid of unwanted samples/multisamples is not user friendly at all for a professional keyboard.

Well, let's think this through. You're asking me to recommend making more code/work because people are not going to use the system as it is designed (naming their multisamples, at least), right?



Sorry, I'm not being a smart a**, but in a way that's the issue. And if most of the users are simply sharing/using the work of others, then it really is the responsibility of those people/sound designers to do their homework...

I agree that both a Delete sample or delete multisamples is a good idea, BTW.

I'll still look into if there is a bug, but that seems to be the first priority, agreed?

Regards,

Jerry

[Sam CA]

Well, let's think this through. You're asking me to recommend making more code/work because people are not going to use the system as it is designed (naming their multisamples, at least), right?

Hi Jerry,
That's actually not the main reason. All i'm saying is that why this keyboard has to keep the referenced multisample a "secret"? if the keyboard knows where the multisample is, I'd like to have that important piece of info shared with me as an operator of that keyboard too! I assure you that 8 out of 10 PA keyboards are full of unused multisamples and users are not even aware of it. For oriental keyboardists is 10 out of 10 keyboards. Why do you think they ask for more memory all the time?

Regardless of who made a mistake along the line by forgetting or not naming or whatever the scenerio is, it only makes sense to have a tool to get rid of junk , or even correct someone else's mistake. Making "more code/more work" will just improve the system, blaming people will not do that in this case.
If you want the keyboard to keep the referenced location a secret as it is now (if the user failed to name the MS, or had no control over that), the best way would be an option to "delete all unassigned/unused MS".

At this point it feels like my keyboard is telling me: I know where the MS is, but i'm not gonna tell you!

[sehasafade12]

Well, let's think this through. You're asking me to recommend making more code/work because people are not going to use the system as it is designed (naming their multisamples, at least), right?

Hi Jerry,
That's actually not the main reason. All i'm saying is that why this keyboard has to keep the referenced multisample a "secret"? if the keyboard knows where the multisample is, I'd like to have that important piece of info shared with me as an operator of that keyboard too! I assure you that 8 out of 10 PA keyboards are full of unused multisamples and users are not even aware of it. For oriental keyboardists is 10 out of 10 keyboards. Why do you think they ask for more memory all the time?

Regardless of who made a mistake along the line by forgetting or not naming or whatever the scenerio is, it only makes sense to have a tool to get rid of junk , or even correct someone else's mistake. Making "more code/more work" will just improve the system, blaming people will not do that in this case.
If you want the keyboard to keep the referenced location a secret as it is now (if the user failed to name the MS, or had no control over that), the best way would be an option to "delete all unassigned/unused MS".

At this point it feels like my keyboard is telling me: I know where the MS is, but i'm not gonna tell you!

Hello Sam,

I agree with you 100%.

Best regards,

Fahim

[BasariStudios]

Lol Sam, right in the Gut...as you said, thats why most people always cry about
more RAM while at the same time they have it, its right there in their keyboard
they just dont know it and dont know how to use it.

[paul]

agree with you SAM

Paul

[LESSISMORE]

Yes, you have to manually delete the User Styles (Fav1-10 / User1-3) (Not the styles themselves one by one)
All performance banks (20)
All sounds etc.. one by one. I know its a pain, but there is a SINGLE button for this.

Media>Erase>Korg SSU

Just loading a set would replace the Styles etc.. but samples REMAIN.

Which is why its best to delete all SAMPLES before loading a new set.

Sound>Red Record Button>Top Right Menu, Delete>3rd Option "ALL Samples etc..."

Hi WaveExtractor

In SSD-U you cannot see something. Its a hidden Folder.
Ther are the sample. They you can delete in the sample-editor.
The Styles and all other stuff are laying in the ssd-s area. (ALL)

[LESSISMORE]

Hi guys,

Is it possible when loading new set which only has like 10 user styles and performances have all the rest of the previous set deleted? because what happens i load this small set of 10 user styles and than on the keyboard im left with all these sounds and samples from previous set?? why don't they delete? now if i want to delete those programs i don't know which are part of new set and which are part of previous set, its really annoying??

Is there something that i could just lock it so it doesn't happen?

Any ideas on this..

Thank you.

Hi PA2x
When you want to work with very small sets, you have to make a full Backup (Media) and to save an ALL.SET.
Now you can arase all datas you dont need. (Styles, Sounds (PCGs) Samples (sample-edotor), Performances...)
You can nearly clean the whole system. (Its better to leave the Fac-PCGs and Drum-kits on the system.)
And now, when you load back some styles and PCGs from your old set, the system will load the right samples automatically.

So you can make your small sets.
But each time, when you load different sets, the system will load the right samples (pcms) from your old set. This samples will stay in your system, till you delete them or you make a full restore from you old set.

So it is not possible to work every time with small sets, when you only use the load-function for sets. So the samples will load each time and the memory get full, like in the old time.

The only one solution is, to make full backup (media) from your "small set(s)", and to load back them with the restore-function.
So you can get small sets every time.
The downside is, that you have to start the PA2 new, after restoring.

[Pa2x]

Thank you Lessismore, that is an option i can see where you coming from, but i think i will stick with just deleting everything before i load a new set, this way im sure that there wont be any hidden multisamples.

I also agree with Assyrianpianist i think he is got a good point there, if i make my own samples and multisamples i would probably name them, but if you just copy-paste from different sets than this would be a night mare writing names for 50000 multisamples.

I dont use not even 1 factory style from Korg, and probably 5% of sounds, so for people like me that option do delete unwanted multisamples would be very useful, or something like 'reset to factory settings' so it deletes everything would also be very helpful.

[Sam CA]

This issue of handling unwanted samples/multi-samples is a big problem and almost all keyboards are infected with trash that can't be identified by users. If korg wasn't so disconnected from the user community, they would quickly realize how things actually work for most people if not all.
I strongly recommand that Korg programmers add this feature , not because people are not using the system properly, but because the design is incomplete! The bottom line is, who cares who did or did not name the multisample. If it's junk, and not used by any sound or style, we want it out of the keyboard instantly. Only people who never loaded any audio samples have a clean keyboard. They should've really bought a PA500 then!

[naweed jan]

Hello Assyrianpianist,

I agree with you they should provide us with a software to fix our PCM files( where the samples are stored) Wave extractor dose view the PCM files but you are not able to remove the samples from PCM.They are other software that can read your PCM such a cool edit pro ect.. but they can't identify each sample and name like wave extractor dose.


There is 2 solution

1,Give us a software that is able to remove files from PCM

2,Change the operating system so that we can multi-select and remove the files that we don't need

I wonder why they don't give you these options.They give you copy,past all that but maybe because they plane all this out.That why you get every one complain about RAM!!! because they have all these junk and they have no idea. They might bring out pa4x might have that option to multi-select $$$$$ hahahaha

[Sam CA]

Hello Assyrianpianist,

I agree with you they should provide us with a software to fix our PCM files( where the samples are stored) Wave extractor dose view the PCM files but you are not able to remove the samples from PCM.They are other software that can read your PCM such a cool edit pro ect.. but they can't identify each sample and name like wave extractor dose.


There is 2 solution

1,Give us a software that is able to remove files from PCM

2,Change the operating system so that we can multi-select and remove the files that we don't need

I wonder why they don't give you these options.They give you copy,past all that but maybe because they plane all this out.That why you get every one complain about RAM!!! because they have all these junk and they have no idea. They might bring out pa4x might have that option to multi-select $$$$$ hahahaha

I know! Isn't that weird? Does any body know if Korg PA3x has an option to "Delete all Unused/Unassigned Multi-samples"?