Is there a serious bug in the Kross 2?

[Telstar5]

https://www.facebook.com/synthesaurus/p ... 0462061112

[bonym]

https://www.facebook.com/synthesaurus/p ... 0462061112

Its the splits in combi mode one, there was a post about it on the Kross 2 FB group.

[onsenonsen]

I read that post, but I did not understand the meaning.

[Biggles]

I have tried it on my Kross 2 and found that I have no problem.

I would suggest that the person who posted reads the manual to be sure they are following the correct adjustment proceedures.

[bonym]

There is a bug, Korg have investigated, and could replicate the issue.

Here are the steps:
1. Go to Sequencer Mode

2. Set up a sequence with different instruments in the tracks

3. Create different zones with different instruments.

4. Save the song.

5. Go to another mode e.g. PROG mode.

6. Go BACK to the sequencer

7. The tracks are the same, as are the effects, but the ZONES are reset.

8. All other parameters seem to have been persisted.

[Biggles]

I have already done that and have no problem at all with my Kross 2.

Strange why some have a problem whilst others do not.

[Telstar5]

Thank You!

[Telstar5]

@Biggies: My guess is that the users w the problem had an earlier software version, 1.00 or thereabouts

[castorex]

I don't think so. The firmware 1.00 is the first official version. If not, the 1.00 version would be available for download on the support page of Korg.

[Biggles]

I have just done the Sequence setup again, then saved it as a Template song in a User bank.

Then I changed to Prog mode, selected an organ sound, played a few notes.

Then changed to Combi mode, selected one and again played a few notes.

Went back to Sequence mode, loaded the saved song and the Zones were all as I had saved them.

Try creating a Combi of the instrument and zone mix you want then in Sequencer mode select the load from Combi option to import into your song the already saved Combi.

This has just worked OK for me.

Good luck.

[StefSax]

Yes, creating a Combi with various keyzones and then importing into the sequencer does work. It's however quite a significant usability issue. I'm happy to see, in the above thread, that Kross has reproduced the problem. I was the person who reported it in the first place (and, trust me, I had read the related documentation from all directions, even upside-down). Cheers!

[Biggles]

Stefsax

Its strange that I cannot replicate the problem on my Kross.

Know what you mean about the manual, sometimes reading it upside down makes sense.

Still convinced that Korg have a native Klingon writing their manuals.

[StefSax]

LOL
To be frank, I am generally quite satisfied with the Kross2 documentation.
Now, did someone elude to a newer firmware version since the initial Sept 2017 1.0 one?
The lack of agility to release new firmware versions faster is one of my primary issue for this platform - unless they are out and I'm just not aware.
Thank you!