Kronos II - when ?

[danatkorg]

Sorry GregC (seems a night of apologies!) - I do not in any way mean that Karo's libraries should be available for the Kronos. Quite the contrary. With the arrival of the Kronos, the OASYS libraries were no longer for sale. The implication is that if you wanted to be part of the Korg authorisation process you need to stop OASYS sales - as they are unprotected so Korg would not get their cut of revenue.

There is no such requirement.

Didn't you mention that KARO indicated that they might be able to help you? Perhaps it would be better to contact them directly.

[cello]

Sorry GregC (seems a night of apologies!) - I do not in any way mean that Karo's libraries should be available for the Kronos. Quite the contrary. With the arrival of the Kronos, the OASYS libraries were no longer for sale. The implication is that if you wanted to be part of the Korg authorisation process you need to stop OASYS sales - as they are unprotected so Korg would not get their cut of revenue.

There is no such requirement.

Didn't you mention that KARO indicated that they might be able to help you? Perhaps it would be better to contact them directly.

LOL I doubt they'll help me! I wanted to buy about 600 euros worth of karo libraries and then the OASYS libraries suddenly disappeared from their website, stating they were getting their libraries ready for the Kronos.

Ergo, the Kronos arrival stopped me getting libraries for my OASYS

[danatkorg]

Sorry GregC (seems a night of apologies!) - I do not in any way mean that Karo's libraries should be available for the Kronos. Quite the contrary. With the arrival of the Kronos, the OASYS libraries were no longer for sale. The implication is that if you wanted to be part of the Korg authorisation process you need to stop OASYS sales - as they are unprotected so Korg would not get their cut of revenue.

There is no such requirement.

Didn't you mention that KARO indicated that they might be able to help you? Perhaps it would be better to contact them directly.

LOL I doubt they'll help me! I wanted to buy about 600 euros worth of karo libraries and then the OASYS libraries suddenly disappeared from their website, stating they were getting their libraries ready for the Kronos.

You mentioned earlier in this thread that KARO had suggested that users email them directly. I do not know what their policy is, but it never hurts to ask.

[JuneauUnderground]

if there is a kronos 2, i will not buy it until i fully master my own kronos.

That's what I said about my M3! And we know how that turned out. Too many keyboards so little time!

[apex]

if there is a kronos 2, i will not buy it until i fully master my own kronos.

That's what I said about my M3! And we know how that turned out. Too many keyboards so little time!

you rig just may rival mine!!!! you got any of that stuff for sale?

[apex]

if there is a kronos 2, i will not buy it until i fully master my own kronos.

That's what I said about my M3! And we know how that turned out. Too many keyboards so little time!

you rig just may rival mine!!!! you got any of that stuff for sale?

actually now that I look at it..... I believe you've got me beat.

[Jan1]

In terms of hardware the next-gen KRONOS could be a big step forward.

I'm thinking of the memristor which combines the storage facilities of harddisk with the speed of DRAM besides the possibility of analog computing.
With software adjustments the memristor could fuse RAM and HD into one, and you would have a KRONOS II without any boot-up time.

[1jordyzzz]

1. Piano is fine already.
2. EPs are fine already.
3. Woodwind modeler could be done in an engine expansion?
4. user samples possibly through a software update
5. I was thinking more, but not that much more... how long would it take to load all that? lol
6. good suggestion... maybe could be done through software update and different samples offered
7. larger screen... ..are you serious? HDMI output for what?
8. that's a lot of polyphony... how many fingers do you have? I only have 10.
9. 32 tracks of mid would be good, but could maybe be done in a software update. I think you can do things like this already just maybe having to use track bounce after you use up all the tracks... .
10. Why would you need to change patches 3 times before you start losing sound?

nice list of your wishes, but I don't think it warrants another $3000 purchase or them even building another Kronos.

