It amazes me how long it took for this issue to come up in this forum.
I started complaining abt t from week I since a got my krnos 61.
It just sucks, any controler or keyboard attadched to it makes the pianos come alive. f*ck*ng hell.... I've tried it through a fantom x8 and a roland xp30 via midi.
It was unbelievable I paid $3.000,00 for a keyboard with a keybed as good as a casio. I also noted the sound (decay) got tighter thus making your playing cleaner. No I am not here preaching 'hey everyone let's buy a controler"... hell no, specially after $$$ we all paid.
,
Anyway..... I feel that the keys on kronos61 just doesn't respond to your playing in terms of articulation and dynamics for fast playing. I had to have velocity curve set @ 3, and I am no pianist. However this problem is not noticed if a person only plays softcock/dark classical pieces and dream of la la land .
there is something really wrong with the way the motherboard receives the info from keys.
Please everyone Pleaasee let's write to krog about this issue. When I wrote to korg USA I got a reply saying 'Please contact your local distributor!!, what a joke.
velocity curve doesn't reach 127
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
michelkeijzers
- Approved Merchant
- Posts: 9112
- Joined: Thu Feb 08, 2007 3:10 pm
- Location: Netherlands
- Contact:
I never tested the velocity values myself but I never had any problem with my velocity/dynamics of piano playing (I'm not a pianist either).
My velocity curve is just the default one and it works fine for me.
Also, the normal way is to contact your local distributor, I don't see what is wrong with that?
If there is really something wrong it is probably in your Kronos only so I can't understand why you ask everybody to write to Korg.
My velocity curve is just the default one and it works fine for me.
Also, the normal way is to contact your local distributor, I don't see what is wrong with that?
If there is really something wrong it is probably in your Kronos only so I can't understand why you ask everybody to write to Korg.
Developer of the free PCG file managing application for most Korg workstations: PCG Tools, see https://www.kronoshaven.com/pcgtools/
Michel,
Why not do a simple test to see if your kronos will transmit all 127 velocities?
I believe you are an honest guy so if you were to find everything works perfectly it would be fact rather than opinion. But! If you find you're board has difficulty reaching all velocities You could assist in relaying that to Korg just in case one day you need the full range of velocity.
There were many fanboys here that denied a keybed problem and tried to lay it off on poor technique or anything but their beloved keyboard. Korg tried to say it was less than 1% but when the fix was announced there were delays because there were so many that needed replaced the parts were back ordered. I am on my 4th Kronos 88 and while the double trigger has been fixed the inability to access all velocities is problematic.
If your playing technique only requires 1-110 that's great for you but there are times when that extra, inaccessible level, can make a difference.
From recent experience the only way to get something addressed is to have a large number of inquiries or complaints sent to korg.
I sold my Kurzweil PC2X when I bought the Kronos but in the 10 years I used it I never failed to be able to access the full range of velocities. I don't think it is unreasonable to expect a much superior product to do the same.
$3,700.00 is a lot of money to spend on a workstation that doesn't respond to velocity any better than a $150.00 Casio. I'm not trying to be mean or mouthy but I've already been through months of delays and expense due to faulty keybed design. It is a little irritating to hear similar remarks concerning this velocity issue. If this is another 1% issue it still sucks for the 1%!
Ten2One
Why not do a simple test to see if your kronos will transmit all 127 velocities?
I believe you are an honest guy so if you were to find everything works perfectly it would be fact rather than opinion. But! If you find you're board has difficulty reaching all velocities You could assist in relaying that to Korg just in case one day you need the full range of velocity.
There were many fanboys here that denied a keybed problem and tried to lay it off on poor technique or anything but their beloved keyboard. Korg tried to say it was less than 1% but when the fix was announced there were delays because there were so many that needed replaced the parts were back ordered. I am on my 4th Kronos 88 and while the double trigger has been fixed the inability to access all velocities is problematic.
If your playing technique only requires 1-110 that's great for you but there are times when that extra, inaccessible level, can make a difference.
From recent experience the only way to get something addressed is to have a large number of inquiries or complaints sent to korg.
I sold my Kurzweil PC2X when I bought the Kronos but in the 10 years I used it I never failed to be able to access the full range of velocities. I don't think it is unreasonable to expect a much superior product to do the same.
$3,700.00 is a lot of money to spend on a workstation that doesn't respond to velocity any better than a $150.00 Casio. I'm not trying to be mean or mouthy but I've already been through months of delays and expense due to faulty keybed design. It is a little irritating to hear similar remarks concerning this velocity issue. If this is another 1% issue it still sucks for the 1%!
Ten2One
-
michelkeijzers
- Approved Merchant
- Posts: 9112
- Joined: Thu Feb 08, 2007 3:10 pm
- Location: Netherlands
- Contact:
I am not sure if I can do such a test because I do not have a DAW (I must be the last person with a synth not having one).
Or can I also see it in the sequencer?
Of course I want to try it out and yes, if 127 cannot be reached that would be strange at least (and then I fully agree Korg should fix it, since at any velocity curve both 0 and 127 should be reachable).
However, vstkeys is talking about the 61 version and you are talking about the 88 version ... I know there have been (are?) issues on the 88 but I didn't know there were on the 61 regarding this issue.
I don't have my Kronos set up now but I will try to check it asap (if you can tell me how to see it in the sequencer).
Or can I also see it in the sequencer?
Of course I want to try it out and yes, if 127 cannot be reached that would be strange at least (and then I fully agree Korg should fix it, since at any velocity curve both 0 and 127 should be reachable).
However, vstkeys is talking about the 61 version and you are talking about the 88 version ... I know there have been (are?) issues on the 88 but I didn't know there were on the 61 regarding this issue.
I don't have my Kronos set up now but I will try to check it asap (if you can tell me how to see it in the sequencer).
Developer of the free PCG file managing application for most Korg workstations: PCG Tools, see https://www.kronoshaven.com/pcgtools/
Michel,
Yes, you can test it on the Kronos 61. Just record an 8 bar (or whatever) pass with one of the piano presets. Begin by playing softly and then progress to the hardest you would ever normally play. Then you can go into the MIDI edit section of the sequencer and check the velocities.
When Max at Korg USA tried it he had great difficulty reaching 127 on a 61 key. I could hear him over the phone striking the keys. He did reach 127 but only by striking the keys with a lot of force.
The velocity curves make a difference and I prefer 4 or 9 (1-3 seem to be for sledge hammer touch and 5-8 seem to lessen sensitivity way to much for me). I have the after touch curve set to 3. When I play as hard as I can I get around 112-115, but this is using much more pressure than I would ever want to play consistently with.
I would really appreciate your assistance in this as I really don't want to cause problems at all. I think the Kronos is the best sounding unit available today and I've gone through a long of trouble just to be able to use one. I think is is a much better piece than the kurzweil except for this glaring problem.
If you try to program drums from the keyboard (as I've done for 15 years) there are times you want to be able to get every aspect of a sound and I can assure you there is a difference between 110-117 and 120-127 velocity.
If I can assist you in any way don't hesitate to ask.
Ten2One
How to check:
While in sequence mode press "track edit" at the bottom of the screen. Then press the down arrow in the upper right corner, the select MIDI event edit, the Set Event Filters screen with appear, press ok. A screen with all the notes you just recorded will be there and the velocities will be at the far right. I just tried one and the velocities were 72-87 and I wasn't intentionally using light touch.
Yes, you can test it on the Kronos 61. Just record an 8 bar (or whatever) pass with one of the piano presets. Begin by playing softly and then progress to the hardest you would ever normally play. Then you can go into the MIDI edit section of the sequencer and check the velocities.
When Max at Korg USA tried it he had great difficulty reaching 127 on a 61 key. I could hear him over the phone striking the keys. He did reach 127 but only by striking the keys with a lot of force.
The velocity curves make a difference and I prefer 4 or 9 (1-3 seem to be for sledge hammer touch and 5-8 seem to lessen sensitivity way to much for me). I have the after touch curve set to 3. When I play as hard as I can I get around 112-115, but this is using much more pressure than I would ever want to play consistently with.
I would really appreciate your assistance in this as I really don't want to cause problems at all. I think the Kronos is the best sounding unit available today and I've gone through a long of trouble just to be able to use one. I think is is a much better piece than the kurzweil except for this glaring problem.
If you try to program drums from the keyboard (as I've done for 15 years) there are times you want to be able to get every aspect of a sound and I can assure you there is a difference between 110-117 and 120-127 velocity.
If I can assist you in any way don't hesitate to ask.
Ten2One
How to check:
While in sequence mode press "track edit" at the bottom of the screen. Then press the down arrow in the upper right corner, the select MIDI event edit, the Set Event Filters screen with appear, press ok. A screen with all the notes you just recorded will be there and the velocities will be at the far right. I just tried one and the velocities were 72-87 and I wasn't intentionally using light touch.
If in combi mode you go to the Velocity Zones page... Or anywhere else where you need to enter an exact actual velocity value, you can select the field and hold down the 'Enter' button and strike a key to enter the velocity value. Then you will see what value you are getting.
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
-
michelkeijzers
- Approved Merchant
- Posts: 9112
- Joined: Thu Feb 08, 2007 3:10 pm
- Location: Netherlands
- Contact:
I am very busy but I hope to check it later this week ... of course I also agree that the full range should be playable (without TOO much force).Ten2One wrote:Michel,
Yes, you can test it on the Kronos 61. Just record an 8 bar (or whatever) pass with one of the piano presets. Begin by playing softly and then progress to the hardest you would ever normally play. Then you can go into the MIDI edit section of the sequencer and check the velocities.
When Max at Korg USA tried it he had great difficulty reaching 127 on a 61 key. I could hear him over the phone striking the keys. He did reach 127 but only by striking the keys with a lot of force.
The velocity curves make a difference and I prefer 4 or 9 (1-3 seem to be for sledge hammer touch and 5-8 seem to lessen sensitivity way to much for me). I have the after touch curve set to 3. When I play as hard as I can I get around 112-115, but this is using much more pressure than I would ever want to play consistently with.
I would really appreciate your assistance in this as I really don't want to cause problems at all. I think the Kronos is the best sounding unit available today and I've gone through a long of trouble just to be able to use one. I think is is a much better piece than the kurzweil except for this glaring problem.
If you try to program drums from the keyboard (as I've done for 15 years) there are times you want to be able to get every aspect of a sound and I can assure you there is a difference between 110-117 and 120-127 velocity.
If I can assist you in any way don't hesitate to ask.
Ten2One
How to check:
While in sequence mode press "track edit" at the bottom of the screen. Then press the down arrow in the upper right corner, the select MIDI event edit, the Set Event Filters screen with appear, press ok. A screen with all the notes you just recorded will be there and the velocities will be at the far right. I just tried one and the velocities were 72-87 and I wasn't intentionally using light touch.
Developer of the free PCG file managing application for most Korg workstations: PCG Tools, see https://www.kronoshaven.com/pcgtools/
@ Ten2One
lol I agrre with you. Too many korg fan boys on this forum and that's why I feel like sometimes we complain to a brick wall.
Not mentioning how many times I get really really really annoyed when people post some "compositions" or demo playing really soft classical or new age whatever or "imrpovised" arrpegios full of reverb.
Ok nothing against hobbists and classical meditation softplaying, it is a free world.
However would be best for some hobbists to refrain to coment on a issue that is out of their area + they have no clue, no daw and can't test the issue.
lol I agrre with you. Too many korg fan boys on this forum and that's why I feel like sometimes we complain to a brick wall.
Not mentioning how many times I get really really really annoyed when people post some "compositions" or demo playing really soft classical or new age whatever or "imrpovised" arrpegios full of reverb.
Ok nothing against hobbists and classical meditation softplaying, it is a free world.
However would be best for some hobbists to refrain to coment on a issue that is out of their area + they have no clue, no daw and can't test the issue.
I think there are many users who don't have or know of any problems with their Kronos. I truly am happy for them but some of them are so resistant to the fact that there have been problems with the Kronos series they turn on the ones having the problem.
I believe in supporting companies that produce great products, i.e. Korg, but it drives me crazy when you try to find a solution to a problem and there is no communication. In that case you have to continue to keep it active or it will just get pushed aside and forgotten. I think the velocity problem may be the new contacts or perhaps an error in programming but whatever it is it needs to be fixed.
This forum is a wonderful place to gain insight into the many facets of the Kronos but it is the only place to communicate with others who may be going through similar situations.
Just because you don't have a condition doesn't mean the condition doesn't exist. I tend to be sympathetic with those going through things and seek to find ways to help rather than scolding them for thinking they have problems.
There are so many super users here that usually before I can respond to an inquiry it is already answered (and answered much, much better than I could have) that about all I could add would be.....yes, what he said!
I would love to have an instrument that allowed me to just play without bringing attention to problem areas, but alas, unit it is fixed I endeavor to persevere.
Ten2One
I believe in supporting companies that produce great products, i.e. Korg, but it drives me crazy when you try to find a solution to a problem and there is no communication. In that case you have to continue to keep it active or it will just get pushed aside and forgotten. I think the velocity problem may be the new contacts or perhaps an error in programming but whatever it is it needs to be fixed.
This forum is a wonderful place to gain insight into the many facets of the Kronos but it is the only place to communicate with others who may be going through similar situations.
Just because you don't have a condition doesn't mean the condition doesn't exist. I tend to be sympathetic with those going through things and seek to find ways to help rather than scolding them for thinking they have problems.
There are so many super users here that usually before I can respond to an inquiry it is already answered (and answered much, much better than I could have) that about all I could add would be.....yes, what he said!
I would love to have an instrument that allowed me to just play without bringing attention to problem areas, but alas, unit it is fixed I endeavor to persevere.
Ten2One
I was one of the very first to get their faulty RH3-keyboards replaced, thus solving the double trigger-problem. I was quite happy with the fix, even though the new keybed had some clunky keys. I didn't even imagine this problem could surface after everything endured. But alas, I can't get velocities up to 127 no matter how hard I hit the keys with velocity curves 4 or 9 (whoch are the best settings for dynamic playing in my taste).
I hope this is just a problem solved with a software fix. Can't imagine why this would be a hardware problem. Anyway, Korg SHOULD fix this. Using the velocity curve 5 (still have to pound the keys really really hard to achive 127) is no answer.
Hope Rich or someone will give an answer:)
I hope this is just a problem solved with a software fix. Can't imagine why this would be a hardware problem. Anyway, Korg SHOULD fix this. Using the velocity curve 5 (still have to pound the keys really really hard to achive 127) is no answer.
Hope Rich or someone will give an answer:)
Rich ? ok folks let's keep posting on this because Rich isn't going to scroll down the inumerous useles stupid posting on this page that are showed top on th list. Such as; what extra keyboard can I buy for king kronos?? a ?? 88 controller recomendations ?? (WTF). Would be great if we could have a issue section where only important issues are posted and unimportant ones deleted or voted by users to get moved elsewhere
vstkeys,
I just noticed the same thing and then I realized I may need an 88 key, $250.00 controller if I can't get my $3,700.00 Kronos to transmit all 127 velocities.
I think this will be handled the same way the double trigger issue was handled, poorly! This is a problem that could affect a large number of users but because it isn't as noticeable as the double trigger problem they may never realize it. My Kronos sounds great but still lacks full use of what it can offer and using it to sequence other parts passes its limitation on to other units.
Now, what were the names of those controllers?
Ten2One
I just noticed the same thing and then I realized I may need an 88 key, $250.00 controller if I can't get my $3,700.00 Kronos to transmit all 127 velocities.
I think this will be handled the same way the double trigger issue was handled, poorly! This is a problem that could affect a large number of users but because it isn't as noticeable as the double trigger problem they may never realize it. My Kronos sounds great but still lacks full use of what it can offer and using it to sequence other parts passes its limitation on to other units.
Now, what were the names of those controllers?
Ten2One
I'm sending back my new kronos 88.
Serial number 3339, from Italy.
Velocity inadequate, flimsy and different from key to key.
Strange irregular spaces clearly visible between white keys.
Law, in my country, in such cases, give me the right to obtain a quick substitution (not only a reparation)...oh, well, yes, I'm a lawyer.
I hope Korg Italy will be correct and fair with me.
Serial number 3339, from Italy.
Velocity inadequate, flimsy and different from key to key.
Strange irregular spaces clearly visible between white keys.
Law, in my country, in such cases, give me the right to obtain a quick substitution (not only a reparation)...oh, well, yes, I'm a lawyer.
I hope Korg Italy will be correct and fair with me.
Yeah okay , chill your horses big shot.vstkeys wrote:Rich ? ok folks let's keep posting on this because Rich isn't going to scroll down the inumerous useles stupid posting on this page that are showed top on th list. Such as; what extra keyboard can I buy for king kronos?? a ?? 88 controller recomendations ?? (WTF).
While I admit that this thread has opened my eyes to the velocity issue ( I always wondered why I have to play very hard on the snare drum while recording into the sequencer , in order to get that bright snap ).
But calling people stupid is very low. Maybe the moderator then should name this forum : Kronos complaints forums , just because your highness wants all other general Kronos inquiry threads deleted ?
Chill out. Am sure Korg will catch up to all these issues in a future os update.
A preview of my upcoming solo piano album: https://youtu.be/Cj9a_xATx-g