freezing

[ingar]

I did had the PA 800 for a year. During that time it freeze from time to time. I sold it because I could not rely one hundred percent on it. I loaded No extra styles or anything and just played in a disent way. But now I wonder to buy a new because I do miss some great styles and the sound was just fantastic. So my question is whether this problem still exist? And one thing,,the pads. I use them with styles, but when I hit endings the pad keep on playing. Why didn`t it stop along with the styles?

[nikola81]

Because some endings have "empty" bars for ritardando or some other purpose and pad continues to follow those bars. Some of the solution would be to import pad into a style or to stop it before or in the middle of the ending.

[Simon]

I did had the PA 800 for a year. During that time it freeze from time to time. I sold it because I could not rely one hundred percent on it. I loaded No extra styles or anything and just played in a disent way. But now I wonder to buy a new because I do miss some great styles and the sound was just fantastic. So my question is whether this problem still exist? And one thing,,the pads. I use them with styles, but when I hit endings the pad keep on playing. Why didn`t it stop along with the styles?

The freezing problem is still there and shining like a BIG star in the sky and it shines even more during a live gig when people are dancing!!! Good Luck

[macboy]

Let's not get into a freezing discussion again.

1. There are people with freezing issues without their fault.
2. There are people with freezing issues it's their own fault.
3. There are people with no freezing issues.

Before you are sure which one you are it is not necessary to state it everytime i think ?

[Simon]

Let's not get into a freezing discussion again.

1. There are people with freezing issues without their fault.
2. There are people with freezing issues it's their own fault.
3. There are people with no freezing issues.

Before you are sure which one you are it is not necessary to state it everytime i think ?

macboy,, since you sound like you actually know what you're talking about...Can you please shed some light on this issue..Even after 25 years of using MANY different keyboards only one time that I came across this kind of problem "GEM3" and that was an easy fix....I'm STILL learning... especially from the pros. I'm sure many other musicians here just like me who would like to learn too.

What do you mean...

1. There are people with freezing issues without their fault.<-- How is that possible?
2. There are people with freezing issues it's their own fault.<-- Can you explain more maybe?

Thank you for your time.
Simon

[karmathanever]

Hi Simon

I think macboy is pointing out that some "freezes" are caused by the user loading corrupted SETs, samples, incompatible files etc... (i.e. user fault) and other freezes may be due to an actual keyboard fault (i.e. Korg hardware/software fault).

If you look back through the forum, there are a lot of posts about "freezing" - you may get some clues to help you...

Good luck

Pete

[Simon]

Hi Simon

I think macboy is pointing out that some "freezes" are caused by the user loading corrupted SETs, samples, incompatible files etc... (i.e. user fault) and other freezes may be due to an actual keyboard fault (i.e. Korg hardware/software fault).

If you look back through the forum, there are a lot of posts about "freezing" - you may get some clues to help you...

Good luck

Pete

Thanks Pete,

Simon

[Rob Sherratt]

Simon,

As you know, I spent considerable time liaising between you and Korg using confidential contacts which developed while making the "Arranger Secrets" DVD's. I passed your .BKP file to Korg for analysis (at Korg's request). Their labs reported back the following which I forwarded to you:

"No software fault has been found by Korg apart from data corruption on your machine.

The probability is that your Pa800 freezing problem is due to faulty sample RAM. You need to reset your Pa800 to a known initial state with no user data or samples on it, and then do the check for faulty sample RAM as described on Korg's web site.

See the thread re Tamimq's freezing problem, eventually traced to faulty sample RAM after Tamimq reset his keyboard to its initialized OS1.60 state. "

You then sent me two PM's containing expletives and other sarcastic remarks directed at me personally, and in the second PM you accused me of being a "Korg Rep" which I am not. Personal attacks like that were completely unwarranted after I had assisted you as best I was able.

Continuing with your childish rants and raves about it on the forum will not solve the data corruption or faulty sample RAM problem on your Pa800. The only thing that will fix the problem is if you do what Korg said and probably get the sample RAM changed at a service center. For some reason Tamimq's faulty sample RAM did not show up until after he had reset his keyboard twice. The first time he did it, the sample RAM tested OK.

I hope you grow up one day soon.

Rob

[macboy]

Rob bad news to see people reacting to you in that way when you are spending free time and effort to help them out !

Maybe you know how I felt some weeks ago when people accused me of being a Korg respresentive

@Pete: thanks for reacting to my post of Simon.

I indeed meant there are freezes due to hardware problems (the RAM issue) and freezes because of corrupted SET's (not direct Korg failure) and people like me with no freezes at all in 2 years and 1000 playing hours

[nikola81]

Welcome to the club
First time i joined this forum i tried to help everywhere i could and someone asked if i was working for Korg.

And as i understand, older keyboards were made with fixed memory modules and features that were checked and preset so no freezing could happen. Today every keyboard is a little computer and it could be "fed" with fault data that could lead to unwanted behavior of the keyboard.

[Rob Sherratt]

Hi Macboy and Nikola81,

Thanks!

