Restart again with OS 3.1

korg1 · Post by **korg1** » Tue Jul 16, 2019 10:04 pm

I experienced a pa4x76 restart twice today.

I perform 6times/week since April and after going back from OS3.01to Os3.0 i only had two restarts total.
After updated again to 3.1 it worked great till today.

The first time i had just edited a style,changed some instruments /mix etc and re-saved it,but i wanted to make sure that my songbook entry for that style didn't have some other settings,so while in songbook mode i chose that entry--->Write--->pick up the style again and when i pressed write ,the keyboard restarted.

The second time happened like this:

I went for a gig
i start up pa4x and pressed songbook.
Right when i chose a SETLIST ,pa4x restarted....Did i caused it by pressing fast?maybe,i don't know.

Can't reproduce it again,but this time it has either to do with songbook,or pa4x's processor,or the ability to handle Direct set from ssd.

I send a message to Paolo ,but to be honest,i don't believe this problem is 100% solved ,i just hope Korg will start searching it again after Os2.2 ,then everything worked better....

Korghelper · Post by **Korghelper** » Wed Jul 17, 2019 12:12 am

Try experimenting with super fast button pressing and slowly repeating the exact same steps once you get a crash.

Any difference?

If we can pin it down to rushing the OS, at least you have yourself a temporary fix (press slower!) and might have given Korg an important clue. There’s a chance that you have started to work faster since OS2 due to greater familiarity, and there’s a chance that the more complex OS3 needs longer to perform the same tasks it did easily in OS2. Maybe both!

A bit of testing might go a long way. Sometimes you can repeat the same steps and get different results unless repeated at the same pace. This can make a problem seemingly more intermittent and frustrating. If you can repeat an error by repeating the speed when you repeat the steps, you are that much closer to a fix!

Asena · Post by **Asena** » Wed Jul 17, 2019 12:40 am

Guys Im sorry but there is a troubble on this,
I had this for 30
minutes back!

After having 4x on, like 2 hrs, ı was editing style,
And it started.
İ will upload it to Korg italy team with set file and video.
Hope that this helps.
Again , realy sorry,

Aripearlmusic · Post by **Aripearlmusic** » Wed Jul 17, 2019 6:04 am

I have noticed that OS 3.1 is slower than 3.01 but my 4x76 has never restarted and hasnt frozen since the week before OS 2.2 came out which also was the last time i had any 3x sounds and undithered 16bit samples (converted from 24 and 32bit) loaded and i rarely use loops in styles but i also check to make sure the sample count matches the exact tempo so it doesnt stress the DSP. Im sampling and programming about 12 hours a day so if it was the OS it would have happened to me already.

korg1 · Post by **korg1** » Wed Jul 17, 2019 7:35 am

Not really,if you don't use certain options,like songbook, Direct set,style editing,loops,sequencer,songplay mode,mp3,mid etc.

If you only load samples and sounds once,probably it will never happen to you,but if you use it extended,i believe you will .

Aripearlmusic · Post by **Aripearlmusic** » Wed Jul 17, 2019 7:49 am

I have been doing 16 track midi editing with several control change and program change events, style editing with 16 measure and 32 measure patterns, sequencer with recording filtering in real-time, i use songbook just for pulling up the music score in my notation app and for alternate keyboard sets. Mp3 playback is probably the only feature i almost never use

korg1 · Post by **korg1** » Wed Jul 17, 2019 8:00 am

You can try out to work with setlist on songbook and with Direct sets (songbook too) and see if you will notice something.

I don't want to blame Global settings or MAXX presets,i still believe it has to do with processor,usb ,HD and songbook

Aripearlmusic · Post by **Aripearlmusic** » Wed Jul 17, 2019 3:33 pm

It would 100% be direct set related if there is any kind of problem with the USB port or the flashdrive being used or data corruption in the set like if songbook is trying to load something that isnt there or if that set was made on OS V1 or 2 and using one of the sounds/styles/keyboard sets thats in a different order now

korg1 · Post by **korg1** » Wed Jul 17, 2019 4:02 pm

No, i did a brand new direct set and songbook from scratch while i was on v3.0 and it is located on my internal SSD Samsung Evo 250Gb .

As you can see i tried to cover every posibility of faulty usb or HD by replacing the factory Philippinese Toshiba drive with an ssd.

