downgrading to OS v1.0.4, possible? fix freezing?

kimu · Post by **kimu** » Fri May 07, 2010 8:46 am

yesterday i had an awful hour of rehearsal with M50 continuously freezing, even starting up already frozen... it simply has been impossible to play for an hour...

then something strange happens... at the N-th restart (N>>1), m50 is not started correctly, the screen shows "updating left panel" and then "power off".

after this, now m50 takes an incredible long time to load OS v1.1.0 but at least has stopped freezing for the next 1h.

as it is simply not tolerable this way of playing, i wanna to downgrade to OS v1.0.4 so questions are:

- is downgrading possible or can cause block of the synth as happened in m3?

- the OS v1.0.4 is free from freezing problem?

thanks

runeharpun · Post by **runeharpun** » Fri May 07, 2010 10:31 am

Hi.
I've only had a couple of freezes, but both happened in the same venue. Du you see any connection with place and freeze. Eg. do you have the same number of freezes when you play other places?

kimu · Post by **kimu** » Fri May 07, 2010 10:37 am

my m50 starts last weeks to behave in this way, before, with OS v1.1.0, i never had any problem for months. and i see no correlation with place where i play. at the beginning i suspect the maybe the power supply was not stable or something like that, but the freeze happens everywhere...

i tried to install the OS again but nothing changes, i suspect it could be some electronic component that is going to fail or work uncorrectly...

X-Trade · Post by **X-Trade** » Fri May 07, 2010 11:50 am

Have you actually tried contacting your KORG distributor for support?

kimu · Post by **kimu** » Fri May 07, 2010 12:09 pm

yes of course, i'am waiting for answer.

EDIT: just got the answer, they are unaware of the problem, just said to send them the keyboard and will have a look....

runeharpun · Post by **runeharpun** » Fri May 07, 2010 12:51 pm

kimu wrote: just got the answer, they are unaware of the problem

So Korg people doesn't pay attention to these forums ?

kimu · Post by **kimu** » Fri May 07, 2010 2:17 pm

i see sometimes Jerry have a look to our request and complaint... but about this problem seems korg is not care very much

kimu · Post by **kimu** » Fri May 07, 2010 2:51 pm

emmhhhh

anyway, someone has ever downgraded the OS from v1.1.0 to v1.0.4 ?

is it possible?

guillex · Post by **guillex** » Fri May 07, 2010 3:38 pm

Umm after reading all this I started feeling scary! Because I just baught my Korg M50, and I will use it everyday!! By now nothing happend, but I would like to know....WHAT I SHOULD DO IF THIS HAPPENS?

TheWindWaker01 · Post by **TheWindWaker01** » Sat May 08, 2010 3:09 am

I had the "updating panel" problem. I don't think there's one certain thing that causes it, its just if something internal is wrong it gives that message. I hope you have your warranty because I needed to use mine to get it fixed.

kimu · Post by **kimu** » Sun May 09, 2010 10:25 am

yes i have still warranty luckily and i am going to send back m50 to tech assistance.

i more and more convincing is not a SW problem of the OS but rather a hardware related problem...

akmon · Post by **akmon** » Sun May 09, 2010 11:04 am

As I have seen, when you reboot the unit and it appears "updating panel", it´s related to hardware problem. Other cases, I hope it´s related to software problem, and it can be fixed with an OS update.

My Korg is M50 61 keys, and I´ve had 4 freeze problems in 1,5 years. Two of them were easily to solve, just changing of mode. The other were solved turning off and then on, but no more.

Still waiting form Korg staff to explain what´s happening with this issue.

McHale · Post by **McHale** » Sun May 09, 2010 8:53 pm

kimu wrote:EDIT: just got the answer, they are unaware of the problem, just said to send them the keyboard and will have a look....

I'm sure they'll be "unaware of the problem" until a fix is found and a service release note is published through the channels. We know that there are Korg reps on these forums and they see these threads, but until there is something to report (a solution or at least a cause), we probably won't see anything here official or unofficial.

I'm sure they are looking into it but if they can't replicate the issue, it's hard to troubleshoot.

The only issue I see on occasion with my 73 (and it's happened to me live a couple times) is the patch I'm playing will magically switch to another patch.