I would not want anyone to believe Simon's assertion on this thread that there is any major problem with OS1.60 on the Pa800. There is not. Korg have previously stated that there may be a problem with sample RAM on some early Pa800's and they are fixing this under warranty at their service centers.

There may also be a fault on some early Pa2x keyboards such as my own, causing LED's to fail prematurely, possibly also causing keys to freeze out. This is still under investigation. We are collecting evidence on the forum in another thread. It is not a software fault.

The difficulty is that just because some part-time musicians are also designers and engineers by profession, people like Simon mistakenly associate us with Korg when in fact we are completely independent.

In the particular case with Simon's Pa800 problem I went out of my way to help him using some confidential contacts inside Korg labs, that were developed through making the "Arranger Secrets" videos. We all know that Korg are putting the finishing touches to the OS2 release and of course they want to make absolutely sure there is no software defect causing crashes.

So Korg kindly agreed to test the data from Simon's keyboard as he well knows. They loaded it on one of their machines which then crashed. They analysed the data in Simon's .BKP file. It turned out to be data corruption on Simon's keybord causing the "freezing" problem, and there was no defect in OS1.60.

My opinion is that Simon does not want the hassle of sorting his Pa800 data problem himself and working out which .SET of .BKP file(s) or maybe even the sample RAM have been causing the corruption to occur.

So it's become everyone else's problem - Simon chose to ignore the feedback from Korg that I forwarded to him, and he blames Korg for the problems. He posted in this thread that there is a major defect in OS1.60 when in fact he was previously given the evidence that there is not, and he sent crude and offensive PM's to me assuming I work for Korg etc.

I replied politely to Simon after I received the first message giving him a chance to apologise for his crude and ignorant communication. And for my part, it's not too late for an apology from Simon even now. In the hope of receiving an apology I have not yet published the offensive PM's that Simon sent to me.

Anyway regardless of whether Simon wishes to behave in an adult manner or not, I mustn't let one bad apple spoil the feast. Sorry to bore everyone else with the dirty laundry.

Best regards,
Rob

[nikola81]

Maybe we could have the people who don't have freezing problems to say how they use their keyboard, what they load, what they don't load. I believe that could be helpful.
I have to say that i had two or three freezes since i bought it in february and i use my keyboard on gigs five days a week. Two of them i don't know how happened but for the third i loaded a loop that was saved under Soundforge as Wav file not windows but as Scott studios wav (it was done in a rush and i didn't notice). That caused a keyboard to freeze and it was better after erasing that grove. So be careful what you load, if some colegue gives me his set i make sure that is for pa800 and ask for the sw version just in case.
Hope this helps.

[Rob Sherratt]

It's been said many times before on other threads, but these are some of the things that always cause data corruption / lock ups:

.BKP files of any kind from different OS/ keyboard
.SET files containing GLOBAL or SONGBOOK from different OS/ keyboard

[nikola81]

I wouldn't recommend using .BKP files and erasing factory styles. There is plenty of places in user and favorite banks (and even loading a spare bank wouldn't take much time). If it goes like this we gonna have more sw uptades and anyway we can't use .bkp files from different version.
Don't load global (even from a same keyboard), this messed up my global preferences when i forgot to save them. I had to do whole setting again.

[Simon]

Rob bad news to see people reacting to you in that way when you are spending free time and effort to help them out !

Maybe you know how I felt some weeks ago when people accused me of being a Korg respresentive

@Pete: thanks for reacting to my post of Simon.

I indeed meant there are freezes due to hardware problems (the RAM issue) and freezes because of corrupted SET's (not direct Korg failure) and people like me with no freezes at all in 2 years and 1000 playing hours

Rob,
are you finished attacking me?? Well here's a copy of our pm's so everyone can read what actually happend..

This was from you...


No software fault has been found by Korg apart from data corruption on your machine.

The probability is that your Pa800 freezing problem is due to faulty sample RAM. You need to reset your Pa800 to a known initial state with no user data or samples on it, and then do the check for faulty sample RAM as described on Korg's web site.

See the thread re Tamimq's freezing problem, eventually traced to faulty sample RAM after Tamimq reset his keyboard to its initialized OS1.60 state.

Best regards,
Rob


Thia was my reply.... Where do you see me

Are you convinced? LOL ....So my keyboard and the "new keyboard" and the rest of the people on here and other websites also have a problem in their sounds / samples....... I am convinced in one thing only is that KORG don't give a s**t about this keyboard anymore and their attention on the new keyboards only.......... and f*ck whoever with PA-800 it's an old keyboard anyways....
Thank you.
Simon

and this was your reply


I won't respond to the sarcasm and bad language you directed at me. It's uncalled for.

Goodbye
Rob



Well I'm sorry,,,THIS WAS DIRECTED to KORG and NOT YOU!! unless you are a KORG Rep...

I spent many nights working on this and I told you that I did what KORG wanted me to do and I have the private e-mails to prove it!!!

Never mind,, from now on I won't even reply to anything you say.I don't need anyone to tell me to grow up and certainly NOT YOU...