Also most of the styles ,even factory ones i use are copied to direct set,so almost all my songbook entries point to Direct set .

Aripearlmusic · Post by **Aripearlmusic** » Wed Jul 17, 2019 5:32 pm

Do any of your styles include control changes and program changes that were done in a DAW that may not be doing what they should be on the corresponding channel on the keyboard?

Have you tested the styles loaded directly instead of in the direct set?

If you are using samples and loops have you already gotten rid of any corrupted samples or improperly sliced loops if there are any?

If you do use loops have you tried slicing them further so you can put them into a drum kit and program that way instead?

Are any of the styles attempting to load non-existent keyboard sets or keyboard sets with sounds that have since been deleted or sounds with samples that are missing?

Have you defragmented your SSD and or checked the SSD for errors?

Did you format the SSD on the keyboard? Has the keyboard ever restarted while recording on to the SSD or while saving anything to the SSD?

Do you use a Mac and enable disc access? Macs filing system with their stupid file and folder shortcuts is notorious for corrupting disks and causing read/write errors for any other system

korg1 · Post by **korg1** » Thu Jul 18, 2019 5:45 am

Why does it feel like I'm living in déjà vu?

-Yeap, styles are ok ,

-Korg claims they eliminate the possibility of loading corrupted samples

-No sliced samples with that set, i want to use mostly factory recources on purpose .

-Keyboard sets are fine ,some are on the fly just for songbook entries,nothing is missing

-SSD is defragmented and checked for errors

DID I MENTION THAT MY FIRST EVER RESTART WITH V3.01 WAS WITH JUST ONLY FACTORY RESOURCES ,NO EXTRA STYLES OR SETS LOADED ,OR ANYTHING ELSE ATTACHED ? (i.e Direct set or usb controller)

Also,as i said, the second time,the restart happened when keyboard powered up ,and i just selected a Songbook Setlist....didn't even select any Style or sound .

Aripearlmusic · Post by **Aripearlmusic** » Thu Jul 18, 2019 6:10 am

Have you checked the flex cable connecting your SSD to make sure that it is secure?

korg1 · Post by **korg1** » Thu Jul 18, 2019 6:30 am

Guys Chill out plz,

If i was the only one with restart problems,then we could discuss these options,but it's not just me....

That means either problem with OS,or korg's parts like flex cables are massive faulty.....i believe first scenario.

AntonySharmman · Post by **AntonySharmman** » Thu Jul 18, 2019 9:38 am

korg1 wrote:-Korg claims they eliminate the possibility of loading corrupted samples

Don't be so sure about that !
No matter of whatever Korg claims , when you load SET in all mode , samples container is loaded untouched with all samples contents
valid or not , Linux system just copy and paste PCM file in this case and the only way for system to test samples or multisamples
integrity is to separately load SOUND banks or standalone SOUNDs.
If you open a faulty SET and load only PCM file , then after exploring samples you will see all samples with same order including
gray/invalid samples ... just copy & paste in Ram procedure !

I keep on shouting it since 10 years for all PaSeries that this is the only way to discover what is wrong with your SET, especially
DK banks and Sound banks containing time sliced samples.

On the other hand Aripearlmusic has made a good point in some above observations.

Aripearlmusic · Post by **Aripearlmusic** » Thu Jul 18, 2019 5:54 pm

If the restart is only happening to those using direct sets and even then only to some it would point to the flex cable going to either the hard disk/ssd/ or USB ports and would explain why it never happened to me also and here is why: Flex cables and other connections can loosen or get dislodged depending on the care of whoever is moving the keyboard and how often and whether the roads you are driving on are properly paved something as simple as a pothole can dislodge a wire. My keyboard stays in the studio basically all the time so it is rarely moved but I open it up every few months to check all the connections and give it a cleaning.

If the restart happens due to power instability that would also explain why it has never happened to me. I did all the wiring to all the outlets in my studio and perform regular power stability tests on the outlets.

With regard to faulty samples or sets there are a few combinations of sounds that when put with all 4 inserts and 3 master effects are using the entirety of the DSP to the point that the sustain pedal doesn't even work reliably so if you add a heavily sampled sound on top with 24 oscillators and three particularly heavy effects you can almost certainly crash the DSP. Add direct set into that and you have a DSP Crasher trifecta.