Page 1 of 1

Kronos Sample Unload Major Bug

Posted: Sat Dec 07, 2013 3:55 pm
by Stratario
I have included a handy little sample package for anybody who is interested in duplicating this test and see the bug for themselves. You can download the sample package from the following link:

http://uppit.com/9s4fkwjq8e8l/Kronos_Un ... e_Test.rar

Statement of the Problem:

When unloading multi-samples in the Global mode from the Sample Manage page, for every multi-sample that is unloaded, one additional multi-sample is lost from the top of the multi-sample list.


Demonstration of the Problem:


Load some multi-samples. If you use the samples package that I posted at the top of this post, you can go to the sampling mode and you should see the list of multi-samples as shown in this picture:

Image

As you can see we have 32 multi-samples. Now we go to the Global mode and to the Sample Manage page. We select one sample to unload. In this case I have chosen next to the last sample.

Image

We proceed to unload the sample. We now go to the Sampling mode and look at the list of the multi-samples. We see the next to the last sample has been successfully unloaded. However, we see the first sample from the top of the list has also disappeared. So here is the bug. For every sample that we unload, we would loose one additional sample from the top of the list.

Image

So we proceed to unload 2 additional samples. We see that now we have lost a total of 3 samples from the top of the list.

Image

I should also mention that when we are in the Sample Manage page, if we put a tick mark in the "Multiple Select" box, we select one sample, or multiple samples to unload and this problem would not happen. So the problem exists only when unloading one sample at a time and only when the "Multiple Select" box is not checked.

Amoo Farrokh
Canada

Posted: Sat Dec 07, 2013 7:19 pm
by TheWolf
I can confirm this with my Kronos X OS v2.1.0.

Some additional observations: It is the scrolling which seems to interfere with proper selection of multi-samples to be removed when the "Multiple Select" is unchecked.

If I select a multi-sample from the visible list without scrolling, then only the selected multi-sample is removed. If I scroll down the list, however, not only the multi-sample I selected after scrolling is removed but also the one that was originally selected before scrolling down.

So, if I immediately select multi-sample 05, then only multi-sample 05 is removed. However, if I first scroll down and select multi-sample 30, then the newly selected multi-sample 30 together with the originally pre-selected multi-sample 01 are both removed. If I first select multi-sample 05, scroll down, select multi-sample 30, then the selected multi-samples 05 and 30 are both removed.

Posted: Sat Dec 07, 2013 7:33 pm
by Stratario
Interesting observation about the scrolling effect. Thanks. And btw, this is not the result of the recent updates. I bought my Kronos about 7 months ago and I immediately installed OS 2.0.6 and I had noticed it back then as well.



Amoo Farrokh
Canada

Posted: Wed Dec 11, 2013 2:58 pm
by Stratario
I am wondering if anybody from Korg has seen this thread? This is an important bug and it needs to be fixed. I also reported it as far back as July of 2013 but it went totally unnoticed:

http://www.korgforums.com/forum/phpBB2/ ... ht=#551677

Hope it gets fixed soon.


Amoo Farrokh
Canada

Posted: Wed Dec 11, 2013 3:53 pm
by AdDeRoo
I had this issue as well some time ago. Don't remember with which OS. I did not encounter it recently anymore though

Posted: Wed Dec 11, 2013 6:04 pm
by ed_f
Stratario wrote:I am wondering if anybody from Korg has seen this thread? This is an important bug and it needs to be fixed. I also reported it as far back as July of 2013 but it went totally unnoticed:

http://www.korgforums.com/forum/phpBB2/ ... ht=#551677

Hope it gets fixed soon.


Amoo Farrokh
Canada
You should file an actual bug report. While many things do gets picked up here on the forum, it is not the official korg bug tracker.

Posted: Wed Dec 11, 2013 7:09 pm
by Stratario
Is there a link for reporting bugs? Would appreciate any info on reporting bugs. Thanks.

Posted: Wed Dec 11, 2013 7:13 pm
by TheWolf
And from a software developer's perspective I would classify this bug as minor since the impact on the overall functionality of the Kronos is not dramatic and since there is a simple work-around available: check the "Multiple Select" but then select only one multi-sample.

Even if they already know about this bug, the Korg developers have very likely more important fixes and features higher up on their list of priorities than this bug.

So, I subscribe to Ed's view: file an official bug report. Be polite, slightly understate¹ the issue and provide all the information you have given here. And then be patient.


____
¹) Software developers hate nothing more than users overstating the importance of a bug. A bug may be very annoying to you but still be minor in the overall picture. So, understatement comes across much better.

Posted: Wed Dec 11, 2013 7:21 pm
by Stratario
Thanks Wolf. Where do I file the report? I just send a report through the Korg product support page. I am also sending an email to Dan at Korg.

Posted: Wed Dec 11, 2013 7:40 pm
by TheWolf
Sending it through the Korg support page should suffice, I think.

Posted: Fri Dec 13, 2013 5:49 pm
by Stratario
I'm happy to report that Dan from Korg has contacted me and he acknowledged the problem. So hopefully it will be fixed in the next update.

What is great bunch of people who work at Korg. We love you Korg.


Amoo Farrokh
Canada

Posted: Sat Dec 14, 2013 2:47 pm
by lotty1
That's why I always buy korg stuff

Because they always look after you.

Plus they make the best gear :D :D

Posted: Sat Dec 14, 2013 8:19 pm
by ed_f
Stratario wrote:I'm happy to report that Dan from Korg has contacted me and he acknowledged the problem. So hopefully it will be fixed in the next update.

What is great bunch of people who work at Korg. We love you Korg.


Amoo Farrokh
Canada
+1

Posted: Mon Dec 16, 2013 10:58 am
by michelkeijzers
ed_f wrote:
Stratario wrote:I'm happy to report that Dan from Korg has contacted me and he acknowledged the problem. So hopefully it will be fixed in the next update.

What is great bunch of people who work at Korg. We love you Korg.


Amoo Farrokh
Canada
+1
+1