MONO LEGATO BUG STILL THERE IN 2.02

tonyt · Post by **tonyt** » Thu Aug 09, 2012 3:57 am

I Just updated to 2.02 and am still experiencing this bug with mono legato sounds while using the midi scale box to detune the keyboard....

This is a very important issue that should be addressed... there is a big market of keyboard players that are not getting close to kronos because they heard about this bug.

We need to use this oriental scale box for on-the-fly detuning.....

Hope anyone can help!!

Tony

BasariStudios · Post by **BasariStudios** » Thu Aug 09, 2012 4:03 am

I cannot help with this since this bug is particular to the AK-2 unit which i dont
use...maybe someone with the Unit can help with this.

ak · Post by ak » Thu Aug 09, 2012 4:47 pm

I would like to see a reply from Korg team. While Os 2 is a good one but I was hoping for a fix or a solution for the above mentioned problem.

BasariStudios · Post by **BasariStudios** » Thu Aug 09, 2012 5:01 pm

Few users of AK2 already confirmed that it is not working.

ak · Post by ak » Thu Aug 09, 2012 9:31 pm

Thanks! Let us wait

alberto77 · Post by **alberto77** » Sat Aug 11, 2012 2:45 am

hello every one , mono legato poly after touch bug , is making me struggling

alberto77 · Post by **alberto77** » Sat Aug 11, 2012 2:53 am

hello every one , i had my kronos one year ago, the problem is tha i culd not operate the (mono legato poly after touch) , this maid me feel upset , cz i had bought meany programs that require so , and had waited mono legato poly after touch the to be fixed by software's 1.6 , 2.0.2 , to fix this bug , but it didn't been fixed , this problem had effected badly my baseness , is it that hard for korg to fix this problem , or the solution is to wait the next year to have it fixed , im really struggling , and dont know what to do .
_________________
mohammed obeidat

ak · Post by ak » Sat Aug 11, 2012 4:13 pm

You have to wait for Korg to give an answer

cello · Post by **cello** » Sat Aug 11, 2012 4:48 pm

Does the mean the Kronos X will also have the bug?

1jordyzzz · Post by **1jordyzzz** » Sat Aug 11, 2012 5:04 pm

cello wrote:Does the mean the Kronos X will also have the bug?

If kronos has it, then surely kronos X also has it.. they had the same software, and it's a software problem...

ak · Post by ak » Sat Aug 11, 2012 5:47 pm

Yes, both Kronos and Kronos X still have the same bug even with version 2. This issue has been since the release of Kronos last year and Korg never promised to fix it or even make a comment about it. I think, it is not a top priority issue so they leave it to future releases.

ak · Post by ak » Mon Aug 13, 2012 2:31 pm

I wonder if Korg and R&D are reading this post. Is there a reason behind this silence?

alberto77 · Post by **alberto77** » Tue Aug 14, 2012 2:03 am

yes we will wait , though this problem is making me depressed , some times i regretted that i had this product , and could had any ather good brand synthesizers in the market .

i agree with bloggers in this forum that korg ether not reading our problems, or it is not a big deal for them ,never the less i had two of my friends preferred to by the older synthesizers versions , because of this problem , but not this inspiring top of the line product .

ak · Post by ak » Tue Aug 14, 2012 3:19 pm

You will have to wait and drink the coffee

BasariStudios · Post by **BasariStudios** » Tue Aug 14, 2012 4:33 pm

Or you can still use it without the AK-2...but i still never understood this bug.