Korg Forums

I keep seeing more and more people having this SYSTEM failure reboot stuff and i keep feeling the sense that this eventually will happen to all Kronos's out there in time.

Now where the hell is Korg to adress this? This is ridiculous that we should just buy that this can happen from time to time.. Im going to tour with a band soon and i plan on playin with Kronos but apperantly it may crash in those occasions as this seem to be a standard thing in Kronos?

We should demand an explanation for this don't you guys agree?

Yep - I want to gig mine and lockups are completely unacceptable - just had one in the last hour.


R
Alan

Mercuryyyy wrote:I keep seeing more and more people having this SYSTEM failure reboot stuff and i keep feeling the sense that this eventually will happen to all Kronos's out there in time.

Now where the hell is Korg to adress this? This is ridiculous that we should just buy that this can happen from time to time.. Im going to tour with a band soon and i plan on playin with Kronos but apperantly it may crash in those occasions as this seem to be a standard thing in Kronos?

We should demand an explanation for this don't you guys agree?

Maybe that explains the editor being late if it's no longer priority #1. All I know is that I've had just the one lockup, performed a full system restore, updated to 1.5 (my lockup occurred prior to 1.5) and I haven't seen it again since (it's been close to a year). I'm using a Kronos 61 with a very low serial number.

Obviously the spectre of this occurring while gigging or some other such high-pressure situation is enough to send the board at least to the sidelines. Anyone who's had a lockup so far: when did yours occur relative to first turning on the board, what board was it and have you seen this issue since the first lockup or since 1.5?

alanjpearson wrote:Yep - I want to gig mine and lockups are completely unacceptable - just had one in the last hour.


R
Alan

Really? That is insane. I can imagine how frustrated it must have been for that to happen in your gig. I mean we didn't buy an expensive keyboard and then for it to be untrustable.

I can not imagine another keyboard being this buggy...

cynkh wrote:

Mercuryyyy wrote:I keep seeing more and more people having this SYSTEM failure reboot stuff and i keep feeling the sense that this eventually will happen to all Kronos's out there in time.

Now where the hell is Korg to adress this? This is ridiculous that we should just buy that this can happen from time to time.. Im going to tour with a band soon and i plan on playin with Kronos but apperantly it may crash in those occasions as this seem to be a standard thing in Kronos?

We should demand an explanation for this don't you guys agree?

Maybe that explains the editor being late if it's no longer priority #1. All I know is that I've had just the one lockup, performed a full system restore, updated to 1.5 (my lockup occurred prior to 1.5) and I haven't seen it again since (it's been close to a year). I'm using a Kronos 61 with a very low serial number.

Obviously the spectre of this occurring while gigging or some other such high-pressure situation is enough to send the board at least to the sidelines. Anyone who's had a lockup so far: when did yours occur relative to first turning on the board, what board was it and have you seen this issue since the first lockup or since 1.5?

I also wonder why Korg did not make some kind of coredump/performance log files to be send to Korg for analysis in such situations.

michelkeijzers wrote:

cynkh wrote:

Mercuryyyy wrote:I keep seeing more and more people having this SYSTEM failure reboot stuff and i keep feeling the sense that this eventually will happen to all Kronos's out there in time.

Now where the hell is Korg to adress this? This is ridiculous that we should just buy that this can happen from time to time.. Im going to tour with a band soon and i plan on playin with Kronos but apperantly it may crash in those occasions as this seem to be a standard thing in Kronos?

We should demand an explanation for this don't you guys agree?

Maybe that explains the editor being late if it's no longer priority #1. All I know is that I've had just the one lockup, performed a full system restore, updated to 1.5 (my lockup occurred prior to 1.5) and I haven't seen it again since (it's been close to a year). I'm using a Kronos 61 with a very low serial number.

Obviously the spectre of this occurring while gigging or some other such high-pressure situation is enough to send the board at least to the sidelines. Anyone who's had a lockup so far: when did yours occur relative to first turning on the board, what board was it and have you seen this issue since the first lockup or since 1.5?

I also wonder why Korg did not make some kind of coredump/performance log files to be send to Korg for analysis in such situations.

Probably too much to put a user through- especially in the musical instrument world. I'm hoping someone at Korg or one of their service techs was able to re-create (and subsequently fix) the issue(s)...

cynkh wrote:

michelkeijzers wrote:

cynkh wrote: Maybe that explains the editor being late if it's no longer priority #1. All I know is that I've had just the one lockup, performed a full system restore, updated to 1.5 (my lockup occurred prior to 1.5) and I haven't seen it again since (it's been close to a year). I'm using a Kronos 61 with a very low serial number.

Obviously the spectre of this occurring while gigging or some other such high-pressure situation is enough to send the board at least to the sidelines. Anyone who's had a lockup so far: when did yours occur relative to first turning on the board, what board was it and have you seen this issue since the first lockup or since 1.5?

I also wonder why Korg did not make some kind of coredump/performance log files to be send to Korg for analysis in such situations.

Probably too much to put a user through- especially in the musical instrument world. I'm hoping someone at Korg or one of their service techs was able to re-create (and subsequently fix) the issue(s)...

Yes probably, let's hope that at the service tech they can read out such a Kronos.

Maybe I'm spoiled, the company I work for can get information out of systems that are running on the other side of the world via an internet connection ... maybe Korg should also get one.

It could have major advantages: e.g. an editor that runs in a browser, so you can even edit your Kronos from another location.

mercuryyyy... you are way off by saying the the crashes are standard things on KRONOS.

How many crashes have you had so far since the time you own it, when was it? And how many after the latest OS?

If the crashes were the standard thing, noone in their right mind would be asking KORG to spend time on the Editor Software instead...

I am not sure I understand. Did you want to get a tally who has experienced no system crashes vs those who have ?

Korg has tech support and a toll free #.

Wouldn't that be the 1st step ? And wouldn't it save you time ?

GregC wrote:I am not sure I understand. Did you want to get a tally who has experienced no system crashes vs those who have ?

Korg has tech support and a toll free #.

Wouldn't that be the 1st step ? And wouldn't it save you time ?

Well, that was me asking for that and just out of morbid curiosity. As I said, I've already been through it and it seems like a quite isolated incident; but, as we're seeing there seem to be more and more making them less isolated. Hopefully they're still a rare occurance on an individual-by-individual basis...

My Kronos 61 has serial 000095, made in Japan

Never had a crash, with the old system or 1.5, but I'm worried...

I'm going to start a tour where Kronos will be responsible for EVERYTHING, from backing tracks, click to the drummer, and all the sounds I play from various controllers.

If it stops, the concert is over!

Hope it never happens!


Later today I'll be working with Steve McNally here in Brazil. We're doing workshops. I'm gonna ask him what are his impressions on these problems.

Shakil wrote:mercuryyyy... you are way off by saying the the crashes are standard things on KRONOS.

How many crashes have you had so far since the time you own it, when was it? And how many after the latest OS?

If the crashes were the standard thing, noone in their right mind would be asking KORG to spend time on the Editor Software instead...

I have not had any crashes after the upgrade BUT that is not my point, my point is that we all seem to be a target for a crash sooner or later by the looks of it. It seems that all the Kronos seems to have a fault in them that seems to have been an accepted thing by the owners and the company. The response from company representives are that, hey just send your Kronos to your local service point and have a good day. Instead they should look closer into why this is happening cause who is to say that the new Kronos you get from Korg or whatever don't have the exact same flaw.

Ultimately it is all about, can i trust this machine, that is what im wondering. Never have i felt this before about a keyboard ever.

Phabius wrote:My Kronos 61 has serial 000095, made in Japan

Never had a crash, with the old system or 1.5, but I'm worried...

I'm going to start a tour where Kronos will be responsible for EVERYTHING, from backing tracks, click to the drummer, and all the sounds I play from various controllers.

If it stops, the concert is over!

Hope it never happens!


Later today I'll be working with Steve McNally here in Brazil. We're doing workshops. I'm gonna ask him what are his impressions on these problems.

I understand the concern. These workstations are complex and a performer should have a backup plan. There is too much at stake.

If my livelihood depended on it , I would have a 2nd Kronos. If not possible, have the Extreme ready to go.

GregC wrote: I understand the concern. These workstations are complex and a performer should have a backup plan. There is too much at stake.

If my livelihood depended on it , I would have a 2nd Kronos. If not possible, have the Extreme ready to go.

Well I'd have a backup Kronos too, but in the real world this just isn't an option for everybody. Having said that, my K is gigged constantly, and stability wise it's been rock solid. I've yet to experience a lock up or crash of any kind, before or after the OS upgrade.

>I can not imagine another keyboard being this buggy...

I have had this happen with a non Korg keyboard.