downgrading to OS v1.0.4, possible? fix freezing?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
downgrading to OS v1.0.4, possible? fix freezing?
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
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
Last edited by kimu on Fri May 07, 2010 2:31 pm, edited 2 times in total.
-
- Full Member
- Posts: 208
- Joined: Sun Jan 11, 2009 12:08 pm
- Location: Norway
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...
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...
Have you actually tried contacting your KORG distributor for support?
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
-
- Full Member
- Posts: 208
- Joined: Sun Jan 11, 2009 12:08 pm
- Location: Norway
-
- Posts: 10
- Joined: Fri Jan 01, 2010 8:32 pm
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.
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.
100% hardware made. All is done in a Korg M50 internal sequencer. Now updated (7/09/12) at http://www.hispasonic.com/akmon
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.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 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.
Current Korg Gear: KRONOS 88 (4GB), M50-73 (PS mod), RADIAS-73, Electribe MX, Triton Pro (MOSS, SCSI, CF, 64MB RAM), SQ-64, DVP-1, MEX-8000, MR-1, KAOSSilator, nanoKey, nanoKontrol, 3x nanoPad 2, 3x DS1H, 7x PS1, FC7 (yes Korg, NOT Yamaha).