Korg Forums

I’m scared to update the PA5X I’m seeing things on utube and mentioned here about I think serious problems with the 1.3 update.

Please Korg (I can’t believe you put this out this way). Please correct with and update to 1,3.1 as I won’t be upgrading until it’s right.

I empathise with your feelings.
A friend of mine actually discussed with me today that he is now cancelling gigs due to the instability of 1.3.0 on his PA5x - this is so not good.
I have no idea where this will all go in the future - I think we may have the first Korg arranger lemon - so hope they are on to this NOW.

Cheers

Pete

karmathanever wrote:I empathise with your feelings.
A friend of mine actually discussed with me today that he is now cancelling gigs due to the instability of 1.3.0 on his PA5x - this is so not good.
I have no idea where this will all go in the future - I think we may have the first Korg arranger lemon - so hope they are on to this NOW.

Cheers

Pete

Yes Pete, it’s a real worry as I like tge changes but I don’t want to loose tge funcionabilty I have now with it. I can’t believe that the beta testers didn’t pick these issues up and If I had jobs booked not only devastated but the loss of $$$$ would be something I would be asking Korg to cover. Well I’ll wait for the explanations to come and v 1.3.1 to come soon I hope .

karmathanever wrote:I empathise with your feelings.
A friend of mine actually discussed with me today that he is now cancelling gigs due to the instability of 1.3.0 on his PA5x - this is so not good.
I have no idea where this will all go in the future - I think we may have the first Korg arranger lemon - so hope they are on to this NOW.

Cheers

Pete

In regards to this recent news which is being repeated in other avenues online, then perhaps we should be concerned about the patterns that are continuing to emerge...

If the current trends of slow action continues, then Korg may establish a new precedent for how not to conduct business by the end of the PA5X product lifecycle...

Close attention continues.

I was really hoping for the best on this . Sadly I don’t think we are going to get “ the best “ from korg anytime soon ….

worth wrote:I was really hoping for the best on this . Sadly I don’t think we are going to get “ the best “ from korg anytime soon ….

This is and was a very expensive investment from the community. I’m horrified that an Update that seemed to take way time than other comparable products was released with so many problems.

I expect before this gets out of hand that the download should be suspended and that every resource they have be redirected to correcting this problem as there seems to be many. I originally started with Yamaha (never had a problem such as this) progressed through all of the iterations And again no problems went then to the PA4X lots of updates and reasonably conducted and fixed in short periods of time and then to Genos (loved it and no problems such as this) and then recently sold my soul to buy the PA5X. I love it so far, and I’m enjoying all of the wonderful enhancements that Korg made.

I did actually write to CMI Australia recently asking why no updates after a very long time with a flagship Arranger. Not knowing about this one that has just released.


OMG Can’t believe they released this with the problems that almost make this board unusable. What the hell is going on Korg?. I want an explanation from you as to, is the Update fault free, is it user fault? Because I want to know whether I should be considering ditching the PA5X for Genos 2 or are you going to make it right and quickly!?

Unbelievable.

The update has many problems, freezes , restarts etc
I didnt do it cause now i have everynight gigs, if you listen to me dont get 1..3.0 update
Previous update was okeyish, it wont freze thats the main part

Armendsh93 wrote:The update has many problems, freezes , restarts etc
I didnt do it cause now i have everynight gigs, if you listen to me dont get 1..3.0 update
Previous update was okeyish, it wont freze thats the main part

Yes no one should update until this is fixed.

Korg as a brand, is the culmination of its actions, and in the case of PA5X, it is swiftly becoming the enduring impression it leaves on the public and customer base.

robkeith wrote: I can’t believe that the beta testers didn’t pick these issues up . . .

That’s the thing, robkeith. Korg is again relying on its ‘beta testers’ a.k.a. its customers, at $6 grand a pop. Seems to be habitual with Korg and, like any really bad habit, it needs to be corrected. In this case a total boycott of this clunker might be the only way. I think if I had a 5X I’d be looking closely at my supplier’s return policy.

I know this doesn’t help yours and others’ dilemmas, and I’m genuinely sorry you’re all having to put up with this crap.

In the event that the rumours are accurate, I am exercising patience in anticipation of Roland's forthcoming flagship arranger. The PA5X is slowly becoming obsolete.

Post deleted.

I totally agree with you robkieth.

I fail to understand why anyone who uses their 5X to gig with rushes full steam ahead to update instead of being cautious and let others discover the bugs.

It is not as though Korg have a good track record of producing significant bug free updates.

I’m waiting for 1.3.1 and even then I’ll wait for you folks to find the bugs.

I’ve been really cautious .

Didn’t buy the 5x when it first came out because it didn’t do what it was advertised to do . Kept my £6000 in my investments and was happy exploring the 4 x .

I waited a couple of years years to see how or if korg would resolve the issues with the 5 x . …… the £6000 I saved is now £8000 through investment growth ….

And now I am waiting for the latest update to be debugged and stabilised but I have to tell you it’s not caution that is preventing me from buying the 5x …. It’s wisdom..

It's funny that Qui has not complained about 1.3.0 locking up, freezing, or anything else.

I myself have been doing a lot of playing with the new update 1.3.0 and have not experienced it locking up or automatically rebooting itself for no reason, like it did with 1.2.0. Now 1.2.1 seemed much more stable than 1.2.0. I am still figuring out all the new features of 1.3.0 but so far no issues. I'm wondering what it is that's causing everybody's problems. It seems better than it was, feature wise anyway. It is still missing features but other than that .....