Issue in loading KSC file after using Sample Robot
Posted: Wed Apr 03, 2024 11:56 am
I would be grateful if someone could help me resolve an issue I am experiencing when loading samples into the Kronos created using “Sample Robot”.
For anyone that hasn’t used it, this is a great tool. I have sampled around 200 patches from various soft synths that I own, loaded them into the Kronos and created new programs. It has worked fine – up until now.
Today I tried to sample a program from the Arturia Prophet V3 called “Pad Ho”. I used the process that I have always used – essentially, sampling various layers of the soft synth, saving the samples and creating a “KSC” file, which are then transferred to the hard drive on the Kronos using a program called “Filezilla”.
The samples are then saved to the hard drive and the resulting KSC file is loaded from the Global section, using “Add KSC”. This is when the problem occurs.
All the previous KSC’s that have been added following previous sampling sessions take up around 6.2M of RAM; however, my latest attempt at loading the “Pad Ho” KSC shows that it takes up 1.9G of RAM. As a result, there is no RAM left to carry out an Autoload of the KSC’s, which is what I have done in the past to load the other KSC’s created.
I have added below a link to a screenshot of the KSC Auto-load page (Apologies - I cannot work out how to add the actual image to this page !).
https://i.gyazo.com/15cea14f35baf7c6c1d ... 4414ae.jpg
You will note the Pad Ho KSC takes up 1.9G whilst the others each take up 6.2M, or lower. I do not know why this is happening.
The “Pad Ho_UserBank KSC” saved on the hard drive has a size of only 1.2M; however, when loading it, it takes up substantially more space, as noted above.
I tried to create a different KSC using Sample Robot (again using the Prophet V3) – when I tried to load this, it also took up 1.9G of RAM.
If anyone could explain what I am doing wrong (or doing differently to what I have done in the past), so that new KSC’s can be loaded without maxing out RAM, I would be grateful.
Thanks in advance.
[/img][/url]
For anyone that hasn’t used it, this is a great tool. I have sampled around 200 patches from various soft synths that I own, loaded them into the Kronos and created new programs. It has worked fine – up until now.
Today I tried to sample a program from the Arturia Prophet V3 called “Pad Ho”. I used the process that I have always used – essentially, sampling various layers of the soft synth, saving the samples and creating a “KSC” file, which are then transferred to the hard drive on the Kronos using a program called “Filezilla”.
The samples are then saved to the hard drive and the resulting KSC file is loaded from the Global section, using “Add KSC”. This is when the problem occurs.
All the previous KSC’s that have been added following previous sampling sessions take up around 6.2M of RAM; however, my latest attempt at loading the “Pad Ho” KSC shows that it takes up 1.9G of RAM. As a result, there is no RAM left to carry out an Autoload of the KSC’s, which is what I have done in the past to load the other KSC’s created.
I have added below a link to a screenshot of the KSC Auto-load page (Apologies - I cannot work out how to add the actual image to this page !).
https://i.gyazo.com/15cea14f35baf7c6c1d ... 4414ae.jpg
You will note the Pad Ho KSC takes up 1.9G whilst the others each take up 6.2M, or lower. I do not know why this is happening.
The “Pad Ho_UserBank KSC” saved on the hard drive has a size of only 1.2M; however, when loading it, it takes up substantially more space, as noted above.
I tried to create a different KSC using Sample Robot (again using the Prophet V3) – when I tried to load this, it also took up 1.9G of RAM.
If anyone could explain what I am doing wrong (or doing differently to what I have done in the past), so that new KSC’s can be loaded without maxing out RAM, I would be grateful.
Thanks in advance.
[/img][/url]