1. piano lacks symphatetic string resonance
2. electric pianos are fine but somebody has complained about CP-80 patch on kronos
3. yes i hope so
4. i hope so too
5. well we never know what will happen in the future.. maybe loading 10 gigabytes onto ram only takes 5 seconds?? some people cannot live with only 3,25 gigs of ram in kronos... they cannot load all the expansion...
6.
7. well at least it will remove the need for a software editor if we can see everything on a larger screen (or a large external screen?)
8. everythings different when you play 16 layer thick combi (orchestral combi on kronos takes 10-15 voices on each note, giving a maximum 10-12 notes to play), not to mention if few of the sounds are expensive (using mod 7 engine or STR-1 engine for instance)
9. even if there's 32 tracks available, the limitation is simple.. not enough polyphony.. even demo songs like the "ubiquity" on the korg kronos produce voice stealing... that's 16 tracks...
10. it's when we press a wrong patch on the setlist.. if we press a wrong patch once and then we press the next one right, the first one's sound will be gone because the SST is used for that wrong patch.. better save than sorry..

[jimknopf]

Discussing the arrival of a hypothetic Kronos 2, one year after the Kronos is on the market, does not make ANY sense to me. The lifecycle of complex keyboards still is around 3-5 years.

If Korg plans the next step for themselves, that's something completely different, but talking about a successor from user perspective now, that looks more to me like a signal of desperately breathless times, than being of any help for buying decisions.

[Melodialworks Music]

Discussing the arrival of a hypothetic Kronos 2, one year after the Kronos is on the market, does not make ANY sense to me. The lifecycle of complex keyboards still is around 3-5 years.

If Korg plans the next step for themselves, that's something completely different, but talking about a successor from user perspective now, that looks more to me like a signal of desperately breathless times, than being of any help for buying decisions.

Unless it produces useful ideas that Korg might actually consider or incorporate.

[NuSkoolTone]

Discussing the arrival of a hypothetic Kronos 2, one year after the Kronos is on the market, does not make ANY sense to me. The lifecycle of complex keyboards still is around 3-5 years.

If Korg plans the next step for themselves, that's something completely different, but talking about a successor from user perspective now, that looks more to me like a signal of desperately breathless times, than being of any help for buying decisions.

Seriously! And IMO encourages them to forgo updates to the Kronos and just go to the Kronos II (Or whatever)!

How about we concentrate on the potential of the CURRENT flagship first eh? Then once they've reached "The Limit" we can speculate about what's next. Deal?

[SanderXpander]

For the SST/pressing the wrong patch on setlist, a simple solution would suffice that probably wouldn't take any processing power; when changing a patch, the first patch goes into SST mode. Keep it there until a new note is played, not just until yet another patch has been selected. You could select 20 patches that way - as long as no note is played, you're fine. Seems a simple failsafe.

[danatkorg]

For the SST/pressing the wrong patch on setlist, a simple solution would suffice that probably wouldn't take any processing power; when changing a patch, the first patch goes into SST mode. Keep it there until a new note is played, not just until yet another patch has been selected. You could select 20 patches that way - as long as no note is played, you're fine. Seems a simple failsafe.

If it was that simple, we would have done it that way. Setting up effects is quick but not instant. There would be a lag on the first note, which wouldn't be acceptable.

As a secondary point, remember that effects can be applied to audio inputs, so they don't necessarily require locally played notes to be active.

- Dan

[michelkeijzers]

Actually all wishes for the Kronos here, should be in the Wish List thread.

I'm sure Korg looks at them and picks feasible or useful functions from there for the Kronos II.

[SanderXpander]

For the SST/pressing the wrong patch on setlist, a simple solution would suffice that probably wouldn't take any processing power; when changing a patch, the first patch goes into SST mode. Keep it there until a new note is played, not just until yet another patch has been selected. You could select 20 patches that way - as long as no note is played, you're fine. Seems a simple failsafe.

If it was that simple, we would have done it that way. Setting up effects is quick but not instant. There would be a lag on the first note, which wouldn't be acceptable.

As a secondary point, remember that effects can be applied to audio inputs, so they don't necessarily require locally played notes to be active.

- Dan

I think with the first point you're misunderstanding me. I understand that you have to load the whole new patch in order to have it ready to be played. I'm saying that if you then switch to a third patch without having played anything, the Kronos currently puts the second patch into SST, cutting off the first patch, even though nothing was played in the second patch. It could be made so that there is an extra condition to SST; not just switching to a new patch but at least one note having been played. Otherwise it keeps the old sounding patch in SST.

Your point with the inputs is a good one, but I use a Ventilator with my Kronos organs that I run back into input 2 and it cuts off when I switch to a patch where I don't have that routing set. So SST is already somewhat "broken" on that, unless I'm doing something wrong.