Page 2 of 5
Posted: Sun Jul 05, 2020 8:33 pm
by Jan1
GregC wrote:
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.
Posted: Sun Jul 05, 2020 8:41 pm
by 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.
Posted: Sun Jul 05, 2020 8:43 pm
by GregC
Jan1 wrote:GregC wrote:
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.
Posted: Sun Jul 05, 2020 8:50 pm
by GregC
timg11 wrote: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?"
.
////
Posted: Sun Jul 05, 2020 9:00 pm
by 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"
Posted: Sun Jul 05, 2020 9:07 pm
by GregC
////
Posted: Sun Jul 05, 2020 9:16 pm
by GregC
GregC wrote:kronoSphere wrote: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.
Posted: Sun Jul 05, 2020 11:07 pm
by 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
Posted: Mon Jul 06, 2020 7:58 pm
by Galf2
timg11 wrote: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.
Posted: Mon Jul 06, 2020 8:33 pm
by GregC
Galf2 wrote:timg11 wrote: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.
Posted: Mon Jul 06, 2020 8:39 pm
by NormC
I don't think new engines are out of the question. Vox and Compact from Grandstage could easily be added.
Posted: Mon Jul 06, 2020 8:47 pm
by GregC
NormC wrote: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.
Posted: Mon Jul 06, 2020 8:50 pm
by Galf2
GregC wrote:
1)MORE Program banks Please.
Maybe all the same this?
1) MORE Program banks and Wavesequence banks Please.
Posted: Mon Jul 06, 2020 8:54 pm
by GregC
Galf2 wrote:GregC wrote:
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.
Posted: Mon Jul 06, 2020 9:02 pm
by Galf2
GregC wrote: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
