I haven't implemented 'Sample Renaming' / OctaEdit doesn't have this functionality.
It's not that I can't do it; but it creates a potential issue around scenarios where a user might rename a sample that is referenced by multiple Projects.
If they don't save all the Projects; then they would end up with broken references to the old sample in the (unsaved) Projects.
There is then the potential that cats might complain; and blame OctaEdit when it has functioned exactly as designed, but the user has failed to complete a process.
Thats not an acceptable risk that I am prepared to take.
The obvious workaround is to auto-save the affected Projects.
That brings in the potential that OctaEdit will save a Project; including changes that the user didn't actually want (e.g. they were playing around without concentrating / just testing etc); they might then blame OctaEdit, when, again, it has functioned exactly as designed, but the user has failed to understand the process / realised what is occuring.
Again, not an acceptable risk that I am prepared to take.
This is just being pragmatic and risk-adverse. I've already been burnt by people complaining on forums / facebook etc about "issues" when it has functioned exactly as designed and documented; yet instead of querying the how and why; they've gone and posted "OctaEdit sucks!!!" publicly on Facebook... once explained to them, they've realised the error of their ways; but as an independent developer relying on word-of-mouth / recommendations; I can't afford, nor deal with that kind of scenario.
In saying all that...
Functionality exists within the Samples module for sample import/export; so you can very quickly select a sample e.g. Flex001 ""KickyKick"; export it as "MyKick"; then reimport it back into Project; overwriting the existing slot. Net result is the same as renaming the file.