Serious system bug on the PSR SX900 causing it malfunction

[beloncfy]

https://youtu.be/K9tuimy-KqU

My SX900 is running the latest firmware which is v1.11

The test registration at here, simply copy to the USB drive and open it.

https://drive.google.com/file/d/1I1QLculORckhH28bljzUweivL1foMxyG/view?usp=sharing

I have set right 3 split point with harmony in my registration.

To trigger this bug, simply play multiple keys simultaneously on the split key for a while like what I did in the Video.

[mikf]

?
I can trigger a bug in my  car if I brake and accelerate simultaneously while trying to operate the electric seats, and put the windows up and down all while all while playing the cd player at full volume. The bug manifests itself as a - voice which sounds just like my wife - saying ' what the hell are you doing'. 🤓😏
Mike

[DrakeM]

So you just need to move the split point or play in a different key and then transpose to your desired key of choice. It is a simple fix.

Drake

[ChrisH]

Wow ..I now remember why I sold my SX900 and got a Tyros ..those clacking keys are as bad as mine were!!!  Yep Drakes solution is fairly obvious!!  Maybe move the split point and do another video ..I'm curious to know what that song was??  Purely out of interest!

[beloncfy]

?
I can trigger a bug in my  car if I brake and accelerate simultaneously while trying to operate the electric seats, and put the windows up and down all while all while playing the cd player at full volume. The bug manifests itself as a - voice which sounds just like my wife - saying ' what the **** are you doing'. 🤓😏
Mike

This is only the demonstration to reproducing the error. I did use this registration and play a song properly across the split point and the error was prompted too, that is the reason why I have discovered this.

[beloncfy]

So you just need to move the split point or play in a different key and then transpose to your desired key of choice. It is a simple fix.

Drake

Actually I use the split point in purpose for 2 different voices in a registration. Only the first registration with right 3 split point having this error.

[beloncfy]

Wow ..I now remember why I sold my SX900 and got a Tyros ..those clacking keys are as bad as mine were!!!  Yep Drakes solution is fairly obvious!!  Maybe move the split point and do another video ..I'm curious to know what that song was??  Purely out of interest!

The split point for presenting 2 different voices in a registration so that I don't need to use another registration or OneTouch button for voice changing. The arrangement of this song is quite complicated overall. I'm still working on the front part and meanwhile has encountered this unexpected error.

This is El Dorado by Thomas Bergersen, below is the link of the current progress that I have done on my PSR SX900 at the moment, still need to work on the ending , more tuning and amendments. Just share for your preview.

(Arranged and Performed by myself on the PSR SX900)
https://drive.google.com/file/d/1CBzzuFDjDA1OsCtHKjaFaUeCfhdi1tyr/view?usp=drivesdk

[Amwilburn]

Don't mind them, Belon; discovering & documenting a reproduceable crash is actually pretty difficult. Yes, it looks like you're trying to crash the system, but that's exactly what Q/A bug testers are supposed to do before product launch

I've been absolutely slammed this weekend, but when I get a chance i'll download your reg and take a look at it; but just FYI I've had weird crashes and behaviours when programming registrations myself (going all the way back to 2005, CVP309 and Tyros... whenever yamaha switched to persistent memory. Before this, when you switched off the keyboard? When you turned it back on again all registration slots were blank -- if you didn't save your work, you were SOL) and sometimes it was because of lost memory (every memory allocation is supposed to have a destructor, but obviously we as humans miss some, and in a nutshell that's why you need to reboot your PC every day or so).

In other words, when I had weird crashes like that, more often than not it's because I hadn't cleared my memory; all Yamaha arrangers actually require periodic reboots (holding down the top right white key, usually c, while booting up. Clears settings but not user files). I even had a weird panic attack once when I noticed holding a triad, one of the 3 notes would always drop out in a second. I called the repairman over (it was still under warranty) but it turns out nothing was wrong with my CVP309; I simply hadn't rebooted it in over 6 months. Since Yamaha wasn't going to cover that brain fart on m y part, I owed him a pack of beers.

ALSO I discovered that even after rebooting, if I loaded up a registration I'd created while the memory was needing rebooting? It would actually bring back that fragmented memory state.

In other words, you may need to reboot your entire keyboard as I've mentioned above, and then instead of loading your registration to correct it, write down all the settings and simply create a new memory registration (which you can then use to overwrite that one saved registration on your existing file) and see if the problem persists. Obviously save the new registration bank as v2, etc. So that you can go back and compare with the potentially corrupted one.


Yes, this took me a while to figure out back in the early 2000's. Hope this helps.

Excellent playing and arranger as usual, m8!!!

Mark

[beloncfy]

Don't mind them, Belon; discovering & documenting a reproduceable crash is actually pretty difficult. Yes, it looks like you're trying to crash the system, but that's exactly what Q/A bug testers are supposed to do before product launch

I've been absolutely slammed this weekend, but when I get a chance i'll download your reg and take a look at it; but just FYI I've had weird crashes and behaviours when programming registrations myself (going all the way back to 2005, CVP309 and Tyros... whenever yamaha switched to persistent memory. Before this, when you switched off the keyboard? When you turned it back on again all registration slots were blank -- if you didn't save your work, you were SOL) and sometimes it was because of lost memory (every memory allocation is supposed to have a destructor, but obviously we as humans miss some, and in a nutshell that's why you need to reboot your PC every day or so).

In other words, when I had weird crashes like that, more often than not it's because I hadn't cleared my memory; all Yamaha arrangers actually require periodic reboots (holding down the top right white key, usually c, while booting up. Clears settings but not user files). I even had a weird panic attack once when I noticed holding a triad, one of the 3 notes would always drop out in a second. I called the repairman over (it was still under warranty) but it turns out nothing was wrong with my CVP309; I simply hadn't rebooted it in over 6 months. Since Yamaha wasn't going to cover that brain fart on m y part, I owed him a pack of beers.

ALSO I discovered that even after rebooting, if I loaded up a registration I'd created while the memory was needing rebooting? It would actually bring back that fragmented memory state.

In other words, you may need to reboot your entire keyboard as I've mentioned above, and then instead of loading your registration to correct it, write down all the settings and simply create a new memory registration (which you can then use to overwrite that one saved registration on your existing file) and see if the problem persists. Obviously save the new registration bank as v2, etc. So that you can go back and compare with the potentially corrupted one.


Yes, this took me a while to figure out back in the early 2000's. Hope this helps.

Excellent playing and arranger as usual, m8!!!

Mark

Hi Mark,
Thanks for your precious experiences, by the way, the SX900 is my first arranger keyboard and I'm lack of experience about dealing with those "fancy bugs" around it.

I guess Yamaha has already abandon the PSR SX series since the next gen is coming soon, my friend had discovered several bugs and reported, but no update from Yamaha too.

Yamaha isn't as good as Apple, Microsoft and Google in term of software development, sadly we really can't expect Yamaha to provide equivalent firmware update and patches as them as what I'm expecting. Eventually we have to live with all of those bugs and try ourself to avoid it as possible.