Korg Forums

Hi guys

Think I've figured it out.

It seems that Korg have set all the "sequence" PADs to the sync setting "Continue" and it should be "Beat"
Just edit a Sequence Pad and change that setting and it all works fine.

Hopefully Korg will change that default setting for the PADs and supply an update.
Alternatively, we can go in and change them all ourselves.

So if you have a few specific PADs causing you the problem, just edit them and change the SYNC setting to "Beat"
That'll solve your problem in the short term.

Hope I'm right and hope this helps.

Cheers

Pete

Hi Pete,

Sorry to disagree, that does not fulfill the right functions of the Continued and Beat intentions and/or needs.

Regards

Hi Ova

Thanks for responding and I may be wrong about all this.

I do understand the differences between the "Continue" and "Beat" and these work correctly according to the manual however there is no support or description (in the manual) for when you start a PAD before the style - I'd like to know what Korg's expectations would be when doing that. Everything in the manual assumes you start a PAD whilst playing the style.

Changing the PAD sync to "Continue" does at least get the PAD in "timing" sync when you play "PAD then style". It might not be 100% suitable but the PAD will be in time with the style.

If "Beat" started the PAD at the corresponding "measure-tick" then I think that is what is being requested.

I am still puzzled why one would start a PAD and then the style putting up with the PAD "restart" disruption (from a musical point of view).

Just trying to hep here as I know we all have different needs.

Wish I had a version 2.0 next to me to try this but as yet, I'm not going back.

Cheers

Pete

Hi Pete,

Depending on one's needs, what you suggest might do the job, at least temporarily.
The way I use the pads are as follows. If the style is on, and I need a pad to merge in anywhere in the time frame, I'll use a Contined Pad. However if I need a pad that must start at the beginning of the next bar, I'll use a Beat Pad.

Now for other scenarios such as an intro where the singer sings on a guitar or a piano chords, I use pads to do the background and fill up with other sounds on the right hand. And where the rhythm starts, in that given song, I need the style to sync exactly with the pads, but in this case the style's start point has to dominate since I have to follow the singer, and not always are they on time, even micro seconds can and will sound out of beat, as it is right now.

I really hope Korg will fix this issue with V3, it wasn't the case with V2.

Thanks again for your inputs.

Avo

ova wrote:Hi Pete,

Depending on one's needs, what you suggest might do the job, at least temporarily.
The way I use the pads are as follows. If the style is on, and I need a pad to merge in anywhere in the time frame, I'll use a Contined Pad. However if I need a pad that must start at the beginning of the next bar, I'll use a Beat Pad.

Now for other scenarios such as an intro where the singer sings on a guitar or a piano chords, I use pads to do the background and fill up with other sounds on the right hand. And where the rhythm starts, in that given song, I need the style to sync exactly with the pads, but in this case the style's start point has to dominate since I have to follow the singer, and not always are they on time, even micro seconds can and will sound out of beat, as it is right now.

I really hope Korg will fix this issue with V3, it wasn't the case with V2.

Thanks again for your inputs.

Avo

+1

Thanks Avo

Am fully understanding this now.

Pete

karmathanever wrote:Thanks Avo

Am fully understanding this now.

Pete

I have the same use case als Avo. I often start pads like "gtr. steel str." before starting the style. this is an excellent opportunity so start "small and soft" when singing. Sync does not work! The next massive bug.

Yes, I now understand but I also do exactly the same - start songs with just gentle PADs and then bring in the style - I guess I have never brought in the style "out of time" with the PAD so never noticed this.

My work around (changing the sync parameter) will fix this temporarily but the PAD will still not sync to the exact same "tick" within the style's measure (per the manual's terminology) but it will be in time with the style.

Hopefully this will get resolved for you.

Cheers

Pete

Video solution of pad bug


<iframe width="560" height="315" src="https://www.youtube.com/embed/A_y80m59luo" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture"></iframe>

Well done and thanks ebuzer52 for putting my suggestion into a video - I'm sure this will help others get through their gigs etc without any worry of out-of-sync disasters.

It's a shame that there is no PAD editor to do this for multiple "sequence" PADs


Take care

Pete

karmathanever wrote:Well done and thanks ebuzer52 for putting my solution into a video - I'm sure this will help others get through their gigs etc without any worry of out-of-sync disasters.

It's a shame that there is no PAD editor to do this for multiple "sequence" PADs


Take care

Pete

Dear Karma;
if I need to tell the truth, I learned this from a friend from Armenia on the first day, but your determination cannot be denied. in this sense I respect you forever. You are our King brother

https://www.youtube.com/watch?v=UP9vv1uzlZE

That's the real problem with Pad Sync.

why korg does not listen and solve the problems of its users??
I use the keyboard 100% of its potency in style play mode and I need it to work. It does not interest me if advocates find solutions to problems. The solution to this "professional keyboard" is to have no problems and be solved as quickly as possible.

not to mention other serious problems that affect the performance of musicians who make this their profession.

Korg pa3x please come back.

Actually it was me who suggested the fix from the beginning. Check the original post. You're welcome

Any news about whether the new v3.1 has addressed this or substituted new factory resources with the ‘Beat’ setting restored as default?

Any news about whether the new v3.1 has addressed this or substituted new factory resources with the ‘Beat’ setting restored as default?

Update and try it...