Upgrade 2.1?

[LZ]

I always wait to upgrade because it seems like there are always bugs, and I can't afford to be down and/or lose work. There have been a number of posts on here lately regarding issues perceived to be related to upgrading to 2.1. I understand some may not be related, but some seem feasibly related and are issues I could not live with. At this point, is there a definitive list of 2.1 issues?

[GregC]

I always wait to upgrade because it seems like there are always bugs, and I can't afford to be down and/or lose work. There have been a number of posts on here lately regarding issues perceived to be related to upgrading to 2.1. I understand some may not be related, but some seem feasibly related and are issues I could not live with. At this point, is there a definitive list of 2.1 issues?

I don't believe you can accurately quantify the issues at this point.

if you are super cautious, wait a month to see what shakes out.

AFAIK the only issue I had was that my USB thumb drive absolutely had to be formatted on my Kronos.

[LZ]

The other credible issue, confirmed buy several and looking into by Dan, is a CX3 issue where notes are cut off when voices are played on another engine on a different channel. That would be a deal breaker in my rig.

The rest are not necessarily tied to the OS version, only by speculation - song freeze, crashes, etc.

[ed_f]

The other credible issue, confirmed buy several and looking into by Dan, is a CX3 issue where notes are cut off when voices are played on another engine on a different channel. That would be a deal breaker in my rig.

The rest are not necessarily tied to the OS version, only by speculation - song freeze, crashes, etc.

If you are worried don't do it. But I think that would be a mistake.

I believe the issue you are referencing is when an external keyboard plays the same note and a note off stops a note being held on the Kronos (not another engine). I actually could only make that happen on midi channel 15 so I don't even find this an issue. For me it also was not a CX-3 issue but a general bug, and the improved sound more than make up for me on this.

[markn]

I believe the issue you are referencing is when an external keyboard plays the same note and a note off stops a note being held on the Kronos (not another engine). I actually could only make that happen on midi channel 15 so I don't even find this an issue. For me it also was not a CX-3 issue but a general bug, and the improved sound more than make up for me on this.

Sorry, i have to disagree here. Kronos reacts to note off commands from all midi channels on the global channel.
This means, you can´t use Kronos if you intend to play it natively on global channel, and additionally with an external keyboard on another than the global midi channel.
Otherwise V2.1.0 seems to be fine...

[Carbon Trader]

If you see the other thread "Problem with Global Transpose in a COMBI" then I believe that is also a new issue in 2.1....

[LZ]

I believe the issue you are referencing is when an external keyboard plays the same note and a note off stops a note being held on the Kronos (not another engine). I actually could only make that happen on midi channel 15 so I don't even find this an issue. For me it also was not a CX-3 issue but a general bug, and the improved sound more than make up for me on this.

Sorry, i have to disagree here. Kronos reacts to note off commands from all midi channels on the global channel.
This means, you can´t use Kronos if you intend to play it natively on global channel, and additionally with an external keyboard on another than the global midi channel.
Otherwise V2.1.0 seems to be fine...

Yeah, that's a dealbreaker for me. I use a 2 tier rig with the lower tier being an A70 MIDI controller. MOST of the songs we play, I'm triggering sounds on the Kronos from the lower tier. OFTEN CX3 on the Kronos local keyboard and piano from the lower tier. I can't be having it cut out notes on almost every song we play.

I'll wait.

[NuSkoolTone]

I believe the issue you are referencing is when an external keyboard plays the same note and a note off stops a note being held on the Kronos (not another engine). I actually could only make that happen on midi channel 15 so I don't even find this an issue. For me it also was not a CX-3 issue but a general bug, and the improved sound more than make up for me on this.

Sorry, i have to disagree here. Kronos reacts to note off commands from all midi channels on the global channel.
This means, you can´t use Kronos if you intend to play it natively on global channel, and additionally with an external keyboard on another than the global midi channel.
Otherwise V2.1.0 seems to be fine...

+1. I've changed my voicings for the noticeable instances this affects me, but still eagerly awaiting a patch.

[ed_f]

I believe the issue you are referencing is when an external keyboard plays the same note and a note off stops a note being held on the Kronos (not another engine). I actually could only make that happen on midi channel 15 so I don't even find this an issue. For me it also was not a CX-3 issue but a general bug, and the improved sound more than make up for me on this.

Sorry, i have to disagree here. Kronos reacts to note off commands from all midi channels on the global channel.
This means, you can´t use Kronos if you intend to play it natively on global channel, and additionally with an external keyboard on another than the global midi channel.
Otherwise V2.1.0 seems to be fine...

+1. I've changed my voicings for the noticeable instances this affects me, but still eagerly awaiting a patch.

Nothing to disagree with. That was my initial findings when I tried it. I would change midi channels and the issue would stop, except on channel 15. I just tried again and it seems to be more complicated depending on different setups and timbres used.

Anyway, guess I shouldn't have thrown in that bit, my main point on the post was, it was not about one engine stopping another.