I'm curious what people think is the best workflow for saving custom sample banks? Having spent the last couple of days working on some new sounds, I have the feeling I'm going about this wrong because my save process seems excessively clunky.
What I am doing:
- Working on a set of related multisamples, which I am all saving into a single .ksc file.
- I have this .ksc set to automatically load on startup in global preferences, so my sounds are instantly available.
- After modifying or adding new samples, I go to disk mode, select the Save Sampling Data page menu command.
The problem with this workflow is that when I save changes for the second time to the same named .ksc file, I get an error that the file already exists, without any option to overwrite it. So I must go in and delete the existing file before I can save, which is a pain to do every time!
Alternatively, I could save to a differently named .ksc file every time, but this would quickly clutter up my drive, not to mention then I would also have to update which .ksc is set to autoload in my global preferences.
A final irritation is that, after restarting the Kronos, I must enter the .ksc name from scratch when I save. I can't find any way to just select an existing file to save over.
I can't help thinking there must be some easier way I am missing, that would let me save changes over an existing file in just a single operation?
Thanks!
Workflow for saving samples
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Re: Workflow for saving samples
Hi,
i have exactly the same experience.
Did you solve this Question?
How should this be used?
i have exactly the same experience.
Did you solve this Question?
How should this be used?
Hi guys.
The KRONOS cannot overwrite a sample library. You must either delete the old library before saving the sample data, or you must use a different file name.
I STRONGLY RECAMMEND that you use a different file name. Never delete your data from the SSD first as if something goes wrong during saving, you will loose everything.
Regards
Sharp
The KRONOS cannot overwrite a sample library. You must either delete the old library before saving the sample data, or you must use a different file name.
I STRONGLY RECAMMEND that you use a different file name. Never delete your data from the SSD first as if something goes wrong during saving, you will loose everything.
Regards
Sharp
-
kid_nepro_2002
- Approved Merchant
- Posts: 557
- Joined: Wed Mar 27, 2002 2:11 pm
- Contact:
Or.... you can just save the file to a different folder. When your sure that the new file is OK, you can delete the old one and move the file to the old folder. Sharp is right…best that your sure everything is ok before deleting the old file.
This way of doing things might seem a bit "clunky", but it's actually a good idea since it forces you to make a backup before deleting anything.
This way of doing things might seem a bit "clunky", but it's actually a good idea since it forces you to make a backup before deleting anything.
<a href="http://www.kidnepro.com">www.kidnepro.com</a>
<a href="http://www.kidnepro.com/KN/Korg/Korg.html">New Sound Libraries For Korg Synths</a>
<a href="http://www.kidnepro.com/KN/Korg/Korg.html">New Sound Libraries For Korg Synths</a>
This design strikes me as clunky compared to a good software save implementation.
Absolutely, it is important not to first delete old data and then save new data, in case power goes out or something else goes wrong in between in which case the whole thing would be lost.
A well written computer program deals with this in one of two ways:
- Some programs will do the save to a temporary file, then only if the saving completes successfully, automatically delete the original file and rename the temporary to replace it.
- Others will rename the old data to a temporary file, then save new data to the old filename. This way if saving fails, the original copy can be recovered from the temporary renamed version.
Either way, this can be done entirely automatically, so the user just chooses save, and this appears to overwrite the existing file, yet can automatically recover the old version if anything goes wrong during the save process.
It is a shame Kronos does not do this.
Absolutely, it is important not to first delete old data and then save new data, in case power goes out or something else goes wrong in between in which case the whole thing would be lost.
A well written computer program deals with this in one of two ways:
- Some programs will do the save to a temporary file, then only if the saving completes successfully, automatically delete the original file and rename the temporary to replace it.
- Others will rename the old data to a temporary file, then save new data to the old filename. This way if saving fails, the original copy can be recovered from the temporary renamed version.
Either way, this can be done entirely automatically, so the user just chooses save, and this appears to overwrite the existing file, yet can automatically recover the old version if anything goes wrong during the save process.
It is a shame Kronos does not do this.
I agree, fully !shawnhar wrote:This design strikes me as clunky compared to a good software save implementation.
Absolutely, it is important not to first delete old data and then save new data, in case power goes out or something else goes wrong in between in which case the whole thing would be lost.
A well written computer program deals with this in one of two ways:
- Some programs will do the save to a temporary file, then only if the saving completes successfully, automatically delete the original file and rename the temporary to replace it.
- Others will rename the old data to a temporary file, then save new data to the old filename. This way if saving fails, the original copy can be recovered from the temporary renamed version.
Either way, this can be done entirely automatically, so the user just chooses save, and this appears to overwrite the existing file, yet can automatically recover the old version if anything goes wrong during the save process.
It is a shame Kronos does not do this.
Strange and not linear behaviour, because kronos overwrite song data if I do "save seq data" after I have modifyed a song....
Yeah...kinda cludegy. I delete it first. I get why that's a bad idea, but I have backups. That way, the auto load remains set. If you change the name, you've got to ALSO go set the new file to auto load.
Ideal (other than Korg fixing the save process) would be to rename the folder it's in (which means one per KSC)...new folder with the old name--save it there. That Should retains the auto load and save a "backup" in case something goes wrong.
Ideal (other than Korg fixing the save process) would be to rename the folder it's in (which means one per KSC)...new folder with the old name--save it there. That Should retains the auto load and save a "backup" in case something goes wrong.
-
Steve Pavao
- KORG R&D
- Posts: 52
- Joined: Mon Jan 22, 2007 4:02 am
- Location: Boston area
-
Steve Pavao
- KORG R&D
- Posts: 52
- Joined: Mon Jan 22, 2007 4:02 am
- Location: Boston area
Hi Redrain,
One of the files saved during a Save All operation is the KSC file. Also saved at that time is its companion directory of sampling data, which has the same name.
The error you're seeing means that either the KSC file already exists, or its companion directory of the same name already exists.
As I said before, I very much agree that it would be nice to allow overwrite of a KSC file. This implies that it would also be nice to allow overwrite of its its companion directory of the same name.
- Steve Pavao
software engineer
Korg R&D
One of the files saved during a Save All operation is the KSC file. Also saved at that time is its companion directory of sampling data, which has the same name.
The error you're seeing means that either the KSC file already exists, or its companion directory of the same name already exists.
As I said before, I very much agree that it would be nice to allow overwrite of a KSC file. This implies that it would also be nice to allow overwrite of its its companion directory of the same name.
- Steve Pavao
software engineer
Korg R&D
