RPPR bug in Setlist within 2.0.2

[TonyP66]

I am using songs with RPPR functionality in my playlist. Before when selecting the right song in the playlist, the RPPR triggers are working fine. Since 2.0.2 I have to switch to SEQ mode before the RPPR triggers are working. Has this behavior been changed on purpose or is it a bug? For me it is unwanted behavior.

[Steve Pavao]

Hi Ton,

In 2.0.2, the following bug was Fixed:

(from the 2.0.2 Release Notes):

"After adding a Song to a Set List, triggering RPPR may not have worked. This has now been fixed."

Perhaps there was an unintended side effect of this fix.

I will PM you so I can get your files and try to recreate your problem.

- Steve Pavao
Korg R&D

[TonyP66]

Thank you Steve. This is so great that you are on top of it and even in your spare time are trying to help and investigate issues. Kudos for you and your colleagues on the forum!

[Steve Pavao]

Got the files. Will look into it soon.

- Steve Pavao
Korg R&D

[John Hendry]

This is one reason beyond sounding better why I believe Korg is way ahead of Roland and the other electronic keyboards....and hand drums. It takes time and a great deal of effort to make such progress and this type of product support working with customers, as well as supporting this fourm, is very unusual.

What other Company the size of Korg communicates directly with it's customers......publicly? That spells confidence and good will on behalf of Korg IMO. It's easy to get spoiled and forget what is required to survive in the business world. Korg does it by getting involved in the real world and breaking a few rules here and there to do so. Korg is a leader because it doesn't follow normal business practices of the crowd. You can generally understand the manual too and that helps but the video manual that came with the X is really a great idea to expand upon because it gets past vocabulary interpretation and you can see what Korg is talking about doing.

John^^

[TonyP66]

Yesterday reported the RPPR bug, yesterday evening already an easy workaround. The bug is not fixed but the workaround makes is so good that by using this, I in no way am affected by the bug.

In short, this resolved the issue for me:

Go into the song and set the Track Parameter->MIDI-> MIDI Channel for Track 1 to the value 1.

Just for your info, my global midi channel is set to ch2.

Thank you Steve Pavao and all at Korg making this product better every day!

[Rigel]

Wow..! I never could have thought a company like Korg might exist. Customer support on this level... Wow! again..
(I'm a new Korg user by the way...)

[danmusician]

Wow..! I never could have thought a company like Korg might exist. Customer support on this level... Wow! again..
(I'm a new Korg user by the way...)

Which is why some of us have felt compelled to defend Korg against some of the hysteria on this board when an issue arises.