Page 1 of 2
Any new PA2X OS Version???
Posted: Thu Sep 17, 2009 3:28 pm
by dimitris
Hello, KORG???
It's been a long time since the release of the last OS Version!!!
Regards,
Dimitris
Posted: Thu Sep 17, 2009 4:22 pm
by karmathanever
Hi Dimitris
Ignoring the ever growing "
wish-lists for new free features", this OS is pretty stable - I am not encountering any bugs or functions that do not work, so I guess Korg are able to focus on the new Kordya
Were you hoping for some fixes?
Cheers
Pete
??
Posted: Thu Sep 17, 2009 4:28 pm
by duby2
I would love to see some new thing for the os system for the pa XXX.
some new repackaging of sets of styles .
But its just about time for korg to stop doing update on the pa keyboards . if we all make it to operating system version 3.0 I would be happy but korg always stop at 3.0 and then comes out with a new keyboard , all the korg keybaord arranger I have own at one time or the other this is what i found to happen ,, just look at the discontinued products line , there you will fine the OS version and were they stop , and by the way , korg has put there each keyboard preload data out there too,, i have down loaded them all .. and unzip them , you will fine some ( maybe ) new old styles there and some demo songs ,witch were use in some of there styles.. its all good ..
and once again .. Thank You KORG for you hard work ...
fix this
Posted: Thu Sep 17, 2009 4:41 pm
by duby2
yes someting need fix
in the preferences : track settings : global song play setup ..
you can pick , melody track , drum, bass, and harnony track .
if you pick harmony track and set it to anything but global or ( when it on global ) the voice processor preset page that has the Latch on/off will work ...
if you set the global song play set , to any track number the the Latch on/off will not work ,in gray out ,, . so when i pick a track for the harmony , I then lose my Latch on/off ... to me it look like a easy fix .. for OS 2.02
Posted: Thu Sep 17, 2009 8:04 pm
by Asena
Sometimes the potansiameters dont work until, you make max volume and take it down , ITS A BUG!
Posted: Fri Sep 18, 2009 3:05 am
by karmathanever
which potentiometers?
under what conditions?
curious....
Posted: Fri Sep 18, 2009 7:53 am
by ex
Korg please, I need new OS 2.02. There is still problem with sysex data transmission. When you want to send sysex data from PA 800 to another keyboard,you get no sysex data from midi out. Thanks Ex
Posted: Sat Sep 19, 2009 4:46 am
by iaoranaemaeva
karmathanever wrote:which potentiometers?
under what conditions?
When a memorized parameter value prevails over current value of the assigned slider until you move it.
Posted: Sat Sep 19, 2009 4:54 am
by iaoranaemaeva
ex wrote:Korg please, I need new OS 2.02. There is still problem with sysex data transmission. When you want to send sysex data from PA 800 to another keyboard,you get no sysex data from midi out. Thanks Ex
Consequently, it is practically impossible to use an external sequencer to send a Pa2X or Pa800 sequence back to the arranger: original SysEx data are lost
Posted: Sat Sep 19, 2009 8:12 am
by karmathanever
When a memorized parameter value prevails over current value of the assigned slider until you move it
Yes, OK.
Sometimes the potansiameters dont work until, you make max volume and take it down , ITS A BUG!
Pa2Xpro is not designed to physically move/reset potentiometers (sliders) - it isn't a bug!!
What do you want the keyboard to do in this case?
Read all sliders and then assign corresponding values? - maybe as an option?
Pete
Posted: Sat Sep 19, 2009 8:25 am
by ex
I play my midifiles with PA 800 sequencer. My old repertoire(50%) was made for Roland istrument(no arranger) and i send this midifiles from Pa 800 sequencer out to Roland and Roland play it correctly. Since OS 2.00 version sysex data are not transmitted and i think there is bug in this latest OS version best regard EX
Posted: Sat Sep 19, 2009 10:19 am
by Paolo@Korg
Pete,
karmathanever wrote:Read all sliders and then assign corresponding values?
The problem, in this case, would be that you would have a value "jump" in the mid of a performance. With volumes, this would be catastrophic. With the way volume sliders work now, changes will always be smooth, since the physical controller will not "grab" a parameter until the current value is reached.
Paolo
Posted: Sat Sep 19, 2009 11:49 am
by Lika
mr. tramannoni I sent to you a PM - did you read it ?
Posted: Sat Sep 19, 2009 2:42 pm
by karmathanever
Hi Paolo
Thanks for your confirmation -
Paolo wrote:With volumes, this would be catastrophic
Completely agree.
I was wondering how this would affect a performance and also still cannot understand why it was "requested" - I cannot figure out when/how this could be a desired feature.
Cheers
Pete
Posted: Sat Sep 19, 2009 5:49 pm
by iaoranaemaeva
tramannoni wrote:The problem, in this case, would be that you would have a value "jump" in the mid of a performance. With volumes, this would be catastrophic.
Yes,Paolo - anyway, it is the same with all non-motorized controller sliders/absolute potentiometers! I don't consider it as a bug, just gave the explanation
Thank you for your prompt response
Alain