See Top 50 Most Wanted

[Jan1]

I think I have a ranking system that is simple :

P1 = a significant and " must have " issue. Whether its a bug, a defect or overdue needed enhancement. Its top Priority and we want Korg Inc to solve it promptly , get to work on it, resolve it quickly etc.

P2 = a ' nice to have ' Korg fixit issue . Could be a small but annoying bug. Could be small performance issue. Unnecessary navigation. Confusing terminology. A menu fix. Etc etc

P3 = everything else

Comments ?

I think that’s a good idea.
Perhaps needless to say that I would put the out of tune notes in the P1 category, KORG should correct that.

[timg11]

I think this thread is helpful to narrow the list, but rather than focus on the negative, let's also identify the positive motivators. When Korg management thinks about developing a Kronos update, I expect they are asking "how is this going to bring in revenue?"

Some OS improvements have the potential to bring in new revenue from existing Kronos owners. I'm talking about indirect revenue, not about charging for the update, which I don't think would be well received.

One example is expanding program banks. Mine have been completely full for years, and even with PCGtools it is quite a bit of work to manage the shortage. I add programs one at a time as I edit them or create them, and for every new program, an old one must go.
When Korg or other sound designers promote new EXs or KRs, I don't even consider them. Finding room for a whole new bank is too daunting.

But, if I suddenly had double the program space, I would definitely do some shopping at https://shop.korg.com/kronos.

[GregC]

I think I have a ranking system that is simple :

P1 = a significant and " must have " issue. Whether its a bug, a defect or overdue needed enhancement. Its top Priority and we want Korg Inc to solve it promptly , get to work on it, resolve it quickly etc.

P2 = a ' nice to have ' Korg fixit issue . Could be a small but annoying bug. Could be small performance issue. Unnecessary navigation. Confusing terminology. A menu fix. Etc etc

P3 = everything else

Comments ?

I think that’s a good idea.
Perhaps needless to say that I would put the out of tune notes in the P1 category, KORG should correct that.

Exactly my opinion. Out of tune piano sample on Kronos is a P1.

Korg should fix immediately. No excuses.

[GregC]

I think this thread is helpful to narrow the list, but rather than focus on the negative, let's also identify the positive motivators. When Korg management thinks about developing a Kronos update, I expect they are asking "how is this going to bring in revenue?"

.

////

[kronoSphere]

Galf2 wrote:
Update List:
1. No motherboard DIY
2. No x64 OS
3. No new version Karma
4. No change in SEQ
5. No new engines


I feel exactly the inverse
That's what I want
And no more false updates like that "split function"

[GregC]

////

[GregC]

Galf2 wrote:
Update List:
1. No motherboard DIY
2. No x64 OS
3. No new version Karma
4. No change in SEQ
5. No new engines


I feel exactly the inverse
That's what I want
And no more false updates like that "split function"

ok, I get it.

How much are you willing to pay for all 5 feature enhancements for your Kronos ?

How do you solve the logistics and the process of installing a new mother board ?

How will Stephen Kay and Korg Inc come to an new agreement on an updated
native Karma ?

And how many Kronos owners agree with your list and are they willing to pay ?


I am not opposed, its about getting a ' collective agreement ' on a Kronos keyboard that is on Year 9 and has not seen any significant feature enhancements in over 3 years.

[kronoSphere]

GregC,

Always lucky are the ones whose their old dreams asked for each day the moon : THey are the ones who land on it !

Let's ask the for the moon and we'll get valuable stardust from Korg

[Galf2]

One example is expanding program banks. Mine have been completely full for years, and even with PCGtools it is quite a bit of work to manage the shortage. I add programs one at a time as I edit them or create them, and for every new program, an old one must go.
When Korg or other sound designers promote new EXs or KRs, I don't even consider them. Finding room for a whole new bank is too daunting.

But, if I suddenly had double the program space, I would definitely do some shopping at https://shop.korg.com/kronos.

I bought two libraries, and I would buy two or three more, but there are no free banks in the Kronos for place new. This is some kind of idiotic problem for me.

[GregC]

One example is expanding program banks. Mine have been completely full for years, and even with PCGtools it is quite a bit of work to manage the shortage. I add programs one at a time as I edit them or create them, and for every new program, an old one must go.
When Korg or other sound designers promote new EXs or KRs, I don't even consider them. Finding room for a whole new bank is too daunting.

But, if I suddenly had double the program space, I would definitely do some shopping at https://shop.korg.com/kronos.

I bought two libraries, and I would buy two or three more, but there are no free banks in the Kronos for place new. This is some kind of idiotic problem for me.

If we can get agreement from more owners here - that might the simple message we present to Korg Inc:

1)MORE Program banks Please.

[NormC]

I don't think new engines are out of the question. Vox and Compact from Grandstage could easily be added.

[GregC]

I don't think new engines are out of the question. Vox and Compact from Grandstage could easily be added.

Hi Norm, I really don't know what or if engines are 'easy' to implement on Kronos.

Currently, I rank ' more engines ' as a "P2 "

P2 is a ' nice to have ' enhancement.

P1 is a " must have " enhancement

If we can get a consensus from owners on:

1) add more engines
2) engines are
a]
b]

with that consensus or collective agreement, I am fine with saying its
P1.

[Galf2]

1)MORE Program banks Please.

Maybe all the same this?
1) MORE Program banks and Wavesequence banks Please.

[GregC]

1)MORE Program banks Please.

Maybe all the same this?
1) MORE Program banks and Wavesequence banks Please.

I am in agreement .

Not many owners have mentioned wavesequnce banks.

Given wavestate [ which I will not buy ] it seems obvious more wavesequnce banks programmed by Korg are a must have.

Kronos has only a few dozen which isn't much.

[Galf2]

Given wavestate [ which I will not buy ] it seems obvious more wavesequnce banks programmed by Korg are a must have.

Kronos has only a few dozen which isn't much.

Yes, that's right