Hi,
This is about Pa4X version 3.1.0.
I notice recently in Style mode, some of my user style's Tempo change randomly when switching between them. This could happen with any user style.
I never had this kind of problem under version 2 for the years I am using the Pa4X.
For example I am playing and switching back and forth between two Style #1 Tempo 125 and Style #2 Tempo 115.
And suddenly Style #2 take the tempo of the Style #1 to 125 or vice versa, weird!
This happened 3 times so far. I did Factory Restore and loading my set but apparently it's not fixing the issue.
Has someone experienced this kind of problem?
Thank you
Tempo Change randomly under v. 3.1.0 problem
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
- AntonySharmman
- Approved Merchant
- Posts: 3741
- Joined: Sat Oct 16, 2010 2:24 pm
- Location: Hellas
- Contact:
- As first be sure that speed dial switch is not temporary assigned to tempo value on screen , try switching styles again and then check if speed
dial is changing values by itself only under vibrations of control panel surface , in this case it has to be repaired.
- Digging deeper , switch between factory styles after factory restore and before loading your existing SET , to see if this happens there ,
if not then nothing to do with OS version & System !
- Now in case of PCG invalid source code (migrated styles of older Pa models) , adjust proper tempo values per conflicting style and re-save
"current style preferences" for each style.
- If this will fail to restore tempo of styles then enter in record mode and re-save those styles with proper tempo.
If all above fail , I see no other option IMO due to recover your custom PCG entries errors.
Hope this helps
dial is changing values by itself only under vibrations of control panel surface , in this case it has to be repaired.
- Digging deeper , switch between factory styles after factory restore and before loading your existing SET , to see if this happens there ,
if not then nothing to do with OS version & System !
- Now in case of PCG invalid source code (migrated styles of older Pa models) , adjust proper tempo values per conflicting style and re-save
"current style preferences" for each style.
- If this will fail to restore tempo of styles then enter in record mode and re-save those styles with proper tempo.
If all above fail , I see no other option IMO due to recover your custom PCG entries errors.
Hope this helps
Music Conductor - Sound Engineer & Developer - Automotive SMPS/RF R&D - Electronics Engineer
Keyboards : Steinway-D, Kronos X, Pa5X 76, Pa4X 76, Montage M7 , Roland-XV88, Emu3,Emax II, Synclavier II , Yamaha DX Series, ΟΒ-8V

wavesΑrt official webpage - KorgPa.gr
DEMO's Playlist - WavesArt Facebook
Keyboards : Steinway-D, Kronos X, Pa5X 76, Pa4X 76, Montage M7 , Roland-XV88, Emu3,Emax II, Synclavier II , Yamaha DX Series, ΟΒ-8V

wavesΑrt official webpage - KorgPa.gr
DEMO's Playlist - WavesArt Facebook
I did all above troubleshooting but unfortunately it happened several times so far.
Yesterday it happened again during a gig with a Factory style that I copy/pasted in User area.
So I decided to report it back in case somebody else has experienced the same problem.
I maybe wrong but I was thinking if the problem could be hardware/software aging?
I am aware of hardware aging (logical) but how about software aging? Does it even make any sense?...
I've never had this kind of issue with my Pa4X before, it was rock solid and I did lot of gigs with confidence with it since 2016.
Personally I suspect the issue could be in Users/Favorite area design.
What's your opinion?
Yesterday it happened again during a gig with a Factory style that I copy/pasted in User area.
So I decided to report it back in case somebody else has experienced the same problem.
I maybe wrong but I was thinking if the problem could be hardware/software aging?
I am aware of hardware aging (logical) but how about software aging? Does it even make any sense?...

I've never had this kind of issue with my Pa4X before, it was rock solid and I did lot of gigs with confidence with it since 2016.
Personally I suspect the issue could be in Users/Favorite area design.
What's your opinion?