Cool - would love to know how/why etc - we need MIDI implementation manuals!!!newkorgguy wrote:I can confirm that it worked on my Kronos X (SOLD) and Pa3X
If i transpose Pa3x -1, Kronos X Global will show -1 for transpose as well
Pete

Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Cool - would love to know how/why etc - we need MIDI implementation manuals!!!newkorgguy wrote:I can confirm that it worked on my Kronos X (SOLD) and Pa3X
If i transpose Pa3x -1, Kronos X Global will show -1 for transpose as well
I am trying to find Pa3x somewhere near me to try it with Kronos....we have confirmation that it works on M3 ,Fantom G6,Triton Le,Tr...it's not important just for Kronos Users,definitely Pa4x is sending bad parameters we can all see that....Nemik wrote:Is only one way to find outkarmathanever wrote:
I don't think PA1/2/34X to Kronos would ever work.![]()
We need to find someone who own Pa3x and Kronos and test it.
Personally for me this function is useless, I'm from group people who don't transpose keys, I play in scale whatever is, no need to transpose, but many people love transpose and since was working on Pa3x I think is no harm to make work on Pa4x.
I am more concern if midi out chord is sending like they say in manual:or still like in Pa600 is sending only notes (by passing) from keyboard before Chord Recognition engine.Chord
Use this channel to send notes recognized by the Chord Recognition
engine to the MIDI OUT or USB DEVICE port. This is useful, for example,
to control an external Harmonizer playing on the Lower part
(even if the part is muted).
This in my opinion is very useful function to work with 2-nd keyboard.
Was be perfect if is working on Chord Sequencer too, could have free hand and still sending chords to external arpeggiator.![]()
BTW, can somebody check on this???
first byte of SYSEX Message is always F0 (Sysex start), last one is F7 (Sysex End), but second byte is Manufacturer id, so means messages can looks different from different devices, but receiver is recognize them and translate.karmathanever wrote:
I am happy to be completely shouted down here but I cannot understand how master transpose changes on one keyboard can change the master transpose on another unless they BOTH recognise the same SYSEX message structure.
Cheers
Pete
There is nothing to laugh.musiccankill wrote:I had the same reaction too but i had to answer!karmathanever wrote:(Cisco vs Korg ??????????)
This seems to be something to laugh. Why are we in a hurry? Pa4x should be bought in 2017 ..... when all the customers did their job as beta testers (and you have to pay 3800$ to do this).Bescki wrote:I have concert tonight after 30 minutes. My pa4x stuck on boot, cannot boot. How a new keyboard can have this problem. If cannot boot i will have really serious problems with organizer. I hope it wont happen to someone else...
I tried to re update the system, but after update again stucks on boot.[/img]
cisco os is named IOS... as far as i know, apple bought the right to name their os from cisco....musiccankill wrote:Hello!
Maybe you wanted to write APPLE instead of CISCO (by reading about IOS now).
And yes apple does a bit better job but it is a way bigger company and they still have many bugs, but you are not a programmer for IOS apps i suppose so you will never find them out!
If bugs didn't exist on their IOS, updates wouldn't come one after the other...
Korg at least always listen to their customers but this time it has gone out of control and they have to do something really quick about it..
I think they put all their effort to implement compression on the new cpu/dsp and add again the other functions that users wanted to support them and this way they got more bugs added in..
They should have first finished with the old bugs that had already been found and then add new functions..I am very positive that the next update will fix most of the problems as now there are no more functions to be implemented..Maybe they fix the compression problem for the users that had already made their set with the decompression of the old os..
We will see!