manoj wrote:I think there is a confusion on what I mentioned as Save. I am trying to write the style from style creator to a user bank. It doesn't allow that. After creating a new style in style creator, when I try write style, it shows access denied. Same issue when I edit a sound in sound mode, and try to write sound.
i think the internal memory is write protected.
Of course there is a confusion of hearing someone "try to save a custom style or sound to a user bank".
That is because in user banks only writing, deleting or renaming is possible with system commands (write, load, delete, rename) in this area of the internal memory.
User bank is no ordinary media due to the pre-configured type of data inside the instrument’s memory, which can be set to write-protect by the user, so that the message "the media is write-protected" is also confused.
*
If no styles and sounds can be written into the user banks, there is obviously a system error. It is probably not possible to understand why this happens and no assumptions will help. It was mentioned in many postings that incompatible data loaded into memory is often responsible for this.
It is therefore recommended not to load any external resources (setfiles) before listening and testing them via Direct Data.
*
I think you should try to test whether the user area reacts to other system commands and whether the existing user bank data is still visible and usable at all.
For example, a user style can be copied to a free user location with a "Copy/Paste".
If this works, the internal memory cannot be write protected.
If the copied user style is clicked and usable, it can be deleted with the "Delete" command of the page menu.
If that works too, that's another indication that the internal memory isn't write-protected.
You can also copy an entire user bank to an empty user bank with "Select All (Bank)" and "Copy and Paste".
If there is already data there, the message "Do you want to overwrite ...." comes up, but if the user bank is empty, it can be filled with the copy/paste.
If that works, you can possibly also delete the user resources of a complete bank, or rename it with a "Rename User Banks" etc. to check the internal memory for write-protect.
*
What else could be done:
If a backup exists use choose the restore command (Media > Utility > Resource Restore). This command will delete from the internal memory all types of data (selected in dialog box), including your custom data. If you did not remove protection from Factory you avoid overwriting the standard musical resources (factory/local), so only custom data are overwritten with backup data - mayby now internal memory will be able to write user styles and user sounds.
If not, next that could be tried is to reinstall last OS (.pkg)
In case due to memory corruption or loading of incompatible data you could ask KORG for a reset file (Pa700-Factory-Reset.pkg).
I think installing Factory-Reset will delete all data from the internal memory.